Light Reading

Standards Road Is Long, Winding... Bumpy

Bruce Sinclair
News Analysis
Bruce Sinclair
6/26/2014
50%
50%

The stage was set. The work had been done, and now it was decision time. The fate of how the Internet would transition to IPv6 was to be decided, in Hong Kong, on February 23, 2006, at a special IETF Softwires meeting.

There was a lot riding on this for my company, then known as Hexago, now gogo6 . We were a small company, and investing in two full-time people, not to mention a fat travel budget, to attend Internet Engineering Task Force (IETF) meetings around the world, was a big deal or, should I say, a big bet. A calculated bet. One typically made only by the largest networking players determined to play standards into a competitive advantage.

At stake was the IPv6 tunneling mechanism to become the gold standard by which all broadband networks and networking vendors would abide. Our transition mechanism, Tunnel Setup Protocol (TSP), was one of two candidates in the running, and without a win, the viability of our company was uncertain.

As we were to learn, however, the road to IPv6 migration would not be as direct as expected, nor would the standards deployment process work out as planned.

Transition mechanisms are the technology and procedures used to migrate to IPv6. In those early days, we saw three paths to migration: dual stack, tunneling, and translation. Among experts at that time, the thinking was: “Dual stack where you can, tunnel where you must, and use translation as a last resort.” Sage advice… in the perfect world.

Here's a look at how the three approaches were viewed:

Dual stack
As Tony Hain, CEO of Hain Consulting and the first chair of the IETF Working Group on IPv6 Transition Technologies (precursor to Softwires), explains: “To some degree, you can call dual stack a procedure. Where the other transition mechanisms are distinct technology instances, dual stack is more of an approach.”

Dual stack yields a dual network where every node and service runs both IPv4 and IPv6, effectively creating two parallel and separate networks. This is the simplest mechanism and most preferred, however implementing dual stack end-to-end can require significant capital and resources.

Tunneling
The next mechanism involves connecting network “islands” separated by different Internet protocols. Packets are encapsulated at one end of the tunnel, routed through the “tunnel” and decapsulated on the other end, after which they continue on their journey. This allows network engineers to fill the gaps in their networks as their transition evolves.

Tunneling comes in many flavors, tailored to specific network types.

  • Configured (manual) tunnels: 6in4. Configured by hand. Secure but labor intensive. Generally used to connect sites.
  • Automatic tunnels: ISATAP, Teredo. Automatically configured but generally not as secure. Used in enterprise to connect users.
  • Brokered tunnels: A tunnel broker automates configured tunnel creation, deletion, and address management. Used in enterprise and by small ISPs to connect users and sites.
  • Softwire tunnels: L2TP, TSP, 6rd, DS-Lite, DSTM, LW4o6, MAP. Built to be deployed in scale by broadband providers. Used to connect users.

"The transition mechanisms being used today are 6rd and DS-Lite for tunneling, and NAT64/DNS64 for translation is also in demand," says John Gudmundson, Senior Manager of Product Marketing for A10 Networks Inc. . "But in practice our customers are also extending their IPv4 address inventory with CGN [carrier-grade network address translation, or NAT]. Many just don’t have a choice."

Translation
And lastly, there is translation, the bad boy of the group. While simple in principle -- IP packets of one type are transformed into packets of the other type -- this approach has a lot of limitations. Translation, such as NAT64, doesn’t work on most security protocols, such as IPSec, and will “break” protocols that include IP addresses in the packet payload (DNS, FTP, SIP…) and apps and services such as Skype, Xbox Live, and Spotify for the same reason.

In 2007, the IETF tried to banish translation by deprecating it to history… but it didn’t work. Nor did we prevail in trying to get our tunneling standard adopted by the IETF.

Hexago was undergoing its own transition. Not long after I joined the company as CEO and raised a $6 million round of VC financing, we lost our founder and his two closest lieutenants, who happened to be our IETF A-team. While I was able to keep the team together for one last fight, it didn't survive against a crack team of 12 IETF specialists, flown in just for this important mission. In the end we would have settled to have two standards, but the IETF Area Chairs were determined to produce a single standard to reference.

We lost. Though we were devastated at the time, in the end it really didn’t matter because no one could have predicted what would happen next.

The rise of the de facto standard
Now, there are standards and there are de facto standards. The first de facto standard to circumvent the IETF was 6rd. Rémi Deprés, 6rd’s inventor and a consultant for the French ISP Free , believed he had a better solution. Never taken seriously at any of the Softwire meetings, 6rd wasn’t even in the running in Hong Kong against TSP and L2TP.

But this didn’t matter, Deprés convinced his management to deploy it anyway. And after connecting 1.5 million subscribers to IPv6 in a five-week span without a hitch, the past was forgotten and the IETF fast-tracked 6rd’s independently submitted RFC to be the second Softwires tunneling standard. Adding to the inventor’s satisfaction were his initials, immortally stamped into his standard.

