IPv6 and the Future of the Internet
MEMBER BRIEFING 1 < Main Index
|Last Revision: 23 July 2001||By Brian Carpenter|
IP version 6 (IPv6) is a new version of the Internet Protocol, designed as a successor to IP version 4 (IPv4) [RFC-791], the predominant protocol in use today. The changes from IPv4 to IPv6 are primarily in the following areas: expanded addressing capabilities; header format simplification; improved support for extensions and options; flow labeling capability; and consolidated authentication and privacy capabilities.
According to population estimates from the US Census Bureau, the world will be home to about 9 billion people in 2050. Whatever the economic constraints may be, we must clearly plan technically for all of these people to have potential Internet access. It would not be acceptable to produce a technology that simply could not scale to be accessible by the whole human population, under appropriate economic conditions. Furthermore, pervasive use of networked devices will probably mean many devices per person, not just one. Simple arithmetic tells us that the maximum of 4 billion public addresses allowed by the current IP version 4, even if backed up by the inconvenient techniques of private addresses and address translation, will simply be inadequate in the future. If the Internet is truly for everyone, we need more addresses, and IP version 6 is the only way to get them.
IPv6 has other benefits, such as provision for "plug and play" automatic configuration, which promises reduced complexity of network deployment and administration. Still, the principal benefit of IPv6 is that of having enough addresses - thereby assisting in restoration of the end-to-end model on which the Internet was based.
To demonstrate that IPv6 really does have enough addresses for everyone, consider that it has 128-bit long addresses. Superficially that appears to offer an unthinkable number of addresses: about 340 trillion, trillion, trillion (3.4x1038). In reality, addresses are structured, and as a result the number effectively available is somewhat less according to the administrative policy adopted. For example, on one model, each site running IPv6 would be given a 48-bit prefix, leaving a mere 80 bits for local use. There could be 35,184,372,088,832 such prefixes - 35 trillion IPv6 sites, which seems to be enough for 9 billion people. (The careful reader will notice that 35 trillion is 245, not 248, due to a technical detail of the address format.)
Whether or not the new protocol is required at all has been the subject of some debate within the technical community. While some argue that IPv6 is required for the future growth of the Internet, there remains a sizable camp who argue that the protocol is "too little, too late" and that IPv4 with the addition of network address translation (NAT) offers a viable system for the future.
However, NAT inhibits many forms of innovative network use beyond the simple client-server model that is popular today, and presents very challenging operational problems when deployed on a massive scale.
Fairness vs. scaling- The rules followed by the regional IP address registries in allocating address blocks to service providers and major customers could become a policy issue as well as a technical one. The rules need to be fair and non-discriminatory, so that all companies and all countries are treated equitably, but at the same time they must allow for massive scaling of the IP routing system if we are to bring connectivity to everyone. These two requirements - fairness and scaling - tend to be in conflict, since a completely fair system simply allows anyone who wants a block of addresses to get one, and that makes compact routing tables virtually impossible.
Privacy- In many cases, the lower 64 bits of an IPv6 address form an identifier, which in the simplest case is derived from the LAN address of the computer's network interface card. In response to concerns that this fixed identifier could be misused as a means of tracking an individual user (or more strictly, the user's PC) for a variety of unwanted purposes, the IETF developed an alternative solution in which the fixed identifier is replaced by a pseudo-random number.
Different from telephony- Another possible public policy matter is the need to explain to politicians and economists that Internet technology is fundamentally different from telephone technology, and some notions (such as "portable numbers" and regulated prices for "universal access") really do not translate to the Internet.
Societal impacts- We cannot yet foresee the societal effects of IPv6. If the dream of pervasive computing based on IPv6 becomes a reality and if some other problems are solved - such as accurate real-time natural language translation - then our grandchildren will see an era of world-wide human communication whose effects we cannot begin to imagine.
In February 2001, ISOC issued a press release about potential privacy issues and possible solutions which was duly noted with satisfaction by many privacy organizations.
In practice, up to now, the work needed has been mainly technical (performed by the IETF) or promotional (performed by the IPv6 Forum). However, we can expect a greater number of policy issues to arise in the future and for ISOC to assume a central role in the debate - consistent with its motto of "the Internet is for everyone."
For More Information
Examples in the News
IPv6 at Center of EU Security Plan
Industry Leaders Accelerate IPv6 Development Efforts
Relevant IETF RFCs
At the last count, 47 RFCs have been published by the principal IETF working groups concerned (in addition to RFCs related to IPv6 from other working groups). The initial specifications for IPv6 were outlined in RFC 1883 of December 1995. These have been replaced by revised standards issued in December 1998 in RFC revised in the form of RFC 2460. Although the actual technical work of standardisation is the IETF's domain, ISOC is proud to fund the RFC publication process as a practical form of support for standardization of IPv6. Search the RFCs.
ISOC Education & Training Activities and IPv6
In ISOCs conference and education area, the annual INET conference includes technical presentations on all aspects of Internet technology, and IPv6 is featured prominently. For example, INET2000 in Yokohama included several papers on IPv6. IPv6 has been added to the ISOCs educational and training programs as well. An IPv6 Tutorial took place at INET2000 and was repeated at INET2001 in Stockholm. Sweden. IPv6 is already briefly discussed in ISOCs Advanced Networking Workshops, and this will have to be boosted to full coverage in due course.
On the Net, Through the Air, In Your Hands: Cellular Technology and the Future of the Internet
About the Author
Current Chair of the ISOC Board of Trustees, Brian Carpenter is an IBM Distinguished Engineer, active in Internet Standards and Technology. Carpenter coordinates IBM relations with the IETF and works on related technical strategy. He is a Member and Former Chair of the Internet Architecture Board (IAB), and currently serves as co-chair of the IETF Differentiated Services working group. This briefing is adapted from an earlier paper published in The IPv6 Journal, RIIS, Tokyo, Summer 2001.
This paper produced with editorial support from the IPv6 Forum. The ISOC Member Briefing series is made possible through the generous assistance of ISOCs Platinum Program Sponsors: APNIC, ARIN, Cisco Systems, IBM, Microsoft, Nortel Networks, Ripe NCC, and Softcomca.com.
The ISOC Member Briefing series is made possible through the generous assistance of ISOC's Platinum Program Sponsors: Afilias, APNIC, ARIN, Microsoft, and the RIPE NCC, Sida. More information on the Platinum Sponsorship Program...
About the Background Paper Series
4, rue des Falaises
Series Editor: Martin Kupres
Copyright C Internet Society 2005.