RFC 5952 on A Recommendation for IPv6 Address Text Representation

rfc-editor@rfc-editor.org Fri, 20 August 2010 18:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4C5E03A6B1E; Fri, 20 Aug 2010 11:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.057
X-Spam-Status: No, score=-102.057 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id DMh8s+O4nQao; Fri, 20 Aug 2010 11:13:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id AC0D83A6B0F; Fri, 20 Aug 2010 11:13:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8AAC9E0656; Fri, 20 Aug 2010 11:14:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5952 on A Recommendation for IPv6 Address Text Representation
From: rfc-editor@rfc-editor.org
Message-Id: <20100820181415.8AAC9E0656@rfc-editor.org>
Date: Fri, 20 Aug 2010 11:14:15 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2010 18:13:43 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5952

        Title:      A Recommendation for IPv6 Address 
                    Text Representation 
        Author:     S. Kawamura, M. Kawashima
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    kawamucho@mesh.ad.jp, 
        Pages:      14
        Characters: 26570
        Updates:    RFC4291

        I-D Tag:    draft-ietf-6man-text-addr-representation-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5952.txt

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]

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC