A Recommendation for IPv6 Address Text Representation
RFC 5952, “A Recommendation for IPv6 Address Text Representation”, is a Proposed Standard document published in August 2010 by S. Kawamura, M. Kawashima. It updates RFC 4291. The canonical text is published by the RFC Editor.
Abstract
As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5952 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5951 Network Management Requirements for MPLS-based Transport Networks
- RFC 5953 Transport Layer Security Transport Model for the Simple Network Management Protocol
- RFC 5950 Network Management Framework for MPLS-based Transport Networks
- RFC 5954 Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261
- RFC 5949 Fast Handovers for Proxy Mobile IPv6
- RFC 5955 The application/timestamped-data Media Type
- RFC 5948 Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16
- RFC 5956 Forward Error Correction Grouping Semantics in the Session Description Protocol