IP protocols/software

LR Live: IPv6 Transition Decisions Loom

NEW YORK -- IPv6 2011 -- After languishing for more than a decade, IPv6 has gotten its share of the spotlight this year, first with the announcement that -- at long last -- IPv4 addresses were nearing exhaust and then with IPv6 World Day, when Internet giants such as Yahoo Inc. (Nasdaq: YHOO) and Google (Nasdaq: GOOG) turned on IPv6 to test connections. (See Global IPv4 Counter Hits Zero and LR: World IPv6 Day Passes the Consumer Test.)

For those outside the telecom and Internet industries, IPv6 will now resume its place in the background, but for network operators and Web content companies, the fun is just beginning. After years of preparation, the industry can show it is ready to handle the long transition to a new Internet addressing scheme, which will include many years of dual support for IPv4 and IPv6 that is expected to be seamless. (See Report: Most ISPs Are IPv6 Ready.)

This week at Light Reading's IPv6: The Time Is Now! event, a host of industry luminaries will be on hand to review, discuss and debate the issues and the decisions that lie ahead for ISPs, Web content companies and enterprises.

And there are many decisions to be made.

For enterprises, one of the biggest challenges is determining what and when to upgrade to IPv6, given the lack of financial drivers -- or rewards -- for that process. At a time when IT budgets are already stretched, businesses know the future lies with IPv6, and they realize there are dangers in being unprepared, but they will proceed with cost-conscious caution, both in upgrading equipment and exploring IPv6 connectivity options. (See Despite Consumer Electronics Surge, Chip Suppliers Face Cost Challenges.)

ISPs face their own challenges. There's not a large network operator on the globe that won't say it's been preparing for IPv6 since the turn of the century, yet there are still many places where connectivity is limited to IPv6 tunnels through an IPv4 connection. Clearly there is still work to be done here, and that work includes deciding how much native IPv6 is needed and where other solutions, such as network-based or large-scale Network Address Translation will be deployed. (See The Ugly Side of IPv6: Carrier-Grade NAT.)

The consumer market is in a different kind of quandary. Retailers, service providers, and content owners all share some of the burden of either preparing the consumer world to understand what this new addressing scheme is all about, or making sure the transition is so seamless that no consumer has to worry about whether his connection is IPv6 and his content is hosted on IPv4 servers or vice versa. (See IPv6 Traffic Keeps Growing, Cable ISPs Say.)

All of this and more, including a review of lessons learned from IPv6 World Day, will be part of what we discuss this week in New York. If you're close by and want to drop in, go here to register. — Carol Wilson, Chief Editor, Events, Light Reading

Vishnu Goel 12/5/2012 | 4:59:22 PM
re: LR Live: IPv6 Transition Decisions Loom

This transition will surely put some new fuel to the fire of Device Makers,Quality approval labs,Operators and all user Enterprises.Perhaps this protocol will open Chip industrys new architectures,and devices and SoC.Most certainly a new breed of entrepreneurs will emerge at hot spots.Vishnu Goel T&M +919810101238

fgoldstein 12/5/2012 | 4:59:20 PM
re: LR Live: IPv6 Transition Decisions Loom

IPv6 is a total waste, a misbegotten aboination that exists simply to create a new "Y2K"-like hysteria.  Only consumers are smarter this time.

There's nothing wrong wtih IPv4 that IPv6 fixes.  (There's a lot wrong with IPv4; IPv6 just doesn't fix any of it.)  The whole idea of one global address space is a mistake.  Applications should be reached by name.  Most computers should only have private addresses.  The IPv4 space is huge enough to support public-facing servers and network gateways.

Lest anyone confuse the issue, telephone numbers are names, not addresses.  (The LRN is the address.  It's invisible to end users.)  IP does not have a c omplete naming and addressing architecture, so data link point of attachment identifiers (IP addresses) are conflated with addresses (not provided) and visible to the application (whatttt?!). 

NAT only breaks broken applications.  View IP addresses as subnet addresses and let applications use names to find each other, and there's no need for v6 ever.

Sign In