Google: IPv6 is easy, not expensive
Google engineers say it was not expensive and required only a small team of developers to enable all of the company's applications to support IPv6, a long-anticipated upgrade to the Internet's main communications protocol.
"We can provide all Google services over IPv6," said Google network engineer Lorenzo Colitti during a panel discussion held here Tuesday at a meeting of the Internet Engineering Task Force (IETF).
Colitti said a "small, core team" spent 18 months enabling IPv6, from the initial network architecture and software engineering work, through a pilot phase, until Google over IPv6 was made publicly available. Google engineers worked on the IPv6 effort as a 20% project -- meaning it was in addition to their regular work -- from July 2007 until January 2009.
Building a pilot IPv6 network "was not expensive," said Colitti, who recommended rolling out IPv6 in stages. "There's nothing inherently unreliable about IPv6."
Google is already reaping the benefits of IPv6. "It's refreshingly simple" to look at a network with globally addressable devices, Colitti said.
Google's comments at the IETF meeting come days after the Web leader held a conference in Mountain View, Calif., for IPv6 implementers.
Also in March, Google published a manifesto on its public policy blog explaining why IPv6 matters.
Google's experience with IPv6 is significant because only a handful of leading-edge U.S. companies have embraced the next-generation Internet protocol.
The IETF created IPv6 in 1995 as a replacement to the existing version of the Internet Protocol, known as IPv4.
IPv6 is needed because the Internet is running out of IPv4 addresses. IPv4 uses 32-bit addresses and can support approximately 4.3 billion individually addressed devices on the Internet. IPv6, on the other hand, uses 128-bit addresses and can support so many devices that only a mathematical expression -- 2 to the 128th power -- can quantify its size.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
On Twitter now
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
VoIP Needs IPv6
Anyone who has done VoIP in an IPv4 environment immediately understands the challenges presented, most notably NAT. This is why FreeSWITCH was built from the ground up to be IPv6 ready. The Google guys are correct - if you don't start using IPv6 in production then it will lag and its uptake will suffer. IPv6 offers a lot of great features and functionality. Granted, getting over the mental hump of jumping from x.x.x.x to xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx is a little challenging at first but it's well worth it in the end.I highly recommend playing with IPv6-ready hardware and software. Better to learn the ins and outs now before IPv4 croaks in 2012. If you want a flexible telephony application that can handle IPv6, including the ability to handle a mix of IPv4 and IPv6 endpoints, check out FreeSWITCH. It is very powerful.