Volume 15, Number 2, June 2012

From the Editor

Deployment of IPv6 took another step forward on June 6, 2012, when numerous website operators, Internet Service Providers (ISPs), and home router vendors participated in the World IPv6 Launch. Organized by the Internet Society, the event attracted significant media attention as the participants enabled IPv6 permanently and rendered it "on by default." More information about the event is available from www.worldipv6launch.org

Migration to IPv6 is not a simple task, as outlined in many previous editions of this journal. Various tools and techniques have been developed, one being the use of so-called Carrier-Grade NATs whereby the end customers connect to the Internet using private (RFC 1918) addresses and the ISP provides translation for both public IPv4 and IPv6 addresses. In April of this year, the Internet Engineering Task Force (IETF) approved and the Internet Assigned Numbers Authority (IANA) allocated a new IPv4 address block ( 100.64.0.0/10), designated for use as "Shared Transition Space" in support of the IPv6 transition. We asked Wesley George to describe the rationale behind the use of this additional private address space and discuss the debate that resulted from this allocation.

The world of telecommunications has changed dramatically as a result of the rapid expansion of the Internet. Traditional telephone lines are being replaced by Voice over IP (VoIP) systems for both private and business use. These changes represent big challenges for traditional telephone carriers, and even for some countries whose income used to depend largely on telephone "settlement charges” for international phone calls. The World Conference on International Telecommunications (WCIT) will take place this coming December in Dubai. Geoff Huston discusses some of the proposed changes to the International Telecommunication Regulations that could affect the Internet in various ways and will be discussed at WCIT.

The IETF is concerned not only with IPv4-to-IPv6 migration, but also with recovery upon router or link failure. In our final article, Russ White describes IP Fast Reroute, a technique for providing fast traffic recovery when these failures occur.

As always, your feedback about anything you read in this journal is most appreciated. Please contact us at ipj@cisco.com and don't forget to renew your subscription and provide us with any postal or e-mail changes.

—Ole J. Jacobsen, ole@cisco.com
Editor and Publisher, IPJ