| 1 |
<pre>Network Working Group J. Jeong, Ed. |
| 2 |
Request for Comments: 5006 ETRI/University of Minnesota |
| 3 |
Category: Experimental S. Park |
| 4 |
SAMSUNG Electronics |
| 5 |
L. Beloeil |
| 6 |
France Telecom R&D |
| 7 |
S. Madanapalli |
| 8 |
Ordyn Technologies |
| 9 |
September 2007 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">IPv6 Router Advertisement Option for DNS Configuration</span> |
| 13 |
|
| 14 |
Status of This Memo |
| 15 |
|
| 16 |
This memo defines an Experimental Protocol for the Internet |
| 17 |
community. It does not specify an Internet standard of any kind. |
| 18 |
Discussion and suggestions for improvement are requested. |
| 19 |
Distribution of this memo is unlimited. |
| 20 |
|
| 21 |
Abstract |
| 22 |
|
| 23 |
This document specifies a new IPv6 Router Advertisement option to |
| 24 |
allow IPv6 routers to advertise DNS recursive server addresses to |
| 25 |
IPv6 hosts. |
| 26 |
|
| 27 |
Table of Contents |
| 28 |
|
| 29 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 30 |
<a href="#section-1.1">1.1</a>. Applicability Statements . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 31 |
<a href="#section-1.2">1.2</a>. Coexistence of RDNSS Option and DHCP Option . . . . . . . <a href="#page-2">2</a> |
| 32 |
<a href="#section-2">2</a>. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 33 |
<a href="#section-3">3</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 34 |
<a href="#section-4">4</a>. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 35 |
<a href="#section-5">5</a>. Neighbor Discovery Extension . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 36 |
<a href="#section-5.1">5.1</a>. Recursive DNS Server Option . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 37 |
<a href="#section-5.2">5.2</a>. Procedure of DNS Configuration . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 38 |
<a href="#section-5.2.1">5.2.1</a>. Procedure in IPv6 Host . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 39 |
<a href="#section-6">6</a>. Implementation Considerations . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 40 |
<a href="#section-6.1">6.1</a>. DNS Server List Management . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 41 |
6.2. Synchronization between DNS Server List and Resolver |
| 42 |
Repository . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 43 |
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 44 |
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 45 |
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 46 |
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 47 |
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 48 |
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Jeong, et al. Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
Neighbor Discovery (ND) for IP Version 6 and IPv6 Stateless Address |
| 60 |
Autoconfiguration provide ways to configure either fixed or mobile |
| 61 |
nodes with one or more IPv6 addresses, default routers and some other |
| 62 |
parameters [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>][3]. To support the access to additional services in |
| 63 |
the Internet that are identified by a DNS name, such as a web server, |
| 64 |
the configuration of at least one recursive DNS server is also needed |
| 65 |
for DNS name resolution. |
| 66 |
|
| 67 |
It is infeasible for nomadic hosts, such as laptops, to be configured |
| 68 |
manually with a DNS resolver each time they connect to a different |
| 69 |
wireless LAN (WLAN) such as IEEE 802.11 a/b/g [<a href="#ref-12" title=""Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications"">12</a>]-[<a href="#ref-15" title=""Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Further Higher Data Rate Extension in the 2.4 GHz Band"">15</a>]. Normally, |
| 70 |
DHCP [<a href="#ref-6" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">6</a>]-[<a href="#ref-8" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">8</a>] is used to locate such resolvers. This document |
| 71 |
provides an alternate, experimental mechanism which uses a new IPv6 |
| 72 |
Router Advertisement (RA) option to allow IPv6 routers to advertise |
| 73 |
DNS recursive server addresses to IPv6 hosts. |
| 74 |
|
| 75 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Applicability Statements</span> |
| 76 |
|
| 77 |
The only standards-track DNS configuration mechanism in the IETF is |
| 78 |
DHCP, and its support in hosts and routers is necessary for reasons |
| 79 |
of interoperability. |
| 80 |
|
| 81 |
RA-based DNS configuration is a useful, optional alternative in |
| 82 |
networks where an IPv6 host's address is autoconfigured through IPv6 |
| 83 |
stateless address autoconfiguration, and where the delays in |
| 84 |
acquiring server addresses and communicating with the servers are |
| 85 |
critical. RA-based DNS configuration allows the host to acquire the |
| 86 |
nearest server addresses on every link. Furthermore, it learns these |
| 87 |
addresses from the same RA message that provides configuration |
| 88 |
information for the link, thereby avoiding an additional protocol |
| 89 |
run. This can be beneficial in some mobile environments, such as |
| 90 |
with Mobile IPv6 [<a href="#ref-10" title=""Mobility Support in IPv6"">10</a>]. |
| 91 |
|
| 92 |
The advantages and disadvantages of the RA-based approach are |
| 93 |
discussed in [<a href="#ref-9" title=""IPv6 Host Configuration of DNS Server Information Approaches"">9</a>] along with other approaches, such as the DHCP and |
| 94 |
well-known anycast addresses approaches. |
| 95 |
|
| 96 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Coexistence of RDNSS Option and DHCP Option</span> |
| 97 |
|
| 98 |
The RDNSS (Recursive DNS Server) option and DHCP option can be used |
| 99 |
together [<a href="#ref-9" title=""IPv6 Host Configuration of DNS Server Information Approaches"">9</a>]. To order the RA and DHCP approaches, the O (Other |
| 100 |
stateful configuration) flag can be used in the RA message [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>]. If |
| 101 |
no RDNSS option is included in the RA messages, an IPv6 host may |
| 102 |
perform DNS configuration through DHCPv6 [<a href="#ref-6" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">6</a>]-[<a href="#ref-8" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">8</a>] regardless of |
| 103 |
whether the O flag is set or not. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Jeong, et al. Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definitions</span> |
| 114 |
|
| 115 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 116 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 117 |
document are to be interpreted as described in [<a href="#ref-1" title=""Key words for use in RFCs to Indicate Requirement Levels"">1</a>]. |
| 118 |
|
| 119 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span> |
| 120 |
|
| 121 |
This document uses the terminology described in [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>] and [<a href="#ref-3" title=""IPv6 Stateless Address Autoconfiguration"">3</a>]. In |
| 122 |
addition, four new terms are defined below: |
| 123 |
|
| 124 |
o Recursive DNS Server (RDNSS): Server which provides a recursive |
| 125 |
DNS resolution service for translating domain names into IP |
| 126 |
addresses as defined in [<a href="#ref-4" title=""Domain Names - Concepts and Facilities"">4</a>] and [<a href="#ref-5" title=""Domain Names - Implementation and Specification"">5</a>]. |
| 127 |
|
| 128 |
o RDNSS Option: IPv6 RA option to deliver the RDNSS information to |
| 129 |
IPv6 hosts [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>]. |
| 130 |
|
| 131 |
o DNS Server List: A data structure for managing DNS Server |
| 132 |
Information in the IPv6 protocol stack in addition to the Neighbor |
| 133 |
Cache and Destination Cache for Neighbor Discovery [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>]. |
| 134 |
|
| 135 |
o Resolver Repository: Configuration repository with RDNSS addresses |
| 136 |
that a DNS resolver on the host uses for DNS name resolution; for |
| 137 |
example, the Unix resolver file (i.e., /etc/resolv.conf) and |
| 138 |
Windows registry. |
| 139 |
|
| 140 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span> |
| 141 |
|
| 142 |
This document defines a new ND option called RDNSS option that |
| 143 |
contains the addresses of recursive DNS servers. Existing ND |
| 144 |
transport mechanisms (i.e., advertisements and solicitations) are |
| 145 |
used. This works in the same way that hosts learn about routers and |
| 146 |
prefixes. An IPv6 host can configure the IPv6 addresses of one or |
| 147 |
more RDNSSes via RA messages periodically sent by a router or |
| 148 |
solicited by a Router Solicitation (RS). |
| 149 |
|
| 150 |
Through the RDNSS option, along with the prefix information option |
| 151 |
based on the ND protocol ([<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>] and [<a href="#ref-3" title=""IPv6 Stateless Address Autoconfiguration"">3</a>]), an IPv6 host can perform |
| 152 |
network configuration of its IPv6 address and RDNSS simultaneously |
| 153 |
without needing a separate message exchange for the RDNSS |
| 154 |
information. The RA option for RDNSS can be used on any network that |
| 155 |
supports the use of ND. |
| 156 |
|
| 157 |
This approach requires RDNSS information to be configured in the |
| 158 |
routers sending the advertisements. The configuration of RDNSS |
| 159 |
addresses in the routers can be done by manual configuration. The |
| 160 |
automatic configuration or redistribution of RDNSS information is |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Jeong, et al. Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 167 |
|
| 168 |
|
| 169 |
possible by running a DHCPv6 client on the router [<a href="#ref-6" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">6</a>]-[<a href="#ref-8" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">8</a>]. The |
| 170 |
automatic configuration of RDNSS addresses in routers is out of scope |
| 171 |
for this document. |
| 172 |
|
| 173 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Neighbor Discovery Extension</span> |
| 174 |
|
| 175 |
The IPv6 DNS configuration mechanism in this document needs a new ND |
| 176 |
option in Neighbor Discovery: the Recursive DNS Server (RDNSS) |
| 177 |
option. |
| 178 |
|
| 179 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Recursive DNS Server Option</span> |
| 180 |
|
| 181 |
The RDNSS option contains one or more IPv6 addresses of recursive DNS |
| 182 |
servers. All of the addresses share the same lifetime value. If it |
| 183 |
is desirable to have different lifetime values, multiple RDNSS |
| 184 |
options can be used. Figure 1 shows the format of the RDNSS option. |
| 185 |
|
| 186 |
0 1 2 3 |
| 187 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 188 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 189 |
| Type | Length | Reserved | |
| 190 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 191 |
| Lifetime | |
| 192 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 193 |
| | |
| 194 |
: Addresses of IPv6 Recursive DNS Servers : |
| 195 |
| | |
| 196 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 197 |
|
| 198 |
Figure 1: Recursive DNS Server (RDNSS) Option Format |
| 199 |
|
| 200 |
Fields: |
| 201 |
|
| 202 |
Type 8-bit identifier of the RDNSS option type as assigned |
| 203 |
by the IANA: 25 |
| 204 |
|
| 205 |
Length 8-bit unsigned integer. The length of the option |
| 206 |
(including the Type and Length fields) is in units of |
| 207 |
8 octets. The minimum value is 3 if one IPv6 address |
| 208 |
is contained in the option. Every additional RDNSS |
| 209 |
address increases the length by 2. The Length field |
| 210 |
is used by the receiver to determine the number of |
| 211 |
IPv6 addresses in the option. |
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Jeong, et al. Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 223 |
|
| 224 |
|
| 225 |
Lifetime 32-bit unsigned integer. The maximum time, in |
| 226 |
seconds (relative to the time the packet is sent), |
| 227 |
over which this RDNSS address MAY be used for name |
| 228 |
resolution. Hosts MAY send a Router Solicitation to |
| 229 |
ensure the RDNSS information is fresh before the |
| 230 |
interval expires. In order to provide fixed hosts |
| 231 |
with stable DNS service and allow mobile hosts to |
| 232 |
prefer local RDNSSes to remote RDNSSes, the value of |
| 233 |
Lifetime should be at least as long as the Maximum RA |
| 234 |
Interval (MaxRtrAdvInterval) in <a href="./rfc4861">RFC 4861</a>, and be at |
| 235 |
most as long as two times MaxRtrAdvInterval; Lifetime |
| 236 |
SHOULD be bounded as follows: MaxRtrAdvInterval <= |
| 237 |
Lifetime <= 2*MaxRtrAdvInterval. A value of all one |
| 238 |
bits (0xffffffff) represents infinity. A value of |
| 239 |
zero means that the RDNSS address MUST no longer be |
| 240 |
used. |
| 241 |
|
| 242 |
Addresses of IPv6 Recursive DNS Servers |
| 243 |
One or more 128-bit IPv6 addresses of the recursive |
| 244 |
DNS servers. The number of addresses is determined |
| 245 |
by the Length field. That is, the number of |
| 246 |
addresses is equal to (Length - 1) / 2. |
| 247 |
|
| 248 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Procedure of DNS Configuration</span> |
| 249 |
|
| 250 |
The procedure of DNS configuration through the RDNSS option is the |
| 251 |
same as with any other ND option [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>]. |
| 252 |
|
| 253 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Procedure in IPv6 Host</span> |
| 254 |
|
| 255 |
When an IPv6 host receives an RDNSS option through RA, it checks |
| 256 |
whether the option is valid. |
| 257 |
|
| 258 |
o If the RDNSS option is valid, the host SHOULD copy the option's |
| 259 |
value into the DNS Server List and the Resolver Repository as long |
| 260 |
as the value of the Length field is greater than or equal to the |
| 261 |
minimum value (3). The host MAY ignore additional RDNSS addresses |
| 262 |
within an RDNSS option and/or additional RDNSS options within an |
| 263 |
RA when it has gathered a sufficient number of RDNSS addresses. |
| 264 |
|
| 265 |
o If the RDNSS option is invalid (e.g., the Length field has a value |
| 266 |
less than 3), the host SHOULD discard the option. |
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Jeong, et al. Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Implementation Considerations</span> |
| 282 |
|
| 283 |
Note: This non-normative section gives some hints for implementing |
| 284 |
the processing of the RDNSS option in an IPv6 host. |
| 285 |
|
| 286 |
For the configuration and management of RDNSS information, the |
| 287 |
advertised RDNSS addresses can be stored and managed in both the DNS |
| 288 |
Server List and the Resolver Repository. |
| 289 |
|
| 290 |
In environments where the RDNSS information is stored in user space |
| 291 |
and ND runs in the kernel, it is necessary to synchronize the DNS |
| 292 |
Server List of RDNSS addresses in kernel space and the Resolver |
| 293 |
Repository in user space. For the synchronization, an implementation |
| 294 |
where ND works in the kernel should provide a write operation for |
| 295 |
updating RDNSS information from the kernel to the Resolver |
| 296 |
Repository. One simple approach is to have a daemon (or a program |
| 297 |
that is called at defined intervals) that keeps monitoring the |
| 298 |
lifetime of RDNSS addresses all the time. Whenever there is an |
| 299 |
expired entry in the DNS Server List, the daemon can delete the |
| 300 |
corresponding entry from the Resolver Repository. |
| 301 |
|
| 302 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. DNS Server List Management</span> |
| 303 |
|
| 304 |
The kernel or user-space process (depending on where RAs are |
| 305 |
processed) should maintain a data structure called a DNS Server List |
| 306 |
which keeps the list of RDNSS addresses. Each entry in the DNS |
| 307 |
Server List consists of an RDNSS address and Expiration-time as |
| 308 |
follows: |
| 309 |
|
| 310 |
o RDNSS address: IPv6 address of the Recursive DNS Server, which is |
| 311 |
available for recursive DNS resolution service in the network |
| 312 |
advertising the RDNSS option; such a network is called site in |
| 313 |
this document. |
| 314 |
|
| 315 |
o Expiration-time: The time when this entry becomes invalid. |
| 316 |
Expiration-time is set to the value of the Lifetime field of the |
| 317 |
RDNSS option plus the current system time. Whenever a new RDNSS |
| 318 |
option with the same address is received, this field is updated to |
| 319 |
have a new expiration time. When Expiration-time becomes less |
| 320 |
than the current system time, this entry is regarded as expired. |
| 321 |
|
| 322 |
Note: An RDNSS address MUST be used only as long as both the RA |
| 323 |
router lifetime and the RDNSS option lifetime have not expired. |
| 324 |
The reason is that the RDNSS may not be currently reachable or may |
| 325 |
not provide service to the host's current address (e.g., due to |
| 326 |
network ingress filtering [<a href="#ref-16" title=""Preventing Use of Recursive Nameservers in Reflector Attacks"">16</a>][17]). |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Jeong, et al. Experimental [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Synchronization between DNS Server List and Resolver Repository</span> |
| 338 |
|
| 339 |
When an IPv6 host receives the information of multiple RDNSS |
| 340 |
addresses within a site through an RA message with RDNSS option(s), |
| 341 |
it stores the RDNSS addresses (in order) into both the DNS Server |
| 342 |
List and the Resolver Repository. The processing of the RDNSS |
| 343 |
option(s) included in an RA message is as follows: |
| 344 |
|
| 345 |
Step (a): Receive and parse the RDNSS option(s). For the RDNSS |
| 346 |
addresses in each RDNSS option, perform Step (b) through Step (d). |
| 347 |
Note that Step (e) is performed whenever an entry expires in the |
| 348 |
DNS Server List. |
| 349 |
|
| 350 |
Step (b): For each RDNSS address, check the following: If the |
| 351 |
RDNSS address already exists in the DNS Server List and the RDNSS |
| 352 |
option's Lifetime field is set to zero, delete the corresponding |
| 353 |
RDNSS entry from both the DNS Server List and the Resolver |
| 354 |
Repository in order to prevent the RDNSS address from being used |
| 355 |
any more for certain reasons in network management, e.g., the |
| 356 |
breakdown of the RDNSS or a renumbering situation. The processing |
| 357 |
of this RDNSS address is finished here. Otherwise, go to Step |
| 358 |
(c). |
| 359 |
|
| 360 |
Step (c): For each RDNSS address, if it already exists in the DNS |
| 361 |
Server List, then just update the value of the Expiration-time |
| 362 |
field according to the procedure specified in the second bullet of |
| 363 |
<a href="#section-6.1">Section 6.1</a>. Otherwise, go to Step (d). |
| 364 |
|
| 365 |
Step (d): For each RDNSS address, if it does not exist in the DNS |
| 366 |
Server List, register the RDNSS address and lifetime with the DNS |
| 367 |
Server List and then insert the RDNSS address in front of the |
| 368 |
Resolver Repository. In the case where the data structure for the |
| 369 |
DNS Server List is full of RDNSS entries, delete from the DNS |
| 370 |
Server List the entry with the shortest expiration time (i.e., the |
| 371 |
entry that will expire first). The corresponding RDNSS address is |
| 372 |
also deleted from the Resolver Repository. In the order in the |
| 373 |
RDNSS option, position the newly added RDNSS addresses in front of |
| 374 |
the Resolver Repository so that the new RDNSS addresses may be |
| 375 |
preferred according to their order in the RDNSS option for the DNS |
| 376 |
name resolution. The processing of these RDNSS addresses is |
| 377 |
finished here. Note that, in the case where there are several |
| 378 |
routers advertising RDNSS option(s) in a subnet, the RDNSSes that |
| 379 |
have been announced recently are preferred. |
| 380 |
|
| 381 |
Step (e): Delete each expired entry from the DNS Server List, and |
| 382 |
delete the RDNSS address corresponding to the entry from the |
| 383 |
Resolver Repository. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Jeong, et al. Experimental [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 394 |
|
| 395 |
The security of the RA option for RDNSS might be worse than ND |
| 396 |
protocol security [<a href="#ref-2" title=""Neighbor Discovery for IP version 6 (IPv6)"">2</a>]. However, any new vulnerability in this RA |
| 397 |
option is not known yet. In this context, it can be claimed that the |
| 398 |
vulnerability of ND is not worse and is a subset of the attacks that |
| 399 |
any node attached to a LAN can do independently of ND. A malicious |
| 400 |
node on a LAN can promiscuously receive packets for any router's MAC |
| 401 |
address and send packets with the router's MAC address as the source |
| 402 |
MAC address in the L2 header. As a result, L2 switches send packets |
| 403 |
addressed to the router to the malicious node. Also, this attack can |
| 404 |
send redirects that tell the hosts to send their traffic somewhere |
| 405 |
else. The malicious node can send unsolicited RA or Neighbor |
| 406 |
Advertisement (NA) replies, answer RS or Neighbor Solicitation (NS) |
| 407 |
requests, etc. Also, an attacker could configure a host to send out |
| 408 |
an RA with a fraudulent RDNSS address, which is presumably an easier |
| 409 |
avenue of attack than becoming a rogue router and having to process |
| 410 |
all traffic for the subnet. It is necessary to disable the RA RDNSS |
| 411 |
option in both routers and clients administratively to avoid this |
| 412 |
problem. All of this can be done independently of implementing ND. |
| 413 |
Therefore, it can be claimed that the RA option for RDNSS has |
| 414 |
vulnerabilities similar to those existing in current mechanisms. |
| 415 |
|
| 416 |
If the Secure Neighbor Discovery (SEND) protocol is used as a |
| 417 |
security mechanism for ND, all the ND options including the RDNSS |
| 418 |
option are automatically included in the signatures [<a href="#ref-11" title=""SEcure Neighbor Discovery (SEND)"">11</a>], so the |
| 419 |
RDNSS transport is integrity-protected. However, since any valid |
| 420 |
SEND node can still insert RDNSS options, SEND cannot verify who is |
| 421 |
or is not authorized to send the options. |
| 422 |
|
| 423 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span> |
| 424 |
|
| 425 |
The IANA has assigned a new IPv6 Neighbor Discovery Option type for |
| 426 |
the RDNSS option defined in this document. |
| 427 |
|
| 428 |
Option Name Type |
| 429 |
RDNSS option 25 |
| 430 |
|
| 431 |
The IANA registry for these options is: |
| 432 |
|
| 433 |
<a href="http://www.iana.org/assignments/icmpv6-parameters">http://www.iana.org/assignments/icmpv6-parameters</a> |
| 434 |
|
| 435 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span> |
| 436 |
|
| 437 |
This document has greatly benefited from inputs by Robert Hinden, |
| 438 |
Pekka Savola, Iljitsch van Beijnum, Brian Haberman and Tim Chown. |
| 439 |
The authors appreciate their contributions. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Jeong, et al. Experimental [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 450 |
|
| 451 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 452 |
|
| 453 |
[<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 454 |
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 455 |
|
| 456 |
[<a id="ref-2">2</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, |
| 457 |
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>, |
| 458 |
September 2007. |
| 459 |
|
| 460 |
[<a id="ref-3">3</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address |
| 461 |
Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007. |
| 462 |
|
| 463 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 464 |
|
| 465 |
[<a id="ref-4">4</a>] Mockapetris, P., "Domain Names - Concepts and Facilities", |
| 466 |
<a href="./rfc1034">RFC 1034</a>, November 1987. |
| 467 |
|
| 468 |
[<a id="ref-5">5</a>] Mockapetris, P., "Domain Names - Implementation and |
| 469 |
Specification", <a href="./rfc1035">RFC 1035</a>, November 1987. |
| 470 |
|
| 471 |
[<a id="ref-6">6</a>] Droms, R., Ed., "Dynamic Host Configuration Protocol for IPv6 |
| 472 |
(DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 473 |
|
| 474 |
[<a id="ref-7">7</a>] Droms, R., "Stateless Dynamic Host Configuration Protocol |
| 475 |
(DHCP) Service for IPv6", <a href="./rfc3736">RFC 3736</a>, April 2004. |
| 476 |
|
| 477 |
[<a id="ref-8">8</a>] Droms, R., Ed., "DNS Configuration options for Dynamic Host |
| 478 |
Configuration Protocol for IPv6 (DHCPv6)", <a href="./rfc3646">RFC 3646</a>, |
| 479 |
December 2003. |
| 480 |
|
| 481 |
[<a id="ref-9">9</a>] Jeong, J., Ed., "IPv6 Host Configuration of DNS Server |
| 482 |
Information Approaches", <a href="./rfc4339">RFC 4339</a>, February 2006. |
| 483 |
|
| 484 |
[<a id="ref-10">10</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in |
| 485 |
IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004. |
| 486 |
|
| 487 |
[<a id="ref-11">11</a>] Arkko, J., Ed., "SEcure Neighbor Discovery (SEND)", <a href="./rfc3971">RFC 3971</a>, |
| 488 |
March 2005. |
| 489 |
|
| 490 |
[<a id="ref-12">12</a>] ANSI/IEEE Std 802.11, "Part 11: Wireless LAN Medium Access |
| 491 |
Control (MAC) and Physical Layer (PHY) Specifications", |
| 492 |
March 1999. |
| 493 |
|
| 494 |
[<a id="ref-13">13</a>] IEEE Std 802.11a, "Part 11: Wireless LAN Medium Access Control |
| 495 |
(MAC) and Physical Layer (PHY) specifications: High-speed |
| 496 |
Physical Layer in the 5 GHZ Band", September 1999. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Jeong, et al. Experimental [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 503 |
|
| 504 |
|
| 505 |
[<a id="ref-14">14</a>] IEEE Std 802.11b, "Part 11: Wireless LAN Medium Access Control |
| 506 |
(MAC) and Physical Layer (PHY) specifications: Higher-Speed |
| 507 |
Physical Layer Extension in the 2.4 GHz Band", September 1999. |
| 508 |
|
| 509 |
[<a id="ref-15">15</a>] IEEE P802.11g/D8.2, "Part 11: Wireless LAN Medium Access |
| 510 |
Control (MAC) and Physical Layer (PHY) specifications: Further |
| 511 |
Higher Data Rate Extension in the 2.4 GHz Band", April 2003. |
| 512 |
|
| 513 |
[<a id="ref-16">16</a>] Damas, J. and F. Neves, "Preventing Use of Recursive |
| 514 |
Nameservers in Reflector Attacks", Work in Progress, July 2007. |
| 515 |
|
| 516 |
[<a id="ref-17">17</a>] Ferguson, P. and D. Senie, "Network Ingress Filtering: |
| 517 |
Defeating Denial of Service Attacks which employ IP Source |
| 518 |
Address Spoofing", <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a>, <a href="./rfc2827">RFC 2827</a>, May 2000. |
| 519 |
|
| 520 |
|
| 521 |
|
| 522 |
|
| 523 |
|
| 524 |
|
| 525 |
|
| 526 |
|
| 527 |
|
| 528 |
|
| 529 |
|
| 530 |
|
| 531 |
|
| 532 |
|
| 533 |
|
| 534 |
|
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Jeong, et al. Experimental [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 559 |
|
| 560 |
|
| 561 |
Authors' Addresses |
| 562 |
|
| 563 |
Jaehoon Paul Jeong (editor) |
| 564 |
ETRI/Department of Computer Science and Engineering |
| 565 |
University of Minnesota |
| 566 |
117 Pleasant Street SE |
| 567 |
Minneapolis, MN 55455 |
| 568 |
USA |
| 569 |
|
| 570 |
Phone: +1 651 587 7774 |
| 571 |
Fax: +1 612 625 0572 |
| 572 |
EMail: [email protected] |
| 573 |
URI: <a href="http://www.cs.umn.edu/~jjeong/">http://www.cs.umn.edu/~jjeong/</a> |
| 574 |
|
| 575 |
|
| 576 |
Soohong Daniel Park |
| 577 |
Mobile Convergence Laboratory |
| 578 |
SAMSUNG Electronics |
| 579 |
416 Maetan-3dong, Yeongtong-Gu |
| 580 |
Suwon, Gyeonggi-Do 443-742 |
| 581 |
Korea |
| 582 |
|
| 583 |
Phone: +82 31 200 4508 |
| 584 |
EMail: [email protected] |
| 585 |
|
| 586 |
|
| 587 |
Luc Beloeil |
| 588 |
France Telecom R&D |
| 589 |
42, rue des coutures |
| 590 |
BP 6243 |
| 591 |
14066 CAEN Cedex 4 |
| 592 |
France |
| 593 |
|
| 594 |
Phone: +33 02 3175 9391 |
| 595 |
EMail: [email protected] |
| 596 |
|
| 597 |
|
| 598 |
Syam Madanapalli |
| 599 |
Ordyn Technologies |
| 600 |
1st Floor, Creator Building, ITPL |
| 601 |
Bangalore - 560066 |
| 602 |
India |
| 603 |
|
| 604 |
Phone: +91-80-40383000 |
| 605 |
EMail: [email protected] |
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Jeong, et al. Experimental [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5006">RFC 5006</a> IPv6 RA Option for DNS Configuration September 2007</span> |
| 615 |
|
| 616 |
|
| 617 |
Full Copyright Statement |
| 618 |
|
| 619 |
Copyright (C) The IETF Trust (2007). |
| 620 |
|
| 621 |
This document is subject to the rights, licenses and restrictions |
| 622 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 623 |
retain all their rights. |
| 624 |
|
| 625 |
This document and the information contained herein are provided on an |
| 626 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 627 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |
| 628 |
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |
| 629 |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 630 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 631 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 632 |
|
| 633 |
Intellectual Property |
| 634 |
|
| 635 |
The IETF takes no position regarding the validity or scope of any |
| 636 |
Intellectual Property Rights or other rights that might be claimed to |
| 637 |
pertain to the implementation or use of the technology described in |
| 638 |
this document or the extent to which any license under such rights |
| 639 |
might or might not be available; nor does it represent that it has |
| 640 |
made any independent effort to identify any such rights. Information |
| 641 |
on the procedures with respect to rights in RFC documents can be |
| 642 |
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>. |
| 643 |
|
| 644 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 645 |
assurances of licenses to be made available, or the result of an |
| 646 |
attempt made to obtain a general license or permission for the use of |
| 647 |
such proprietary rights by implementers or users of this |
| 648 |
specification can be obtained from the IETF on-line IPR repository at |
| 649 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 650 |
|
| 651 |
The IETF invites any interested party to bring to its attention any |
| 652 |
copyrights, patents or patent applications, or other proprietary |
| 653 |
rights that may cover technology that may be required to implement |
| 654 |
this standard. Please address the information to the IETF at |
| 655 |
[email protected]. |
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
Jeong, et al. Experimental [Page 12] |
| 669 |
</pre> |