| 1 |
<pre>Network Working Group S. Thomson |
| 2 |
Request for Comments: 4862 Cisco |
| 3 |
Obsoletes: <a href="./rfc2462">2462</a> T. Narten |
| 4 |
Category: Standards Track IBM |
| 5 |
T. Jinmei |
| 6 |
Toshiba |
| 7 |
September 2007 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">IPv6 Stateless Address Autoconfiguration</span> |
| 11 |
|
| 12 |
Status of This Memo |
| 13 |
|
| 14 |
This document specifies an Internet standards track protocol for the |
| 15 |
Internet community, and requests discussion and suggestions for |
| 16 |
improvements. Please refer to the current edition of the "Internet |
| 17 |
Official Protocol Standards" (STD 1) for the standardization state |
| 18 |
and status of this protocol. Distribution of this memo is unlimited. |
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
This document specifies the steps a host takes in deciding how to |
| 23 |
autoconfigure its interfaces in IP version 6. The autoconfiguration |
| 24 |
process includes generating a link-local address, generating global |
| 25 |
addresses via stateless address autoconfiguration, and the Duplicate |
| 26 |
Address Detection procedure to verify the uniqueness of the addresses |
| 27 |
on a link. |
| 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 |
<span class="grey">Thomson, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 60 |
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 61 |
<a href="#section-2.1">2.1</a>. Requirements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 62 |
<a href="#section-3">3</a>. Design Goals . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 63 |
<a href="#section-4">4</a>. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 64 |
<a href="#section-4.1">4.1</a>. Site Renumbering . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 65 |
<a href="#section-5">5</a>. Protocol Specification . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 66 |
<a href="#section-5.1">5.1</a>. Node Configuration Variables . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 67 |
<a href="#section-5.2">5.2</a>. Autoconfiguration-Related Structures . . . . . . . . . . . <a href="#page-11">11</a> |
| 68 |
<a href="#section-5.3">5.3</a>. Creation of Link-Local Addresses . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 69 |
<a href="#section-5.4">5.4</a>. Duplicate Address Detection . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 70 |
<a href="#section-5.4.1">5.4.1</a>. Message Validation . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 71 |
<a href="#section-5.4.2">5.4.2</a>. Sending Neighbor Solicitation Messages . . . . . . . . <a href="#page-14">14</a> |
| 72 |
<a href="#section-5.4.3">5.4.3</a>. Receiving Neighbor Solicitation Messages . . . . . . . <a href="#page-15">15</a> |
| 73 |
<a href="#section-5.4.4">5.4.4</a>. Receiving Neighbor Advertisement Messages . . . . . . <a href="#page-16">16</a> |
| 74 |
<a href="#section-5.4.5">5.4.5</a>. When Duplicate Address Detection Fails . . . . . . . . <a href="#page-17">17</a> |
| 75 |
<a href="#section-5.5">5.5</a>. Creation of Global Addresses . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 76 |
<a href="#section-5.5.1">5.5.1</a>. Soliciting Router Advertisements . . . . . . . . . . . <a href="#page-18">18</a> |
| 77 |
<a href="#section-5.5.2">5.5.2</a>. Absence of Router Advertisements . . . . . . . . . . . <a href="#page-18">18</a> |
| 78 |
<a href="#section-5.5.3">5.5.3</a>. Router Advertisement Processing . . . . . . . . . . . <a href="#page-18">18</a> |
| 79 |
<a href="#section-5.5.4">5.5.4</a>. Address Lifetime Expiry . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 80 |
<a href="#section-5.6">5.6</a>. Configuration Consistency . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 81 |
<a href="#section-5.7">5.7</a>. Retaining Configured Addresses for Stability . . . . . . . <a href="#page-22">22</a> |
| 82 |
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 83 |
<a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 84 |
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 85 |
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 86 |
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 87 |
<a href="#appendix-A">Appendix A</a>. Loopback Suppression and Duplicate Address |
| 88 |
Detection . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 89 |
<a href="#appendix-B">Appendix B</a>. Changes since <a href="./rfc1971">RFC 1971</a> . . . . . . . . . . . . . . . <a href="#page-26">26</a> |
| 90 |
<a href="#appendix-C">Appendix C</a>. Changes since <a href="./rfc2462">RFC 2462</a> . . . . . . . . . . . . . . . <a href="#page-27">27</a> |
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Thomson, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
This document specifies the steps a host takes in deciding how to |
| 116 |
autoconfigure its interfaces in IP version 6 (IPv6). The |
| 117 |
autoconfiguration process includes generating a link-local address, |
| 118 |
generating global addresses via stateless address autoconfiguration, |
| 119 |
and the Duplicate Address Detection procedure to verify the |
| 120 |
uniqueness of the addresses on a link. |
| 121 |
|
| 122 |
The IPv6 stateless autoconfiguration mechanism requires no manual |
| 123 |
configuration of hosts, minimal (if any) configuration of routers, |
| 124 |
and no additional servers. The stateless mechanism allows a host to |
| 125 |
generate its own addresses using a combination of locally available |
| 126 |
information and information advertised by routers. Routers advertise |
| 127 |
prefixes that identify the subnet(s) associated with a link, while |
| 128 |
hosts generate an "interface identifier" that uniquely identifies an |
| 129 |
interface on a subnet. An address is formed by combining the two. |
| 130 |
In the absence of routers, a host can only generate link-local |
| 131 |
addresses. However, link-local addresses are sufficient for allowing |
| 132 |
communication among nodes attached to the same link. |
| 133 |
|
| 134 |
The stateless approach is used when a site is not particularly |
| 135 |
concerned with the exact addresses hosts use, so long as they are |
| 136 |
unique and properly routable. On the other hand, Dynamic Host |
| 137 |
Configuration Protocol for IPv6 (DHCPv6) [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] is used when a |
| 138 |
site requires tighter control over exact address assignments. Both |
| 139 |
stateless address autoconfiguration and DHCPv6 may be used |
| 140 |
simultaneously. |
| 141 |
|
| 142 |
IPv6 addresses are leased to an interface for a fixed (possibly |
| 143 |
infinite) length of time. Each address has an associated lifetime |
| 144 |
that indicates how long the address is bound to an interface. When a |
| 145 |
lifetime expires, the binding (and address) become invalid and the |
| 146 |
address may be reassigned to another interface elsewhere in the |
| 147 |
Internet. To handle the expiration of address bindings gracefully, |
| 148 |
an address goes through two distinct phases while assigned to an |
| 149 |
interface. Initially, an address is "preferred", meaning that its |
| 150 |
use in arbitrary communication is unrestricted. Later, an address |
| 151 |
becomes "deprecated" in anticipation that its current interface |
| 152 |
binding will become invalid. While an address is in a deprecated |
| 153 |
state, its use is discouraged, but not strictly forbidden. New |
| 154 |
communication (e.g., the opening of a new TCP connection) should use |
| 155 |
a preferred address when possible. A deprecated address should be |
| 156 |
used only by applications that have been using it and would have |
| 157 |
difficulty switching to another address without a service disruption. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Thomson, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 167 |
|
| 168 |
|
| 169 |
To ensure that all configured addresses are likely to be unique on a |
| 170 |
given link, nodes run a "duplicate address detection" algorithm on |
| 171 |
addresses before assigning them to an interface. The Duplicate |
| 172 |
Address Detection algorithm is performed on all addresses, |
| 173 |
independently of whether they are obtained via stateless |
| 174 |
autoconfiguration or DHCPv6. This document defines the Duplicate |
| 175 |
Address Detection algorithm. |
| 176 |
|
| 177 |
The autoconfiguration process specified in this document applies only |
| 178 |
to hosts and not routers. Since host autoconfiguration uses |
| 179 |
information advertised by routers, routers will need to be configured |
| 180 |
by some other means. However, it is expected that routers will |
| 181 |
generate link-local addresses using the mechanism described in this |
| 182 |
document. In addition, routers are expected to successfully pass the |
| 183 |
Duplicate Address Detection procedure described in this document on |
| 184 |
all addresses prior to assigning them to an interface. |
| 185 |
|
| 186 |
<a href="#section-2">Section 2</a> provides definitions for terminology used throughout this |
| 187 |
document. <a href="#section-3">Section 3</a> describes the design goals that lead to the |
| 188 |
current autoconfiguration procedure. <a href="#section-4">Section 4</a> provides an overview |
| 189 |
of the protocol, while <a href="#section-5">Section 5</a> describes the protocol in detail. |
| 190 |
|
| 191 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 192 |
|
| 193 |
IP - Internet Protocol Version 6. The terms IPv4 and IPv6 are used |
| 194 |
only in contexts where necessary to avoid ambiguity. |
| 195 |
|
| 196 |
node - a device that implements IP. |
| 197 |
|
| 198 |
router - a node that forwards IP packets not explicitly addressed to |
| 199 |
itself. |
| 200 |
|
| 201 |
host - any node that is not a router. |
| 202 |
|
| 203 |
upper layer - a protocol layer immediately above IP. Examples are |
| 204 |
transport protocols such as TCP and UDP, control protocols such as |
| 205 |
ICMP, routing protocols such as OSPF, and Internet or lower-layer |
| 206 |
protocols being "tunneled" over (i.e., encapsulated in) IP such as |
| 207 |
IPX, AppleTalk, or IP itself. |
| 208 |
|
| 209 |
link - a communication facility or medium over which nodes can |
| 210 |
communicate at the link layer, i.e., the layer immediately below |
| 211 |
IP. Examples are Ethernets (simple or bridged); PPP links; X.25, |
| 212 |
Frame Relay, or ATM networks; and Internet (or higher) layer |
| 213 |
"tunnels", such as tunnels over IPv4 or IPv6 itself. The protocol |
| 214 |
described in this document will be used on all types of links |
| 215 |
unless specified otherwise in the link-type-specific document |
| 216 |
describing how to operate IP on the link in line with [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Thomson, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 223 |
|
| 224 |
|
| 225 |
interface - a node's attachment to a link. |
| 226 |
|
| 227 |
packet - an IP header plus payload. |
| 228 |
|
| 229 |
address - an IP-layer identifier for an interface or a set of |
| 230 |
interfaces. |
| 231 |
|
| 232 |
unicast address - an identifier for a single interface. A packet |
| 233 |
sent to a unicast address is delivered to the interface identified |
| 234 |
by that address. |
| 235 |
|
| 236 |
multicast address - an identifier for a set of interfaces (typically |
| 237 |
belonging to different nodes). A packet sent to a multicast |
| 238 |
address is delivered to all interfaces identified by that address. |
| 239 |
|
| 240 |
anycast address - an identifier for a set of interfaces (typically |
| 241 |
belonging to different nodes). A packet sent to an anycast |
| 242 |
address is delivered to one of the interfaces identified by that |
| 243 |
address (the "nearest" one, according to the routing protocol's |
| 244 |
measure of distance). See [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. |
| 245 |
|
| 246 |
solicited-node multicast address - a multicast address to which |
| 247 |
Neighbor Solicitation messages are sent. The algorithm for |
| 248 |
computing the address is given in [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. |
| 249 |
|
| 250 |
link-layer address - a link-layer identifier for an interface. |
| 251 |
Examples include IEEE 802 addresses for Ethernet links and E.164 |
| 252 |
addresses for Integrated Services Digital Network (ISDN) links. |
| 253 |
|
| 254 |
link-local address - an address having link-only scope that can be |
| 255 |
used to reach neighboring nodes attached to the same link. All |
| 256 |
interfaces have a link-local unicast address. |
| 257 |
|
| 258 |
global address - an address with unlimited scope. |
| 259 |
|
| 260 |
communication - any packet exchange among nodes that requires that |
| 261 |
the address of each node used in the exchange remain the same for |
| 262 |
the duration of the packet exchange. Examples are a TCP |
| 263 |
connection or a UDP request-response. |
| 264 |
|
| 265 |
tentative address - an address whose uniqueness on a link is being |
| 266 |
verified, prior to its assignment to an interface. A tentative |
| 267 |
address is not considered assigned to an interface in the usual |
| 268 |
sense. An interface discards received packets addressed to a |
| 269 |
tentative address, but accepts Neighbor Discovery packets related |
| 270 |
to Duplicate Address Detection for the tentative address. |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Thomson, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 279 |
|
| 280 |
|
| 281 |
preferred address - an address assigned to an interface whose use by |
| 282 |
upper-layer protocols is unrestricted. Preferred addresses may be |
| 283 |
used as the source (or destination) address of packets sent from |
| 284 |
(or to) the interface. |
| 285 |
|
| 286 |
deprecated address - An address assigned to an interface whose use |
| 287 |
is discouraged, but not forbidden. A deprecated address should no |
| 288 |
longer be used as a source address in new communications, but |
| 289 |
packets sent from or to deprecated addresses are delivered as |
| 290 |
expected. A deprecated address may continue to be used as a |
| 291 |
source address in communications where switching to a preferred |
| 292 |
address causes hardship to a specific upper-layer activity (e.g., |
| 293 |
an existing TCP connection). |
| 294 |
|
| 295 |
valid address - a preferred or deprecated address. A valid address |
| 296 |
may appear as the source or destination address of a packet, and |
| 297 |
the Internet routing system is expected to deliver packets sent to |
| 298 |
a valid address to their intended recipients. |
| 299 |
|
| 300 |
invalid address - an address that is not assigned to any interface. |
| 301 |
A valid address becomes invalid when its valid lifetime expires. |
| 302 |
Invalid addresses should not appear as the destination or source |
| 303 |
address of a packet. In the former case, the Internet routing |
| 304 |
system will be unable to deliver the packet; in the latter case, |
| 305 |
the recipient of the packet will be unable to respond to it. |
| 306 |
|
| 307 |
preferred lifetime - the length of time that a valid address is |
| 308 |
preferred (i.e., the time until deprecation). When the preferred |
| 309 |
lifetime expires, the address becomes deprecated. |
| 310 |
|
| 311 |
valid lifetime - the length of time an address remains in the valid |
| 312 |
state (i.e., the time until invalidation). The valid lifetime |
| 313 |
must be greater than or equal to the preferred lifetime. When the |
| 314 |
valid lifetime expires, the address becomes invalid. |
| 315 |
|
| 316 |
interface identifier - a link-dependent identifier for an interface |
| 317 |
that is (at least) unique per link [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. Stateless address |
| 318 |
autoconfiguration combines an interface identifier with a prefix |
| 319 |
to form an address. From address autoconfiguration's perspective, |
| 320 |
an interface identifier is a bit string of known length. The |
| 321 |
exact length of an interface identifier and the way it is created |
| 322 |
is defined in a separate link-type specific document that covers |
| 323 |
issues related to the transmission of IP over a particular link |
| 324 |
type (e.g., [<a href="./rfc2464" title=""Transmission of IPv6 Packets over Ethernet Networks"">RFC2464</a>]). Note that the address architecture |
| 325 |
[<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] also defines the length of the interface identifiers for |
| 326 |
some set of addresses, but the two sets of definitions must be |
| 327 |
consistent. In many cases, the identifier will be derived from |
| 328 |
the interface's link-layer address. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Thomson, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirements</span> |
| 338 |
|
| 339 |
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, |
| 340 |
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this |
| 341 |
document, are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 342 |
|
| 343 |
Note that this document intentionally limits the use of the keywords |
| 344 |
to the protocol specification (<a href="#section-5">Section 5</a>). |
| 345 |
|
| 346 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Design Goals</span> |
| 347 |
|
| 348 |
Stateless autoconfiguration is designed with the following goals in |
| 349 |
mind: |
| 350 |
|
| 351 |
o Manual configuration of individual machines before connecting them |
| 352 |
to the network should not be required. Consequently, a mechanism |
| 353 |
is needed that allows a host to obtain or create unique addresses |
| 354 |
for each of its interfaces. Address autoconfiguration assumes |
| 355 |
that each interface can provide a unique identifier for that |
| 356 |
interface (i.e., an "interface identifier"). In the simplest |
| 357 |
case, an interface identifier consists of the interface's link- |
| 358 |
layer address. An interface identifier can be combined with a |
| 359 |
prefix to form an address. |
| 360 |
|
| 361 |
o Small sites consisting of a set of machines attached to a single |
| 362 |
link should not require the presence of a DHCPv6 server or router |
| 363 |
as a prerequisite for communicating. Plug-and-play communication |
| 364 |
is achieved through the use of link-local addresses. Link-local |
| 365 |
addresses have a well-known prefix that identifies the (single) |
| 366 |
shared link to which a set of nodes attach. A host forms a link- |
| 367 |
local address by appending an interface identifier to the link- |
| 368 |
local prefix. |
| 369 |
|
| 370 |
o A large site with multiple networks and routers should not require |
| 371 |
the presence of a DHCPv6 server for address configuration. In |
| 372 |
order to generate global addresses, hosts must determine the |
| 373 |
prefixes that identify the subnets to which they attach. Routers |
| 374 |
generate periodic Router Advertisements that include options |
| 375 |
listing the set of active prefixes on a link. |
| 376 |
|
| 377 |
o Address configuration should facilitate the graceful renumbering |
| 378 |
of a site's machines. For example, a site may wish to renumber |
| 379 |
all of its nodes when it switches to a new network service |
| 380 |
provider. Renumbering is achieved through the leasing of |
| 381 |
addresses to interfaces and the assignment of multiple addresses |
| 382 |
to the same interface. Lease lifetimes provide the mechanism |
| 383 |
through which a site phases out old prefixes. The assignment of |
| 384 |
multiple addresses to an interface provides for a transition |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Thomson, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 391 |
|
| 392 |
|
| 393 |
period during which both a new address and the one being phased |
| 394 |
out work simultaneously. |
| 395 |
|
| 396 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Overview</span> |
| 397 |
|
| 398 |
This section provides an overview of the typical steps that take |
| 399 |
place when an interface autoconfigures itself. Autoconfiguration is |
| 400 |
performed only on multicast-capable links and begins when a |
| 401 |
multicast-capable interface is enabled, e.g., during system startup. |
| 402 |
Nodes (both hosts and routers) begin the autoconfiguration process by |
| 403 |
generating a link-local address for the interface. A link-local |
| 404 |
address is formed by appending an identifier of the interface to the |
| 405 |
well-known link-local prefix [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. |
| 406 |
|
| 407 |
Before the link-local address can be assigned to an interface and |
| 408 |
used, however, a node must attempt to verify that this "tentative" |
| 409 |
address is not already in use by another node on the link. |
| 410 |
Specifically, it sends a Neighbor Solicitation message containing the |
| 411 |
tentative address as the target. If another node is already using |
| 412 |
that address, it will return a Neighbor Advertisement saying so. If |
| 413 |
another node is also attempting to use the same address, it will send |
| 414 |
a Neighbor Solicitation for the target as well. The exact number of |
| 415 |
times the Neighbor Solicitation is (re)transmitted and the delay time |
| 416 |
between consecutive solicitations is link-specific and may be set by |
| 417 |
system management. |
| 418 |
|
| 419 |
If a node determines that its tentative link-local address is not |
| 420 |
unique, autoconfiguration stops and manual configuration of the |
| 421 |
interface is required. To simplify recovery in this case, it should |
| 422 |
be possible for an administrator to supply an alternate interface |
| 423 |
identifier that overrides the default identifier in such a way that |
| 424 |
the autoconfiguration mechanism can then be applied using the new |
| 425 |
(presumably unique) interface identifier. Alternatively, link-local |
| 426 |
and other addresses will need to be configured manually. |
| 427 |
|
| 428 |
Once a node ascertains that its tentative link-local address is |
| 429 |
unique, it assigns the address to the interface. At this point, the |
| 430 |
node has IP-level connectivity with neighboring nodes. The remaining |
| 431 |
autoconfiguration steps are performed only by hosts; the |
| 432 |
(auto)configuration of routers is beyond the scope of this document. |
| 433 |
|
| 434 |
The next phase of autoconfiguration involves obtaining a Router |
| 435 |
Advertisement or determining that no routers are present. If routers |
| 436 |
are present, they will send Router Advertisements that specify what |
| 437 |
sort of autoconfiguration a host can do. Note that the DHCPv6 |
| 438 |
service for address configuration may still be available even if no |
| 439 |
routers are present. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Thomson, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 447 |
|
| 448 |
|
| 449 |
Routers send Router Advertisements periodically, but the delay |
| 450 |
between successive advertisements will generally be longer than a |
| 451 |
host performing autoconfiguration will want to wait [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. To |
| 452 |
obtain an advertisement quickly, a host sends one or more Router |
| 453 |
Solicitations to the all-routers multicast group. |
| 454 |
|
| 455 |
Router Advertisements also contain zero or more Prefix Information |
| 456 |
options that contain information used by stateless address |
| 457 |
autoconfiguration to generate global addresses. It should be noted |
| 458 |
that a host may use both stateless address autoconfiguration and |
| 459 |
DHCPv6 simultaneously. One Prefix Information option field, the |
| 460 |
"autonomous address-configuration flag", indicates whether or not the |
| 461 |
option even applies to stateless autoconfiguration. If it does, |
| 462 |
additional option fields contain a subnet prefix, together with |
| 463 |
lifetime values, indicating how long addresses created from the |
| 464 |
prefix remain preferred and valid. |
| 465 |
|
| 466 |
Because routers generate Router Advertisements periodically, hosts |
| 467 |
will continually receive new advertisements. Hosts process the |
| 468 |
information contained in each advertisement as described above, |
| 469 |
adding to and refreshing information received in previous |
| 470 |
advertisements. |
| 471 |
|
| 472 |
By default, all addresses should be tested for uniqueness prior to |
| 473 |
their assignment to an interface for safety. The test should |
| 474 |
individually be performed on all addresses obtained manually, via |
| 475 |
stateless address autoconfiguration, or via DHCPv6. To accommodate |
| 476 |
sites that believe the overhead of performing Duplicate Address |
| 477 |
Detection outweighs its benefits, the use of Duplicate Address |
| 478 |
Detection can be disabled through the administrative setting of a |
| 479 |
per-interface configuration flag. |
| 480 |
|
| 481 |
To speed the autoconfiguration process, a host may generate its link- |
| 482 |
local address (and verify its uniqueness) in parallel with waiting |
| 483 |
for a Router Advertisement. Because a router may delay responding to |
| 484 |
a Router Solicitation for a few seconds, the total time needed to |
| 485 |
complete autoconfiguration can be significantly longer if the two |
| 486 |
steps are done serially. |
| 487 |
|
| 488 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Site Renumbering</span> |
| 489 |
|
| 490 |
Address leasing facilitates site renumbering by providing a mechanism |
| 491 |
to time-out addresses assigned to interfaces in hosts. At present, |
| 492 |
upper-layer protocols such as TCP provide no support for changing |
| 493 |
end-point addresses while a connection is open. If an end-point |
| 494 |
address becomes invalid, existing connections break and all |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Thomson, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 503 |
|
| 504 |
|
| 505 |
communication to the invalid address fails. Even when applications |
| 506 |
use UDP as a transport protocol, addresses must generally remain the |
| 507 |
same during a packet exchange. |
| 508 |
|
| 509 |
Dividing valid addresses into preferred and deprecated categories |
| 510 |
provides a way of indicating to upper layers that a valid address may |
| 511 |
become invalid shortly and that future communication using the |
| 512 |
address will fail, should the address's valid lifetime expire before |
| 513 |
communication ends. To avoid this scenario, higher layers should use |
| 514 |
a preferred address (assuming one of sufficient scope exists) to |
| 515 |
increase the likelihood that an address will remain valid for the |
| 516 |
duration of the communication. It is up to system administrators to |
| 517 |
set appropriate prefix lifetimes in order to minimize the impact of |
| 518 |
failed communication when renumbering takes place. The deprecation |
| 519 |
period should be long enough that most, if not all, communications |
| 520 |
are using the new address at the time an address becomes invalid. |
| 521 |
|
| 522 |
The IP layer is expected to provide a means for upper layers |
| 523 |
(including applications) to select the most appropriate source |
| 524 |
address given a particular destination and possibly other |
| 525 |
constraints. An application may choose to select the source address |
| 526 |
itself before starting a new communication or may leave the address |
| 527 |
unspecified, in which case, the upper networking layers will use the |
| 528 |
mechanism provided by the IP layer to choose a suitable address on |
| 529 |
the application's behalf. |
| 530 |
|
| 531 |
Detailed address selection rules are beyond the scope of this |
| 532 |
document and are described in [<a href="./rfc3484" title=""Default Address Selection for Internet Protocol version 6 (IPv6)"">RFC3484</a>]. |
| 533 |
|
| 534 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Protocol Specification</span> |
| 535 |
|
| 536 |
Autoconfiguration is performed on a per-interface basis on multicast- |
| 537 |
capable interfaces. For multihomed hosts, autoconfiguration is |
| 538 |
performed independently on each interface. Autoconfiguration applies |
| 539 |
primarily to hosts, with two exceptions. Routers are expected to |
| 540 |
generate a link-local address using the procedure outlined below. In |
| 541 |
addition, routers perform Duplicate Address Detection on all |
| 542 |
addresses prior to assigning them to an interface. |
| 543 |
|
| 544 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Node Configuration Variables</span> |
| 545 |
|
| 546 |
A node MUST allow the following autoconfiguration-related variable to |
| 547 |
be configured by system management for each multicast-capable |
| 548 |
interface: |
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Thomson, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 559 |
|
| 560 |
|
| 561 |
DupAddrDetectTransmits The number of consecutive Neighbor |
| 562 |
Solicitation messages sent while performing Duplicate Address |
| 563 |
Detection on a tentative address. A value of zero indicates that |
| 564 |
Duplicate Address Detection is not performed on tentative |
| 565 |
addresses. A value of one indicates a single transmission with no |
| 566 |
follow-up retransmissions. |
| 567 |
|
| 568 |
Default: 1, but may be overridden by a link-type specific value in |
| 569 |
the document that covers issues related to the transmission of IP |
| 570 |
over a particular link type (e.g., [<a href="./rfc2464" title=""Transmission of IPv6 Packets over Ethernet Networks"">RFC2464</a>]). |
| 571 |
|
| 572 |
Autoconfiguration also assumes the presence of the variable |
| 573 |
RetransTimer as defined in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. For autoconfiguration |
| 574 |
purposes, RetransTimer specifies the delay between consecutive |
| 575 |
Neighbor Solicitation transmissions performed during Duplicate |
| 576 |
Address Detection (if DupAddrDetectTransmits is greater than 1), |
| 577 |
as well as the time a node waits after sending the last Neighbor |
| 578 |
Solicitation before ending the Duplicate Address Detection |
| 579 |
process. |
| 580 |
|
| 581 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Autoconfiguration-Related Structures</span> |
| 582 |
|
| 583 |
Beyond the formation of a link-local address and use of Duplicate |
| 584 |
Address Detection, how routers (auto)configure their interfaces is |
| 585 |
beyond the scope of this document. |
| 586 |
|
| 587 |
A host maintains a list of addresses together with their |
| 588 |
corresponding lifetimes. The address list contains both |
| 589 |
autoconfigured addresses and those configured manually. |
| 590 |
|
| 591 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Creation of Link-Local Addresses</span> |
| 592 |
|
| 593 |
A node forms a link-local address whenever an interface becomes |
| 594 |
enabled. An interface may become enabled after any of the following |
| 595 |
events: |
| 596 |
|
| 597 |
- The interface is initialized at system startup time. |
| 598 |
|
| 599 |
- The interface is reinitialized after a temporary interface failure |
| 600 |
or after being temporarily disabled by system management. |
| 601 |
|
| 602 |
- The interface attaches to a link for the first time. This |
| 603 |
includes the case where the attached link is dynamically changed |
| 604 |
due to a change of the access point of wireless networks. |
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Thomson, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 615 |
|
| 616 |
|
| 617 |
- The interface becomes enabled by system management after having |
| 618 |
been administratively disabled. |
| 619 |
|
| 620 |
A link-local address is formed by combining the well-known link-local |
| 621 |
prefix FE80::0 [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] (of appropriate length) with an interface |
| 622 |
identifier as follows: |
| 623 |
|
| 624 |
1. The left-most 'prefix length' bits of the address are those of |
| 625 |
the link-local prefix. |
| 626 |
|
| 627 |
2. The bits in the address to the right of the link-local prefix are |
| 628 |
set to all zeroes. |
| 629 |
|
| 630 |
3. If the length of the interface identifier is N bits, the right- |
| 631 |
most N bits of the address are replaced by the interface |
| 632 |
identifier. |
| 633 |
|
| 634 |
If the sum of the link-local prefix length and N is larger than 128, |
| 635 |
autoconfiguration fails and manual configuration is required. The |
| 636 |
length of the interface identifier is defined in a separate link- |
| 637 |
type-specific document, which should also be consistent with the |
| 638 |
address architecture [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] (see <a href="#section-2">Section 2</a>). These documents will |
| 639 |
carefully define the length so that link-local addresses can be |
| 640 |
autoconfigured on the link. |
| 641 |
|
| 642 |
A link-local address has an infinite preferred and valid lifetime; it |
| 643 |
is never timed out. |
| 644 |
|
| 645 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Duplicate Address Detection</span> |
| 646 |
|
| 647 |
Duplicate Address Detection MUST be performed on all unicast |
| 648 |
addresses prior to assigning them to an interface, regardless of |
| 649 |
whether they are obtained through stateless autoconfiguration, |
| 650 |
DHCPv6, or manual configuration, with the following exceptions: |
| 651 |
|
| 652 |
- An interface whose DupAddrDetectTransmits variable is set to zero |
| 653 |
does not perform Duplicate Address Detection. |
| 654 |
|
| 655 |
- Duplicate Address Detection MUST NOT be performed on anycast |
| 656 |
addresses (note that anycast addresses cannot syntactically be |
| 657 |
distinguished from unicast addresses). |
| 658 |
|
| 659 |
- Each individual unicast address SHOULD be tested for uniqueness. |
| 660 |
Note that there are implementations deployed that only perform |
| 661 |
Duplicate Address Detection for the link-local address and skip |
| 662 |
the test for the global address that uses the same interface |
| 663 |
identifier as that of the link-local address. Whereas this |
| 664 |
document does not invalidate such implementations, this kind of |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Thomson, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 671 |
|
| 672 |
|
| 673 |
"optimization" is NOT RECOMMENDED, and new implementations MUST |
| 674 |
NOT do that optimization. This optimization came from the |
| 675 |
assumption that all of an interface's addresses are generated from |
| 676 |
the same identifier. However, the assumption does actually not |
| 677 |
stand; new types of addresses have been introduced where the |
| 678 |
interface identifiers are not necessarily the same for all unicast |
| 679 |
addresses on a single interface [<a href="./rfc4941" title=""Privacy Extensions for Stateless Address Autoconfiguration in IPv6"">RFC4941</a>] [<a href="./rfc3972" title=""Cryptographically Generated Addresses (CGA)"">RFC3972</a>]. Requiring |
| 680 |
that Duplicate Address Detection be performed for all unicast |
| 681 |
addresses will make the algorithm robust for the current and |
| 682 |
future special interface identifiers. |
| 683 |
|
| 684 |
The procedure for detecting duplicate addresses uses Neighbor |
| 685 |
Solicitation and Advertisement messages as described below. If a |
| 686 |
duplicate address is discovered during the procedure, the address |
| 687 |
cannot be assigned to the interface. If the address is derived from |
| 688 |
an interface identifier, a new identifier will need to be assigned to |
| 689 |
the interface, or all IP addresses for the interface will need to be |
| 690 |
manually configured. Note that the method for detecting duplicates |
| 691 |
is not completely reliable, and it is possible that duplicate |
| 692 |
addresses will still exist (e.g., if the link was partitioned while |
| 693 |
Duplicate Address Detection was performed). |
| 694 |
|
| 695 |
An address on which the Duplicate Address Detection procedure is |
| 696 |
applied is said to be tentative until the procedure has completed |
| 697 |
successfully. A tentative address is not considered "assigned to an |
| 698 |
interface" in the traditional sense. That is, the interface must |
| 699 |
accept Neighbor Solicitation and Advertisement messages containing |
| 700 |
the tentative address in the Target Address field, but processes such |
| 701 |
packets differently from those whose Target Address matches an |
| 702 |
address assigned to the interface. Other packets addressed to the |
| 703 |
tentative address should be silently discarded. Note that the "other |
| 704 |
packets" include Neighbor Solicitation and Advertisement messages |
| 705 |
that have the tentative (i.e., unicast) address as the IP destination |
| 706 |
address and contain the tentative address in the Target Address |
| 707 |
field. Such a case should not happen in normal operation, though, |
| 708 |
since these messages are multicasted in the Duplicate Address |
| 709 |
Detection procedure. |
| 710 |
|
| 711 |
It should also be noted that Duplicate Address Detection must be |
| 712 |
performed prior to assigning an address to an interface in order to |
| 713 |
prevent multiple nodes from using the same address simultaneously. |
| 714 |
If a node begins using an address in parallel with Duplicate Address |
| 715 |
Detection, and another node is already using the address, the node |
| 716 |
performing Duplicate Address Detection will erroneously process |
| 717 |
traffic intended for the other node, resulting in such possible |
| 718 |
negative consequences as the resetting of open TCP connections. |
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Thomson, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 727 |
|
| 728 |
|
| 729 |
The following subsections describe specific tests a node performs to |
| 730 |
verify an address's uniqueness. An address is considered unique if |
| 731 |
none of the tests indicate the presence of a duplicate address within |
| 732 |
RetransTimer milliseconds after having sent DupAddrDetectTransmits |
| 733 |
Neighbor Solicitations. Once an address is determined to be unique, |
| 734 |
it may be assigned to an interface. |
| 735 |
|
| 736 |
<span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. Message Validation</span> |
| 737 |
|
| 738 |
A node MUST silently discard any Neighbor Solicitation or |
| 739 |
Advertisement message that does not pass the validity checks |
| 740 |
specified in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. A Neighbor Solicitation or Advertisement |
| 741 |
message that passes these validity checks is called a valid |
| 742 |
solicitation or valid advertisement, respectively. |
| 743 |
|
| 744 |
<span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. Sending Neighbor Solicitation Messages</span> |
| 745 |
|
| 746 |
Before sending a Neighbor Solicitation, an interface MUST join the |
| 747 |
all-nodes multicast address and the solicited-node multicast address |
| 748 |
of the tentative address. The former ensures that the node receives |
| 749 |
Neighbor Advertisements from other nodes already using the address; |
| 750 |
the latter ensures that two nodes attempting to use the same address |
| 751 |
simultaneously should detect each other's presence. |
| 752 |
|
| 753 |
To check an address, a node sends DupAddrDetectTransmits Neighbor |
| 754 |
Solicitations, each separated by RetransTimer milliseconds. The |
| 755 |
solicitation's Target Address is set to the address being checked, |
| 756 |
the IP source is set to the unspecified address, and the IP |
| 757 |
destination is set to the solicited-node multicast address of the |
| 758 |
target address. |
| 759 |
|
| 760 |
If the Neighbor Solicitation is going to be the first message sent |
| 761 |
from an interface after interface (re)initialization, the node SHOULD |
| 762 |
delay joining the solicited-node multicast address by a random delay |
| 763 |
between 0 and MAX_RTR_SOLICITATION_DELAY as specified in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 764 |
This serves to alleviate congestion when many nodes start up on the |
| 765 |
link at the same time, such as after a power failure, and may help to |
| 766 |
avoid race conditions when more than one node is trying to solicit |
| 767 |
for the same address at the same time. |
| 768 |
|
| 769 |
Even if the Neighbor Solicitation is not going to be the first |
| 770 |
message sent, the node SHOULD delay joining the solicited-node |
| 771 |
multicast address by a random delay between 0 and |
| 772 |
MAX_RTR_SOLICITATION_DELAY if the address being checked is configured |
| 773 |
by a router advertisement message sent to a multicast address. The |
| 774 |
delay will avoid similar congestion when multiple nodes are going to |
| 775 |
configure addresses by receiving the same single multicast router |
| 776 |
advertisement. |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Thomson, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 783 |
|
| 784 |
|
| 785 |
Note that when a node joins a multicast address, it typically sends a |
| 786 |
Multicast Listener Discovery (MLD) report message [<a href="./rfc2710" title=""Multicast Listener Discovery (MLD) for IPv6"">RFC2710</a>] [<a href="./rfc3810" title=""Multicast Listener Discovery Version 2 (MLDv2) for IPv6"">RFC3810</a>] |
| 787 |
for the multicast address. In the case of Duplicate Address |
| 788 |
Detection, the MLD report message is required in order to inform MLD- |
| 789 |
snooping switches, rather than routers, to forward multicast packets. |
| 790 |
In the above description, the delay for joining the multicast address |
| 791 |
thus means delaying transmission of the corresponding MLD report |
| 792 |
message. Since the MLD specifications do not request a random delay |
| 793 |
to avoid race conditions, just delaying Neighbor Solicitation would |
| 794 |
cause congestion by the MLD report messages. The congestion would |
| 795 |
then prevent the MLD-snooping switches from working correctly and, as |
| 796 |
a result, prevent Duplicate Address Detection from working. The |
| 797 |
requirement to include the delay for the MLD report in this case |
| 798 |
avoids this scenario. [<a href="./rfc3590" title=""Source Address Selection for the Multicast Listener Discovery (MLD) Protocol"">RFC3590</a>] also talks about some interaction |
| 799 |
issues between Duplicate Address Detection and MLD, and specifies |
| 800 |
which source address should be used for the MLD report in this case. |
| 801 |
|
| 802 |
In order to improve the robustness of the Duplicate Address Detection |
| 803 |
algorithm, an interface MUST receive and process datagrams sent to |
| 804 |
the all-nodes multicast address or solicited-node multicast address |
| 805 |
of the tentative address during the delay period. This does not |
| 806 |
necessarily conflict with the requirement that joining the multicast |
| 807 |
group be delayed. In fact, in some cases it is possible for a node |
| 808 |
to start listening to the group during the delay period before MLD |
| 809 |
report transmission. It should be noted, however, that in some link- |
| 810 |
layer environments, particularly with MLD-snooping switches, no |
| 811 |
multicast reception will be available until the MLD report is sent. |
| 812 |
|
| 813 |
<span class="h4"><a class="selflink" id="section-5.4.3" href="#section-5.4.3">5.4.3</a>. Receiving Neighbor Solicitation Messages</span> |
| 814 |
|
| 815 |
On receipt of a valid Neighbor Solicitation message on an interface, |
| 816 |
node behavior depends on whether or not the target address is |
| 817 |
tentative. If the target address is not tentative (i.e., it is |
| 818 |
assigned to the receiving interface), the solicitation is processed |
| 819 |
as described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. If the target address is tentative, and |
| 820 |
the source address is a unicast address, the solicitation's sender is |
| 821 |
performing address resolution on the target; the solicitation should |
| 822 |
be silently ignored. Otherwise, processing takes place as described |
| 823 |
below. In all cases, a node MUST NOT respond to a Neighbor |
| 824 |
Solicitation for a tentative address. |
| 825 |
|
| 826 |
If the source address of the Neighbor Solicitation is the unspecified |
| 827 |
address, the solicitation is from a node performing Duplicate Address |
| 828 |
Detection. If the solicitation is from another node, the tentative |
| 829 |
address is a duplicate and should not be used (by either node). If |
| 830 |
the solicitation is from the node itself (because the node loops back |
| 831 |
multicast packets), the solicitation does not indicate the presence |
| 832 |
of a duplicate address. |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Thomson, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 839 |
|
| 840 |
|
| 841 |
Implementer's Note: many interfaces provide a way for upper layers to |
| 842 |
selectively enable and disable the looping back of multicast packets. |
| 843 |
The details of how such a facility is implemented may prevent |
| 844 |
Duplicate Address Detection from working correctly. See <a href="#appendix-A">Appendix A</a> |
| 845 |
for further discussion. |
| 846 |
|
| 847 |
The following tests identify conditions under which a tentative |
| 848 |
address is not unique: |
| 849 |
|
| 850 |
- If a Neighbor Solicitation for a tentative address is received |
| 851 |
before one is sent, the tentative address is a duplicate. This |
| 852 |
condition occurs when two nodes run Duplicate Address Detection |
| 853 |
simultaneously, but transmit initial solicitations at different |
| 854 |
times (e.g., by selecting different random delay values before |
| 855 |
joining the solicited-node multicast address and transmitting an |
| 856 |
initial solicitation). |
| 857 |
|
| 858 |
- If the actual number of Neighbor Solicitations received exceeds |
| 859 |
the number expected based on the loopback semantics (e.g., the |
| 860 |
interface does not loop back the packet, yet one or more |
| 861 |
solicitations was received), the tentative address is a duplicate. |
| 862 |
This condition occurs when two nodes run Duplicate Address |
| 863 |
Detection simultaneously and transmit solicitations at roughly the |
| 864 |
same time. |
| 865 |
|
| 866 |
<span class="h4"><a class="selflink" id="section-5.4.4" href="#section-5.4.4">5.4.4</a>. Receiving Neighbor Advertisement Messages</span> |
| 867 |
|
| 868 |
On receipt of a valid Neighbor Advertisement message on an interface, |
| 869 |
node behavior depends on whether the target address is tentative or |
| 870 |
matches a unicast or anycast address assigned to the interface: |
| 871 |
|
| 872 |
1. If the target address is tentative, the tentative address is not |
| 873 |
unique. |
| 874 |
|
| 875 |
2. If the target address matches a unicast address assigned to the |
| 876 |
receiving interface, it would possibly indicate that the address |
| 877 |
is a duplicate but it has not been detected by the Duplicate |
| 878 |
Address Detection procedure (recall that Duplicate Address |
| 879 |
Detection is not completely reliable). How to handle such a case |
| 880 |
is beyond the scope of this document. |
| 881 |
|
| 882 |
3. Otherwise, the advertisement is processed as described in |
| 883 |
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Thomson, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h4"><a class="selflink" id="section-5.4.5" href="#section-5.4.5">5.4.5</a>. When Duplicate Address Detection Fails</span> |
| 898 |
|
| 899 |
A tentative address that is determined to be a duplicate as described |
| 900 |
above MUST NOT be assigned to an interface, and the node SHOULD log a |
| 901 |
system management error. |
| 902 |
|
| 903 |
If the address is a link-local address formed from an interface |
| 904 |
identifier based on the hardware address, which is supposed to be |
| 905 |
uniquely assigned (e.g., EUI-64 for an Ethernet interface), IP |
| 906 |
operation on the interface SHOULD be disabled. By disabling IP |
| 907 |
operation, the node will then: |
| 908 |
|
| 909 |
- not send any IP packets from the interface, |
| 910 |
|
| 911 |
- silently drop any IP packets received on the interface, and |
| 912 |
|
| 913 |
- not forward any IP packets to the interface (when acting as a |
| 914 |
router or processing a packet with a Routing header). |
| 915 |
|
| 916 |
In this case, the IP address duplication probably means duplicate |
| 917 |
hardware addresses are in use, and trying to recover from it by |
| 918 |
configuring another IP address will not result in a usable network. |
| 919 |
In fact, it probably makes things worse by creating problems that are |
| 920 |
harder to diagnose than just disabling network operation on the |
| 921 |
interface; the user will see a partially working network where some |
| 922 |
things work, and other things do not. |
| 923 |
|
| 924 |
On the other hand, if the duplicate link-local address is not formed |
| 925 |
from an interface identifier based on the hardware address, which is |
| 926 |
supposed to be uniquely assigned, IP operation on the interface MAY |
| 927 |
be continued. |
| 928 |
|
| 929 |
Note: as specified in <a href="#section-2">Section 2</a>, "IP" means "IPv6" in the above |
| 930 |
description. While the background rationale about hardware address |
| 931 |
is independent of particular network protocols, its effect on other |
| 932 |
protocols is beyond the scope of this document. |
| 933 |
|
| 934 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Creation of Global Addresses</span> |
| 935 |
|
| 936 |
Global addresses are formed by appending an interface identifier to a |
| 937 |
prefix of appropriate length. Prefixes are obtained from Prefix |
| 938 |
Information options contained in Router Advertisements. Creation of |
| 939 |
global addresses as described in this section SHOULD be locally |
| 940 |
configurable. However, the processing described below MUST be |
| 941 |
enabled by default. |
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Thomson, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a>. Soliciting Router Advertisements</span> |
| 954 |
|
| 955 |
Router Advertisements are sent periodically to the all-nodes |
| 956 |
multicast address. To obtain an advertisement quickly, a host sends |
| 957 |
out Router Solicitations as described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 958 |
|
| 959 |
<span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a>. Absence of Router Advertisements</span> |
| 960 |
|
| 961 |
Even if a link has no routers, the DHCPv6 service to obtain addresses |
| 962 |
may still be available, and hosts may want to use the service. From |
| 963 |
the perspective of autoconfiguration, a link has no routers if no |
| 964 |
Router Advertisements are received after having sent a small number |
| 965 |
of Router Solicitations as described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 966 |
|
| 967 |
Note that it is possible that there is no router on the link in this |
| 968 |
sense, but there is a node that has the ability to forward packets. |
| 969 |
In this case, the forwarding node's address must be manually |
| 970 |
configured in hosts to be able to send packets off-link, since the |
| 971 |
only mechanism to configure the default router's address |
| 972 |
automatically is the one using Router Advertisements. |
| 973 |
|
| 974 |
<span class="h4"><a class="selflink" id="section-5.5.3" href="#section-5.5.3">5.5.3</a>. Router Advertisement Processing</span> |
| 975 |
|
| 976 |
For each Prefix-Information option in the Router Advertisement: |
| 977 |
|
| 978 |
a) If the Autonomous flag is not set, silently ignore the Prefix |
| 979 |
Information option. |
| 980 |
|
| 981 |
b) If the prefix is the link-local prefix, silently ignore the |
| 982 |
Prefix Information option. |
| 983 |
|
| 984 |
c) If the preferred lifetime is greater than the valid lifetime, |
| 985 |
silently ignore the Prefix Information option. A node MAY wish to |
| 986 |
log a system management error in this case. |
| 987 |
|
| 988 |
d) If the prefix advertised is not equal to the prefix of an |
| 989 |
address configured by stateless autoconfiguration already in the |
| 990 |
list of addresses associated with the interface (where "equal" |
| 991 |
means the two prefix lengths are the same and the first prefix- |
| 992 |
length bits of the prefixes are identical), and if the Valid |
| 993 |
Lifetime is not 0, form an address (and add it to the list) by |
| 994 |
combining the advertised prefix with an interface identifier of |
| 995 |
the link as follows: |
| 996 |
|
| 997 |
| 128 - N bits | N bits | |
| 998 |
+---------------------------------------+------------------------+ |
| 999 |
| link prefix | interface identifier | |
| 1000 |
+----------------------------------------------------------------+ |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Thomson, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
If the sum of the prefix length and interface identifier length |
| 1010 |
does not equal 128 bits, the Prefix Information option MUST be |
| 1011 |
ignored. An implementation MAY wish to log a system management |
| 1012 |
error in this case. The length of the interface identifier is |
| 1013 |
defined in a separate link-type specific document, which should |
| 1014 |
also be consistent with the address architecture [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] (see |
| 1015 |
<a href="#section-2">Section 2</a>). |
| 1016 |
|
| 1017 |
It is the responsibility of the system administrator to ensure |
| 1018 |
that the lengths of prefixes contained in Router Advertisements |
| 1019 |
are consistent with the length of interface identifiers for that |
| 1020 |
link type. It should be noted, however, that this does not mean |
| 1021 |
the advertised prefix length is meaningless. In fact, the |
| 1022 |
advertised length has non-trivial meaning for on-link |
| 1023 |
determination in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] where the sum of the prefix length and |
| 1024 |
the interface identifier length may not be equal to 128. Thus, it |
| 1025 |
should be safe to validate the advertised prefix length here, in |
| 1026 |
order to detect and avoid a configuration error specifying an |
| 1027 |
invalid prefix length in the context of address autoconfiguration. |
| 1028 |
|
| 1029 |
Note that a future revision of the address architecture [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] |
| 1030 |
and a future link-type-specific document, which will still be |
| 1031 |
consistent with each other, could potentially allow for an |
| 1032 |
interface identifier of length other than the value defined in the |
| 1033 |
current documents. Thus, an implementation should not assume a |
| 1034 |
particular constant. Rather, it should expect any lengths of |
| 1035 |
interface identifiers. |
| 1036 |
|
| 1037 |
If an address is formed successfully and the address is not yet in |
| 1038 |
the list, the host adds it to the list of addresses assigned to |
| 1039 |
the interface, initializing its preferred and valid lifetime |
| 1040 |
values from the Prefix Information option. Note that the check |
| 1041 |
against the prefix performed at the beginning of this step cannot |
| 1042 |
always detect the address conflict in the list. It could be |
| 1043 |
possible that an address already in the list, configured either |
| 1044 |
manually or by DHCPv6, happens to be identical to the newly |
| 1045 |
created address, whereas such a case should be atypical. |
| 1046 |
|
| 1047 |
e) If the advertised prefix is equal to the prefix of an address |
| 1048 |
configured by stateless autoconfiguration in the list, the |
| 1049 |
preferred lifetime of the address is reset to the Preferred |
| 1050 |
Lifetime in the received advertisement. The specific action to |
| 1051 |
perform for the valid lifetime of the address depends on the Valid |
| 1052 |
Lifetime in the received advertisement and the remaining time to |
| 1053 |
the valid lifetime expiration of the previously autoconfigured |
| 1054 |
address. We call the remaining time "RemainingLifetime" in the |
| 1055 |
following discussion: |
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Thomson, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
1. If the received Valid Lifetime is greater than 2 hours or |
| 1066 |
greater than RemainingLifetime, set the valid lifetime of the |
| 1067 |
corresponding address to the advertised Valid Lifetime. |
| 1068 |
|
| 1069 |
2. If RemainingLifetime is less than or equal to 2 hours, ignore |
| 1070 |
the Prefix Information option with regards to the valid |
| 1071 |
lifetime, unless the Router Advertisement from which this |
| 1072 |
option was obtained has been authenticated (e.g., via Secure |
| 1073 |
Neighbor Discovery [<a href="./rfc3971" title=""SEcure Neighbor Discovery (SEND)"">RFC3971</a>]). If the Router Advertisement |
| 1074 |
was authenticated, the valid lifetime of the corresponding |
| 1075 |
address should be set to the Valid Lifetime in the received |
| 1076 |
option. |
| 1077 |
|
| 1078 |
3. Otherwise, reset the valid lifetime of the corresponding |
| 1079 |
address to 2 hours. |
| 1080 |
|
| 1081 |
The above rules address a specific denial-of-service attack in |
| 1082 |
which a bogus advertisement could contain prefixes with very small |
| 1083 |
Valid Lifetimes. Without the above rules, a single |
| 1084 |
unauthenticated advertisement containing bogus Prefix Information |
| 1085 |
options with short Valid Lifetimes could cause all of a node's |
| 1086 |
addresses to expire prematurely. The above rules ensure that |
| 1087 |
legitimate advertisements (which are sent periodically) will |
| 1088 |
"cancel" the short Valid Lifetimes before they actually take |
| 1089 |
effect. |
| 1090 |
|
| 1091 |
Note that the preferred lifetime of the corresponding address is |
| 1092 |
always reset to the Preferred Lifetime in the received Prefix |
| 1093 |
Information option, regardless of whether the valid lifetime is |
| 1094 |
also reset or ignored. The difference comes from the fact that |
| 1095 |
the possible attack for the preferred lifetime is relatively |
| 1096 |
minor. Additionally, it is even undesirable to ignore the |
| 1097 |
preferred lifetime when a valid administrator wants to deprecate a |
| 1098 |
particular address by sending a short preferred lifetime (and the |
| 1099 |
valid lifetime is ignored by accident). |
| 1100 |
|
| 1101 |
<span class="h4"><a class="selflink" id="section-5.5.4" href="#section-5.5.4">5.5.4</a>. Address Lifetime Expiry</span> |
| 1102 |
|
| 1103 |
A preferred address becomes deprecated when its preferred lifetime |
| 1104 |
expires. A deprecated address SHOULD continue to be used as a source |
| 1105 |
address in existing communications, but SHOULD NOT be used to |
| 1106 |
initiate new communications if an alternate (non-deprecated) address |
| 1107 |
of sufficient scope can easily be used instead. |
| 1108 |
|
| 1109 |
Note that the feasibility of initiating new communication using a |
| 1110 |
non-deprecated address may be an application-specific decision, as |
| 1111 |
only the application may have knowledge about whether the (now) |
| 1112 |
deprecated address was (or still is) in use by the application. For |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Thomson, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
example, if an application explicitly specifies that the protocol |
| 1122 |
stack use a deprecated address as a source address, the protocol |
| 1123 |
stack must accept that; the application might request it because that |
| 1124 |
IP address is used in higher-level communication and there might be a |
| 1125 |
requirement that the multiple connections in such a grouping use the |
| 1126 |
same pair of IP addresses. |
| 1127 |
|
| 1128 |
IP and higher layers (e.g., TCP, UDP) MUST continue to accept and |
| 1129 |
process datagrams destined to a deprecated address as normal since a |
| 1130 |
deprecated address is still a valid address for the interface. In |
| 1131 |
the case of TCP, this means TCP SYN segments sent to a deprecated |
| 1132 |
address are responded to using the deprecated address as a source |
| 1133 |
address in the corresponding SYN-ACK (if the connection would |
| 1134 |
otherwise be allowed). |
| 1135 |
|
| 1136 |
An implementation MAY prevent any new communication from using a |
| 1137 |
deprecated address, but system management MUST have the ability to |
| 1138 |
disable such a facility, and the facility MUST be disabled by |
| 1139 |
default. |
| 1140 |
|
| 1141 |
Other subtle cases should also be noted about source address |
| 1142 |
selection. For example, the above description does not clarify which |
| 1143 |
address should be used between a deprecated, smaller-scope address |
| 1144 |
and a non-deprecated, sufficient scope address. The details of the |
| 1145 |
address selection including this case are described in [<a href="./rfc3484" title=""Default Address Selection for Internet Protocol version 6 (IPv6)"">RFC3484</a>] and |
| 1146 |
are beyond the scope of this document. |
| 1147 |
|
| 1148 |
An address (and its association with an interface) becomes invalid |
| 1149 |
when its valid lifetime expires. An invalid address MUST NOT be used |
| 1150 |
as a source address in outgoing communications and MUST NOT be |
| 1151 |
recognized as a destination on a receiving interface. |
| 1152 |
|
| 1153 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Configuration Consistency</span> |
| 1154 |
|
| 1155 |
It is possible for hosts to obtain address information using both |
| 1156 |
stateless autoconfiguration and DHCPv6 since both may be enabled at |
| 1157 |
the same time. It is also possible that the values of other |
| 1158 |
configuration parameters, such as MTU size and hop limit, will be |
| 1159 |
learned from both Router Advertisements and DHCPv6. If the same |
| 1160 |
configuration information is provided by multiple sources, the value |
| 1161 |
of this information should be consistent. However, it is not |
| 1162 |
considered a fatal error if information received from multiple |
| 1163 |
sources is inconsistent. Hosts accept the union of all information |
| 1164 |
received via Neighbor Discovery and DHCPv6. |
| 1165 |
|
| 1166 |
If inconsistent information is learned from different sources, an |
| 1167 |
implementation may want to give information learned securely |
| 1168 |
precedence over information learned without protection. For |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Thomson, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
instance, <a href="./rfc3971#section-8">Section 8 of [RFC3971]</a> discusses how to deal with |
| 1178 |
information learned through Secure Neighbor Discovery conflicting |
| 1179 |
with information learned through plain Neighbor Discovery. The same |
| 1180 |
discussion can apply to the preference between information learned |
| 1181 |
through plain Neighbor Discovery and information learned via secured |
| 1182 |
DHCPv6, and so on. |
| 1183 |
|
| 1184 |
In any case, if there is no security difference, the most recently |
| 1185 |
obtained values SHOULD have precedence over information learned |
| 1186 |
earlier. |
| 1187 |
|
| 1188 |
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. Retaining Configured Addresses for Stability</span> |
| 1189 |
|
| 1190 |
An implementation that has stable storage may want to retain |
| 1191 |
addresses in the storage when the addresses were acquired using |
| 1192 |
stateless address autoconfiguration. Assuming the lifetimes used are |
| 1193 |
reasonable, this technique implies that a temporary outage (less than |
| 1194 |
the valid lifetime) of a router will never result in losing a global |
| 1195 |
address of the node even if the node were to reboot. When this |
| 1196 |
technique is used, it should also be noted that the expiration times |
| 1197 |
of the preferred and valid lifetimes must be retained, in order to |
| 1198 |
prevent the use of an address after it has become deprecated or |
| 1199 |
invalid. |
| 1200 |
|
| 1201 |
Further details on this kind of extension are beyond the scope of |
| 1202 |
this document. |
| 1203 |
|
| 1204 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 1205 |
|
| 1206 |
Stateless address autoconfiguration allows a host to connect to a |
| 1207 |
network, configure an address, and start communicating with other |
| 1208 |
nodes without ever registering or authenticating itself with the |
| 1209 |
local site. Although this allows unauthorized users to connect to |
| 1210 |
and use a network, the threat is inherently present in the Internet |
| 1211 |
architecture. Any node with a physical attachment to a network can |
| 1212 |
generate an address (using a variety of ad hoc techniques) that |
| 1213 |
provides connectivity. |
| 1214 |
|
| 1215 |
The use of stateless address autoconfiguration and Duplicate Address |
| 1216 |
Detection opens up the possibility of several denial-of-service |
| 1217 |
attacks. For example, any node can respond to Neighbor Solicitations |
| 1218 |
for a tentative address, causing the other node to reject the address |
| 1219 |
as a duplicate. A separate document [<a href="./rfc3756" title=""IPv6 Neighbor Discovery (ND) Trust Models and Threats"">RFC3756</a>] discusses details |
| 1220 |
about these attacks, which can be addressed with the Secure Neighbor |
| 1221 |
Discovery protocol [<a href="./rfc3971" title=""SEcure Neighbor Discovery (SEND)"">RFC3971</a>]. It should also be noted that [<a href="./rfc3756" title=""IPv6 Neighbor Discovery (ND) Trust Models and Threats"">RFC3756</a>] |
| 1222 |
points out that the use of IP security is not always feasible |
| 1223 |
depending on network environments. |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Thomson, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span> |
| 1234 |
|
| 1235 |
Thomas Narten and Susan Thompson were the authors of RFCs 1971 and |
| 1236 |
2462. For this revision of the RFC, Tatuya Jinmei was the sole |
| 1237 |
editor. |
| 1238 |
|
| 1239 |
The authors of <a href="./rfc2461">RFC 2461</a> would like to thank the members of both the |
| 1240 |
IPNG (which is now IPV6) and ADDRCONF working groups for their input. |
| 1241 |
In particular, thanks to Jim Bound, Steve Deering, Richard Draves, |
| 1242 |
and Erik Nordmark. Thanks also goes to John Gilmore for alerting the |
| 1243 |
WG of the "0 Lifetime Prefix Advertisement" denial-of-service attack |
| 1244 |
vulnerability; this document incorporates changes that address this |
| 1245 |
vulnerability. |
| 1246 |
|
| 1247 |
A number of people have contributed to identifying issues with <a href="./rfc2461">RFC</a> |
| 1248 |
<a href="./rfc2461">2461</a> and to proposing resolutions to the issues as reflected in this |
| 1249 |
version of the document. In addition to those listed above, the |
| 1250 |
contributors include Jari Arkko, James Carlson, Brian E. Carpenter, |
| 1251 |
Gregory Daley, Elwyn Davies, Ralph Droms, Jun-ichiro Itojun Hagino, |
| 1252 |
Christian Huitema, Suresh Krishnan, Soohong Daniel Park, Markku |
| 1253 |
Savela, Pekka Savola, Hemant Singh, Bernie Volz, Margaret Wasserman, |
| 1254 |
and Vlad Yasevich. |
| 1255 |
|
| 1256 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 1257 |
|
| 1258 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 1259 |
|
| 1260 |
[<a id="ref-RFC2464">RFC2464</a>] Crawford, M., "Transmission of IPv6 Packets over |
| 1261 |
Ethernet Networks", <a href="./rfc2464">RFC 2464</a>, December 1998. |
| 1262 |
|
| 1263 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1264 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1265 |
|
| 1266 |
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing |
| 1267 |
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006. |
| 1268 |
|
| 1269 |
[<a id="ref-RFC4861">RFC4861</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, |
| 1270 |
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>, |
| 1271 |
September 2007. |
| 1272 |
|
| 1273 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 1274 |
|
| 1275 |
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., |
| 1276 |
and M. Carney, "Dynamic Host Configuration Protocol for |
| 1277 |
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 1278 |
|
| 1279 |
[<a id="ref-RFC3484">RFC3484</a>] Draves, R., "Default Address Selection for Internet |
| 1280 |
Protocol version 6 (IPv6)", <a href="./rfc3484">RFC 3484</a>, February 2003. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Thomson, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
[<a id="ref-RFC4941">RFC4941</a>] Narten, T., Draves, R., and S. Krishnan, "Privacy |
| 1290 |
Extensions for Stateless Address Autoconfiguration in |
| 1291 |
IPv6", <a href="./rfc4941">RFC 4941</a>, September 2007. |
| 1292 |
|
| 1293 |
[<a id="ref-RFC3972">RFC3972</a>] Aura, T., "Cryptographically Generated Addresses |
| 1294 |
(CGA)", <a href="./rfc3972">RFC 3972</a>, March 2005. |
| 1295 |
|
| 1296 |
[<a id="ref-RFC2710">RFC2710</a>] Deering, S., Fenner, W., and B. Haberman, "Multicast |
| 1297 |
Listener Discovery (MLD) for IPv6", <a href="./rfc2710">RFC 2710</a>, |
| 1298 |
October 1999. |
| 1299 |
|
| 1300 |
[<a id="ref-RFC3810">RFC3810</a>] Vida, R. and L. Costa, "Multicast Listener Discovery |
| 1301 |
Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>, June 2004. |
| 1302 |
|
| 1303 |
[<a id="ref-RFC3590">RFC3590</a>] Haberman, B., "Source Address Selection for the |
| 1304 |
Multicast Listener Discovery (MLD) Protocol", <a href="./rfc3590">RFC 3590</a>, |
| 1305 |
September 2003. |
| 1306 |
|
| 1307 |
[<a id="ref-RFC3971">RFC3971</a>] Arkko, J., Kempf, J., Zill, B., and P. Nikander, |
| 1308 |
"SEcure Neighbor Discovery (SEND)", <a href="./rfc3971">RFC 3971</a>, |
| 1309 |
March 2005. |
| 1310 |
|
| 1311 |
[<a id="ref-RFC3756">RFC3756</a>] Nikander, P., Kempf, J., and E. Nordmark, "IPv6 |
| 1312 |
Neighbor Discovery (ND) Trust Models and Threats", |
| 1313 |
<a href="./rfc3756">RFC 3756</a>, May 2004. |
| 1314 |
|
| 1315 |
[<a id="ref-RFC1112">RFC1112</a>] Deering, S., "Host extensions for IP multicasting", |
| 1316 |
STD 5, <a href="./rfc1112">RFC 1112</a>, August 1989. |
| 1317 |
|
| 1318 |
[<a id="ref-IEEE802.11">IEEE802.11</a>] IEEE, "Wireless LAN Medium Access Control (MAC) and |
| 1319 |
Physical Layer (PHY) Specifications", ANSI/IEEE |
| 1320 |
STd 802.11, August 1999. |
| 1321 |
|
| 1322 |
|
| 1323 |
|
| 1324 |
|
| 1325 |
|
| 1326 |
|
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
|
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Thomson, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Loopback Suppression and Duplicate Address Detection</span> |
| 1346 |
|
| 1347 |
Determining whether a received multicast solicitation was looped back |
| 1348 |
to the sender or actually came from another node is implementation- |
| 1349 |
dependent. A problematic case occurs when two interfaces attached to |
| 1350 |
the same link happen to have the same identifier and link-layer |
| 1351 |
address, and they both send out packets with identical contents at |
| 1352 |
roughly the same time (e.g., Neighbor Solicitations for a tentative |
| 1353 |
address as part of Duplicate Address Detection messages). Although a |
| 1354 |
receiver will receive both packets, it cannot determine which packet |
| 1355 |
was looped back and which packet came from the other node simply by |
| 1356 |
comparing packet contents (i.e., the contents are identical). In |
| 1357 |
this particular case, it is not necessary to know precisely which |
| 1358 |
packet was looped back and which was sent by another node; if one |
| 1359 |
receives more solicitations than were sent, the tentative address is |
| 1360 |
a duplicate. However, the situation may not always be this |
| 1361 |
straightforward. |
| 1362 |
|
| 1363 |
The IPv4 multicast specification [<a href="./rfc1112" title=""Host extensions for IP multicasting"">RFC1112</a>] recommends that the |
| 1364 |
service interface provide a way for an upper-layer protocol to |
| 1365 |
inhibit local delivery of packets sent to a multicast group that the |
| 1366 |
sending host is a member of. Some applications know that there will |
| 1367 |
be no other group members on the same host, and suppressing loopback |
| 1368 |
prevents them from having to receive (and discard) the packets they |
| 1369 |
themselves send out. A straightforward way to implement this |
| 1370 |
facility is to disable loopback at the hardware level (if supported |
| 1371 |
by the hardware), with packets looped back (if requested) by |
| 1372 |
software. On interfaces in which the hardware itself suppresses |
| 1373 |
loopbacks, a node running Duplicate Address Detection simply counts |
| 1374 |
the number of Neighbor Solicitations received for a tentative address |
| 1375 |
and compares them with the number expected. If there is a mismatch, |
| 1376 |
the tentative address is a duplicate. |
| 1377 |
|
| 1378 |
In those cases where the hardware cannot suppress loopbacks, however, |
| 1379 |
one possible software heuristic to filter out unwanted loopbacks is |
| 1380 |
to discard any received packet whose link-layer source address is the |
| 1381 |
same as the receiving interface's. There is even a link-layer |
| 1382 |
specification that requires that any such packets be discarded |
| 1383 |
[<a href="#ref-IEEE802.11" title=""Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications"">IEEE802.11</a>]. Unfortunately, use of that criteria also results in |
| 1384 |
the discarding of all packets sent by another node using the same |
| 1385 |
link-layer address. Duplicate Address Detection will fail on |
| 1386 |
interfaces that filter received packets in this manner: |
| 1387 |
|
| 1388 |
o If a node performing Duplicate Address Detection discards received |
| 1389 |
packets that have the same source link-layer address as the |
| 1390 |
receiving interface, it will also discard packets from other nodes |
| 1391 |
that also use the same link-layer address, including Neighbor |
| 1392 |
Advertisement and Neighbor Solicitation messages required to make |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Thomson, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
Duplicate Address Detection work correctly. This particular |
| 1402 |
problem can be avoided by temporarily disabling the software |
| 1403 |
suppression of loopbacks while a node performs Duplicate Address |
| 1404 |
Detection, if it is possible to disable the suppression. |
| 1405 |
|
| 1406 |
o If a node that is already using a particular IP address discards |
| 1407 |
received packets that have the same link-layer source address as |
| 1408 |
the interface, it will also discard Duplicate Address Detection- |
| 1409 |
related Neighbor Solicitation messages sent by another node that |
| 1410 |
also use the same link-layer address. Consequently, Duplicate |
| 1411 |
Address Detection will fail, and the other node will configure a |
| 1412 |
non-unique address. Since it is generally impossible to know when |
| 1413 |
another node is performing Duplicate Address Detection, this |
| 1414 |
scenario can be avoided only if software suppression of loopback |
| 1415 |
is permanently disabled. |
| 1416 |
|
| 1417 |
Thus, to perform Duplicate Address Detection correctly in the case |
| 1418 |
where two interfaces are using the same link-layer address, an |
| 1419 |
implementation must have a good understanding of the interface's |
| 1420 |
multicast loopback semantics, and the interface cannot discard |
| 1421 |
received packets simply because the source link-layer address is the |
| 1422 |
same as the interface's. It should also be noted that a link-layer |
| 1423 |
specification can conflict with the condition necessary to make |
| 1424 |
Duplicate Address Detection work. |
| 1425 |
|
| 1426 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Changes since <a href="./rfc1971">RFC 1971</a></span> |
| 1427 |
|
| 1428 |
o Changed document to use term "interface identifier" rather than |
| 1429 |
"interface token" for consistency with other IPv6 documents. |
| 1430 |
|
| 1431 |
o Clarified definition of deprecated address to make clear it is OK |
| 1432 |
to continue sending to or from deprecated addresses. |
| 1433 |
|
| 1434 |
o Added rules to <a href="#section-5.5.3">Section 5.5.3</a> Router Advertisement processing to |
| 1435 |
address potential denial-of-service attack when prefixes are |
| 1436 |
advertised with very short Lifetimes. |
| 1437 |
|
| 1438 |
o Clarified wording in <a href="#section-5.5.4">Section 5.5.4</a> to make clear that all upper |
| 1439 |
layer protocols must process (i.e., send and receive) packets sent |
| 1440 |
to deprecated addresses. |
| 1441 |
|
| 1442 |
|
| 1443 |
|
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Thomson, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
<span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Changes since <a href="./rfc2462">RFC 2462</a></span> |
| 1458 |
|
| 1459 |
Major changes that can affect existing implementations: |
| 1460 |
|
| 1461 |
o Specified that a node performing Duplicate Address Detection delay |
| 1462 |
joining the solicited-node multicast group, not just delay sending |
| 1463 |
Neighbor Solicitations, explaining the detailed reason. |
| 1464 |
|
| 1465 |
o Added a requirement for a random delay before sending Neighbor |
| 1466 |
Solicitations for Duplicate Address Detection if the address being |
| 1467 |
checked is configured by a multicasted Router Advertisements. |
| 1468 |
|
| 1469 |
o Clarified that on failure of Duplicate Address Detection, IP |
| 1470 |
network operation should be disabled and that the rule should |
| 1471 |
apply when the hardware address is supposed to be unique. |
| 1472 |
|
| 1473 |
Major clarifications: |
| 1474 |
|
| 1475 |
o Clarified how the length of interface identifiers should be |
| 1476 |
determined, described the relationship with the prefix length |
| 1477 |
advertised in Router Advertisements, and avoided using a |
| 1478 |
particular length hard-coded in this document. |
| 1479 |
|
| 1480 |
o Clarified the processing of received neighbor advertisements while |
| 1481 |
performing Duplicate Address Detection. |
| 1482 |
|
| 1483 |
o Removed the text regarding the M and O flags, considering the |
| 1484 |
maturity of implementations and operational experiences. |
| 1485 |
ManagedFlag and OtherConfigFlag were removed accordingly. (Note |
| 1486 |
that this change does not mean the use of these flags is |
| 1487 |
deprecated.) |
| 1488 |
|
| 1489 |
o Avoided the wording of "stateful configuration", which is known to |
| 1490 |
be quite confusing, and simply used "DHCPv6" wherever appropriate. |
| 1491 |
|
| 1492 |
o Recommended to perform Duplicate Address Detection for all unicast |
| 1493 |
addresses more strongly, considering a variety of different |
| 1494 |
interface identifiers, while keeping care of existing |
| 1495 |
implementations. |
| 1496 |
|
| 1497 |
o Clarified wording in <a href="#section-5.5.4">Section 5.5.4</a> to make clear that a deprecated |
| 1498 |
address specified by an application can be used for any |
| 1499 |
communication. |
| 1500 |
|
| 1501 |
o Clarified the prefix check described in <a href="#section-5.5.3">Section 5.5.3</a> using more |
| 1502 |
appropriate terms and that the check is done against the prefixes |
| 1503 |
of addresses configured by stateless autoconfiguration. |
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Thomson, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
o Changed the references to the IP security Authentication Header to |
| 1514 |
references to <a href="./rfc3971">RFC 3971</a> (Secure Neighbor Discovery). Also revised |
| 1515 |
the Security Considerations section with a reference to <a href="./rfc3756">RFC 3756</a>. |
| 1516 |
|
| 1517 |
o Added a note when an implementation uses stable storage for |
| 1518 |
autoconfigured addresses. |
| 1519 |
|
| 1520 |
o Added consideration about preference between inconsistent |
| 1521 |
information sets, one from a secured source and the other learned |
| 1522 |
without protection. |
| 1523 |
|
| 1524 |
Other miscellaneous clarifications: |
| 1525 |
|
| 1526 |
o Removed references to site-local and revised wording around the |
| 1527 |
keyword. |
| 1528 |
|
| 1529 |
o Removed redundant code in denial-of-service protection in |
| 1530 |
<a href="#section-5.5.3">Section 5.5.3</a>. |
| 1531 |
|
| 1532 |
o Clarified that a unicasted Neighbor Solicitation or Advertisement |
| 1533 |
should be discarded while performing Duplicate Address Detection. |
| 1534 |
|
| 1535 |
o Noted in <a href="#section-5.3">Section 5.3</a> that an interface can be considered as |
| 1536 |
becoming enabled when a wireless access point changes. |
| 1537 |
|
| 1538 |
|
| 1539 |
|
| 1540 |
|
| 1541 |
|
| 1542 |
|
| 1543 |
|
| 1544 |
|
| 1545 |
|
| 1546 |
|
| 1547 |
|
| 1548 |
|
| 1549 |
|
| 1550 |
|
| 1551 |
|
| 1552 |
|
| 1553 |
|
| 1554 |
|
| 1555 |
|
| 1556 |
|
| 1557 |
|
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Thomson, et al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
Authors' Addresses |
| 1570 |
|
| 1571 |
Susan Thomson |
| 1572 |
Cisco Systems |
| 1573 |
|
| 1574 |
EMail: [email protected] |
| 1575 |
|
| 1576 |
|
| 1577 |
Thomas Narten |
| 1578 |
IBM Corporation |
| 1579 |
P.O. Box 12195 |
| 1580 |
Research Triangle Park, NC 27709-2195 |
| 1581 |
USA |
| 1582 |
|
| 1583 |
Phone: +1 919-254-7798 |
| 1584 |
EMail: [email protected] |
| 1585 |
|
| 1586 |
|
| 1587 |
Tatuya Jinmei |
| 1588 |
Corporate Research & Development Center, Toshiba Corporation |
| 1589 |
1 Komukai Toshiba-cho, Saiwai-ku |
| 1590 |
Kawasaki-shi, Kanagawa 212-8582 |
| 1591 |
Japan |
| 1592 |
|
| 1593 |
Phone: +81 44-549-2230 |
| 1594 |
EMail: [email protected] |
| 1595 |
|
| 1596 |
|
| 1597 |
|
| 1598 |
|
| 1599 |
|
| 1600 |
|
| 1601 |
|
| 1602 |
|
| 1603 |
|
| 1604 |
|
| 1605 |
|
| 1606 |
|
| 1607 |
|
| 1608 |
|
| 1609 |
|
| 1610 |
|
| 1611 |
|
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Thomson, et al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc4862">RFC 4862</a> IPv6 Stateless Address Autoconfiguration September 2007</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
Full Copyright Statement |
| 1626 |
|
| 1627 |
Copyright (C) The IETF Trust (2007). |
| 1628 |
|
| 1629 |
This document is subject to the rights, licenses and restrictions |
| 1630 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 1631 |
retain all their rights. |
| 1632 |
|
| 1633 |
This document and the information contained herein are provided on an |
| 1634 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 1635 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |
| 1636 |
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |
| 1637 |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 1638 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1639 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1640 |
|
| 1641 |
Intellectual Property |
| 1642 |
|
| 1643 |
The IETF takes no position regarding the validity or scope of any |
| 1644 |
Intellectual Property Rights or other rights that might be claimed to |
| 1645 |
pertain to the implementation or use of the technology described in |
| 1646 |
this document or the extent to which any license under such rights |
| 1647 |
might or might not be available; nor does it represent that it has |
| 1648 |
made any independent effort to identify any such rights. Information |
| 1649 |
on the procedures with respect to rights in RFC documents can be |
| 1650 |
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>. |
| 1651 |
|
| 1652 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1653 |
assurances of licenses to be made available, or the result of an |
| 1654 |
attempt made to obtain a general license or permission for the use of |
| 1655 |
such proprietary rights by implementers or users of this |
| 1656 |
specification can be obtained from the IETF on-line IPR repository at |
| 1657 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1658 |
|
| 1659 |
The IETF invites any interested party to bring to its attention any |
| 1660 |
copyrights, patents or patent applications, or other proprietary |
| 1661 |
rights that may cover technology that may be required to implement |
| 1662 |
this standard. Please address the information to the IETF at |
| 1663 |
[email protected]. |
| 1664 |
|
| 1665 |
|
| 1666 |
|
| 1667 |
|
| 1668 |
|
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
Thomson, et al. Standards Track [Page 30] |
| 1677 |
</pre> |