A Recommendation for IPv6 Address Text Representation (RFC5952)
Original Publication Date: 2010-Aug-01
Included in the Prior Art Database: 2010-Aug-21
Internet Society Requests For Comment (RFCs)
S. Kawamura: AUTHOR [+2]
A single IPv6 address can be text represented in many ways. Examples are shown below.
Internet Engineering Task Force (IETF) S. Kawamura Request for Comments: 5952 NEC BIGLOBE, Ltd. Updates: 4291 M. Kawashima Category: Standards Track NEC AccessTechnica, Ltd. ISSN: 2070-1721 August 2010
A Recommendation for IPv6 Address Text Representation
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5952.
Kawashima Standards Track [Page 1]
RFC 5952 IPv6 Text Representation August 2010
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Kawamura & Kawashima Standards Track ...