Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 4291

Authors:

S. Kawamura
M. Kawashima

Stream:

IETF

Source:

6man (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5952

Discuss this RFC: Send questions or comments to the mailing listipv6@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5952

Abstract

As IPv6 deployment increases, there will be a dramatic increase inthe need to use IPv6 addresses in text. While the IPv6 addressarchitecture in Section 2.2 of RFC 4291 describes a flexible modelfor text representation of an IPv6 address, this flexibility has beencausing problems for operators, system engineers, and users. Thisdocument defines a canonical textual representation format. It doesnot define a format for internal storage, such as within anapplication or database. It is expected that the canonical formatwill be followed by humans and systems when representing IPv6addresses as text, but all implementations must accept and be able tohandle any legitimate RFC 4291 format. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.