IPv6

IPv6
Name	IPv6
Developer	IETF Internet Engineering Task Force
Introduced	1998
Predecessor	IPv4
Status	Standard

IPv6 is the Internet Protocol version designed to replace IPv4 by providing a vastly larger address space and modernized protocol features. It was developed by the IETF and standardized through a series of RFC documents to meet scaling needs driven by entities such as ARPA, CERN, ITU, and major industry players like Cisco Systems, IBM, Microsoft, and Google. The design addresses limits encountered during the growth of networks involving organizations like DARPA, NSF, APNIC, RIPE NCC, and national registries such as ARIN.

History

Early motivation arose from address exhaustion seen in the late 1980s and early 1990s as networks operated by DARPA research, NSFNET, and commercial providers like AT&T expanded. The IETF formed working groups with contributors from Bell Labs, Sun Microsystems, Intel, and Juniper Networks to study successor protocols alongside proposals from Xerox PARC researchers and academics affiliated with MIT and Stanford University. Key milestones include publication of RFC series by authors associated with Steve Deering and collaborators linked to David Clark and meetings at IETF plenary sessions, interleaving technical debate with policy considerations raised by ICANN and regional internet registries such as LACNIC. Adoption discussions at conferences involving IETF 1994, IETF 1998, and industry events at COMDEX and Interop influenced rollout strategies.

Technical specifications

Specifications are defined in multiple RFCs developed under the aegis of the IETF and working groups such as 6MAN and 6LOWPAN. The protocol employs a 128-bit addressing format contrasting the 32-bit space used by IPv4 and includes a simplified header design with fixed fields inspired by research from RFC 2460 authors. Features include extension headers, flow labels, next-header semantics, and support for neighbor discovery protocols influenced by work at Bell Labs and experimental deployments by Hewlett-Packard and Sun Microsystems. The specification interacts with link-layer protocols such as Ethernet, IEEE 802.11, and PPP and with routing protocols like OSPF, BGP, and IS-IS adapted via standards efforts at IETF routing groups. Low-power and lossy network adaptations reference 6LoWPAN work connected to ARM and Atmel implementations.

Addressing and allocation

Addressing uses a 128-bit scheme categorized into unicast, multicast, and anycast addresses. Allocation and registry policies are managed by IANA and regional registries such as ARIN, RIPE NCC, APNIC, LACNIC, and AfriNIC, with allocation policies often shaped by stakeholders including ICANN and national regulators. Address blocks are represented using hexadecimal notation and prefix lengths; common ranges include link-local prefixes defined in standards authored by IETF contributors, global unicast blocks assigned to ISPs such as Verizon, AT&T, NTT, and Deutsche Telekom, and specialized ranges used by enterprises like Amazon (company), Facebook, and Microsoft Azure. Assignment practices involve DHCPv6, Stateless Address Autoconfiguration (SLAAC) methodologies influenced by academic work at University of California, Berkeley and Columbia University.

Deployment and adoption

Early deployments occurred in research networks such as CERNET, GEANT, and university backbones including MIT and Stanford University campuses. Commercial adoption progressed via ISPs like Sprint Corporation, Verizon, Comcast, and backbone operators such as Level 3 Communications and NTT Communications. Major platform vendors—including Cisco Systems, Juniper Networks, Huawei, Microsoft, Apple, and Google—implemented stacks enabling client, server, and cloud environments across Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Measurement studies by groups at APNIC Labs and academic teams from University of Oxford and Princeton University documented adoption growth influenced by events like IPv4 exhaustion announcements from IANA and policy shifts at ARIN.

Transition mechanisms

Transition methods were standardized and experimented with by industry and standards bodies including IETF working groups and vendors such as Cisco Systems and Juniper Networks. Techniques include dual-stack operation, tunneling approaches like 6in4, 6to4, and GRE tunnels used by operators such as Hurricane Electric and T-Mobile, and translation mechanisms like NAT64 and DNS64 deployed in networks operated by Cloudflare and large content providers such as Akamai. Migration strategies were debated in multistakeholder forums involving ICANN, regional registries, and operators like Level 3 Communications and Telefonica.

Security and privacy

Security considerations referenced in IETF documents align with work by researchers at SRI International, MITRE Corporation, and university security groups at Carnegie Mellon University and University of Cambridge. IPv6 introduced features affecting security posture: removal of widespread IPv4 NAT assumptions, IPsec integration efforts promoted by NSA and standardized in IETF, and privacy extensions for address randomization influenced by proposals from Microsoft Research and academic labs. Operational security practices developed by vendors (e.g., Cisco Systems guides), CERT teams like CERT/CC, and national agencies such as NIST address threats including neighbor discovery attacks, routing exploits against BGP, and transition-related risks exploited in tunneling scenarios.

Implementation and compatibility

Implementations are provided by major operating systems and network stacks including Linux, FreeBSD, OpenBSD, Windows, macOS, and networking equipment from Cisco Systems, Juniper Networks, Huawei, and Arista Networks. Embedded and IoT platforms from ARM, Espressif Systems, and TI support specialized stacks such as those compliant with 6LoWPAN for constrained hardware used in projects by IETF 6TiSCH and industry consortia like Zigbee Alliance. Compatibility testing and interoperability events involving IETF interoperability labs, vendor interoperability forums at Interop, and testbeds at research institutions like CERN and RIPE NCC help ensure cross-vendor operation across legacy IPv4 infrastructure.

Category:Internet protocols