Internet Protocol version 6

Internet Protocol version 6
Michel Bakni · CC BY-SA 4.0 · source
Name	Internet Protocol version 6
Introduced	1998
Developer	Internet Engineering Task Force
Predecessor	Internet Protocol version 4
Standard	RFC 2460, RFC 8200

Internet Protocol version 6 is the principal protocol for addressing and routing packets on the Internet designed to replace Internet Protocol version 4 by expanding address space and simplifying packet processing. Developed by the Internet Engineering Task Force and standardized in documents such as RFC 2460 and RFC 8200, the protocol underpins modern IETF work, interconnects with Transmission Control Protocol, User Datagram Protocol, and influences architectures used by Cisco Systems, Juniper Networks, and major cloud providers like Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Background and Motivation

IPv6 emerged from exhaustion of IPv4 address space and scalability problems highlighted by the growth of the World Wide Web, expansion of mobile telephony networks handled by 3GPP, and the proliferation of devices in the Internet of Things driven by companies such as Intel Corporation and ARM Holdings. Work in the IETF and the Internet Architecture Board followed earlier addressing schemes from Classless Inter-Domain Routing proposals and lessons from ARPANET, NSFNET, and enterprise networks run by AT&T and Verizon Communications. The specification aimed to address limitations identified in operational reports from IETF Working Groups, technical publications by ACM and IEEE, and deployment experiences documented by academic groups at MIT, Stanford University, and University of California, Berkeley.

Addressing and Header Structure

IPv6 uses 128-bit addresses organized into global unicast, unique local, multicast, and anycast categories, facilitating hierarchical allocation by registries such as Internet Assigned Numbers Authority, Regional Internet Registries, ARIN, RIPE NCC, and APNIC. Address notation employs hexadecimal and colons drawing on conventions common in publications from IEEE Standards Association. The base header was simplified relative to IPv4 to improve forwarding efficiency, influenced by router designs from Juniper Networks and Cisco Systems and research at Bell Labs and Carnegie Mellon University. Extension headers provide optional functionality, and interaction with link-layer technologies such as Ethernet, Wi‑Fi, LTE, and 5G is specified to support tethering and mobility handled by protocols from IETF Mobile IP work and specifications by 3GPP.

Routing and Transition Mechanisms

Routing for IPv6 is implemented in interior and exterior protocols including OSPFv3, BGP, and multipath techniques adapted from Equal-cost multi-path routing research; vendors like Cisco Systems, Huawei, and Arista Networks provide implementations. Transition mechanisms such as dual stack, tunneling (including 6in4 and GRE), and translation (NAT64, DNS64) were recommended by IETF task forces and used in operational environments managed by Cloudflare, Akamai Technologies, and national research networks like GEANT. Migration studies cited experiences from Japan, South Korea, Brazil, and Germany and coordination with Internet registries LACNIC and AfriNIC informed policy for address allocation and routing table growth tracked by organizations such as CIDR research groups and monitors like RouteViews.

Security and Privacy Features

IPv6 integrates security considerations with mandatory support for IPsec authentication and encapsulation modes in standards from the IETF Security Area, although practical deployment varies among vendors including Microsoft, Apple Inc., and Red Hat. Privacy extensions for temporary addresses were introduced to mitigate tracking concerns raised by privacy advocates and regulators in the European Union and national bodies; these extensions interact with DNS practices managed by ICANN and privacy frameworks from institutions such as Electronic Frontier Foundation. Threats such as IPv6-enabled reconnaissance, rogue RA attacks, and transition-induced vulnerabilities have been analyzed by security researchers at SANS Institute, CERT Coordination Center, and academic groups at University of Cambridge and ETH Zurich.

Deployment and Adoption

Adoption has progressed unevenly: content providers like Google, Facebook, Netflix, and Wikipedia have enabled IPv6 access, while many ISPs and enterprises lag due to legacy infrastructure from Comcast and regional incumbents. National strategies in United States, India, China, and Brazil differ, influenced by policy from ministries and standards bodies including ITU and regional registries such as AFRINIC. Measurements by APNIC, RIPE NCC, and research projects at University College London and KAIST track adoption metrics, and major operating systems—Windows, Linux, macOS, Android, iOS—include native stacks that facilitate deployment.

Implementation and Performance

Implementations exist in open-source projects like Linux kernel, FreeBSD, OpenBSD, BIND for DNS, and commercial stacks by Microsoft and Cisco Systems, optimized for forwarding in hardware by vendors such as Broadcom and Intel Corporation. Performance tradeoffs involve MTU handling, path MTU discovery, and header processing costs studied in benchmarks from IETF workshops, performance labs at Google, and academic papers from ACM SIGCOMM and IEEE INFOCOM. High-performance data centers and CDNs run IPv6 on routers and load balancers by F5 Networks and Nginx while research on offload and acceleration continues at institutions like Tsinghua University and University of California, Los Angeles.

Category:Internet protocols