Due to the delay in implementing IPv6, dual stack and tunneling, the only two sanctioned transition mechanisms, were becoming less and less relevant as each day passed, due to their dependence on the ever-dwindling supply of IPv4 addresses.

This unavailability of IPv4 and a viable transition mechanism created a vacuum. Carrier Grade NAT is not a transition mechanism, but it did fill a need and started to take hold along with a new class of hybrid transition mechanisms that combined tunneling and translation. (See The Dark Side of IPv6.)

Not long after Deprés crashed the party with 6rd, a third Softwires tunneling standard was added to the mix. Alain Durand, from Comcast Corp. (Nasdaq: CMCSA, CMCSK) and then Juniper Networks Inc. (NYSE: JNPR), had developed a hybrid tunneling mechanism called DS-Lite that combined v4 over v6 tunneling with one layer of NAT.

Hybrid transition mechanisms such as DS-Lite and, more recently, MAP and LW4o6 (optimized DS-Lite) indirectly help migration by encouraging native IPv6-only networks as the start point and using reverse tunneling and address sharing (or translation) to connect to IPv4. Eventually the tunneled traffic and translation disappears, leaving the operator with a next-generation IPv6 network.

Next page: Expect the unexpected

(3)  | 
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
gogoBruce
50%
50%
gogoBruce,
User Rank: Blogger
8/12/2014 | 8:15:09 AM
Re: IPv6 in 3GPP Mobile
rossc_ie, true, CGN is being used as a transition mechanism but I don't classify it that way as it is not transitioning anything, rather, it's extending the life/use of IPv4.  That said, you make an accurate analysis.  

For a deep dive into one way IPv6 is bing used in mobile, listen to my podcast interview with Cameron Byrne on what he and his team did at T-Mobile: http://www.gogo6.com/14
rossc_ie
50%
50%
rossc_ie,
User Rank: Light Beer
8/12/2014 | 7:39:14 AM
IPv6 in 3GPP Mobile
There's another in the seemingly endless list of transition solutions. Only some of which were mentioned in the article and most of which (6to4, teredo, etc) are best forgotten.  

Smartphones and mobile Internet access took off relatively late, when IPv4 addresses were already being rationed out. So "carrier grade NAT" CGN is ubiquitous in mobile in a way it is not in established fixed Internet providers. So most mobile customer access is already translated, currently mostly from private IPv4 to public IPv4 on the Internet side of the CGN. Some operators have started assigning only IPv6 prefixes to the mobile devices. Native IPv6 bypasses the CGN and legacy IPv4 is translated to and from IPv6 by NAT64 is the CGN.  Android 4.4+ and Windows Phone 8.1 also support the (RFC 6877) "clat" function for the small number of Apps (Skype) that still haven't been updated to support IPv6. 

The advantage over dual-stack is that it transitions more directly to single-stack on the 3GPP link while still supporting legacy IPv4 access. Deployed mobile networks have much better support for single-stack IPv6 in GTP than for dual-stack in GTP because the latter was only introduced with LTE/EPC.
SachinEE
50%
50%
SachinEE,
User Rank: Light Sabre
6/28/2014 | 5:26:27 AM
RE: Internet transition to IPv6
The approaches used to view the issue were spot on. However, two of them really got to my attention- the dual stack yields and tunneling. As stated, the dual stack yields a dual network. This allows both the IPv4 and IPv6 to run parallel directions. As much as using this strategy requires a lot of capital and resources, I would say it's worth it. The other approach where different internet protocols are used is another good one. In my view, these two approaches can yield excellent results if used.
Flash Poll
From The Founder
Last week I dropped in on "Hotlanta," Georgia to moderate Light Reading's inaugural DroneComm conference – a unique colloquium investigating the potential for drone communications to disrupt the world's telecom ecosystem. As you will see, it was a day of exploration and epiphany...
LRTV Documentaries
Verizon's Emmons: SDN Key to Cost-Effective Scaling

5|22|15   |   03:53   |   (0) comments


For Verizon and other network operators to ramp up available bandwidth cost effectively, they need to move to SDN and agree on how to do that.
LRTV Documentaries
Lack of Universal SDN a Challenge

5|21|15   |   04:51   |   (3) comments


Heavy Reading Analyst Sterling Perrin talks about how uncertainty about SDN standards and approaches may be slowing deployment.
LRTV Custom TV
Steve Vogelsang Interview: Carrier SDN

5|20|15   |   05:02   |   (0) comments


Sterling Perrin speaks to Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, about the new Carrier SDN-enabling Network Services Platform and the operator challenges it solves.
LRTV Custom TV
Carrier SDN: On-Demand Networks for an On-Demand World

