Date: Thu, 26 Aug 2010 12:09:01 -0700 From: Doug Barton <dougb@FreeBSD.org> To: freebsd-doc@FreeBSD.org Subject: Fwd: RFC 5952 on A Recommendation for IPv6 Address Text Representation Message-ID: <4C76BBCD.5010209@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Please be aware of the following in regards to using IPv6 addresses in docs going forward. If you want to read just the guidelines skip to Section 4. :) Doug - -------- Original Message -------- Subject: RFC 5952 on A Recommendation for IPv6 Address Text Representation Date: Fri, 20 Aug 2010 11:14:15 -0700 (PDT) From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: ipv6@ietf.org, rfc-editor@rfc-editor.org 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, ~ kawashimam@necat.nec.co.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 ~ http://www.ietf.org/mailman/listinfo/ietf-announce ~ http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCAAGBQJMdrvNAAoJEFzGhvEaGryEcHUIAKgbnmH7ZaaqRlGtRdxx2FzZ yX4WMflFdC6NBzDgpkuuHG7IDbWU0ryHIa7q+fGTSCesW+1teCfjnjmlyXxFasn+ C5y3Z7hsPgA+52BWG2pSgSiRyMl5H1BuZbQEqjX0WZnCNffKuGlKa4BdhvOeCuvT c8+gxmZCZyRouBfjPgyoo94zunBn/8M2ax4GKwbAUpmUe4X+SEsTtOJ6cUQkElFT yCaoo9iURG+KpOjTBWSOs42HkWArj6cu9RrBgc9tYh4SEX+/X27DnyjQDsjbAk2M +ONjJfiLH/XGB8z2O1Pf4J4BCQRXrZVhMGngCQNEU8p/ZT4nxRcguDW7an0t9v0= =r+fL -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C76BBCD.5010209>