metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 5952: A Recommendation for IPv6 Address Text Representation

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5952
Published
August 2010
Authors
S. Kawamura; M. Kawashima
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
14
Also known as
—
Updates:
RFC 4291

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5952-a-recommendation-for-ipv6-address-text-representation