RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing
In plain English — editorial summary, not part of the RFC
The IPv6 unicast addressing format includes a separation between the prefix used to route packets to a subnet and the interface identifier used to specify a given interface connected to that subnet. Currently, the interface identifier is defined as 64 bits long for almost every case, leaving 64 bits for the subnet prefix. This document describes the advantages of this fixed boundary and analyzes the issues that would be involved in treating it as a variable boundary.
Document record
- Document ID
- RFC7421
- Published
- January 2015
- Authors
- B. Carpenter; T. Chown; F. Gont; S. Jiang; A. Petrescu; A. Yourtchenko
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7428Transmission of IPv6 Packets over ITU-T G.9959 NetworksCurrent
February 2015
- RFC 7429Distributed Mobility Management: Current Practices and Gap AnalysisCurrent
January 2015
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 7402Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Current
April 2015
- RFC 7401Host Identity Protocol Version 2 (HIPv2)Updated
April 2015
- RFC 74006LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
November 2014
- RFC 7389Separation of Control and User Plane for Proxy Mobile IPv6Current
October 2014
- RFC 7388Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
October 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?