| 
 | Please Whitelist This Site?I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
 If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads. If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK. Thanks for your understanding! Sincerely, Charles KozierokAuthor and Publisher, The TCP/IP Guide
 | 
 
 
   
  
    | 
  
| NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
 |  |  | 
| 
 
 
 | 
 
 IPv6 Motivation and Overview
 (Page 3 of 3)
 Design Goals of IPv6 The problem of addressing was the 
main motivation for creating IPv6. Unfortunately, this has caused many 
people to think that the address space expansion is the only 
change made in IP, which is definitely not the case. Since making a 
change to IP is such a big deal, it's something done rarely. It made 
sense to correct not just the addressing issue but to update the protocol 
in a number of other respects as well, to ensure its viability. In fact, 
even the addressing changes in IPv6 go far beyond just adding more bits 
to IP address fields. Some of the most important goals 
in designing IPv6 include: 
IPv6: The Evolution of IPLarger Address Space: This is what we 
discussed earlier. IPv6 had to provide more addresses for the growing 
Internet.
 
Better Management of Address Space: It 
was desired that IPv6 not only include more addresses, but a more capable 
way of dividing the address space and using the bits in each address.
 
Elimination of Addressing Kludges: 
Technologies like NAT 
are effectively kludges that make up for the lack of address 
space in IPv4. IPv6 eliminates the need for NAT and similar workarounds, 
allowing every TCP/IP device to have a public address.
 
Easier TCP/IP Administration: The designers 
of IPv6 hoped to resolve some of the current labor-intensive requirements 
of IPv4, such as the need to configure IP addresses. Even though tools 
like DHCP eliminate the need to manually configure many hosts, it only 
partially solves the problem.
 
Modern Design For Routing: In contrast 
to IPv4, which was designed before we all had any idea what the modern 
Internet would be like, IPv6 was created specifically for efficient 
routing in our current Internet, and with the flexibility for the future.
 
Better Support For Multicasting: Multicasting 
was an option under IPv4 from the start, but support for it has been 
slow in coming.
 
Better Support For Security: IPv4 was 
designed at a time when security wasn't much of an issue, because there 
were a relatively small number of networks on the internet, and their 
administrators often knew each other. Today, security on the public 
Internet is a big issue, and the future success of the Internet requires 
that security concerns be resolved.
 
Better Support For Mobility: When IPv4 
was created, there really was no concept of mobile IP devices. The problems 
associated with computers that move between networks led to the need 
for Mobile 
IP. IPv6 builds on Mobile IP and provides 
mobility support within IP itself.
 At the same time that IPv6 was intended 
to address the issues above and many others with traditional IP, we 
should keep in mind that its changes are evolutionary, not revolutionary. 
During the many discussions in the IETF in the 1990s, there were some 
who said that while we were updating IP, perhaps we should make a complete, 
radical change to a new type of internetworking protocol completely. 
The end decision was not to do this, but to define a more capable version 
of the IP we've been using all along. The reason for this is simple: IP, 
like our trusted older car, works. IPv6 represents an 
update that strives to add to the best characteristics of IPv4 rather 
than making everyone start over from scratch with something new and 
unproven. This design ensures that whatever pain may result from the 
change from IPv4 to IPv6 can be managed, and hopefully, minimized.  |  Key Concept: The new version of the Internet Protocol is Internet Protocol Version 6 (IPv6). It was created to correct some of the significant problems of IPv4, especially the looming exhaustion of the IPv4 address space, and to improve the operation of the protocol as a whole, to take TCP/IP in to the future.
 | 
 
 
 
 | 
 | If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |  
|  | 
 | 
 
 
 Home - 
Table Of Contents - Contact Us
 
 The TCP/IP Guide (http://www.TCPIPGuide.com)
 Version 3.0 - Version Date: September 20, 2005
 
 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
 Not responsible for any loss resulting from the use of this site.
 |