Agencies Slowly Appreciating Need for IPv6 Upgrade—Official
Happy with the Internet Protocol version 4 now in use and with no money for upgrades, federal agencies were slow to take seriously the Bush administration’s order to redo their networks for IPv6, the government’s IPv6 chief told the IEEE Globecom conference Thursday. But they're increasingly taking heed as vendors caterwaul over yet- unwritten compliance requirements for selling routers and the like to the government, said Peter Tseronis, chairman of the Federal IPv6 Working Group. His day job is network services director for the Education Department.
Sign up for a free preview to unlock the rest of this article
If your job depends on informed compliance, you need International Trade Today. Delivered every business day and available any time online, only International Trade Today helps you stay current on the increasingly complex international trade regulatory environment.
IPv6’s main advantages are greater address space for a host of non-PC devices expected to come online the next several years, and improved built-in network security. Applications under discussion include sensors in ventilation systems to reroute smoke and on highways to divert traffic ahead of accidents, and soldiers in the field are already transmitting through several IPv6- enabled devices, Tseronis said. Agencies must have IPv6 transition plans ready by June 30.
Agency leaders have a “don’t mess with it” attitude regarding the Internet that is out of sync with other technology purchases, Tseronis said. He tried to sneak in funding for Education’s IPv6 efforts through a routine Office of Management and Budget request, but got a “mini- slap on the wrist” from OMB and was told to simply to use the technology refresh money that’s in each agency’s budget. Even then, convincing his budget director to replace Cat 3 cable -- long ago eclipsed by the Cat 5 standard -- was an uphill battle, and the agency still can’t technically handle IP phones. The foot-dragging is slowing IPv6 adoption elsewhere, he said, pointing to a meeting this year with French and Japanese ministers, who said their countries were waiting for U.S. action.
Vendors have been complaining that they can’t meet IPv6 compliance requirements before the government settles on a profile or baseline, Tseronis said. The Defense Department, about 5 years ahead of the rest of the government in the IPv6 transition, has a testing lab for vendors, but it’s in the middle of nowhere, he said. The government is preparing for “phase two” of the transition, which includes labs for testing and accreditation, and deployment plans should be “rubber stamped hopefully in the next day or so.” The updated IPv6 profile should be out in January, he said.
Asked how Education recently declared itself compliant with the OMB requirement to be IPv6-ready, Tseronis cited close coordination with Cisco, whose equipment powers Education networks. Education can handle the bare minimum of “ping, trace, screenshot,” or successfully transmitting and receiving IPv6 packets on its intranets and the Internet. It’s meeting with Cisco next week to discuss the IPv6-enabled applications that Education wants to use in the next 3 to 5 years, such as its School 2.0 initiative. Agencies can get a jump on compliance by working closely with their service providers, he said.
Lower level agency officials can best convince their superiors to dedicate money to the IPv6 transition by avoiding jargon, Tseronis said. “Use the excuse that your equipment needs to be upgraded” to support the “next- generation Internet,” without mentioning IPv6, and discuss buzzworthy applications enabled by IPv6, such as telepresence, he said. Tseronis said he was naive when in 2005 he took on the responsibility of federal IPv6 coordination, thinking 2 ? years would be plenty of time. “It doesn’t end for the government in June,” Tseronis said, predicting no “rudder changing” on IPv6 efforts after the 2008 election either.