| 1 |
<pre>Network Working Group D. Haskin |
| 2 |
Request for Comments: 2472 E. Allen |
| 3 |
Obsoletes: <a href="./rfc2023">2023</a> Bay Networks, Inc. |
| 4 |
Category: Standards Track December 1998 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">IP Version 6 over PPP</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This document specifies an Internet standards track protocol for the |
| 12 |
Internet community, and requests discussion and suggestions for |
| 13 |
improvements. Please refer to the current edition of the "Internet |
| 14 |
Official Protocol Standards" (STD 1) for the standardization state |
| 15 |
and status of this protocol. Distribution of this memo is unlimited. |
| 16 |
|
| 17 |
Copyright Notice |
| 18 |
|
| 19 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 20 |
|
| 21 |
Abstract |
| 22 |
|
| 23 |
The Point-to-Point Protocol (PPP) [<a href="#ref-1" title=""The Point-to-Point Protocol"">1</a>] provides a standard method of |
| 24 |
encapsulating Network Layer protocol information over point-to-point |
| 25 |
links. PPP also defines an extensible Link Control Protocol, and |
| 26 |
proposes a family of Network Control Protocols (NCPs) for |
| 27 |
establishing and configuring different network-layer protocols. |
| 28 |
|
| 29 |
This document defines the method for transmission of IP Version 6 [<a href="#ref-2" title=""Internet Protocol, Version 6 (IPv6) Specification"">2</a>] |
| 30 |
packets over PPP links as well as the Network Control Protocol (NCP) |
| 31 |
for establishing and configuring the IPv6 over PPP. It also specifies |
| 32 |
the method of forming IPv6 link-local addresses on PPP links. |
| 33 |
|
| 34 |
Table of Contents |
| 35 |
|
| 36 |
<a href="#section-1">1</a>. Introduction .......................................... <a href="#page-2">2</a> |
| 37 |
<a href="#section-1.1">1.1</a>. Specification of Requirements ..................... <a href="#page-2">2</a> |
| 38 |
<a href="#section-2">2</a>. Sending IPv6 Datagrams ................................ <a href="#page-2">2</a> |
| 39 |
<a href="#section-3">3</a>. A PPP Network Control Protocol for IPv6 ............... <a href="#page-3">3</a> |
| 40 |
<a href="#section-4">4</a>. IPV6CP Configuration Options .......................... <a href="#page-4">4</a> |
| 41 |
<a href="#section-4.1">4.1</a>. Interface-Identifier .............................. <a href="#page-4">4</a> |
| 42 |
<a href="#section-4.2">4.2</a>. IPv6-Compression-Protocol.......................... <a href="#page-9">9</a> |
| 43 |
<a href="#section-5">5</a>. Stateless Autoconfiguration and Link-Local Addresses .. <a href="#page-10">10</a> |
| 44 |
<a href="#section-6">6</a> Security Considerations ............................... <a href="#page-11">11</a> |
| 45 |
<a href="#section-7">7</a> Acknowledgments ....................................... <a href="#page-11">11</a> |
| 46 |
<a href="#section-8">8</a> Changes from <a href="./rfc2023">RFC-2023</a> ................................. <a href="#page-11">11</a> |
| 47 |
<a href="#section-9">9</a> References ............................................ <a href="#page-12">12</a> |
| 48 |
<a href="#section-10">10</a> Authors' Addresses .................................... <a href="#page-13">13</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-11">11</a> Full Copyright Statement .............................. <a href="#page-14">14</a> |
| 58 |
|
| 59 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 60 |
|
| 61 |
PPP has three main components: |
| 62 |
|
| 63 |
1) A method for encapsulating datagrams over serial links. |
| 64 |
|
| 65 |
2) A Link Control Protocol (LCP) for establishing, configuring, and |
| 66 |
testing the data-link connection. |
| 67 |
|
| 68 |
3) A family of Network Control Protocols (NCPs) for establishing and |
| 69 |
configuring different network-layer protocols. |
| 70 |
|
| 71 |
In order to establish communications over a point-to-point link, each |
| 72 |
end of the PPP link must first send LCP packets to configure and test |
| 73 |
the data link. After the link has been established and optional |
| 74 |
facilities have been negotiated as needed by the LCP, PPP must send |
| 75 |
NCP packets to choose and configure one or more network-layer |
| 76 |
protocols. Once each of the chosen network-layer protocols has been |
| 77 |
configured, datagrams from each network-layer protocol can be sent |
| 78 |
over the link. |
| 79 |
|
| 80 |
In this document, the NCP for establishing and configuring the IPv6 |
| 81 |
over PPP is referred as the IPv6 Control Protocol (IPV6CP). |
| 82 |
|
| 83 |
The link will remain configured for communications until explicit LCP |
| 84 |
or NCP packets close the link down, or until some external event |
| 85 |
occurs (power failure at the other end, carrier drop, etc.). |
| 86 |
|
| 87 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Specification of Requirements</span> |
| 88 |
|
| 89 |
In this document, several words are used to signify the requirements |
| 90 |
of the specification. |
| 91 |
|
| 92 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 93 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 94 |
document are to be interpreted as described in [<a href="#ref-7" title=""Key words for use in RFCs to Indicate Requirement Levels,"">7</a>]. |
| 95 |
|
| 96 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Sending IPv6 Datagrams</span> |
| 97 |
|
| 98 |
Before any IPv6 packets may be communicated, PPP MUST reach the |
| 99 |
Network-Layer Protocol phase, and the IPv6 Control Protocol MUST |
| 100 |
reach the Opened state. |
| 101 |
|
| 102 |
Exactly one IPv6 packet is encapsulated in the Information field of |
| 103 |
PPP Data Link Layer frames where the Protocol field indicates type |
| 104 |
hex 0057 (Internet Protocol Version 6). |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 111 |
|
| 112 |
|
| 113 |
The maximum length of an IPv6 packet transmitted over a PPP link is |
| 114 |
the same as the maximum length of the Information field of a PPP data |
| 115 |
link layer frame. PPP links supporting IPv6 MUST allow the |
| 116 |
information field at least as large as the minimum link MTU size |
| 117 |
required for IPv6 [<a href="#ref-2" title=""Internet Protocol, Version 6 (IPv6) Specification"">2</a>]. |
| 118 |
|
| 119 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. A PPP Network Control Protocol for IPv6</span> |
| 120 |
|
| 121 |
The IPv6 Control Protocol (IPV6CP) is responsible for configuring, |
| 122 |
enabling, and disabling the IPv6 protocol modules on both ends of the |
| 123 |
point-to-point link. IPV6CP uses the same packet exchange mechanism |
| 124 |
as the Link Control Protocol (LCP). IPV6CP packets may not be |
| 125 |
exchanged until PPP has reached the Network-Layer Protocol phase. |
| 126 |
IPV6CP packets received before this phase is reached should be |
| 127 |
silently discarded. |
| 128 |
|
| 129 |
The IPv6 Control Protocol is exactly the same as the Link Control |
| 130 |
Protocol [<a href="#ref-1" title=""The Point-to-Point Protocol"">1</a>] with the following exceptions: |
| 131 |
|
| 132 |
Data Link Layer Protocol Field |
| 133 |
|
| 134 |
Exactly one IPV6CP packet is encapsulated in the Information |
| 135 |
field of PPP Data Link Layer frames where the Protocol field |
| 136 |
indicates type hex 8057 (IPv6 Control Protocol). |
| 137 |
|
| 138 |
Code field |
| 139 |
|
| 140 |
Only Codes 1 through 7 (Configure-Request, Configure-Ack, |
| 141 |
Configure-Nak, Configure-Reject, Terminate-Request, |
| 142 |
Terminate-Ack and Code-Reject) are used. Other Codes should |
| 143 |
be treated as unrecognized and should result in Code-Rejects. |
| 144 |
|
| 145 |
Timeouts |
| 146 |
|
| 147 |
IPV6CP packets may not be exchanged until PPP has reached the |
| 148 |
Network-Layer Protocol phase. An implementation should be |
| 149 |
prepared to wait for Authentication and Link Quality |
| 150 |
Determination to finish before timing out waiting for a |
| 151 |
Configure-Ack or other response. It is suggested that an |
| 152 |
implementation give up only after user intervention or a |
| 153 |
configurable amount of time. |
| 154 |
|
| 155 |
Configuration Option Types |
| 156 |
|
| 157 |
IPV6CP has a distinct set of Configuration Options. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IPV6CP Configuration Options</span> |
| 170 |
|
| 171 |
IPV6CP Configuration Options allow negotiation of desirable IPv6 |
| 172 |
parameters. IPV6CP uses the same Configuration Option format defined |
| 173 |
for LCP [<a href="#ref-1" title=""The Point-to-Point Protocol"">1</a>], with a separate set of Options. If a Configuration |
| 174 |
Option is not included in a Configure-Request packet, the default |
| 175 |
value for that Configuration Option is assumed. |
| 176 |
|
| 177 |
Up-to-date values of the IPV6CP Option Type field are specified in |
| 178 |
the most recent "Assigned Numbers" RFC [<a href="#ref-4" title=""Assigned Numbers"">4</a>]. Current values are |
| 179 |
assigned as follows: |
| 180 |
|
| 181 |
1 Interface-Identifier |
| 182 |
2 IPv6-Compression-Protocol |
| 183 |
|
| 184 |
The only IPV6CP options defined in this document are Interface- |
| 185 |
Identifier and IPv6-Compression-Protocol. Any other IPV6CP |
| 186 |
configuration options that can be defined over time are to be defined |
| 187 |
in separate documents. |
| 188 |
|
| 189 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Interface-Identifier</span> |
| 190 |
|
| 191 |
Description |
| 192 |
|
| 193 |
This Configuration Option provides a way to negotiate a unique 64- |
| 194 |
bit interface identifier to be used for the address |
| 195 |
autoconfiguration [<a href="#ref-3" title=""IPv6 Stateless Address Autoconfiguration"">3</a>] at the local end of the link (see <a href="#section-5">section 5</a>). |
| 196 |
A Configure-Request MUST contain exactly one instance of the |
| 197 |
Interface-Identifier option [<a href="#ref-1" title=""The Point-to-Point Protocol"">1</a>]. The interface identifier MUST be |
| 198 |
unique within the PPP link; i.e. upon completion of the |
| 199 |
negotiation different Interface-Identifier values are to be |
| 200 |
selected for the ends of the PPP link. The interface identifier |
| 201 |
MAY also be unique over a broader scope. |
| 202 |
|
| 203 |
Before this Configuration Option is requested, an implementation |
| 204 |
chooses its tentative Interface-Identifier. The non-zero value of |
| 205 |
the tentative Interface-Identifier SHOULD be chosen such that the |
| 206 |
value is both unique to the link and, if possible, consistently |
| 207 |
reproducible across initializations of the IPV6CP finite state |
| 208 |
machine (administrative Close and reOpen, reboots, etc). The |
| 209 |
rationale for preferring a consistently reproducible unique |
| 210 |
interface identifier to a completely random interface identifier is |
| 211 |
to provide stability to global scope addresses that can be formed |
| 212 |
from the interface identifier. |
| 213 |
|
| 214 |
Assuming that interface identifier bits are numbered from 0 to 63 |
| 215 |
in canonical bit order where the most significant bit is the bit |
| 216 |
number 0, the bit number 6 is the "u" bit (universal/local bit |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 223 |
|
| 224 |
|
| 225 |
in IEEE EUI-64 [<a href="#ref-5" title=""Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority"">5</a>] terminology) which indicates whether or not the |
| 226 |
interface identifier is based on a globally unique IEEE identifier |
| 227 |
(EUI-48 or EUI-64 [<a href="#ref-5" title=""Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority"">5</a>]) (see the case 1 below). It is set to |
| 228 |
one (1) if a globally unique IEEE identifier is used to derive |
| 229 |
the interface identifier, and it is set to zero (0) otherwise. |
| 230 |
|
| 231 |
The following are methods for choosing the tentative Interface |
| 232 |
Identifier in the preference order: |
| 233 |
|
| 234 |
1) If an IEEE global identifier (EUI-48 or EUI-64) is |
| 235 |
available anywhere on the node, it should be used to construct |
| 236 |
the tentative Interface-Identifier due to its uniqueness |
| 237 |
properties. When extracting an IEEE global identifier from |
| 238 |
another device on the node, care should be taken to that the |
| 239 |
extracted identifier is presented in canonical ordering [<a href="#ref-8" title=""A Caution On The Canonical Ordering Of Link-Layer Addresses"">8</a>]. |
| 240 |
|
| 241 |
The only transformation from an EUI-64 identifier is to invert |
| 242 |
the "u" bit (universal/local bit in IEEE EUI-64 terminology). |
| 243 |
For example, for a globally unique EUI-64 identifier of the |
| 244 |
form: |
| 245 |
|
| 246 |
most-significant least-significant |
| 247 |
bit bit |
| 248 |
|0 1|1 3|3 4|4 6| |
| 249 |
|0 5|6 1|2 7|8 3| |
| 250 |
+----------------+----------------+----------------+----------------+ |
| 251 |
|cccccc0gcccccccc|cccccccceeeeeeee|eeeeeeeeeeeeeeee|eeeeeeeeeeeeeeee| |
| 252 |
+----------------+----------------+----------------+----------------+ |
| 253 |
|
| 254 |
where "c" are the bits of the assigned company_id, "0" is the |
| 255 |
value of the universal/local bit to indicate global scope, "g" |
| 256 |
is group/individual bit, and "e" are the bits of the extension |
| 257 |
identifier, |
| 258 |
|
| 259 |
the IPv6 interface identifier would be of the form: |
| 260 |
|
| 261 |
most-significant least-significant |
| 262 |
bit bit |
| 263 |
|0 1|1 3|3 4|4 6| |
| 264 |
|0 5|6 1|2 7|8 3| |
| 265 |
+----------------+----------------+----------------+----------------+ |
| 266 |
|cccccc1gcccccccc|cccccccceeeeeeee|eeeeeeeeeeeeeeee|eeeeeeeeeeeeeeee| |
| 267 |
+----------------+----------------+----------------+----------------+ |
| 268 |
|
| 269 |
The only change is inverting the value of the universal/local |
| 270 |
bit. |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 279 |
|
| 280 |
|
| 281 |
In the case of a EUI-48 identifier, it is first converted to the |
| 282 |
EUI-64 format by inserting two bytes, with hexadecimal values of |
| 283 |
0xFF and 0xFE, in the middle of the 48 bit MAC (between the |
| 284 |
company_id and extension-identifier portions of the EUI-48 |
| 285 |
value). For example, for a globally unique 48 bit EUI-48 |
| 286 |
identifier of the form: |
| 287 |
|
| 288 |
most-significant least-significant |
| 289 |
bit bit |
| 290 |
|0 1|1 3|3 4| |
| 291 |
|0 5|6 1|2 7| |
| 292 |
+----------------+----------------+----------------+ |
| 293 |
|cccccc0gcccccccc|cccccccceeeeeeee|eeeeeeeeeeeeeeee| |
| 294 |
+----------------+----------------+----------------+ |
| 295 |
|
| 296 |
where "c" are the bits of the assigned company_id, "0" is the |
| 297 |
value of the universal/local bit to indicate global scope, "g" |
| 298 |
is group/individual bit, and "e" are the bits of the extension |
| 299 |
identifier, the IPv6 interface identifier would be of the form: |
| 300 |
|
| 301 |
most-significant least-significant |
| 302 |
bit bit |
| 303 |
|0 1|1 3|3 4|4 6| |
| 304 |
|0 5|6 1|2 7|8 3| |
| 305 |
+----------------+----------------+----------------+----------------+ |
| 306 |
|cccccc1gcccccccc|cccccccc11111111|11111110eeeeeeee|eeeeeeeeeeeeeeee| |
| 307 |
+----------------+----------------+----------------+----------------+ |
| 308 |
|
| 309 |
2) If an IEEE global identifier is not available a different source |
| 310 |
of uniqueness should be used. Suggested sources of uniqueness |
| 311 |
include link-layer addresses, machine serial numbers, et cetera. |
| 312 |
|
| 313 |
In this case the "u" bit of the interface identifier MUST be set |
| 314 |
to zero (0). |
| 315 |
|
| 316 |
3) If a good source of uniqueness cannot be found, it is |
| 317 |
recommended that a random number be generated. In this case the |
| 318 |
"u" bit of the interface identifier MUST be set to zero (0). |
| 319 |
|
| 320 |
Good sources [<a href="#ref-1" title=""The Point-to-Point Protocol"">1</a>] of uniqueness or randomness are required for the |
| 321 |
Interface-Identifier negotiation to succeed. If neither a unique |
| 322 |
number or a random number can be generated it is recommended that a |
| 323 |
zero value be used for the Interface-Identifier transmitted in the |
| 324 |
Configure-Request. In this case the PPP peer may provide a valid |
| 325 |
non-zero Interface-Identifier in its response as described below. |
| 326 |
Note that if at least one of the PPP peers is able to generate |
| 327 |
separate non-zero numbers for itself and its peer, the identifier |
| 328 |
negotiation will succeed. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 335 |
|
| 336 |
|
| 337 |
When a Configure-Request is received with the Interface-Identifier |
| 338 |
Configuration Option and the receiving peer implements this option, |
| 339 |
the received Interface-Identifier is compared with the Interface- |
| 340 |
Identifier of the last Configure-Request sent to the peer. |
| 341 |
Depending on the result of the comparison an implementation MUST |
| 342 |
respond in one of the following ways: |
| 343 |
|
| 344 |
If the two Interface-Identifiers are different but the received |
| 345 |
Interface-Identifier is zero, a Configure-Nak is sent with a non- |
| 346 |
zero Interface-Identifier value suggested for use by the remote |
| 347 |
peer. Such a suggested Interface-Identifier MUST be different from |
| 348 |
the Interface-Identifier of the last Configure-Request sent to the |
| 349 |
peer. It is recommended that the value suggested be consistently |
| 350 |
reproducible across initializations of the IPV6CP finite state |
| 351 |
machine (administrative Close and reOpen, reboots, etc). The "u" |
| 352 |
universal/local) bit of the suggested identifier MUST be set to |
| 353 |
zero (0) regardless of its source unless the globally unique EUI- |
| 354 |
48/EUI-64 derived identifier is provided for the exclusive use by |
| 355 |
the remote peer. |
| 356 |
|
| 357 |
If the two Interface-Identifiers are different and the received |
| 358 |
Interface-Identifier is not zero, the Interface-Identifier MUST be |
| 359 |
acknowledged, i.e. a Configure-Ack is sent with the requested |
| 360 |
Interface-Identifier, meaning that the responding peer agrees with |
| 361 |
the Interface-Identifier requested. |
| 362 |
|
| 363 |
If the two Interface-Identifiers are equal and are not zero, a |
| 364 |
Configure-Nak MUST be sent specifying a different non-zero |
| 365 |
Interface-Identifier value suggested for use by the remote peer. |
| 366 |
It is recommended that the value suggested be consistently |
| 367 |
reproducible across initializations of the IPV6CP finite state |
| 368 |
machine (administrative Close and reOpen, reboots, etc). The "u" |
| 369 |
universal/local) bit of the suggested identifier MUST be set to |
| 370 |
zero (0) regardless of its source unless the globally unique EUI- |
| 371 |
48/EUI-64 derived identifier is provided for the exclusive use by |
| 372 |
the remote peer. |
| 373 |
|
| 374 |
If the two Interface-Identifiers are equal to zero, the Interface- |
| 375 |
Identifiers negotiation MUST be terminated by transmitting the |
| 376 |
Configure-Reject with the Interface-Identifier value set to zero. |
| 377 |
In this case a unique Interface-Identifier can not be negotiated. |
| 378 |
|
| 379 |
If a Configure-Request is received with the Interface-Identifier |
| 380 |
Configuration Option and the receiving peer does not implement this |
| 381 |
option, Configure-Rej is sent. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 391 |
|
| 392 |
|
| 393 |
A new Configure-Request SHOULD NOT be sent to the peer until normal |
| 394 |
processing would cause it to be sent (that is, until a Configure- |
| 395 |
Nak is received or the Restart timer runs out). |
| 396 |
|
| 397 |
A new Configure-Request MUST NOT contain the Interface-Identifier |
| 398 |
option if a valid Interface-Identifier Configure-Reject is |
| 399 |
received. |
| 400 |
|
| 401 |
Reception of a Configure-Nak with a suggested Interface-Identifier |
| 402 |
different from that of the last Configure-Nak sent to the peer |
| 403 |
indicates a unique Interface-Identifier. In this case a new |
| 404 |
Configure-Request MUST be sent with the identifier value suggested |
| 405 |
in the last Configure-Nak from the peer. But if the received |
| 406 |
Interface-Identifier is equal to the one sent in the last |
| 407 |
Configure-Nak, a new Interface-Identifier MUST be chosen. In this |
| 408 |
case, a new Configure-Request SHOULD be sent with the new tentative |
| 409 |
Interface-Identifier. This sequence (transmit Configure-Request, |
| 410 |
receive Configure-Request, transmit Configure-Nak, receive |
| 411 |
Configure-Nak) might occur a few times, but it is extremely |
| 412 |
unlikely to occur repeatedly. More likely, the Interface- |
| 413 |
Identifiers chosen at either end will quickly diverge, terminating |
| 414 |
the sequence. |
| 415 |
|
| 416 |
If negotiation of the Interface-Identifier is required, and the |
| 417 |
peer did not provide the option in its Configure-Request, the |
| 418 |
option SHOULD be appended to a Configure-Nak. The tentative value |
| 419 |
of the Interface-Identifier given must be acceptable as the remote |
| 420 |
Interface-Identifier; i.e. it should be different from the |
| 421 |
identifier value selected for the local end of the PPP link. The |
| 422 |
next Configure-Request from the peer may include this option. If |
| 423 |
the next Configure-Request does not include this option the peer |
| 424 |
MUST NOT send another Configure-Nak with this option included. It |
| 425 |
should assume that the peer's implementation does not support this |
| 426 |
option. |
| 427 |
|
| 428 |
By default, an implementation SHOULD attempt to negotiate the |
| 429 |
Interface-Identifier for its end of the PPP connection. |
| 430 |
|
| 431 |
A summary of the Interface-Identifier Configuration Option format is |
| 432 |
shown below. The fields are transmitted from left to right. |
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 447 |
|
| 448 |
|
| 449 |
0 1 2 3 |
| 450 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 451 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 452 |
| Type | Length | Interface-Identifier (MS Bytes) |
| 453 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 454 |
Interface-Identifier (cont) |
| 455 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 456 |
Interface-Identifier (LS Bytes) | |
| 457 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 458 |
|
| 459 |
Type |
| 460 |
|
| 461 |
1 |
| 462 |
|
| 463 |
Length |
| 464 |
|
| 465 |
10 |
| 466 |
|
| 467 |
Interface-Identifier |
| 468 |
|
| 469 |
The 64-bit Interface-Identifier which is very likely to be unique on |
| 470 |
the link or zero if a good source of uniqueness can not be found. |
| 471 |
|
| 472 |
Default |
| 473 |
|
| 474 |
If no valid interface identifier can be successfully negotiated, no |
| 475 |
default Interface-Identifier value should be assumed. The procedures |
| 476 |
for recovering from such a case are unspecified. One approach is to |
| 477 |
manually configure the interface identifier of the interface. |
| 478 |
|
| 479 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. IPv6-Compression-Protocol</span> |
| 480 |
|
| 481 |
Description |
| 482 |
|
| 483 |
This Configuration Option provides a way to negotiate the use of a |
| 484 |
specific IPv6 packet compression protocol. The |
| 485 |
IPv6-Compression-Protocol Configuration Option is used to indicate the |
| 486 |
ability to receive compressed packets. Each end of the link must |
| 487 |
separately request this option if bi-directional compression is |
| 488 |
desired. By default, compression is not enabled. |
| 489 |
|
| 490 |
IPv6 compression negotiated with this option is specific to IPv6 |
| 491 |
datagrams and is not to be confused with compression resulting from |
| 492 |
negotiations via Compression Control Protocol (CCP), which potentially |
| 493 |
effect all datagrams. |
| 494 |
|
| 495 |
A summary of the IPv6-Compression-Protocol Configuration Option format |
| 496 |
is shown below. The fields are transmitted from left to right. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 503 |
|
| 504 |
|
| 505 |
0 1 2 3 |
| 506 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 507 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 508 |
| Type | Length | IPv6-Compression-Protocol | |
| 509 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 510 |
| Data ... |
| 511 |
+-+-+-+-+ |
| 512 |
|
| 513 |
Type |
| 514 |
|
| 515 |
2 |
| 516 |
|
| 517 |
Length |
| 518 |
|
| 519 |
>= 4 |
| 520 |
|
| 521 |
IPv6-Compression-Protocol |
| 522 |
|
| 523 |
The IPv6-Compression-Protocol field is two octets and indicates |
| 524 |
the compression protocol desired. Values for this field are |
| 525 |
always the same as the PPP Data Link Layer Protocol field values |
| 526 |
for that same compression protocol. |
| 527 |
|
| 528 |
No IPv6-Compression-Protocol field values are currently assigned. |
| 529 |
Specific assignments will be made in documents that define |
| 530 |
specific compression algorithms. |
| 531 |
|
| 532 |
Data |
| 533 |
|
| 534 |
The Data field is zero or more octets and contains additional |
| 535 |
data as determined by the particular compression protocol. |
| 536 |
|
| 537 |
Default |
| 538 |
|
| 539 |
No IPv6 compression protocol enabled. |
| 540 |
|
| 541 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Stateless Autoconfiguration and Link-Local Addresses</span> |
| 542 |
|
| 543 |
The Interface Identifier of IPv6 unicast addresses [<a href="#ref-6" title=""IP Version 6 Addressing Architecture"">6</a>] of a PPP |
| 544 |
interface, SHOULD be negotiated in the IPV6CP phase of the PPP |
| 545 |
connection setup (see <a href="#section-4.1">section 4.1</a>). If no valid Interface Identifier |
| 546 |
has been successfully negotiated, procedures for recovering from such |
| 547 |
a case are unspecified. One approach is to manually configure the |
| 548 |
Interface Identifier of the interface. |
| 549 |
|
| 550 |
As long as the Interface Identifier is negotiated in the IPV6CP phase |
| 551 |
of the PPP connection setup, it is redundant to perform duplicate |
| 552 |
address detection as a part of the IPv6 Stateless Autoconfiguration |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 559 |
|
| 560 |
|
| 561 |
protocol [<a href="#ref-3" title=""IPv6 Stateless Address Autoconfiguration"">3</a>]. Therefore it is recommended that for PPP links with |
| 562 |
the IPV6CP Interface-Identifier option enabled the default value of |
| 563 |
the DupAddrDetectTransmits autoconfiguration variable [<a href="#ref-3" title=""IPv6 Stateless Address Autoconfiguration"">3</a>] be zero. |
| 564 |
|
| 565 |
Link-local addresses of PPP interfaces have the following format: |
| 566 |
|
| 567 |
| 10 bits | 54 bits | 64 bits | |
| 568 |
+----------+------------------------+-----------------------------+ |
| 569 |
|1111111010| 0 | Interface Identifier | |
| 570 |
+----------+------------------------+-----------------------------+ |
| 571 |
|
| 572 |
The most significant 10 bits of the address is the Link-Local prefix |
| 573 |
FE80::. 54 zero bits pad out the address between the Link-Local |
| 574 |
prefix and the Interface Identifier fields. |
| 575 |
|
| 576 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 577 |
|
| 578 |
The IPv6 Control Protocol extension to PPP can be used with all |
| 579 |
defined PPP authentication and encryption mechanisms. |
| 580 |
|
| 581 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span> |
| 582 |
|
| 583 |
This document borrows from the Magic-Number LCP option and as such is |
| 584 |
partially based on previous work done by the PPP working group. |
| 585 |
|
| 586 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Changes from <a href="./rfc2023">RFC-2023</a></span> |
| 587 |
|
| 588 |
The following changes were made from <a href="./rfc2023">RFC-2023</a> "IP Version 6 over |
| 589 |
PPP": |
| 590 |
|
| 591 |
- Changed to use "Interface Identifier" instead of the "Interface |
| 592 |
Token" term according to the terminology adopted in [<a href="#ref-6" title=""IP Version 6 Addressing Architecture"">6</a>]. |
| 593 |
|
| 594 |
- Increased the size of Interface Identifier to 64 bits according to |
| 595 |
the newly adopted IPv6 addressing architecture [<a href="#ref-6" title=""IP Version 6 Addressing Architecture"">6</a>]. |
| 596 |
|
| 597 |
- Added methods for selection of an interface identifier that is |
| 598 |
consistently reproducible across initializations of the IPV6CP |
| 599 |
finite state machine. |
| 600 |
|
| 601 |
- Added the interface identifier selection methods for generating |
| 602 |
globally unique interface identifier from an unique an IEEE global |
| 603 |
identifier when it is available anywhere on the node. |
| 604 |
|
| 605 |
- Changed to send a Configure-Nak instead a Configure-Ack in response |
| 606 |
to receiving a Configure-Request with a zero Interface-Identifier |
| 607 |
value. |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 615 |
|
| 616 |
|
| 617 |
- Replaced the value assignment of the IPv6-Compression-Protocol |
| 618 |
field of the IPv6-Compression-Protocol Configuration option with |
| 619 |
the text stating that no IPv6-Compression-Protocol field values are |
| 620 |
currently assigned and that specific assignments will be made in |
| 621 |
documents that define specific compression algorithms. |
| 622 |
|
| 623 |
- Added new and updated references. |
| 624 |
|
| 625 |
- Minor text clarifications and improvements. |
| 626 |
|
| 627 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 628 |
|
| 629 |
[<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol", STD 51, <a href="./rfc1661">RFC</a> |
| 630 |
<a href="./rfc1661">1661</a>, July 1994. |
| 631 |
|
| 632 |
[<a id="ref-2">2</a>] Deering, S., and R. Hinden, Editors, "Internet Protocol, Version |
| 633 |
6 (IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998. |
| 634 |
|
| 635 |
[<a id="ref-3">3</a>] Thomson, S., and T. Narten, "IPv6 Stateless Address |
| 636 |
Autoconfiguration", <a href="./rfc2462">RFC 2462</a>, December 1998. |
| 637 |
|
| 638 |
[<a id="ref-4">4</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC</a> |
| 639 |
<a href="./rfc1700">1700</a>, October 1994. See also: <a href="http://www.iana.org/numbers.html">http://www.iana.org/numbers.html</a> |
| 640 |
|
| 641 |
[<a id="ref-5">5</a>] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) |
| 642 |
Registration Authority", |
| 643 |
<a href="http://standards.ieee.org/db/oui/tutorials/EUI64.html">http://standards.ieee.org/db/oui/tutorials/EUI64.html</a>, March |
| 644 |
1997. |
| 645 |
|
| 646 |
[<a id="ref-6">6</a>] Hinden, R., and S. Deering, "IP Version 6 Addressing |
| 647 |
Architecture", <a href="./rfc2373">RFC 2373</a>, July 1998. |
| 648 |
|
| 649 |
[<a id="ref-7">7</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 650 |
Levels," <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 651 |
|
| 652 |
[<a id="ref-8">8</a>] Narten T., and C. Burton, "A Caution On The Canonical Ordering |
| 653 |
Of Link-Layer Addresses", <a href="./rfc2469">RFC 2469</a>, December 1998. |
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Authors' Addresses</span> |
| 674 |
|
| 675 |
Dimitry Haskin |
| 676 |
Bay Networks, Inc. |
| 677 |
600 Technology Park |
| 678 |
Billerica, MA 01821 |
| 679 |
|
| 680 |
EMail: [email protected] |
| 681 |
|
| 682 |
|
| 683 |
Ed Allen |
| 684 |
Bay Networks, Inc. |
| 685 |
600 Technology Park |
| 686 |
Billerica, MA 01821 |
| 687 |
|
| 688 |
EMail: [email protected] |
| 689 |
|
| 690 |
|
| 691 |
|
| 692 |
|
| 693 |
|
| 694 |
|
| 695 |
|
| 696 |
|
| 697 |
|
| 698 |
|
| 699 |
|
| 700 |
|
| 701 |
|
| 702 |
|
| 703 |
|
| 704 |
|
| 705 |
|
| 706 |
|
| 707 |
|
| 708 |
|
| 709 |
|
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Haskin & Allen 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="./rfc2472">RFC 2472</a> IP Version 6 over PPP December 1998</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Full Copyright Statement</span> |
| 730 |
|
| 731 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 732 |
|
| 733 |
This document and translations of it may be copied and furnished to |
| 734 |
others, and derivative works that comment on or otherwise explain it |
| 735 |
or assist in its implementation may be prepared, copied, published |
| 736 |
and distributed, in whole or in part, without restriction of any |
| 737 |
kind, provided that the above copyright notice and this paragraph are |
| 738 |
included on all such copies and derivative works. However, this |
| 739 |
document itself may not be modified in any way, such as by removing |
| 740 |
the copyright notice or references to the Internet Society or other |
| 741 |
Internet organizations, except as needed for the purpose of |
| 742 |
developing Internet standards in which case the procedures for |
| 743 |
copyrights defined in the Internet Standards process must be |
| 744 |
followed, or as required to translate it into languages other than |
| 745 |
English. |
| 746 |
|
| 747 |
The limited permissions granted above are perpetual and will not be |
| 748 |
revoked by the Internet Society or its successors or assigns. |
| 749 |
|
| 750 |
This document and the information contained herein is provided on an |
| 751 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 752 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 753 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 754 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 755 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 756 |
|
| 757 |
|
| 758 |
|
| 759 |
|
| 760 |
|
| 761 |
|
| 762 |
|
| 763 |
|
| 764 |
|
| 765 |
|
| 766 |
|
| 767 |
|
| 768 |
|
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
Haskin & Allen Standards Track [Page 14] |
| 781 |
</pre> |