5|20|15   |   20:52   |   (0) comments


Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, talks about requirements and benefits of Carrier SDN during the keynote address at the Light Reading Carrier SDN event May 2015.
LRTV Documentaries
The Security Challenge of SDN

5|19|15   |   02:52   |   (0) comments


CenturyLink VP James Feger discusses concerns that virtualization could create new vulnerabilities unless network operators build in safeguards.
LRTV Custom TV
NFV Elasticity – Highly Available VNF Scale-Out Architectures for the Mobile Edge

5|18|15   |   5:50   |   (0) comments


Peter Marek and Paul Stevens from Advantech Networks and Communications Group talk about their NFV Elasticity initiative and the company's latest platforms for deploying virtual network functions at the edge of the network. Packetarium XL and the new Versatile Server Module: 'designed to reach parts of the network that other servers cannot reach.'
LRTV Huawei Video Resource Center
Bay Area Spark Meetup 2015

5|14|15   |   3:54   |   (0) comments


Developed in 2009, Apache Spark is a powerful open source processing engine built around speed, ease of use and sophisticated analytics. This spring, Huawei hosted a meetup for Spark developers and data scientists in Santa Clara, California. Light Reading spoke with organizers and attendees about Huawei's code contributions and long-term commitment to Spark.
LRTV Custom TV
The Transport SDN Buzz

5|12|15   |   06:01   |   (1) comment


Sterling Perrin, senior analyst at Heavy Reading, speaks with Peter Ashwood-Smith of Huawei and Guru Parulkar of ON.Lab about the evolution of transport SDN and the integration of technologies.
LRTV Custom TV
Next-Generation CCAP: Cisco cBR-8 Evolved CCAP

5|5|15   |   04:49   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explained the innovation design of Cisco's cBR-8, the industry's first Evolved CCAP, including DOCSIS 3.1 design from ground-up, distributed CCAP with Remote PHY and path to virtualization. Cisco's cBR-8 Evolved CCAP is the platform that will last through the transitions.
LRTV Custom TV
Meeting the Demands of Bandwidth & Service Group Growth

5|1|15   |   5:35   |   (0) comments


Jorge Salinger, Comcast's Vice President of Access Architecture, explains how DOCSIS 3.1 and multi-service CCAP can meet the demands of the bandwidth and service group growth.
LRTV Custom TV
DOCSIS 3.1: Transforming Cable From Hardware-Defined Network to Software-Defined Network

4|29|15   |   03:48   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explains how DOCSIS 3.1 can transform cable HFC network to a more agile software-defined network.
LRTV Huawei Video Resource Center
Predicting Traffic Patterns for Quality Mobile Broadband

4|29|15   |   6:45   |   (0) comments


Accessing information ubiquitously creates complexity and creates heavy traffic onto the network, especially at large-scale events like sporting events or festivals. In this video, Huawei's Mohammad Hussain speaks to experts about how to predict traffic and improve user experience during periods of heavy traffic.
Upcoming Live Events
June 8, 2015, Chicago, IL
June 9, 2015, Chicago, IL
June 9-10, 2015, Chicago, IL
June 10, 2015, Chicago, IL
September 29-30, 2015, The Westin Grand Müchen, Munich, Germany
October 6, 2015, The Westin Peachtree Plaza, Atlanta, GA
October 6, 2015, Westin Peachtree Plaza, Atlanta, GA
All Upcoming Live Events
Infographics
Network functions virtualization (NFV) is not the easiest of topics to take on board, so here's a Light Reading infographic, developed following conversations with the folks at HP, that helps make sense of where NFV is taking the industry.
Hot Topics
Verizon Saves 60% Swapping Copper for Fiber
Sarah Thomas, Editorial Operations Director, 5/19/2015
Choosing a Technology Supplier? Consider Changing Your Selection Criteria
Steve Saunders, CEO and founder, Light Reading, 5/18/2015
Chattanooga Charts Killer Gigabit Apps
Mari Silbey, Senior Editor, Cable/Video, 5/20/2015
10 Alternate Uses for Tablets
Eryn Leavens, Copy Desk Editor, 5/22/2015
Smarter 'Dumb' TVs Will Drive OTT Adoption
Mari Silbey, Senior Editor, Cable/Video, 5/18/2015
Like Us on Facebook
Twitter Feed
Webinar Archive
BETWEEN THE CEOs - Executive Interviews
With 200 customers in 60 countries, Stockholm-based Net Insight has carved out a solid leadership position in one of the hottest vertical markets going in comms right now: helping service providers and broadcasters deliver video and other multimedia traffic over IP networks. How has Net Insight managed to achieve this success in the face of immense competition from the industry giants?
My ongoing interview tour of the leading minds of the telecom industry recently took me to Richardson, Texas, where I met with Rod Naphan, CTO and SVP, Solutions, ...
I recently popped down to Texas to chat with CEO Eric L. Pratt about his company, Taqua.
Cats with Phones