Changes

4,325 bytes added ,  3 years ago
no edit summary
Line 1: Line 1: −
'''IPv6 (Internet Protocol Version 6)''' is the version of internet protocol which supports the 128-bit [[IP Address|IP addresses]]. It has been developed as the next generation protocol to increase the 4 billion IP Addresses available and it will eventually replace the nearly exhausted [[IPv4]], which supports 32-bit address space.<ref>[http://www.iana.org/about/glossary/ www.iana,org]</ref> IPv6 has been developed to provide advantages over the current internet protocol. It is expected to solve several network problems by eliminating the need for [[NAT|Network Address Translation]] (NAT).
+
{{Glossary|
 +
|note  =
 +
|logo    =
 +
|link =
 +
}}
 +
 
 +
'''Internet Protocol Version 6 (IPv6)''' is a version of [[Internet Protocol|the IP protocol]] which supports 128-bit [[IP Address|IP addresses]]. It has been developed as the next generation protocol to increase the 4 billion IP Addresses available and it will eventually replace the nearly exhausted [[IPv4]], which supports 32-bit address space.<ref>[http://www.iana.org/about/glossary/ www.iana,org]</ref> IPv6 has been developed to provide advantages over the current internet protocol. It is expected to solve several network problems by eliminating the need for [[NAT|Network Address Translation]] (NAT).
 +
 
 +
In late December 2015, IPv6 reached 10% adoption worldwide. <ref>[http://arstechnica.com/business/2016/01/ipv6-celebrates-its-20th-birthday-by-reaching-10-percent-deployment/ Ars Technica-IPv6 Reaches 10%]</ref> Late december 2019 it reached around 30% adoption worldwide, according to measurements by Google.
    
==Background==
 
==Background==
As early as 1990, internet experts predicted that the 4 billion available IP addresses under the IPv4 were not enough to accommodate the rapid growth of internet users worldwide. During the [[IETF|Internet Engineering Task Force]] Meeting (IETF) in Vancouver in 1990, [[Phil Gross]], Chairman of the [[IESG|Internet Steering Group]] (IESG), together with [[Frank Solensky]] and [[Sue Hares]], informed that the Class B space will be exhausted as early as March, 1994. The solution to the problem was to assign multiple Class C address.This expansion signaled a great problem, which meant deciding whether to limit the size and growth rate of the internet or to disrupt the network by changing to new strategies or technology.<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>
+
As early as 1990, internet experts predicted that the 4 billion available IP addresses under the IPv4 would not be enough to accommodate the rapid growth of internet users worldwide. During the [[IETF|Internet Engineering Task Force]] Meeting (IETF) in Vancouver in 1990, [[Phil Gross]], Chairman of the [[IESG|Internet Steering Group]] (IESG), together with [[Frank Solensky]] and [[Sue Hares]], noted that the Class B space will be exhausted as early as March, 1994. The solution to the problem was to assign multiple Class C address.This expansion signaled a great problem, which meant deciding whether to limit the size and growth rate of the Internet or to disrupt the network by changing to new strategies or technology.<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>
   −
In 1991, the [[IAB|Internet Architecture Board]] (IAB) recommended the need for additional address flexibility. Based on this recommendation, the [[Internet Engineering Task Force]] formed the  Routing and Addressing (Road) Group to  examine the consumption of address space and the exponential growth in inter-domain routing entries.<ref>[http://www.potaroo.net/papers/2002-10-ipv6/IPv6.pdf IP Version 6 Geoff Huston]</ref> The Road Group enumerated three possible serious problems, which include:<ref>[http://www.rfc-archive.org/getrfc.php?rfc=1519 RFC Archive]</ref>Exhaustion of the class B network address space, Growth of routing tables in Internet routers beyond the ability of current software, hardware, and people to effectively manage it, and eventual exhaustion of the 32-bit IP address space. It also recommended immediate and long term solutions which include the adoption of CIDR route aggregation proposal, reducing the growth rate of routing table and called for proposals "to form working groups to explore separate approaches for bigger Internet addresses."<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>  
+
In 1991, the [[IAB|Internet Architecture Board]] (IAB) recommended the need for additional address flexibility. Based on this recommendation, the [[IETF|Internet Engineering Task Force]] formed the  Routing and Addressing (Road) Group to  examine the consumption of address space and the exponential growth in inter-domain routing entries.<ref>[http://www.potaroo.net/papers/2002-10-ipv6/IPv6.pdf IP Version 6 Geoff Huston]</ref> The Road Group enumerated three possible serious problems, which include:<ref>[http://www.rfc-archive.org/getrfc.php?rfc=1519 RFC Archive]</ref>Exhaustion of the class B network address space, Growth of routing tables in Internet routers beyond the ability of current software, hardware, and people to effectively manage it, and eventual exhaustion of the 32-bit IP address space. It also recommended immediate and long term solutions which included the adoption of CIDR route aggregation proposal, reducing the growth rate of routing table, and called for proposals "to form working groups to explore separate approaches for bigger Internet addresses."<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>  
   −
In 1993, IETF formed the [[Internet Protocol Next Generation Group]] to evaluate the proposals and determine how to proceed in selecting a successor to the IPv4. THe group evaluated and reviewed the proposals of [[CATNIP]], [[SIPP]] and [[TUBA]]. After numerous discussions, the Directorate recommended the adoption of [[SIPP|Simple Internet Protocol Plus]] (SIPP) Spec. (128 bit version as the basis for the next generation of Internet Protocol. The version number 6 was assigned by [[IANA]] and it was officially called IPv6.<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>
+
In 1993, IETF formed the [[Internet Protocol Next Generation Group]] to evaluate the proposals and determine how to proceed in selecting a successor to IPv4. THe group evaluated and reviewed the proposals of [[CATNIP]], [[SIPP]] and [[TUBA]]. After numerous discussions, the Directorate recommended the adoption of [[SIPP|Simple Internet Protocol Plus]] (SIPP) Spec.128 bit version as the basis for the next generation of Internet Protocol. The version number 6 was assigned by [[IANA]] and it was officially called IPv6.<ref>[http://datatracker.ietf.org/doc/rfc1752/?include_text=1 RFC 1752]</ref>
    
==IPv6 Working Group==
 
==IPv6 Working Group==
The [[IPv6 Working Group]] was created by the [[IESG]] as to implement the recommendations of the Internet Protocol Next Generation's Directors set forth during the IETF meeting in July, 1994 as described in [[RFC]] 1752 entitled, The Recommendation for the IP Next Generation Protocol. The IPv6 working group's primary role is to oversee the specification and standardization of IPv6.<ref>[http://datatracker.ietf.org/wg/ipv6/charter/ IP Version 6 Working Group]</ref>
+
The [[IPv6 Working Group]] was created by the [[IESG]] to implement the recommendations of the Internet Protocol Next Generation's Directors set forth during the IETF meeting in July, 1994, as described in [[RFC]] 1752 entitled, The Recommendation for the IP Next Generation Protocol. The IPv6 working group's primary role is to oversee the specification and standardization of IPv6.<ref>[http://datatracker.ietf.org/wg/ipv6/charter/ IP Version 6 Working Group]</ref>
    
==IPv6 Features & Benefits==
 
==IPv6 Features & Benefits==
IPv6 has the following features and benefits:<ref>[http://tools.ietf.org/html/rfc1883 RFC 1883]</ref> <ref>[http://www.cu.ipv6tf.org/pdf/ipv6dswp.pdf www.cu.ipv6tf.org]</ref>
+
IPv6 has the following features and benefits:<ref>RFC 1883</ref> <ref>[http://www.cu.ipv6tf.org/pdf/ipv6dswp.pdf www.cu.ipv6tf.org]</ref>
 
# Expanded addressing capabilities of 128 bits, a larger number of addressing nodes and a simpler auto configuration of addresses.
 
# Expanded addressing capabilities of 128 bits, a larger number of addressing nodes and a simpler auto configuration of addresses.
 
# Simplified header for routing efficiency and performance
 
# Simplified header for routing efficiency and performance
Line 20: Line 28:  
# Deeper hierarchy and policies for network architecture flexibility
 
# Deeper hierarchy and policies for network architecture flexibility
 
# Efficient support for routing and route aggregation
 
# Efficient support for routing and route aggregation
# Server less autoconfiguration, easier renumbering, multihoming, and improved plug and play support
+
# Serverless autoconfiguration, easier renumbering, multihoming, and improved plug and play support
 
# Security with mandatory IP Security (IPSec) support for all IPv6 devices
 
# Security with mandatory IP Security (IPSec) support for all IPv6 devices
 
# Improved support for Mobile IP and mobile computing devices (direct-path)
 
# Improved support for Mobile IP and mobile computing devices (direct-path)
# Enhanced multicast support with increased addresses and efficient mechanism
+
# Enhanced multicast support with increased addresses and efficient mechanisms
 +
 
 +
==IPv6 Address Notation Vs IPV4 Address Notation==
 +
Consider the following for example, the IPv4 address "192.168.100.32" may appear in IPv6 notation as "0000:0000:0000:0000:0000:0000:C0A8:6420" or "::C0A8:6420".
   −
==IPv6 Address Notation==
   
An IPv6 address is written in hexadecimal quartets separated by colon for example: 2001:cdba:1900:0000:0000:0000:1757:3618 If there is a four-digit group of zeroes within an IPv6 address, it can be reduced to a single zero and delete the group of 4 zeroes and the address can be written as:2011:cdba:1900:0:0:0:1757:3818 or 2001:cdba:1900:3257:9652<ref>[http://ipv6.com/articles/general/IPv6-Addressing.htm IPv6 Address Notation]</ref>
 
An IPv6 address is written in hexadecimal quartets separated by colon for example: 2001:cdba:1900:0000:0000:0000:1757:3618 If there is a four-digit group of zeroes within an IPv6 address, it can be reduced to a single zero and delete the group of 4 zeroes and the address can be written as:2011:cdba:1900:0:0:0:1757:3818 or 2001:cdba:1900:3257:9652<ref>[http://ipv6.com/articles/general/IPv6-Addressing.htm IPv6 Address Notation]</ref>
 +
 +
The most obvious benefit of IPv6 is the exponentially greater number of IP addresses it can support compared to IPv4. Many countries outside the U.S. suffer from a shortage of IP addresses today. Because IPv6 and IPv4 protocols coexist, those locales with an address shortage can easily deploy new IPv6 networks that work with the rest of the Internet. Experts believe it will take many more years before all networks fully change over to IPv6.
 +
 +
Other benefits of IPv6 are less obvious but equally important. The internals of the IPv6 protocol have been designed with scalability and extensibility in mind. This will allow many different kinds of devices besides PCs, like cell phones and home appliances, to more easily join the Internet in future.
 +
 +
    
==Types of IPv6 Addresses==
 
==Types of IPv6 Addresses==
IPv6 has three types of addresses, which include:
+
IPv6 supports the following three IP address types:
* [[Unicast Address]], which serves as a single interface identifier and it is delivered to the interface identified by the address;
+
* [[Unicast Address]]
* [[Multicast Address]], an identifier for a group/set of interfaces that may belong to the different nodes delivered to multiple interfaces
+
* [[Multicast Address]]
* [[Anycast Address]], an identifiers for a set of interfaces that may belong to different nodes and it is delivered to any of the interfaces identified by the address.<ref>[http://ip6.com/articles/general/IPv6-Addressing.htm Types of IPv6 Address]</ref>
+
* [[Anycast Address]]
 +
 
 +
Unicast and multicast messaging in IPv6 are conceptually the same as in IPv4. IPv6 does not support broadcast, but its multicast mechanism accomplishes essentially the same effect. Multicast addresses in IPv6 start with 'FF' (255) just like IPv4 addresses.
 +
 
 +
Anycast in IPv6 is a variation on multicast. Whereas multicast delivers messages to all nodes in the multicast group, anycast delivers messages to any one node in the multicast group. Anycast is an advanced networking concept designed to support the failover and load balancing needs of applications.
 +
 
 +
IPv6 reserves just two special addresses: 0:0:0:0:0:0:0:0 and 0:0:0:0:0:0:0:1. IPv6 uses 0:0:0:0:0:0:0:0 internal to the protocol implementation, so nodes cannot use it for their own communication purposes. IPv6 uses 0:0:0:0:0:0:0:1 as its loopback address, equivalent to 127.0.0.1 in IPv4.
 +
 
 +
Also Known As: IPng (Internet Protocol Next Generation)
    
==IPv6 Special Addresses==
 
==IPv6 Special Addresses==
Line 46: Line 70:     
==IPv6 Forum==
 
==IPv6 Forum==
On July 17, 1999, the [[IPv6 Forum]], a non-profit organization was established composed of international Internet vendors, Industry Subject Matter Experts, Research & Education Networks to help educate and inform the global internet community regarding the importance of deploying the IPv6.<ref>[http://www.ipv6forum.com/modules.php?op=modload&name=News&file=article&sid=9 IPv6 Forum]</ref>
+
On July 17, 1999, the [[IPv6 Forum]], a non-profit organization, was established and composed of international Internet vendors, Industry Subject Matter Experts, and Research & Education Networks to help educate and inform the global Internet community regarding the importance of deploying the IPv6.<ref>[http://www.ipv6forum.com/modules.php?op=modload&name=News&file=article&sid=9 IPv6 Forum]</ref>
    
==IPv6 Deployment==
 
==IPv6 Deployment==
Om December 1995, [[IANA]] formally assumed the responsibility of the address management functions of IPv6 subsequently in 1996, the IPv6 standard is completed and its production allocation is made available to [[ISP]]s in 1999. The early phase of IPv6 deployment started in 2000 using tunneling techniques over a common IPv4 layer.[[Google]] and [[Comcast]] are among the large internet operators deploying IPv6.<ref>[http://www.oecd.org/dataoecd/48/51/44953210.pdf www.oecd.org]</ref> By mid 2007, public interest on the use of IPv6 increased based on the Autonomous System (AS) routing table. Between 2004 to 2008, IPv6 routes increased from 2.5 % TO 3%. iN 2008, the size of IPv6 deployment in terms of host capability is between 2-3 per one thousand internet hosts.<ref>[http://meetings.ripe.net/ripe-56/presentations/Huston-Measuring_IPv6_Deployment.pdf Measuring IPv6 Deployment]</ref>
+
In December, 1995, [[IANA]] formally assumed the responsibility of the address management functions of IPv6; subsequently, in 1996, the IPv6 standard was completed, in 1999 its production allocation was made available to [[ISP]]s. The early phase of IPv6 deployment started in 2000 using tunneling techniques over a common IPv4 layer. [[Google]] and [[Comcast]] were among the large Internet operators deploying IPv6 at the time.<ref>[http://www.oecd.org/dataoecd/48/51/44953210.pdf www.oecd.org]</ref> By mid 2007, public interest on the use of IPv6 increased based on the [[AS|Autonomous System]] routing table. Between 2004 to 2008, IPv6 routes increased from 2.5 % TO 3%. As of 2008, the size of IPv6 deployment in terms of host capability is between 2-3 per one thousand Internet hosts.<ref>[http://meetings.ripe.net/ripe-56/presentations/Huston-Measuring_IPv6_Deployment.pdf Measuring IPv6 Deployment]</ref>
 +
 
 +
==ICANN's IPv6 Global Allocation Policy==
 +
On July 16, 2006, [[ICANN]] released its policy statement regarding the allocation of IPv6 address space, which include:<ref>[http://www.icann.org/en/policies/proposed-ipv6-policy-14jul06.htm Proposed Global Policy for Allocation of IPv6 Address Space]</ref>
 +
*  The unit of IPv6 address space allocation from [[IANA]] will be /12. A sufficient number of address space will allocated to every [[RIR|Regional Internet Registries]] to support their registries needs for 18 months. Each RIR will be responsible for choosing their own allocation reservation strategies to ensure effective and efficient work.
 +
* Every RIR with less than /12 of un-allocated address space will receive an IPv6 allocation from IANA following ICANN's implementation of the IPv6 Address Space Global Allocation Policy.
 +
* Any RIR will be eligible for an additional allocation of IPv6 address space if an RIR has less than 50% of the /12 and an RIR's IPv6 address space is less than its established necessary space for the next 9 months period. In this situation IANA will make a single IPv6 allocation to meet the RIR's established address space for 18 months.
 +
* The IPv6 necessary space will be calculated this way, '''NECESSARY SPACE=AVERAGE # OF ADDRESSES ALLOCATED PER MONTH x LENGTH OF PERIOD IN MONTHS'''
 +
* The allocation of IPV6 addresses to an RIR should be announced and updated by IANA, and the [[NRO|National Resource Organization]] (NRO, the coordinating body for the 5 RIRs responsible for distributing IP addresses and AS numbers), and each RIR's respective website. The administrative procedures to manage this process will be handled by ICANN and the NRO.
    
==Google Experiment on IPv6==
 
==Google Experiment on IPv6==
 
The experiment conducted by Google on IPv6 end-user connectivity and traffic levels in 2009 found that:<ref>[http://www.oecd.org/dataoecd/48/51/44953210.pdf Result of Google Experiment on IPv6]</ref>
 
The experiment conducted by Google on IPv6 end-user connectivity and traffic levels in 2009 found that:<ref>[http://www.oecd.org/dataoecd/48/51/44953210.pdf Result of Google Experiment on IPv6]</ref>
* 0.25% of users were IPv6 capable as September 2009 and half of the users were using MacOs and Windows Vista
+
* 0.25% of users were IPv6 capable as September 2009 and half of the users were using MacOS and Windows Vista
* 0.9% of end-users using other technically oriented websites were connected to IPv6 when possible as of June 2009
+
* 0.9% of end-users using other technically oriented websites were connected to IPv6 when possible as of June, 2009
 
* Leading countries countries capable of using IPv6 as of September 2009 were France (1%), China (0.4%), Sweden (0.2%), Japan, Netherlands and United States (less than 0.1%)
 
* Leading countries countries capable of using IPv6 as of September 2009 were France (1%), China (0.4%), Sweden (0.2%), Japan, Netherlands and United States (less than 0.1%)
* networks originating majority of IPv6 traffic come from universities and research institutions with the exemption of [[free.fr]], a French IPv6 enabled ISP.
+
* Networks originating majority of IPv6 traffic come from universities and research institutions with the exemption of [[free.fr]], a French IPv6 enabled ISP.
   −
==ICANN's IPv6 Global Allocation Policy==
+
==IPv4 Final Depletion==
On July 16, 2006, [[ICANN]] released its' policy statement regarding the allocation of IPv6 address space which include:<ref>[http://www.icann.org/en/policies/proposed-ipv6-policy-14jul06.htm Proposed Global Policy for Allocation of IPv6 Address Space]</ref>
+
On February 3, 2011, [[ICANN]] along with the [[NRO|Number Resources Organization]] (NRO), the [[IAB|Internet Architecture Board]] (IAB) and the [[ISOC|Internet Society]] (ISOC) informed the global Internet community that the remaining IPv4 addresses were all allocated by the [[IANA|Internet Assigned Names and Numbers]] (IANA) to the [[RIR|Regional Internet Registries]] (RIRs). ICANN's President and CEO at the time, [[Rod Beckstrom]], noted that IPv6 adoption is very important and the Internet technical community had been planning and working for a long period of time to deploy IPv6 when IPV4 addresses are completely depleted. In addition, [[Raúl Echeberría]], Chairman of the [[NRO]], emphasized that  “deploying IPv6 is now a requirement, not an option".<ref>[http://www.icann.org/en/news/releases/release-03feb11-en.pdf Available Pool of Unallocated IPv4 Internet Addresses Now Completely Emptied]</ref>
*  The unit of IPv6 address space allocation from [[IANA]] will be /12. A sufficient number of address space will allocated to every [[RIR]] to support their registries needs for 18 months.RIR will be responsible in choosing their own allocation reservation strategies to ensure effective and efficient work.
+
 
* Every RIR with less than /12 of un-allocated address space will receive an IPv6 allocation from IANA following ICANN's implementation of the IPv6 Address Space Global Allocation Policy.
+
==World IPv6 Day==
* Any RIR will be eligible for an additional allocation of IPv6 address space if an RIR has less than 50% of the /12 and an RIR's IPv6 address space is less than its established necessary space for the next 9 months period. During this situations, IANA will make a single IPv6 allocation  enough to meet the RIR's established address space for 18 months.
+
On June 8, 2011, [[ISOC]] led the [[World IPv6 Day]], a global trial of the deployment of the IPv6 ; 400 organizations such as [[Google]], [[Facebook]], [[Yahoo]]!, [[Akamai]] and [[Limelight Networks]] participated. The participants enabled IPv6 on their primary service for 24 hours to find out the potential challenges related to using the new Internet protocol. Based on the result of the trial, services were accessed normally by the majority of the Internet users; however, there were some cases wherein users experienced difficulty in accessing the services of some of the participants.<ref>[http://isoc.org/wp/newsletter/?p=3861 World IPv6 Day]</ref>
* The IPv6 necessary space will be calculated this way, '''NECESSARY SPACE=AVERAGE NO. OF ADDRESSES ALLOCATED PER MONTH x LENGTH OF PERIOD IN MONTHS'''
+
 
* The allocation of IPV6 addresses to an RIR should be announced an updated on IANA, National Resource Organization ([[NRO]]), the coordinating body for the 5 RIRs responsible in distributing IP addresses and AS numbers; and RIR respective websites. The administrative procedures to manage this process will be handled by ICANN and NRO.
+
According to [[John Curran]], chief executive of the [[ARIN|American Registry for Internet Numbers]] (ARIN), the trial was successful. [[Rob Malan]], chief technology officer of [[Arbor Networks]], also noted that the test went without major problems. Some analysts believe that potential problems may occur when companies start to actually use the new protocol in the next few years as [[IPv4]] and IPv6 need to co-exist for a period of time. Some experts are also concern about Internet security issues, citing that there are no standards in the process of encapsulation, a technology used to enable IPv4 and IPv6 sites to communicate with each other during the transition period.<ref>[http://www.computerworld.com/s/article/9217459/World_IPv6_Day_draws_attention_to_security_issues_with_new_protocol World IPv6 Day draws attention to security issues with new protocol]</ref>
    
==References==
 
==References==
Line 70: Line 102:     
[[Category: Glossary]]
 
[[Category: Glossary]]
 +
[[Category: Acronym]]
Bureaucrats, Check users, lookupuser, Administrators, translator
3,197

edits