| 1 |
<pre>Internet Engineering Task Force (IETF) H. Singh |
| 2 |
Request for Comments: 5942 W. Beebee |
| 3 |
Updates: <a href="./rfc4861">4861</a> Cisco Systems, Inc. |
| 4 |
Category: Standards Track E. Nordmark |
| 5 |
ISSN: 2070-1721 Oracle, Inc. |
| 6 |
July 2010 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
IPv6 specifies a model of a subnet that is different than the IPv4 |
| 14 |
subnet model. The subtlety of the differences has resulted in |
| 15 |
incorrect implementations that do not interoperate. This document |
| 16 |
spells out the most important difference: that an IPv6 address isn't |
| 17 |
automatically associated with an IPv6 on-link prefix. This document |
| 18 |
also updates (partially due to security concerns caused by incorrect |
| 19 |
implementations) a part of the definition of "on-link" from <a href="./rfc4861">RFC 4861</a>. |
| 20 |
|
| 21 |
Status of This Memo |
| 22 |
|
| 23 |
This is an Internet Standards Track document. |
| 24 |
|
| 25 |
This document is a product of the Internet Engineering Task Force |
| 26 |
(IETF). It represents the consensus of the IETF community. It has |
| 27 |
received public review and has been approved for publication by the |
| 28 |
Internet Engineering Steering Group (IESG). Further information on |
| 29 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 30 |
|
| 31 |
Information about the current status of this document, any errata, |
| 32 |
and how to provide feedback on it may be obtained at |
| 33 |
<a href="http://www.rfc-editor.org/info/rfc5942">http://www.rfc-editor.org/info/rfc5942</a>. |
| 34 |
|
| 35 |
Copyright Notice |
| 36 |
|
| 37 |
Copyright (c) 2010 IETF Trust and the persons identified as the |
| 38 |
document authors. All rights reserved. |
| 39 |
|
| 40 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 41 |
Provisions Relating to IETF Documents |
| 42 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 43 |
publication of this document. Please review these documents |
| 44 |
carefully, as they describe your rights and restrictions with respect |
| 45 |
to this document. Code Components extracted from this document must |
| 46 |
include Simplified BSD License text as described in Section 4.e of |
| 47 |
the Trust Legal Provisions and are provided without warranty as |
| 48 |
described in the Simplified BSD License. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 55 |
|
| 56 |
|
| 57 |
This document may contain material from IETF Documents or IETF |
| 58 |
Contributions published or made publicly available before November |
| 59 |
10, 2008. The person(s) controlling the copyright in some of this |
| 60 |
material may not have granted the IETF Trust the right to allow |
| 61 |
modifications of such material outside the IETF Standards Process. |
| 62 |
Without obtaining an adequate license from the person(s) controlling |
| 63 |
the copyright in such materials, this document may not be modified |
| 64 |
outside the IETF Standards Process, and derivative works of it may |
| 65 |
not be created outside the IETF Standards Process, except to format |
| 66 |
it for publication as an RFC or to translate it into languages other |
| 67 |
than English. |
| 68 |
|
| 69 |
Table of Contents |
| 70 |
|
| 71 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 72 |
<a href="#section-2">2</a>. Requirements Language ...........................................<a href="#page-4">4</a> |
| 73 |
<a href="#section-3">3</a>. Host Behavior ...................................................<a href="#page-4">4</a> |
| 74 |
<a href="#section-4">4</a>. Host Rules ......................................................<a href="#page-7">7</a> |
| 75 |
<a href="#section-5">5</a>. Observed Incorrect Implementation Behavior ......................<a href="#page-8">8</a> |
| 76 |
<a href="#section-6">6</a>. Updates to <a href="./rfc4861">RFC 4861</a> .............................................<a href="#page-9">9</a> |
| 77 |
<a href="#section-7">7</a>. Conclusion ......................................................<a href="#page-9">9</a> |
| 78 |
<a href="#section-8">8</a>. Security Considerations .........................................<a href="#page-9">9</a> |
| 79 |
<a href="#section-9">9</a>. Contributors ....................................................<a href="#page-9">9</a> |
| 80 |
<a href="#section-10">10</a>. Acknowledgements ...............................................<a href="#page-9">9</a> |
| 81 |
<a href="#section-11">11</a>. References ....................................................<a href="#page-10">10</a> |
| 82 |
<a href="#section-11.1">11.1</a>. Normative References .....................................<a href="#page-10">10</a> |
| 83 |
<a href="#section-11.2">11.2</a>. Informative References ...................................<a href="#page-10">10</a> |
| 84 |
|
| 85 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 86 |
|
| 87 |
IPv4 implementations typically associate a netmask with an address |
| 88 |
when an IPv4 address is assigned to an interface. That netmask |
| 89 |
together with the IPv4 address designates an on-link prefix. Nodes |
| 90 |
consider addresses covered by an on-link prefix to be directly |
| 91 |
attached to the same link as the sending node, i.e., they send |
| 92 |
traffic for such addresses directly rather than to a router. See |
| 93 |
<a href="./rfc1122#section-3.3.1">Section 3.3.1 of [RFC1122]</a>. Prior to the development of subnetting |
| 94 |
[<a href="./rfc0950" title=""Internet Standard Subnetting Procedure"">RFC0950</a>] and Classless Inter-Domain Routing (CIDR) [<a href="./rfc4632" title=""Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan"">RFC4632</a>], an |
| 95 |
address's netmask could be derived directly from the address simply |
| 96 |
by determining whether it was a Class A, B, or C address. Today, |
| 97 |
assigning an address to an interface also requires specifying a |
| 98 |
netmask to use. In the absence of specifying a specific netmask when |
| 99 |
assigning an address, some implementations would fall back to |
| 100 |
deriving the netmask from the class of the address. |
| 101 |
|
| 102 |
The behavior of IPv6 as specified in Neighbor Discovery (ND) |
| 103 |
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] is quite different. The on-link determination is separate |
| 104 |
from the address assignment. A host can have IPv6 addresses without |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 111 |
|
| 112 |
|
| 113 |
any related on-link prefixes or can have on-link prefixes that are |
| 114 |
not related to any IPv6 addresses that are assigned to the host. Any |
| 115 |
assigned address on an interface should initially be considered as |
| 116 |
having no internal structure as shown in [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>]. |
| 117 |
|
| 118 |
In IPv6, by default, a host treats only the link-local prefix as |
| 119 |
on-link. |
| 120 |
|
| 121 |
The reception of a Prefix Information Option (PIO) with the L-bit set |
| 122 |
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] and a non-zero valid lifetime creates (or updates) an entry |
| 123 |
in the Prefix List. All prefixes on a host's Prefix List (i.e., |
| 124 |
those prefixes that have not yet timed out) are considered to be |
| 125 |
on-link by that host. |
| 126 |
|
| 127 |
The on-link definition in the Terminology section of [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>], as |
| 128 |
modified by this document, defines the complete list of cases in |
| 129 |
which a host considers an address to be on-link. Individual address |
| 130 |
entries can be expired by the Neighbor Unreachability Detection |
| 131 |
mechanism. |
| 132 |
|
| 133 |
IPv6 packets sent using the Conceptual Sending Algorithm as described |
| 134 |
in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] only trigger address resolution for IPv6 addresses that |
| 135 |
the sender considers to be on-link. Packets to any other address are |
| 136 |
sent to a default router. If there is no default router, then the |
| 137 |
node should send an ICMPv6 Destination Unreachable indication as |
| 138 |
specified in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] -- more details are provided in the "Host |
| 139 |
Behavior" and "Host Rules" sections of this document. (Note that |
| 140 |
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] changed the behavior when the Default Router List is empty. |
| 141 |
|
| 142 |
In the old version of Neighbor Discovery [<a href="./rfc2461" title=""Neighbor Discovery for IP Version 6 (IPv6)"">RFC2461</a>], if the Default |
| 143 |
Router List is empty, rather than sending the ICMPv6 Destination |
| 144 |
Unreachable indication, the [<a href="./rfc2461" title=""Neighbor Discovery for IP Version 6 (IPv6)"">RFC2461</a>] node assumed that the |
| 145 |
destination was on-link.) Note that ND is scoped to a single link. |
| 146 |
All Neighbor Solicitation (NS) responses are assumed to be sent out |
| 147 |
the same interface on which the corresponding query was received |
| 148 |
without using the Conceptual Sending Algorithm. |
| 149 |
|
| 150 |
Failure of host implementations to correctly implement the IPv6 |
| 151 |
subnet model can result in lack of IPv6 connectivity. See the |
| 152 |
"Observed Incorrect Implementation Behavior" section for details. |
| 153 |
|
| 154 |
This document deprecates the last two bullets from the definition of |
| 155 |
"on-link" in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] to address security concerns arising from |
| 156 |
particular ND implementations. |
| 157 |
|
| 158 |
Host behavior is clarified in the "Host Behavior" and "Host Rules" |
| 159 |
sections. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span> |
| 170 |
|
| 171 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 172 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 173 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 174 |
|
| 175 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Host Behavior</span> |
| 176 |
|
| 177 |
1. The original Neighbor Discovery (ND) specification [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] was |
| 178 |
unclear in its usage of the term "on-link" in a few places. In |
| 179 |
IPv6, an address is on-link (with respect to a specific link), if |
| 180 |
the address has been assigned to an interface attached to that |
| 181 |
link. Any node attached to the link can send a datagram directly |
| 182 |
to an on-link address without forwarding the datagram through a |
| 183 |
router. However, in order for a node to know that a destination |
| 184 |
is on-link, it must obtain configuration information to that |
| 185 |
effect. In IPv6, there are two main ways of maintaining |
| 186 |
information about on-link destinations. First, a host maintains |
| 187 |
a Prefix List that identifies ranges of addresses that are to be |
| 188 |
considered on-link. Second, Redirects can identify individual |
| 189 |
destinations that are on-link; such Redirects update the |
| 190 |
Destination Cache. |
| 191 |
|
| 192 |
The Prefix List is populated via the following means: |
| 193 |
|
| 194 |
* Receipt of a valid Router Advertisement (RA) that specifies a |
| 195 |
prefix with the L-bit set. Such a prefix is considered |
| 196 |
on-link for a period specified in the Valid Lifetime and is |
| 197 |
added to the Prefix List. (The link-local prefix is |
| 198 |
effectively considered a permanent entry on the Prefix List.) |
| 199 |
|
| 200 |
* Indication of an on-link prefix (which may be a /128) via |
| 201 |
manual configuration, or some other yet-to-be-specified |
| 202 |
configuration mechanism. |
| 203 |
|
| 204 |
A Redirect can also signal whether an address is on-link. If a |
| 205 |
host originates a packet, but the first-hop router routes the |
| 206 |
received packet back out onto the same link, the router also |
| 207 |
sends the host a Redirect. If the Target and Destination Address |
| 208 |
of the Redirect are the same, the Target Address is to be treated |
| 209 |
as on-link as specified in <a href="./rfc4861#section-8">Section 8 of [RFC4861]</a>. That is, the |
| 210 |
host updates its Destination Cache (but not its Prefix List -- |
| 211 |
though the impact is similar). |
| 212 |
|
| 213 |
2. It should be noted that ND does not have a way to indicate a |
| 214 |
destination is "off-link". Rather, a destination is assumed to |
| 215 |
be off-link, unless there is explicit information indicating that |
| 216 |
it is on-link. Such information may later expire or be changed, |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 223 |
|
| 224 |
|
| 225 |
in which case a destination may revert back to being considered |
| 226 |
off-link, but that is different than there being an explicit |
| 227 |
mechanism for signaling that a destination is off-link. Redirect |
| 228 |
messages do not contain sufficient information to signal that an |
| 229 |
address is off-link. Instead, Redirect messages indicate a |
| 230 |
preferred next hop that is a more appropriate choice to use than |
| 231 |
the originator of the Redirect. |
| 232 |
|
| 233 |
3. IPv6 also defines the term "neighbor" to refer to nodes attached |
| 234 |
to the same link and that can send packets directly to each |
| 235 |
other. Received ND packets that pass the required validation |
| 236 |
tests can only come from a neighbor attached to the link on which |
| 237 |
the ND packet was received. Unfortunately, [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] is |
| 238 |
imprecise in its definition of "on-link" and states that a node |
| 239 |
considers an address to be on-link if: |
| 240 |
|
| 241 |
* a Neighbor Advertisement (NA) message is received for the |
| 242 |
(target) address, or |
| 243 |
|
| 244 |
* any Neighbor Discovery message is received from the address. |
| 245 |
|
| 246 |
Neither of these tests are acceptable definitions for an address |
| 247 |
to be considered as on-link as defined above, and this document |
| 248 |
deprecates and removes both of them from the formal definition of |
| 249 |
"on-link". Neither of these tests should be used as |
| 250 |
justification for modifying the Prefix List or Destination Cache |
| 251 |
for an address. |
| 252 |
|
| 253 |
The conceptual sending algorithm of [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] defines a Prefix |
| 254 |
List, Destination Cache, and Default Router List. The |
| 255 |
combination of Prefix List, Destination Cache, and Default Router |
| 256 |
List form what many implementations consider to be the IP data |
| 257 |
forwarding table for a host. Note that the Neighbor Cache is a |
| 258 |
separate data structure referenced by the Destination Cache, but |
| 259 |
entries in the Neighbor Cache are not necessarily in the |
| 260 |
Destination Cache. It is quite possible (and intentional) that |
| 261 |
entries be added to the Neighbor Cache for addresses that would |
| 262 |
not be considered on-link as defined above. For example, upon |
| 263 |
receipt of a valid NS, <a href="./rfc4861#section-7.2.3">Section 7.2.3 of [RFC4861]</a> states: |
| 264 |
|
| 265 |
If an entry does not already exist, the node SHOULD create a |
| 266 |
new one and set its reachability state to STALE as specified |
| 267 |
in <a href="#section-7.3.3">Section 7.3.3</a>. If an entry already exists, and the cached |
| 268 |
link-layer address differs from the one in the received Source |
| 269 |
Link-Layer option, the cached address should be replaced by |
| 270 |
the received address, and the entry's reachability state MUST |
| 271 |
be set to STALE. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 279 |
|
| 280 |
|
| 281 |
The intention of the above feature is to add an address to the |
| 282 |
Neighbor Cache, even though it might not be considered on-link |
| 283 |
per the Prefix List. The benefit of such a step is to have the |
| 284 |
receiver populate the Neighbor Cache with an address it will |
| 285 |
almost certainly be sending packets to shortly, thus avoiding the |
| 286 |
need for an additional round of ND to perform address resolution. |
| 287 |
But because there is no validation of the address being added to |
| 288 |
the Neighbor Cache, an intruder could spoof the address and cause |
| 289 |
a receiver to add an address for a remote site to its Neighbor |
| 290 |
Cache. This vulnerability is a specific instance of the broad |
| 291 |
set of attacks that are possible by an on-link neighbor |
| 292 |
[<a href="./rfc3756" title=""IPv6 Neighbor Discovery (ND) Trust Models and Threats"">RFC3756</a>]. This causes no problems in practice, so long as the |
| 293 |
entry only exists in the Neighbor Cache and the address is not |
| 294 |
considered to be on-link by the IP forwarding code (i.e., the |
| 295 |
address is not added to the Prefix List and is not marked as |
| 296 |
on-link in the Destination Cache). |
| 297 |
|
| 298 |
4. After the update to the on-link definition in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>], certain |
| 299 |
text from <a href="./rfc4861#section-7.2.3">Section 7.2.3 of [RFC4861]</a> may appear, upon a cursory |
| 300 |
examination, to be inconsistent with the updated definition of |
| 301 |
"on-link" because the text does not ensure that the source |
| 302 |
address is already deemed on-link through other methods: |
| 303 |
|
| 304 |
If the Source Address is not the unspecified address and, on |
| 305 |
link layers that have addresses, the solicitation includes a |
| 306 |
Source Link-Layer Address option, then the recipient SHOULD |
| 307 |
create or update the Neighbor Cache entry for the IP Source |
| 308 |
Address of the solicitation. |
| 309 |
|
| 310 |
Similarly, the following text from <a href="./rfc4861#section-6.2.6">Section 6.2.6 of [RFC4861]</a> may |
| 311 |
also seem inconsistent: |
| 312 |
|
| 313 |
If there is no existing Neighbor Cache entry for the |
| 314 |
solicitation's sender, the router creates one, installs the |
| 315 |
link-layer address and sets its reachability state to STALE as |
| 316 |
specified in <a href="#section-7.3.3">Section 7.3.3</a>. |
| 317 |
|
| 318 |
However, the text in the aforementioned sections of [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>], |
| 319 |
upon closer inspection, is actually consistent with the |
| 320 |
deprecation of the last two bullets of the on-link definition |
| 321 |
because there are two different ways in which on-link |
| 322 |
determination can affect the state of ND: through updating the |
| 323 |
Prefix List or updating the Destination Cache. Through |
| 324 |
deprecating the last two bullets of the on-link definition, the |
| 325 |
Prefix List is explicitly not to be changed when a node receives |
| 326 |
an NS, NA, or Router Solicitation (RS). The Neighbor Cache can |
| 327 |
still be updated through receipt of an NS, NA, or RS. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 335 |
|
| 336 |
|
| 337 |
5. [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] is written from the perspective of a host with a single |
| 338 |
interface on which Neighbor Discovery is run. All ND traffic |
| 339 |
(whether sent or received) traverses the single interface. On |
| 340 |
hosts with multiple interfaces, care must be taken to ensure that |
| 341 |
the scope of ND processing from one link stays local to that |
| 342 |
link. That is, when responding to an NS, the NA would be sent |
| 343 |
out on the same link on which it was received. Likewise, a host |
| 344 |
would not respond to a received NS for an address only assigned |
| 345 |
to an interface on a different link. Although implementations |
| 346 |
may choose to implement Neighbor Discovery using a single data |
| 347 |
structure that merges the Neighbor Caches of all interfaces, an |
| 348 |
implementation's behavior must be consistent with the above |
| 349 |
model. |
| 350 |
|
| 351 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Host Rules</span> |
| 352 |
|
| 353 |
A correctly implemented IPv6 host MUST adhere to the following rules: |
| 354 |
|
| 355 |
1. The assignment of an IPv6 address -- whether through IPv6 |
| 356 |
stateless address autoconfiguration [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>], DHCPv6 [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>], |
| 357 |
or manual configuration -- MUST NOT implicitly cause a prefix |
| 358 |
derived from that address to be treated as on-link and added to |
| 359 |
the Prefix List. A host considers a prefix to be on-link only |
| 360 |
through explicit means, such as those specified in the on-link |
| 361 |
definition in the Terminology section of [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] (as modified |
| 362 |
by this document) or via manual configuration. Note that the |
| 363 |
requirement for manually configured addresses is not explicitly |
| 364 |
mentioned in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 365 |
|
| 366 |
2. In the absence of other sources of on-link information, including |
| 367 |
Redirects, if the RA advertises a prefix with the on-link (L) bit |
| 368 |
set and later the Valid Lifetime expires, the host MUST then |
| 369 |
consider addresses of the prefix to be off-link, as specified by |
| 370 |
the PIO paragraph of <a href="./rfc4861#section-6.3.4">Section 6.3.4 of [RFC4861]</a>. |
| 371 |
|
| 372 |
3. In the absence of other sources of on-link information, including |
| 373 |
Redirects, if the RA advertises a prefix with the on-link (L) bit |
| 374 |
set and later the Valid Lifetime expires, the host MUST then |
| 375 |
update its Prefix List with respect to the entry. In most cases, |
| 376 |
this will result in the addresses covered by the prefix |
| 377 |
defaulting back to being considered off-link, as specified by the |
| 378 |
PIO paragraph of <a href="./rfc4861#section-6.3.4">Section 6.3.4 of [RFC4861]</a>. However, there are |
| 379 |
cases where an address could be covered by multiple entries in |
| 380 |
the Prefix List, where expiration of one prefix would result in |
| 381 |
destinations then being covered by a different entry. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 391 |
|
| 392 |
|
| 393 |
4. Implementations compliant with [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] MUST adhere to the |
| 394 |
following rules. If the Default Router List is empty and there |
| 395 |
is no other source of on-link information about any address or |
| 396 |
prefix: |
| 397 |
|
| 398 |
a. The host MUST NOT assume that all destinations are on-link. |
| 399 |
|
| 400 |
b. The host MUST NOT perform address resolution for non-link- |
| 401 |
local addresses. |
| 402 |
|
| 403 |
c. Since the host cannot assume the destination is on-link, and |
| 404 |
off-link traffic cannot be sent to a default router (since |
| 405 |
the Default Router List is empty), address resolution cannot |
| 406 |
be performed. This case is specified in the last paragraph |
| 407 |
of <a href="./rfc4943#section-4">Section 4 of [RFC4943]</a>: when there is no route to the |
| 408 |
destination, the host should send an ICMPv6 Destination |
| 409 |
Unreachable indication (for example, a locally delivered |
| 410 |
error message) as specified in the Terminology section of |
| 411 |
[<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 412 |
|
| 413 |
On-link information concerning particular addresses and prefixes |
| 414 |
can make those specific addresses and prefixes on-link, but does |
| 415 |
not change the default behavior mentioned above for addresses and |
| 416 |
prefixes not specified. [<a href="./rfc4943" title=""IPv6 Neighbor Discovery On-Link Assumption Considered Harmful"">RFC4943</a>] provides justification for |
| 417 |
these rules. |
| 418 |
|
| 419 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Observed Incorrect Implementation Behavior</span> |
| 420 |
|
| 421 |
One incorrect implementation behavior illustrates the severe |
| 422 |
consequences when the IPv6 subnet model is not understood by the |
| 423 |
implementers of several popular host operating systems. In an access |
| 424 |
concentrator network ([<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>]), a host receives a Router |
| 425 |
Advertisement message with no on-link prefix advertised. An address |
| 426 |
could be acquired through the DHCPv6 identity association for non- |
| 427 |
temporary addresses (IA_NA) option from [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] (which does not |
| 428 |
include a prefix length), or through manual configuration (if no |
| 429 |
prefix length is specified). The host incorrectly assumes an |
| 430 |
invented prefix is on-link. This invented prefix typically is a /64 |
| 431 |
that was written by the developer of the operating system network |
| 432 |
module API to any IPv6 application as a "default" prefix length when |
| 433 |
a length isn't specified. This may cause the API to seem to work in |
| 434 |
the case of a network interface initiating stateless address |
| 435 |
autoconfiguration (SLAAC); however, it can cause connectivity |
| 436 |
problems in Non-Broadcast Multi-Access (NBMA) networks. Having |
| 437 |
incorrectly assumed an invented prefix, the host performs address |
| 438 |
resolution when the host should send all non-link-local traffic to a |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 447 |
|
| 448 |
|
| 449 |
default router. Neither the router nor any other host will respond |
| 450 |
to the address resolution, preventing this host from sending IPv6 |
| 451 |
traffic. |
| 452 |
|
| 453 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Updates to <a href="./rfc4861">RFC 4861</a></span> |
| 454 |
|
| 455 |
This document deprecates the following two bullets from the on-link |
| 456 |
definition in <a href="./rfc4861#section-2.1">Section 2.1 of [RFC4861]</a>: |
| 457 |
|
| 458 |
o a Neighbor Advertisement message is received for the (target) |
| 459 |
address, or |
| 460 |
|
| 461 |
o any Neighbor Discovery message is received from the address. |
| 462 |
|
| 463 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Conclusion</span> |
| 464 |
|
| 465 |
This document clarifies and summarizes the relationship between links |
| 466 |
and subnet prefixes described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. Configuration of an IPv6 |
| 467 |
address does not imply the existence of corresponding on-link |
| 468 |
prefixes. One should also look at API considerations for prefix |
| 469 |
length as described in the last paragraph of <a href="./rfc4903#section-4.2">Section 4.2 of |
| 470 |
[RFC4903]</a>. This document also updates the definition of "on-link" |
| 471 |
from [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] by deprecating the last two bullets. |
| 472 |
|
| 473 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 474 |
|
| 475 |
This document addresses a security concern present in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. As |
| 476 |
a result, the last two bullets of the on-link definition in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] |
| 477 |
have been deprecated. US-CERT Vulnerability Note VU#472363 lists the |
| 478 |
implementations affected. |
| 479 |
|
| 480 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Contributors</span> |
| 481 |
|
| 482 |
Thomas Narten contributed significant text and provided substantial |
| 483 |
guidance to the production of this document. |
| 484 |
|
| 485 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span> |
| 486 |
|
| 487 |
Thanks (in alphabetical order) to Adeel Ahmed, Jari Arkko, Ralph |
| 488 |
Droms, Alun Evans, Dave Forster, Prashanth Krishnamurthy, Suresh |
| 489 |
Krishnan, Josh Littlefield, Bert Manfredi, David Miles, Madhu Sudan, |
| 490 |
Jinmei Tatuya, Dave Thaler, Bernie Volz, and Vlad Yasevich for their |
| 491 |
consistent input, ideas, and review during the production of this |
| 492 |
document. The security problem related to an NS message that |
| 493 |
provides one reason for invalidating a part of the on-link definition |
| 494 |
was found by David Miles. Jinmei Tatuya found the security problem |
| 495 |
to also exist with an RS message. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span> |
| 506 |
|
| 507 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span> |
| 508 |
|
| 509 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 510 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 511 |
|
| 512 |
[<a id="ref-RFC4861">RFC4861</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, |
| 513 |
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>, |
| 514 |
September 2007. |
| 515 |
|
| 516 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span> |
| 517 |
|
| 518 |
[<a id="ref-RFC0950">RFC0950</a>] Mogul, J. and J. Postel, "Internet Standard Subnetting |
| 519 |
Procedure", STD 5, <a href="./rfc950">RFC 950</a>, August 1985. |
| 520 |
|
| 521 |
[<a id="ref-RFC1122">RFC1122</a>] Braden, R., "Requirements for Internet Hosts - |
| 522 |
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>, October 1989. |
| 523 |
|
| 524 |
[<a id="ref-RFC2461">RFC2461</a>] Narten, T., Nordmark, E., and W. Simpson, "Neighbor |
| 525 |
Discovery for IP Version 6 (IPv6)", <a href="./rfc2461">RFC 2461</a>, |
| 526 |
December 1998. |
| 527 |
|
| 528 |
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., |
| 529 |
and M. Carney, "Dynamic Host Configuration Protocol for |
| 530 |
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 531 |
|
| 532 |
[<a id="ref-RFC3756">RFC3756</a>] Nikander, P., Kempf, J., and E. Nordmark, "IPv6 Neighbor |
| 533 |
Discovery (ND) Trust Models and Threats", <a href="./rfc3756">RFC 3756</a>, |
| 534 |
May 2004. |
| 535 |
|
| 536 |
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing |
| 537 |
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006. |
| 538 |
|
| 539 |
[<a id="ref-RFC4388">RFC4388</a>] Woundy, R. and K. Kinnear, "Dynamic Host Configuration |
| 540 |
Protocol (DHCP) Leasequery", <a href="./rfc4388">RFC 4388</a>, February 2006. |
| 541 |
|
| 542 |
[<a id="ref-RFC4632">RFC4632</a>] Fuller, V. and T. Li, "Classless Inter-domain Routing |
| 543 |
(CIDR): The Internet Address Assignment and Aggregation |
| 544 |
Plan", <a href="https://www.rfc-editor.org/bcp/bcp122">BCP 122</a>, <a href="./rfc4632">RFC 4632</a>, August 2006. |
| 545 |
|
| 546 |
[<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless |
| 547 |
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007. |
| 548 |
|
| 549 |
[<a id="ref-RFC4903">RFC4903</a>] Thaler, D., "Multi-Link Subnet Issues", <a href="./rfc4903">RFC 4903</a>, |
| 550 |
June 2007. |
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Singh, 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="./rfc5942">RFC 5942</a> IPv6 Subnet Model July 2010</span> |
| 559 |
|
| 560 |
|
| 561 |
[<a id="ref-RFC4943">RFC4943</a>] Roy, S., Durand, A., and J. Paugh, "IPv6 Neighbor |
| 562 |
Discovery On-Link Assumption Considered Harmful", |
| 563 |
<a href="./rfc4943">RFC 4943</a>, September 2007. |
| 564 |
|
| 565 |
Authors' Addresses |
| 566 |
|
| 567 |
Hemant Singh |
| 568 |
Cisco Systems, Inc. |
| 569 |
1414 Massachusetts Ave. |
| 570 |
Boxborough, MA 01719 |
| 571 |
USA |
| 572 |
|
| 573 |
Phone: +1 978 936 1622 |
| 574 |
EMail: [email protected] |
| 575 |
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a> |
| 576 |
|
| 577 |
|
| 578 |
Wes Beebee |
| 579 |
Cisco Systems, Inc. |
| 580 |
1414 Massachusetts Ave. |
| 581 |
Boxborough, MA 01719 |
| 582 |
USA |
| 583 |
|
| 584 |
Phone: +1 978 936 2030 |
| 585 |
EMail: [email protected] |
| 586 |
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a> |
| 587 |
|
| 588 |
Erik Nordmark |
| 589 |
Oracle, Inc. |
| 590 |
17 Network Circle |
| 591 |
Menlo Park, CA 94025 |
| 592 |
USA |
| 593 |
|
| 594 |
Phone: +1 650 786 2921 |
| 595 |
EMail: [email protected] |
| 596 |
|
| 597 |
|
| 598 |
|
| 599 |
|
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
Singh, et al. Standards Track [Page 11] |
| 613 |
</pre> |