| 1 |
<pre>Network Working Group S. Thomson |
| 2 |
Request for Comments: 1886 Bellcore |
| 3 |
Category: Standards Track C. Huitema |
| 4 |
INRIA |
| 5 |
December 1995 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">DNS Extensions to support IP version 6</span> |
| 9 |
|
| 10 |
|
| 11 |
Status of this Memo |
| 12 |
|
| 13 |
This document specifies an Internet standards track protocol for the |
| 14 |
Internet community, and requests discussion and suggestions for |
| 15 |
improvements. Please refer to the current edition of the "Internet |
| 16 |
Official Protocol Standards" (STD 1) for the standardization state |
| 17 |
and status of this protocol. Distribution of this memo is unlimited. |
| 18 |
|
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
This document defines the changes that need to be made to the Domain |
| 23 |
Name System to support hosts running IP version 6 (IPv6). The |
| 24 |
changes include a new resource record type to store an IPv6 address, |
| 25 |
a new domain to support lookups based on an IPv6 address, and updated |
| 26 |
definitions of existing query types that return Internet addresses as |
| 27 |
part of additional section processing. The extensions are designed |
| 28 |
to be compatible with existing applications and, in particular, DNS |
| 29 |
implementations themselves. |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
<span class="grey">Thompson & Huitema Standards Track [Page 1]</span></pre> |
| 50 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 51 |
<span class="grey"><a href="./rfc1886">RFC 1886</a> IPv6 DNS Extensions December 1995</span> |
| 52 |
|
| 53 |
|
| 54 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. INTRODUCTION</span> |
| 55 |
|
| 56 |
Current support for the storage of Internet addresses in the Domain |
| 57 |
Name System (DNS)[<a href="#ref-1" title=""Domain Names - Concepts and Facilities"">1</a>,<a href="#ref-2" title=""Domain Names - Implementation and Specifica- tion"">2</a>] cannot easily be extended to support IPv6 |
| 58 |
addresses[3] since applications assume that address queries return |
| 59 |
32-bit IPv4 addresses only. |
| 60 |
|
| 61 |
To support the storage of IPv6 addresses we define the following |
| 62 |
extensions: |
| 63 |
|
| 64 |
o A new resource record type is defined to map a domain name to an |
| 65 |
IPv6 address. |
| 66 |
|
| 67 |
o A new domain is defined to support lookups based on address. |
| 68 |
|
| 69 |
o Existing queries that perform additional section processing to |
| 70 |
locate IPv4 addresses are redefined to perform additional |
| 71 |
section processing on both IPv4 and IPv6 addresses. |
| 72 |
|
| 73 |
The changes are designed to be compatible with existing software. The |
| 74 |
existing support for IPv4 addresses is retained. Transition issues |
| 75 |
related to the co-existence of both IPv4 and IPv6 addresses in DNS |
| 76 |
are discussed in [<a href="#ref-4" title=""Transition Mechanisms for IPv6 Hosts and Routers"">4</a>]. |
| 77 |
|
| 78 |
|
| 79 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. NEW RESOURCE RECORD DEFINITION AND DOMAIN</span> |
| 80 |
|
| 81 |
A new record type is defined to store a host's IPv6 address. A host |
| 82 |
that has more than one IPv6 address must have more than one such |
| 83 |
record. |
| 84 |
|
| 85 |
|
| 86 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> AAAA record type</span> |
| 87 |
|
| 88 |
The AAAA resource record type is a new record specific to the |
| 89 |
Internet class that stores a single IPv6 address. |
| 90 |
|
| 91 |
The value of the type is 28 (decimal). |
| 92 |
|
| 93 |
|
| 94 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> AAAA data format</span> |
| 95 |
|
| 96 |
A 128 bit IPv6 address is encoded in the data portion of an AAAA |
| 97 |
resource record in network byte order (high-order byte first). |
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
<span class="grey">Thompson & Huitema Standards Track [Page 2]</span></pre> |
| 103 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 104 |
<span class="grey"><a href="./rfc1886">RFC 1886</a> IPv6 DNS Extensions December 1995</span> |
| 105 |
|
| 106 |
|
| 107 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> AAAA query</span> |
| 108 |
|
| 109 |
An AAAA query for a specified domain name in the Internet class |
| 110 |
returns all associated AAAA resource records in the answer section of |
| 111 |
a response. |
| 112 |
|
| 113 |
A type AAAA query does not perform additional section processing. |
| 114 |
|
| 115 |
|
| 116 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Textual format of AAAA records</span> |
| 117 |
|
| 118 |
The textual representation of the data portion of the AAAA resource |
| 119 |
record used in a master database file is the textual representation |
| 120 |
of a IPv6 address as defined in [<a href="#ref-3" title=""IP Version 6 Addressing Architecture"">3</a>]. |
| 121 |
|
| 122 |
|
| 123 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> IP6.INT Domain</span> |
| 124 |
|
| 125 |
A special domain is defined to look up a record given an address. The |
| 126 |
intent of this domain is to provide a way of mapping an IPv6 address |
| 127 |
to a host name, although it may be used for other purposes as well. |
| 128 |
The domain is rooted at IP6.INT. |
| 129 |
|
| 130 |
An IPv6 address is represented as a name in the IP6.INT domain by a |
| 131 |
sequence of nibbles separated by dots with the suffix ".IP6.INT". The |
| 132 |
sequence of nibbles is encoded in reverse order, i.e. the low-order |
| 133 |
nibble is encoded first, followed by the next low-order nibble and so |
| 134 |
on. Each nibble is represented by a hexadecimal digit. For example, |
| 135 |
the inverse lookup domain name corresponding to the address |
| 136 |
|
| 137 |
4321:0:1:2:3:4:567:89ab |
| 138 |
|
| 139 |
would be |
| 140 |
|
| 141 |
b.a.9.8.7.6.5.0.4.0.0.0.3.0.0.0.2.0.0.0.1.0.0.0.0.0.0.0.1.2.3.4.IP6.INT. |
| 142 |
|
| 143 |
|
| 144 |
|
| 145 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MODIFICATIONS TO EXISTING QUERY TYPES</span> |
| 146 |
|
| 147 |
All existing query types that perform type A additional section |
| 148 |
processing, i.e. name server (NS), mail exchange (MX) and mailbox |
| 149 |
(MB) query types, must be redefined to perform both type A and type |
| 150 |
AAAA additional section processing. These new definitions mean that a |
| 151 |
name server must add any relevant IPv4 addresses and any relevant |
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
<span class="grey">Thompson & Huitema Standards Track [Page 3]</span></pre> |
| 156 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 157 |
<span class="grey"><a href="./rfc1886">RFC 1886</a> IPv6 DNS Extensions December 1995</span> |
| 158 |
|
| 159 |
|
| 160 |
IPv6 addresses available locally to the additional section of a |
| 161 |
response when processing any one of the above queries. |
| 162 |
|
| 163 |
|
| 164 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. SECURITY CONSIDERATIONS</span> |
| 165 |
|
| 166 |
Security issues are not discussed in this memo. |
| 167 |
|
| 168 |
|
| 169 |
|
| 170 |
|
| 171 |
|
| 172 |
|
| 173 |
|
| 174 |
|
| 175 |
|
| 176 |
|
| 177 |
|
| 178 |
|
| 179 |
|
| 180 |
|
| 181 |
|
| 182 |
|
| 183 |
|
| 184 |
|
| 185 |
|
| 186 |
|
| 187 |
|
| 188 |
|
| 189 |
|
| 190 |
|
| 191 |
|
| 192 |
|
| 193 |
|
| 194 |
|
| 195 |
|
| 196 |
|
| 197 |
|
| 198 |
|
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
<span class="grey">Thompson & Huitema Standards Track [Page 4]</span></pre> |
| 209 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 210 |
<span class="grey"><a href="./rfc1886">RFC 1886</a> IPv6 DNS Extensions December 1995</span> |
| 211 |
|
| 212 |
|
| 213 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. REFERENCES</span> |
| 214 |
|
| 215 |
|
| 216 |
[<a id="ref-1">1</a>] Mockapetris, P., "Domain Names - Concepts and Facilities", STD |
| 217 |
13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November 1987. |
| 218 |
|
| 219 |
[<a id="ref-2">2</a>] Mockapetris, P., "Domain Names - Implementation and Specifica- |
| 220 |
tion", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences Institute, |
| 221 |
November 1987. |
| 222 |
|
| 223 |
[<a id="ref-3">3</a>] Hinden, R., and S. Deering, Editors, "IP Version 6 Addressing |
| 224 |
Architecture", <a href="./rfc1884">RFC 1884</a>, Ipsilon Networks, Xerox PARC, December |
| 225 |
1995. |
| 226 |
|
| 227 |
|
| 228 |
[<a id="ref-4">4</a>] Gilligan, R., and E. Nordmark, "Transition Mechanisms for IPv6 |
| 229 |
Hosts and Routers", Work in Progress. |
| 230 |
|
| 231 |
|
| 232 |
Authors' Addresses |
| 233 |
|
| 234 |
Susan Thomson |
| 235 |
Bellcore |
| 236 |
MRE 2P343 |
| 237 |
445 South Street |
| 238 |
Morristown, NJ 07960 |
| 239 |
U.S.A. |
| 240 |
|
| 241 |
Phone: +1 201-829-4514 |
| 242 |
EMail: [email protected] |
| 243 |
|
| 244 |
|
| 245 |
Christian Huitema |
| 246 |
INRIA, Sophia-Antipolis |
| 247 |
2004 Route des Lucioles |
| 248 |
BP 109 |
| 249 |
F-06561 Valbonne Cedex |
| 250 |
France |
| 251 |
|
| 252 |
Phone: +33 93 65 77 15 |
| 253 |
EMail: [email protected] |
| 254 |
|
| 255 |
|
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
Thompson & Huitema Standards Track [Page 5] |
| 262 |
</pre> |