1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
<pre>Network Working Group G. Huston
Request for Comments: 4159 APNIC
BCP: 109 August 2005
Category: Best Current Practice
<span class="h1">Deprecation of "ip6.int"</span>
Status of This Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document advises of the deprecation of the use of "ip6.int" for
Standards Conformant IPv6 implementations.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. IPv6 Standards Action</span>
In August 2001 the IETF published [<a href="./rfc3152" title=""Delegation of IP6.ARPA"">RFC3152</a>], which advised that the
use of "ip6.int" as the domain for reverse-mapping of IPv6 addresses
to DNS names was deprecated. The document noted that the use of
"ip6.int" would be phased out in an orderly fashion.
As of 1 September 2005, the IETF advises the community that the DNS
domain "ip6.int" should no longer be used to perform reverse mapping
of IPv6 addresses to domain names, and that the domain "ip6.arpa"
should be used henceforth, in accordance with the IANA Considerations
described in [<a href="./rfc3596" title=""DNS Extensions to Support IP Version 6"">RFC3596</a>]. The domain "ip6.int" is deprecated, and its
use in IPv6 implementations that conform to the IPv6 Internet
Standards is discontinued.
The Regional Internet Registries (RIRs) are advised that maintenance
of delegation of entries in "ip6.int" is no longer required as part
of infrastructure services in support of Internet Standards
Conformant IPv6 implementations as of 1 September 2005. The RIRs are
requested to work with their communities to adopt a schedule
regarding the cessation of support of registration services for the
"ip6.int" domain.
<span class="grey">Huston Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4159">RFC 4159</a> ip6.int August 2005</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
IANA is advised that the "ip6.int" domain for reverse mapping of IPv6
addresses to domain names is no longer part of Internet Standards
Conformant support of IPv6 as of 1 September 2005.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
While DNS spoofing of address to name mapping has been exploited in
IPv4, removal of the "ip6.int" zone from the standard IPv6
specification creates no new threats to the security of the internet.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
The document was prepared with the assistance of Kurt Lindqvist,
Thomas Narten, Paul Wilson, David Kessens, Bob Hinden, Brian
Haberman, and Bill Manning.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Normative References</span>
[<a id="ref-RFC3152">RFC3152</a>] Bush, R., "Delegation of IP6.ARPA", <a href="https://www.rfc-editor.org/bcp/bcp49">BCP 49</a>, <a href="./rfc3152">RFC 3152</a>,
August 2001.
[<a id="ref-RFC3596">RFC3596</a>] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS
Extensions to Support IP Version 6", <a href="./rfc3596">RFC 3596</a>, October
2003.
Author's Address
Geoff Huston
APNIC
EMail: gih@apnic.net
<span class="grey">Huston Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4159">RFC 4159</a> ip6.int August 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Huston Best Current Practice [Page 3]
</pre>
|
