7 Network Working Group G. Huston
8 Request for Comments: 4159 APNIC
10 Category: Best Current Practice
13 Deprecation of "ip6.int"
17 This document specifies an Internet Best Current Practices for the
18 Internet Community, and requests discussion and suggestions for
19 improvements. Distribution of this memo is unlimited.
23 Copyright (C) The Internet Society (2005).
27 This document advises of the deprecation of the use of "ip6.int" for
28 Standards Conformant IPv6 implementations.
30 1. IPv6 Standards Action
32 In August 2001 the IETF published [RFC3152], which advised that the
33 use of "ip6.int" as the domain for reverse-mapping of IPv6 addresses
34 to DNS names was deprecated. The document noted that the use of
35 "ip6.int" would be phased out in an orderly fashion.
37 As of 1 September 2005, the IETF advises the community that the DNS
38 domain "ip6.int" should no longer be used to perform reverse mapping
39 of IPv6 addresses to domain names, and that the domain "ip6.arpa"
40 should be used henceforth, in accordance with the IANA Considerations
41 described in [RFC3596]. The domain "ip6.int" is deprecated, and its
42 use in IPv6 implementations that conform to the IPv6 Internet
43 Standards is discontinued.
45 The Regional Internet Registries (RIRs) are advised that maintenance
46 of delegation of entries in "ip6.int" is no longer required as part
47 of infrastructure services in support of Internet Standards
48 Conformant IPv6 implementations as of 1 September 2005. The RIRs are
49 requested to work with their communities to adopt a schedule
50 regarding the cessation of support of registration services for the
58 Huston Best Current Practice [Page 1]
60 RFC 4159 ip6.int August 2005
63 2. IANA Considerations
65 IANA is advised that the "ip6.int" domain for reverse mapping of IPv6
66 addresses to domain names is no longer part of Internet Standards
67 Conformant support of IPv6 as of 1 September 2005.
69 3. Security Considerations
71 While DNS spoofing of address to name mapping has been exploited in
72 IPv4, removal of the "ip6.int" zone from the standard IPv6
73 specification creates no new threats to the security of the internet.
77 The document was prepared with the assistance of Kurt Lindqvist,
78 Thomas Narten, Paul Wilson, David Kessens, Bob Hinden, Brian
79 Haberman, and Bill Manning.
81 5. Normative References
83 [RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152,
86 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS
87 Extensions to Support IP Version 6", RFC 3596, October
114 Huston Best Current Practice [Page 2]
116 RFC 4159 ip6.int August 2005
119 Full Copyright Statement
121 Copyright (C) The Internet Society (2005).
123 This document is subject to the rights, licenses and restrictions
124 contained in BCP 78, and except as set forth therein, the authors
125 retain all their rights.
127 This document and the information contained herein are provided on an
128 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
129 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
130 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
131 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
132 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
133 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
135 Intellectual Property
137 The IETF takes no position regarding the validity or scope of any
138 Intellectual Property Rights or other rights that might be claimed to
139 pertain to the implementation or use of the technology described in
140 this document or the extent to which any license under such rights
141 might or might not be available; nor does it represent that it has
142 made any independent effort to identify any such rights. Information
143 on the procedures with respect to rights in RFC documents can be
144 found in BCP 78 and BCP 79.
146 Copies of IPR disclosures made to the IETF Secretariat and any
147 assurances of licenses to be made available, or the result of an
148 attempt made to obtain a general license or permission for the use of
149 such proprietary rights by implementers or users of this
150 specification can be obtained from the IETF on-line IPR repository at
151 http://www.ietf.org/ipr.
153 The IETF invites any interested party to bring to its attention any
154 copyrights, patents or patent applications, or other proprietary
155 rights that may cover technology that may be required to implement
156 this standard. Please address the information to the IETF at ietf-
161 Funding for the RFC Editor function is currently provided by the
170 Huston Best Current Practice [Page 3]