Feds: IPv6 is a priority

For the last year, it's been all quiet on the IPv6 front in the United States. But now the U.S. government is making noise about this next-generation Internet technology, as it forges ahead with plans to deploy secure, IPv6-enabled network services.

In June 2008, all federal agencies met an Office of Management and Budget (OMB) deadline to demonstrate that their backbone networks were IPv6 capable. 

A few weeks ago, the Federal CIO Council issued a road map that disclosed the next steps agencies should be taking toward IPv6 deployment.

The road map says every federal CIO should develop a business case for IPv6 and integrate IPv6 into their agency's enterprise architecture and capital investment plans.

"Like other areas of strategic investment which lead to new levels of productivity, greater mission successes and citizen access to government, IPv6 integration must be prioritized at the agency level and executed in a well planned, phased approach with success criteria measurements and alignment with other key government [IT] initiatives," the report states.

Pete Tseronis, Federal IPv6 Working Group Chair and Deputy Associate CIO of the Department of Energy, says the road map is designed to keep federal CIOs, enterprise architects and policymakers focused on investing in Internet infrastructure. Tseronis helped develop the road map.

"We can't keep operating in an IPv4 world when we're talking about sensor networks, wireless communications and mobile networks," Tseronis says. "We need more IP addresses – globally unique IP addresses — and that's what IPv6 provides…We need a target network architecture that's scalable, secure and stable."

The road map says federal CIOs need to develop concrete plans to deploy IPv6 and that they will be required to provide quarterly progress reports that include IPv6 to OMB.

"For those who may think that IPv6 is on ice, it's anything but," Tseronis says. He adds that in order for an agency to receive a green light from OMB on its enterprise architecture, it will need a strategy for deploying secure IPv6-enabled network services followed by IPv6-enabled applications.

"Agencies are being assessed on their progression towards IPv6," Tseronis says. "Agencies are on the hook to deploy IPv6."

IPv6 is a long-anticipated upgrade to the Internet's main communications protocol, which is known as IPv4. IPv4 uses 32-bit IP addresses, which means it can support only 4.3 billion individually addressable devices on the Internet. In contrast, IPv6 uses 128-bit IP addresses to support an almost-limitless number of individually addressable devices. IPv6 also includes built-in IP security mechanisms, easier network configuration and enhanced support for mobile devices.

The U.S. government's pro-IPv6 report is coming out at a time when few carriers or network equipment vendors are talking about next-generation Internet technology. Because of a weak global economy, the issues of Internet scaling and enabling new services have taken a backseat to cutting costs, ekeing out profits and surviving the downturn.

"From the enterprise space, we're seeing very, very little activity around IPv6," says Maria Fire, product manager for Alcatel-Lucent's VitalQIP, an IPv6-enabled IP address management (IPAM) tool.

Fire says she recently gave a presentation to 65 VitalQIP customers in the United States, and none of them were migrating to IPv6.

"It's a question of who can afford to replace their existing infrastructure with IPv6-capable stuff," Fire says. "We're really not seeing a whole lot of new trends in IPv6. Interest is very, very minimal in terms of enterprises. There's a little bit of interest in higher education and a little bit of interest on the carrier side."

The U.S. federal government, however, is focused on migrating to IPv6 because of the anticipated depletion of IPv4 addresses in 2012. 

The road map is a "very, very good document," says Yanick Pouffary, an IPv6 Forum Fellow and Technology Director of the North American IPv6 Task Force. "Basically, they're putting a framework around what it means for agencies to use IPv6 and to deploy it. It's not a question of if IPv6 gets deployed; it's how IPv6 will get deployed. It gives guidance to CIOs, chief architects or other individuals who are responsible for IT so they can plan for IPv6 and understand how IPv6 fits in the vision of their agency."

Pouffary, who contributed to the road map, says the document shows that the U.S. federal government is "very serious" about IPv6 deployment.

According to the new road map, federal CIOs see IPv6 as "an integrating framework and organizing principal for the next generation of federal IT infrastructure."

Tseronis says having an IPv6-enabled infrastructure will be required for agencies to support social networking services that are a priority of the Obama administration. 

"The agency infrastructure-both internal to the data center and external to the service provider community-needs to be primed and ready for next-generation Web 2.0 or Gov 2.0 services," Tseronis says. "IPv6 is the Internet protocol that we're going to need to leverage for that."

The road map identifies two other drivers for federal agencies to deploy IPv6: cloud computing and peer-to-peer applications.

The road map predicts that by the end of 2011, there will be clients and servers that have no choice but to have an IPv6 address because IPv4 addresses will be used up. This means that operators of public-facing Web sites including federal agencies will need to serve IPv6 clients.

The report recommends that agencies adopt a dual-stack approach, running IPv4 and IPv6 side-by-side during the transition to the new Internet protocol.

The integration of IPv6 "should not be taken lightly," the report warns.

"When you read the Federal CIO document on IPv6, they are clearly giving direction that CIOs need to not take IPv6 lightly," says Scott Camarotti, vice president of federal markets for Global Crossing. "The federal agencies are starting to become a little more cognizant about IPv6…They're starting to realize the benefits of edge-to-edge communications and how supply chain management and CRM tools could benefit from an IPv6 addressing scheme."

The IPv6 road map "gives some pretty clear direction following up on the OMB mandate [from June 2008] about what these agencies should do and what their architectures should look like," Camarotti says. "Hopefully, it will give them a boost about taking this more seriously."

'Rigged' product demo in SAP suit goes missing

A presale product demonstration software package that is key to Waste Management's rancorous lawsuit against SAP has gone missing and both sides are claiming the other should have it, according to documents filed in a U.S. District Court.

Waste Management sued SAP in March 2008 in District Court of Harris County, Texas, 164th Judicial District, claiming more than US$100 million in damages in connection with an allegedly failed ERP (enterprise resource planning) project.

The trash hauler has said SAP used "rigged and manipulated" demonstrations during sales presentations. A motion Waste Management filed May 18 said the demos were a key element of the "false representations" SAP made to "induce Waste Management into entering a software licensing and implementation agreement."

Waste Management has been asking SAP for a copy of the demo since mid-2008, according to the motion.

But in a May 22 filing, SAP said it had the system until August or September 2006, but does not any longer.

SAP has "searched extensively" for the system and wants it "as much or more" as Waste Management, since it "will help SAP disprove WM's fraud claim," the filing states. In addition, SAP said it has produced ample discovery materials related to the demo, such as its scripts and hundreds of e-mails.

In fact, Waste Management should have the demo in its possession, as it was transferred to the trash hauler's system in late 2005 and early 2006, according to SAP, which demanded in a May 14 filing that Waste Management turn it over.

But Waste Management has filed an affidavit from a company IT manager who says that to his knowledge, Waste Management never installed or operated the demo.

But it is possible Waste Management simply hasn't looked extensively enough for the software, SAP said in a filing.

Neither company responded to requests for additional comment.

However the dispute plays out, it suggests that customers would be wise to preserve a copy of product demonstrations as they form new license agreements with vendors.

Indeed, contract language should seek to encompass all manner of pre-sales materials, according to a 2006 Forrester Research report, "An Enterprise Software Licensee's Bill of Rights."

"Instead of relying on the generic terms and conditions, vendors should include all of the proposals, sales-cycle presentations, demos, and promises in the entire agreement," it states.

Meanwhile, SAP and Waste Management's duel over the demo comes amid a series of back-and-forth filings related to pre-trial discovery, with no sign of settlement imminent.

In response to Waste Management's complaint, SAP has said in part that the company failed to "timely and accurately define its business requirements" and did not supply "sufficient, knowledgeable, decision-empowered users and managers" to work on the project.

The verbiage, as well as an SAP request for Waste Management documents related to a failed PeopleSoft implementation, may indicate the vendor plans to argue the trash company has a pattern of unsuccessful software projects.