IPv6 faces trial by fire tonight

Internet standards body chief explains why he's turning off IPv4

PHILADELPHIA -- The Internet engineering community will be eating its own dog food tonight. For one hour, the 1,250 network experts at the Internet Engineering Task Force meeting will be able to access the Internet only through IPv6. The IETF created IPv6 in the mid-1990s, but this upgrade to the Internet's main communications protocol has not yet been widely deployed -- even by the technology's biggest proponents here. Network World National Correspondent Carolyn Duffy Marsan talked with IETF Chair Russ Housley about the group's IPv6 experiment, why the transition to IPv6 is taking so long, and whether the IETF leadership is starting to panic about IPv4 addresses running out. Here are excerpts from their conversation:

You're turning off the IPv4 network during the plenary session tonight and requiring everyone here to use IPv6. Is this significant or is this a publicity stunt?

I didn't do it as a publicity stunt. It's become more of one than I intended. It's our strong preference to preserve the end-to-end model of the Internet and deploy IPv6 and not [network address translation.] We need to have network people use the IPv6 implementations, find out where they're fragile and fix them so IPv6 deployment will be smooth. This experiment also is about finding out how hard it is to deploy IPv6. A lot of IETF people want to have their Web sites accessible during the IPv6 experiment, and they are taking the necessary steps to make their Web sites available on IPv4 and IPv6. IPv6 has been available on our network for the whole meeting, but we're turning off the IPv4 part of our network for one hour. The point of this is to get people to move out of their comfort zones with IPv4 and start using IPv6.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

PHILADELPHIA -- The Internet engineering community will be eating its own dog food tonight. For one hour, the 1,250 network experts at the Internet Engineering Task Force meeting will be able to access the Internet only through IPv6. The IETF created IPv6 in the mid-1990s, but this upgrade to the Internet's main communications protocol has not yet been widely deployed -- even by the technology's biggest proponents here. Network World National Correspondent Carolyn Duffy Marsan talked with IETF Chair Russ Housley about the group's IPv6 experiment, why the transition to IPv6 is taking so long, and whether the IETF leadership is starting to panic about IPv4 addresses running out. Here are excerpts from their conversation:

You're turning off the IPv4 network during the plenary session tonight and requiring everyone here to use IPv6. Is this significant or is this a publicity stunt?

I didn't do it as a publicity stunt. It's become more of one than I intended. It's our strong preference to preserve the end-to-end model of the Internet and deploy IPv6 and not [network address translation.] We need to have network people use the IPv6 implementations, find out where they're fragile and fix them so IPv6 deployment will be smooth. This experiment also is about finding out how hard it is to deploy IPv6. A lot of IETF people want to have their Web sites accessible during the IPv6 experiment, and they are taking the necessary steps to make their Web sites available on IPv4 and IPv6. IPv6 has been available on our network for the whole meeting, but we're turning off the IPv4 part of our network for one hour. The point of this is to get people to move out of their comfort zones with IPv4 and start using IPv6.

The IETF created IPv6 13 years ago, and it's only in a handful of production networks. Why is it taking so long?

Economics. If you are able to get your application to work on IPv4, there's no economic reason to invest in IPv6. You're just creating a second way for the same job to get done. The thing that's changing is that we're going to run out of IPv4 addresses and so we have a choice facing us. One is to have NAT upon NAT so that the Internet continues to work, or we can preserve the end-to-end model by moving away from IPv4 to IPv6. I'm hoping that IPv6 will be the answer because we want it to be easy to add new applications to the Internet. The more things that are in the middle such as NATs, the harder it will be for new applications to deploy.

It didn't take this long for the Internet to adopt MPLS or Session Initiation Protocol. What did the IETF do wrong when it designed IPv6?

Nothing. At the time MPLS and SIP were developed, there were already economic reasons to deploy them. IPv6 was developed because we knew the IPv4 address shortage was coming. But the economics for deploying IPv6 doesn't happen until the IPv4 address space becomes very scarce. All the technical pieces were there, but it's the economics that are driving when it is actually used by service providers. The IETF doesn't have economic levers.