![]() RFC 5952 IPv6 Text Representation August 2010ġ. Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. ![]() This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Will be followed by humans and systems when representing IPv6Īddresses as text, but all implementations must accept and be able to Not define a format for internal storage, such as within anĪpplication or database. Thisĭocument defines a canonical textual representation format. While the IPv6 addressĪrchitecture in Section 2.2 of RFC 4291 describes a flexible modelįor text representation of an IPv6 address, this flexibility has beenĬausing problems for operators, system engineers, and users. Request for Comments: 5952 NEC BIGLOBE, Ltd.Ĭategory: Standards Track NEC AccessTechnica, Ltd.Ī Recommendation for IPv6 Address Text RepresentationĪs IPv6 deployment increases, there will be a dramatic increase in ![]() Internet Engineering Task Force (IETF) S. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |