idnits 2.17.1 draft-simpson-ipv6-discov-formats-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 300 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 77: '... The Extensions SHOULD be included in...' RFC 2119 keyword, line 81: '...e Reserved field MUST be zero on trans...' RFC 2119 keyword, line 82: '... MUST be ignored on receipt. Future...' RFC 2119 keyword, line 88: '...ral Solicitation MUST contain at least...' RFC 2119 keyword, line 111: '...ng interface. It MUST NOT contain the...' (25 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 203 has weird spacing: '... Number the n...' == Line 830 has weird spacing: '... Number the l...' == Line 995 has weird spacing: '...Address the...' == Line 1040 has weird spacing: '...ticator var...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 1994) is 10754 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'D-Send' -- Possible downref: Non-RFC (?) normative reference: ref. 'Eastlake' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6-Address' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6-ICMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'Mobility' ** Obsolete normative reference: RFC 1305 (Obsoleted by RFC 5905) ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) ** Downref: Normative reference to an Informational RFC: RFC 1701 Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group W A Simpson 2 Internet Draft Daydreamer 3 expires in six months November 1994 5 IPv6 Neighbor Discovery -- ICMP Message Formats 6 draft-simpson-ipv6-discov-formats-01.txt | 8 Status of this Memo 10 This document is a submission to the IPng Working Group of the 11 Internet Engineering Task Force (IETF). Comments should be submitted 12 to the ipng@sunroof.eng.sun.com mailing list. 14 Distribution of this memo is unlimited. 16 This document is an Internet-Draft. Internet Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its Areas, 18 and its Working Groups. Note that other groups may also distribute 19 working documents as Internet Drafts. 21 Internet Drafts are draft documents valid for a maximum of six 22 months, and may be updated, replaced, or obsoleted by other documents 23 at any time. It is not appropriate to use Internet Drafts as 24 reference material, or to cite them other than as a ``working draft'' 25 or ``work in progress.'' 27 To learn the current status of any Internet-Draft, please check the 28 ``1id-abstracts.txt'' listing contained in the internet-drafts Shadow 29 Directories on ds.internic.net (US East Coast), nic.nordu.net 30 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 31 Rim). 33 Abstract 35 This document specifies ICMP messages for identification of and | 36 forwarding to adjacent IPv6 nodes, including Mobility, Next Hop | 37 Determination and Router Discovery. 39 1. Additional ICMP Packets 41 The datagram format and basic facilities are already defined for ICMP | 42 as modified for IPv6 [IPv6-ICMP]. 44 Up-to-date values of the ICMP Type field are specified in the most | 45 recent "Assigned Numbers" [RFC-1700]. This document concerns the 46 following values: 48 33 Where-Are-You Solicitations 49 34 I-Am-Here Advertisements 50 35 Mobile Registration Request 51 36 Mobile Registration Reply 53 1.1. Where-Are-You Solicitations 55 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 56 | Type | Code | Checksum | 57 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 58 | Reserved | | 59 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 60 | Extensions ... 61 +-+-+-+-+-+-+-+-+-+-+-+- 63 Type 33 65 Code Up-to-date values are specified in the most recent | 66 "Assigned Numbers" [RFC-1700]. Current values are 67 assigned as follows: 69 0 RESERVED 70 1 General 71 2 Router 72 3 Service (reserved) | 74 Checksum The ICMP Checksum. 76 Extensions zero or more Extensions. This field is variable in | 77 length. The Extensions SHOULD be included in the | 78 order described. These Extensions are described in | 79 a later chapter. 81 The contents of the Reserved field MUST be zero on transmission, and 82 MUST be ignored on receipt. Future backward-compatible changes to 83 the protocol may specify the contents of the Reserved field or of 84 additional octets at the end of the message. 86 1.1.1. General Solicitation 88 The General Solicitation MUST contain at least the following values: 90 Link Header (if any): | 92 Destination the link equivalent of the Solicited-Nodes IPv6 | 93 Multicast Address. The mapping is described in | 94 [IPv6-Address]. | 96 IPv6 Header: 98 Destination the calculated Solicited-Nodes IPv6 Multicast | 99 Address. The scope is intra-link. | 101 This is calculated by starting with the | 102 exclusive-or of each byte of the target IPv6 | 103 Unicast Address, then adding the result to the | 104 base Solicited-Nodes multicast (FF02::7:0). | 106 For example, to calculate the destination value | 107 for target A::B:C, the exclusive-or is E. The | 108 calculated destination would be FF02::7:E. 110 Source any IPv6 Unicast Address associated with the | 111 sending interface. It MUST NOT contain the 112 Unspecified Address. | 114 Hop Limit 1 116 ICMP fields: 118 Code 1 for General Solicitation. 120 Extensions: 122 Other-Identifier any IPv6 Unicast Address of the target. The | 123 Prefix Size and Metric are always zero. | 125 Maximum-Receive-Unit | 126 for interfaces which do not have a fixed hardware | 127 MTU. 129 Media-Access for interfaces which are not point-to-point 130 links. | 132 Node-Heard for each Router Advertisement that has been 133 heard, in order of preference. 135 In the unlikely event that not all extensions fit in a single 136 solicitation, as constrained by the MTU of the link, the remaining 137 extensions are removed. 139 The use of the General Solicitation is described in [D-Send]. | 141 1.1.2. Router Solicitation 143 The Router Solicitation MUST contain at least the following values: 145 Link Header (if any): | 147 Destination the link equivalent of the All-Routers IPv6 | 148 Multicast Address. The mapping is described in | 149 [IPv6-Address]. | 151 IPv6 Header: 153 Destination the All-Routers IPv6 Multicast Address (FF02::3). | 154 The scope is intra-link. 156 Source any IPv6 Unicast Address associated with the | 157 sending interface. It MAY contain the 158 Unspecified Address, when the node has not yet | 159 determined an IPv6 Unicast Address. | 161 Hop Limit 1 163 ICMP fields: 165 Code 2 for Router Solicitation. | 167 Extensions: | 169 Maximum-Receive-Unit | 170 for interfaces which do not have a fixed hardware | 171 MTU. | 173 Media-Access for interfaces which are not point-to-point | 174 links. 176 The use of the Router Solicitation is described in [D-Send]. | 178 1.2. I-Am-Here Advertisements | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Type | Code | Checksum | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Sequence Number | LifeTime | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Extensions ... 186 +-+-+-+-+-+-+-+-+-+-+-+- 188 Type 34 190 Code Up-to-date values are specified in the most recent | 191 "Assigned Numbers" [RFC-1700]. Current values are 192 assigned as follows: 194 0 RESERVED 195 1 General 196 2 Router 197 3 Service (reserved) | 198 4 Local Redirect 199 5 Remote Redirect 201 Checksum The ICMP Checksum. 203 Sequence Number the number of Advertisement messages sent since the | 204 node was initialized. The value MUST include this | 205 advertisement. That is, the first Advertisement 206 contains the value one, and the value zero indicates 207 that the number has rolled over. 209 LifeTime the seconds remaining before the advertised | 210 information is considered expired. The maximum time 211 is approximately 18.2 hours. 213 Extensions zero or more Extensions. This field is variable in | 214 length. The Extensions SHOULD be included in the | 215 order described. These Extensions are described in | 216 a later chapter. 218 1.2.1. General Advertisement 220 The General Advertisement MUST contain at least the following values: 222 IPv6 Header: 224 Destination the Source specified in the solicitation, when | 225 the Source is not the Unspecified Address, the | 226 node is not serving several clients, and the node | 227 is not operating as a Mobile Node. | 229 Otherwise, the All-Nodes IPv6 Multicast Address | 230 (FF02::1). The scope is intra-link. These | 231 decisions are described in [D-Send] and | 232 [Mobility]. 234 Source the Destination specified in the solicitation. | 236 Hop Limit 1 238 ICMP fields: 240 Code 1 for General Advertisement. 242 Lifetime the interface's configured AdvertisementLifetime. 244 Extensions: 246 Maximum-Receive-Unit | 247 for interfaces which do not have a fixed hardware | 248 MTU. 250 Media-Access for interfaces which are not point-to-point 251 links. 253 Other-Identifier for each of that node's known IPv6 Unicast | 254 Addresses other than the IPv6 Unicast Address | 255 specified in the IPv6 Source field. The Prefix | 256 Size and Metric are always zero. | 258 This supports multiple addresses per interface, | 259 as well as multi-homed nodes. This enables the | 260 recipient node to determine the best next-hop, | 261 when the next-hop is on another interface | 262 attached to the same advertising node. | 264 Node-Heard for the sender of the General Solicitation. | 265 In addition, each Router Advertisement that has | 266 been heard, in order of preference. 268 In the unlikely event that not all extensions fit in a single 269 advertisement, as constrained by the MTU of the link, the 270 remaining extensions are removed. 272 The use of the General Advertisement is described in [D-Send]. | 274 1.2.2. Router Advertisement 276 The Router Advertisement MUST contain at least the following values: 278 IPv6 Header: 280 Destination the All-Nodes IPv6 Multicast Address (FF02::1). | 281 The scope is intra-link. 283 Source the Primary Identifier of the router. | 285 The same IPv6 Unicast Address is used for all | 286 interfaces. When a router has more than one 287 interface on the same link, or a multi-homed host 288 can hear the same router on more than one link, 289 it is necessary to unambiguously know which 290 router sent this advertisement. The individual | 291 cluster prefixes for the links are distinguished | 292 in the Routing-Information extension. | 294 Hop Limit 1 296 ICMP fields: 298 Code 2 for Router Advertisement. 300 Lifetime the interface's configured AdvertisementLifetime. 302 Extensions: 304 Hop-Limit the current Internet Time-To-Live. Up-to-date | 305 values are specified in the most recent "Assigned | 306 Numbers" [RFC-1700]. | 308 Maximum-Receive-Unit | 309 for interfaces which do not have a fixed hardware | 310 MTU. 312 Media-Access for interfaces which are not point-to-point 313 links. | 315 Mobility-Support for interfaces which support Mobile Registration, | 316 either as a Foreign Agent or Home Agent. | 318 In the absence of this extension, all routers are | 319 expected to support decapsulation and forwarding | 320 from an interface, without explicit registration | 321 by a Mobile Node. | 323 Change-Identifier for each of that interface's IPv6 Unicast or | 324 Cluster Addresses which has changed from a value | 325 previously advertised with the Routing- | 326 Information or Other-Identifier extensions. | 327 Included at least once, and repeated until the | 328 original LifeTime expires. 330 Routing-Information 331 for each of that interface's associated IPv6 | 332 Unicast Addresses whose Advertise flags are TRUE. * 334 Other-Identifier for each of that node's other IPv6 Unicast or | 335 Cluster Addresses which have not already been 336 included through prefix subsumption. This may be | 337 another address for the same interface, or may | 338 identify another interface on the same node. | 340 When a number of interfaces, such as point-to- | 341 point interfaces, may be aggregated with the same | 342 prefix, only one extension need be included. | 344 Node-Heard for each Router Advertisement that has been 345 heard, in order of preference. 347 In the unlikely event that not all extensions fit in a single 348 advertisement, as constrained by the MTU of the link, multiple 349 advertisements are sent, with each containing as many remaining | 350 extensions as can fit. 352 The use of the Router Advertisement is described in [D-Send]. | 354 1.2.3. Local Redirect | 356 The Local Redirect MUST contain at least the following values: 358 IPv6 Header: 360 Destination the Source specified in the packet being 361 redirected. 363 Source the Primary Identifier of the router. | 365 Hop Limit 1 367 ICMP fields: 369 Code 4 for Local Redirect. 371 Sequence the last Sequence from the target node 372 Advertisement. 374 Lifetime the remaining Lifetime from the target node 375 Advertisement. 377 Extensions: 379 Maximum-Receive-Unit | 380 for interfaces which do not have a fixed hardware | 381 MTU, the Maximum-Receive-Unit extension from the | 382 target node Advertisement. 384 Media-Access for interfaces which are not point-to-point 385 links, the Media-Access extension from the target 386 node Advertisement. 388 Other-Identifier for each IPv6 Unicast or Cluster Address | 389 associated with the target node. The Metric is | 390 always zero. 392 When the redirect applies to an entire cluster, | 393 the Prefix Size is set to the size of the cluster | 394 prefix. This enables the recipient node to | 395 determine the best next-hop without multiple | 396 redirects for each cluster. 398 Transit-Information 399 one or more, when the redirect is limited to a 400 specific Quality of Service. The Metric is | 401 always zero. 403 Redirected-Header The target header. 405 In the unlikely event that not all extensions fit in a single 406 redirect, as constrained by the MTU of the link, the remaining 407 extensions are removed. Only a single redirect is sent. 409 The use of the Local Redirect is described in [D-Send]. | 411 1.2.4. Remote Redirect 413 The Remote Redirect MUST contain at least the following values: 415 IPv6 Header: 417 Destination the Source specified in the packet being 418 redirected. 420 Source the Destination specified in the packet being | 421 redirected. | 423 Hop Limit from the Router Advertisement. 425 An Authentication Header is required. 427 ICMP fields: 429 Code 5 for Remote Redirect. 431 Sequence the last Sequence from the target node 432 Advertisement. 434 Lifetime the remaining Lifetime from the target node 435 Advertisement. 437 Extensions: 439 Change-Identifier for each of that interface's IPv6 Unicast or | 440 Cluster Addresses which is now reached via a | 441 Care-Of-Address. 443 Redirected-Header The target header. 445 In the unlikely event that not all extensions fit in a single 446 redirect, as constrained by the MTU of the link, the remaining 447 extensions are removed. Only a single redirect is sent. 449 The use of the Remote Redirect is described in [Mobility]. | 451 1.3. Mobile Registration Request 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Type | Code | Checksum | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | unused | LifeTime | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | | 459 + Identification + 460 | | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | | 463 ~ Home Agent ~ 464 | | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | | 467 ~ Care-Of-Address ~ 468 | | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 | Extensions ... 471 +-+-+-+-+-+-+-+-+-+-+-+- 473 IPv6 Header: 475 Destination The IPv6 Unicast Address of the Agent, when | 476 known. 478 Otherwise, the Mobile-Agents IPv6 Multicast | 479 Address (FF02::11). The scope is intra-link. | 480 Examination of the Care-Of-Address is used to 481 deliver the datagram to the correct Agent. 483 Source any IPv6 Unicast Address associated with the | 484 sending interface. 486 A Mobile Node MUST use the transient Care-Of- 487 Address when assigned; otherwise, the Home- 488 Address is used. 490 ICMP fields: 492 Type 35 | 494 Code Bitmask of optional capabilities: 496 1 - retain prior registrations 497 2 - registering through Foreign Agent 499 LifeTime The seconds remaining before the registration is 500 considered expired. A value of zero indicates a 501 request for de-registration. A value of all ones 502 indicates infinity. * 504 Identification A sequence number assigned by the Mobile Node. 505 This is used to assist in matching Requests with 506 Replies. 508 A Network Time Protocol [RFC-1305] formatted 509 value is preferred. The low-order 32 bits of the 510 NTP format represent fractional seconds, and 511 those bits which are not available from a time 512 source SHOULD be generated from a good source of 513 randomness. 515 A battery-backed clock is the usual source of 516 this value. In more robust implementations, 517 Global Positioning System or authenticated NTP 518 values MAY be used. The elapsed time since 519 system startup or another such monotonically 520 increasing counter MAY be used, but is considered 521 less secure, as it could repeat each time the 522 machine is restarted, or when a poor source of 523 randomness is used for the low-order bits. See | 524 [Eastlake] for a discussion of sources of | 525 randomness. 527 It is possible to use an entirely random 528 "nonce" in this field, or to generate nonces 529 from previous registration exchanges. We have 530 not standardized this procedure because of 531 intellectual property concerns. It is also 532 incompatible with the expected venue of the 533 protocol, and presents difficulties with 534 interoperability and security validation. 536 The value MUST NOT be the same as an immediately 537 preceeding request, and SHOULD NOT repeat during 538 the lifetime of the Mobility Security Association 539 between the Mobile Node and the Home Agent. | 541 Home Agent The IPv6 Unicast Address of a Home Agent. | 543 Care-Of-Address The IPv6 Unicast Address for the decapsulation | 544 end of a tunnel. 546 Extensions: 548 Other-Identifier the Home-Address of the Mobile Node. The Metric | 549 is always zero. | 551 When the request applies to an entire cluster, | 552 the Prefix Size is set to the size of the cluster | 553 prefix. | 555 Maximum-Receive-Unit | 556 for interfaces which do not have a fixed hardware | 557 MTU. | 559 Media-Access for interfaces which are not point-to-point | 560 links. 562 Mobile-Home Authentication 563 Immediately follows all non-authentication * 564 extensions. 566 When forwarded by a Foreign Agent, all extensions are copied without | 567 modification. Those extensions which are specific to the Foreign | 568 Agent are ignored by the Home Agent. | 570 The use of the Registration Request is described in [Mobility]. 572 1.4. Mobile Registration Reply 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 | Type | Code | Checksum | 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 | unused | LifeTime | 578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 | | 580 + Identification + 581 | | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 583 | Extensions ... 584 +-+-+-+-+-+-+-+-+-+-+-+- 586 IPv6 Header: 588 The Source and Destination of the Request message are swapped for 589 the Reply message. 591 Note that the Source of the original Mobile Registration Request 592 must be saved in order for a Foreign Agent to return the reply to 593 the correct Mobile Node. 595 ICMP fields: 597 Type 36 | 599 Code One of the following codes: 601 0 service will be provided. 603 denied by Foreign Agent, 604 16 reason unspecified. 605 17 administratively prohibited. 606 18 insufficient resources. 607 19 Mobile Node failed authentication. 608 20 Home Agent failed authentication. 609 21 Request LifeTime too long. 611 denied by Home Agent, 612 32 reason unspecified. 613 33 administratively prohibited. 614 34 insufficient resources. 615 35 Mobile Node failed authentication. 616 36 Foreign Agent failed authentication. 618 Up-to-date values of the Code field are specified | 619 in the most recent "Assigned Numbers" [RFC-1700]. 621 LifeTime The seconds remaining before the registration is 622 considered expired. A value of zero confirms a 623 request for de-registration. A value of all ones 624 indicates infinity. | 626 The value MAY be changed by the Home Agent. 628 Identification Copied from the Request message. 630 Extensions: 632 Other-Identifier the Home-Address of the Mobile Node. The Metric | 633 is always zero. | 635 When the reply applies to an entire cluster, the | 636 Prefix Size is set to the size of the cluster | 637 prefix. 639 Mobile-Home Authentication 640 Immediately follows all non-authentication * 641 extensions. 643 Note that the Care-Of-Address and Home Agent are 644 not present in the message. This provides a 645 separate calculation value for mutual 646 authentication. 648 When forwarded by a Foreign Agent, all extensions are copied without | 649 modification. Those extensions which are specific to the Foreign | 650 Agent are ignored by the Home Agent. | 652 The use of the Registration Reply is described in [Mobility]. 654 2. Extensions 656 Extensions allow variable amounts of information to be carried within 657 each Solicitation or Advertisement packet. Some extensions are 658 common to both packet types. 660 The end of the list of Extensions is indicated by the Payload Length 661 of the IPv6 packet. 663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 664 | Extension | Length | Data ... 665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 667 Extension This document concerns the following values: 669 0 Single Pad (no length field) 670 1 Multiple Pads (with length field) 671 2 Change-Identifier | 672 3 Other-Identifier | 673 4 Node-Heard | 674 5 Routing-Information 675 6 Service-Information (reserved) | 676 7 Transit-Information 677 13 Hop-Limit | 678 14 Maximum-Receive-Unit 679 15 Media-Access 680 16 Mobility-Support | 681 17 Home-Address (obsolete) 682 32 Mobile-Home Authentication 683 64 Minimal Encapsulation (obsolete) | 684 65 GRE Encapsulation 685 254 Redirected-Header | 687 Up-to-date values are specified in the most recent | 688 "Assigned Numbers" [RFC-1700]. 690 Length the length of the Data field. The Length does not | 691 include the Extension and Length octets. | 693 The Single Pad (extension 0) is a special case, | 694 which has neither Length field nor Data field. 696 Data zero or more octets. The format and length of the | 697 Data field is determined by the Extension and Length 698 fields. 700 When an extension is encountered which is not recognized, it is 701 ignored. The Length field is used to skip the data field in | 702 searching for the next extension. 704 Every extension is aligned such that internal fields fall on natural 705 boundaries, except that fields larger than 64-bits need only be 706 aligned to 64-bit boundaries. 708 Any unused portion of the datagram between such Extensions is padded 709 as appropriate. The final Extension in a datagram does not require 710 trailing padding. 712 2.1. Single Pad 714 +-+-+-+-+-+-+-+-+ 715 | Extension | 716 +-+-+-+-+-+-+-+-+ 718 Extension 0 720 2.2. Multiple Pads 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 723 | Extension | Length | Data ... | 724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 726 Extension 1 728 Length the length of the Data field. | 730 Data zero or more bytes of zeroes. | 732 2.3. Change-Identifier 734 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ * 735 | Extension | Length | 0 | Prefix Size | | 736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 737 | | * 738 ~ Identifier ~ | 739 | | 740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 742 Extension 2 744 Length 34 | 746 Prefix Size the number of bits in the Identifier which define | 747 the cluster prefix width for the link. The value 748 ranges from 0 to 126. | 750 If the Identifier does not indicate a valid prefix, | 751 the value is zero. | 753 Non-routers MUST set this field to zero. | 755 Identifier an IPv6 Unicast or Cluster Address. 757 For Router Advertisements, gives advance indication that an address | 758 or prefix will no longer be routable. Applications SHOULD cease to | 759 accept new connections with the old value. Existing connections | 760 SHOULD issue a Remote Redirect. 762 For Remote Redirects, provides a Care-Of-Address to a Correspondent. | 764 2.4. Other-Identifier 766 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 767 | Extension | Length | 0 | Prefix Size | | 768 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 769 | Metric | | 770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 771 | | 772 ~ Identifier ~ | 773 | | 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 776 Extension 3 778 Length 22 | 780 Prefix Size the number of bits in the Identifier which define | 781 the cluster prefix width for the link. The value 782 ranges from 0 to 126. 784 If the Identifier does not indicate a valid prefix, | 785 the value is zero. 787 Non-routers MUST set this field to zero. 789 Metric the preference level for use of this node to forward | 790 packets to the Identifier. Lower values indicate 791 greater preference. 793 Non-routers MUST set this field to zero. | 795 Identifier an IPv6 Unicast or Cluster Address. 797 For usage, see the specific message description. | 799 2.5. Node-Heard | 801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 802 | Extension | Length | 0 | Prefix Size | | 803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 804 | Sequence Number | Remaining LifeTime | 805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 | | 807 ~ Primary Identifier ~ | 808 | | 809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 810 | MRU | 0 | Speed | | 811 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 812 | Quality | 813 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 814 | Advertisement Count | 815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 816 | Error Count | 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 Extension 4 821 Length 38 | 823 Prefix Size the number of bits in the Primary Identifier which | 824 define the cluster prefix width for the link. The 825 value ranges from 0 to 126. 827 If the Primary Identifier does not indicate a valid | 828 prefix, the value is zero. 830 Sequence Number the last heard sequence number from the node. | 832 Remaining LifeTime 833 the seconds remaining before the entry is considered | 834 expired. | 836 Primary Identifier | 837 the primary IPv6 Unicast or Cluster Address for the | 838 node, taken from the Source field of the 839 Advertisement heard. 841 MRU the maximum size packet that the node will receive | 842 over the link. 844 Speed the speed of the link over which the advertisement | 845 or solicitation was heard. Higher values indicate 846 greater speed. The speed value is related to int( 847 10 * ln( speed / 100 ) ) in bits per second. 849 0 link is down 850 1 - 9 reserved 851 10 300 or less 852 24 1,200 96 1,544,000 T1 853 31 2,400 99 2,048,000 E1 854 38 4,800 106 4,000,000 Token Ring 855 42 7,200 110 6,312,000 T2 856 45 9,600 115 10,000,000 Ethernet 857 49 14,400 119 16,000,000 Token Ring 858 52 19,200 859 56 28,800 130 44,736,000 T3 860 59 38,400 142 155,520,000 STS-3,STM-1 861 63 57,600 202 622,080,000 STS-12,STM-4 862 64 64,000 216 2,488,320,000 STS-48,STM-16 863 71 128,000 864 73 153,600 865 78 256,000 867 Quality an indication of the signal quality received from | 868 this node. Higher values indicate greater quality. 870 Advertisement Count 871 the number of advertisements that have been heard | 872 from the identified node. 874 Error Count the number of errors which have been detected on the | 875 link with the identified node. 877 This extension is included in an Advertisement message to indicate a | 878 node which has been heard. 880 The MRU, Speed, Quality, Advertisement Count, and Error Count are 881 primarily used for selecting among multiple paths in a wireless 882 environment. 884 2.6. Routing-Information 886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 887 | Extension | Length | Preference |C| Prefix Size | | 888 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 889 | | * 890 ~ Identifier ~ | 891 | | 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 894 Extension 5 896 Length 18 | 898 Preference the preference level for use of this node to forward | 899 packets having a Source longest match with the | 900 Identifier. Higher values indicate greater | 901 preference. 903 C Cluster bit. When this bit is set to 1, the IPv6 904 Cluster is entirely confined to the link. When 905 forwarding, a node MAY use the prefix to determine 906 whether a target node is on the link. * 908 Prefix Size the number of bits in the Identifier which define | 909 the cluster prefix width for the link. The value 910 ranges from 0 to 126. 912 If the Identifier does not indicate a valid prefix, | 913 the value is zero. | 915 Identifier one of the IPv6 Unicast or Cluster Addresses for | 916 this interface. 918 This extension is found in Router Advertisements. | 920 2.7. Transit-Information | 922 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 | Extension | Length | 0 | QoS | | 924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 925 | Metric | 926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 928 Extension 7 930 Length 6 932 QoS a quality of service for which transit will be | 933 accepted. 935 Metric the preference level for use of this link to forward | 936 packets of the indicated Quality of Service. Lower 937 values indicate greater preference. 939 For redirects, this indicates that the redirect is limited to only | 940 the particular service. If this extension is not included, the 941 redirect includes all services. 943 2.8. Hop-Limit | 945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 946 | Extension | Length | Hops | | 947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 949 Extension 13 | 951 Length 1 | 953 Hops the currently recommended IPv6 Hop Limit. | 955 Up-to-date values are specified in the most recent | 956 "Assigned Numbers" [RFC-1700]. 958 2.9. Maximum-Receive-Unit 960 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 961 | Extension | Length | MRU | 962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 964 Extension 14 966 Length 2 968 MRU the maximum size packet that the node will receive | 969 over the link. 971 This extension MUST be included in those messages sent from an | 972 interface for which there is no dependable MTU, such as Frame-Relay 973 or Asynchronous Transfer Mode. 975 It MUST NOT be included in messages such as the Remote Redirect which 976 pass through intermediate nodes. 978 2.10. Media-Access 980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 981 | Extension | Length | Family | | 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 | Media Address ... | 984 +-+-+-+-+-+-+-+-+-+-+-+- 986 Extension 15 988 Length >= 2 | 990 Family the Address Family Number. | 992 Up-to-date values are specified in the most recent | 993 "Assigned Numbers" [RFC-1700]. 995 Media Address the media address which is used to access this node. | 996 This field is variable in length. 998 The Media Address is always specified in Canonical 999 order. 1001 This extension MUST be included in those messages sent from an | 1002 interface on a multi-access media. 1004 It MUST NOT be included in a message sent from a point-to-point 1005 interface, or in messages such as the Remote Redirect which pass 1006 through intermediate nodes. 1008 2.11. Mobility-Support | 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 | Extension | Length |F| Reserved | 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1014 Extension 16 | 1016 Length >= 1 | 1018 F Foreign Agent bit. When this bit is set to 1, | 1019 Mobile Registration through the Foreign Agent is | 1020 required, even when the Mobile Node has acquired a | 1021 transient Care-Of-Address. | 1023 Reserved Sent as zero; ignored on reception. | 1025 This extension is found in Router Advertisements. | 1027 2.12. Mobile-Home Authentication Extension 1029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1030 | Extension | Length | | 1031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1032 | Authenticator ... | 1033 +-+-+-+-+-+-+-+-+-+-+-+- | 1035 Extension 32 1037 Length The number of data bytes in the Extension (16 when 1038 MD5 is used). 1040 Authenticator variable length (128 bits for MD5), 64-bit aligned. | 1042 A hash value taken over a stream of bytes consisting 1043 of the shared secret, followed by (concatenated 1044 with) the fields in the Mobile Registration message 1045 beginning with the Type field, including all prior 1046 extensions, and the Type and Length of this 1047 extension, but not including the Authenticator field 1048 itself. 1050 This extension is found in all Mobile Registration Requests and | 1051 Replies. 1053 The value differs depending on the direction the message is sent, 1054 since the Mobile Registration Request and Reply have different 1055 fields. 1057 2.13. GRE Encapsulation Extension | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1060 | Extension | Length | 1061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1063 Extension 65 | 1065 Length 0 | 1067 This extension is found in Router Advertisements and Mobile | 1068 Registration Requests. GRE is described in [RFC-1701]. | 1070 2.14. Redirected-Header | 1072 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1073 | Extension | Length | 1074 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1075 | IPv6 Header(s) ... 1076 +-+-+-+-+-+-+-+-+-+-+-+- 1078 Extension 254 | 1080 Length >= 64 | 1082 IPv6 Header(s) variable length, 64-bit aligned. | 1084 This extension is included in the Local or Remote Redirect to verify | 1085 the traffic that is being redirected. | 1087 Security Considerations 1089 Whenever Ran gets them done. | 1091 References 1093 [D-Send] | 1095 [Eastlake] | 1097 [IPv6-Address] 1099 [IPv6-ICMP] | 1101 [Mobility] 1103 [RFC-1305] | 1105 [RFC-1700] | 1107 [RFC-1701] 1109 Acknowledgements 1111 Many thanks to Fred Goldstein, K1IO (DEC, BBN) for his pioneering | 1112 work on Radio Shortest Path First (RSPF) for Amateur Packet Radio. | 1114 Thanks also for suggestions and contributions from the Simple-IP | 1115 Working Group and the Mobile-IP Working Group. | 1117 Special thanks for implementation review by Alex Conta (DEC), Dan | 1118 McDonald (Naval Research Laboratory), and Fred Rabouw (Network | 1119 Systems Netherlands). 1121 Author's Address 1123 Questions about this memo can also be directed to: 1125 William Allen Simpson 1126 Daydreamer 1127 Computer Systems Consulting Services 1128 1384 Fontaine 1129 Madison Heights, Michigan 48071 1131 Bill.Simpson@um.cc.umich.edu 1132 bsimpson@MorningStar.com