idnits 2.17.1 draft-simpson-ipv6-discov-formats-00.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. == 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 5 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 79: '...e Reserved field MUST be zero on trans...' RFC 2119 keyword, line 80: '... MUST be ignored on receipt. Future...' RFC 2119 keyword, line 86: '...ral Solicitation MUST contain at least...' RFC 2119 keyword, line 90: '...v6 Address of the target. It MUST NOT...' RFC 2119 keyword, line 94: '... node. It MUST NOT contain the ...' (23 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (September 1994) is 10815 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) == Unused Reference: 'Eastlake' is defined on line 1041, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'Eastlake' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6-ICMP' ** Obsolete normative reference: RFC 1305 (Obsoleted by RFC 5905) ** Obsolete normative reference: RFC 1310 (Obsoleted by RFC 1602) Summary: 13 errors (**), 0 flaws (~~), 2 warnings (==), 4 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 September 1994 5 IPv6 Neighbor Discovery -- ICMP Message Formats 6 draft-simpson-ipv6-discov-formats-00.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 the identification and 36 location of adjacent IPv6 nodes. 38 1. Additional ICMP Packets 40 The Packet format and basic facilities are already defined for ICMP 41 as modified for IPv6 [IPv6-ICMP]. 43 Up-to-date values of the ICMP Type field are specified in the most 44 recent "Assigned Numbers" [RFC-1310]. This document concerns the 45 following values: 47 33 Solicitation 48 34 Advertisement 49 35 Mobile Registration Request 50 36 Mobile Registration Reply 52 1.1. Solicitation 54 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 55 | Type | Code | Checksum | 56 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 57 | Reserved | 58 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 59 | Extensions ... 60 +-+-+-+-+-+-+-+-+-+-+-+- 62 Type 33 64 Code Up-to-date values are specified in the most recent 65 "Assigned Numbers" [RFC-1310]. Current values are 66 assigned as follows: 68 0 RESERVED 69 1 General 70 2 Router 71 3 Service 73 Checksum The ICMP Checksum. 75 Extensions This field is variable in length and contains zero 76 or more Extensions. These Extensions are described 77 in a later section. 79 The contents of the Reserved field MUST be zero on transmission, and 80 MUST be ignored on receipt. Future backward-compatible changes to 81 the protocol may specify the contents of the Reserved field or of 82 additional octets at the end of the message. 84 1.1.1. General Solicitation 86 The General Solicitation MUST contain at least the following values: 88 IPv6 Header: 90 Destination an IPv6 Address of the target. It MUST NOT 91 contain a multicast address. 93 Source any IPv6 Address associated with the sending 94 node. It MUST NOT contain the Unspecified 95 Address. 97 ICMP fields: 99 Code 1 for General Solicitation. 101 Extensions: 103 Media-Access for interfaces which are not point-to-point 104 links. 106 System-Heard for each Router Advertisement that has been 107 heard, in order of preference. 109 In the unlikely event that not all extensions fit in a single 110 solicitation, as constrained by the MTU of the link, the remaining 111 extensions are removed. 113 1.1.2. Router Solicitation 115 The Router Solicitation MUST contain at least the following values: 117 IPv6 Header: 119 Destination the all-routers multicast. The scope is set to 120 intra-link. 122 Source any IPv6 Address associated with the sending 123 node. It MAY contain the Unspecified Address, 124 when the node has not yet determined an IPv6 125 Address. 127 ICMP fields: 129 Code 2 for Router Solicitation. 131 There are no required extensions. 133 1.1.3. Service Solicitation 135 The Service Solicitation MUST contain at least the following values: 137 IPv6 Header: 139 Destination the multicast group associated with the service. 140 The scope is set to intra-site. 142 Source any IPv6 Address associated with the sending 143 node. It MUST NOT contain the Unspecified 144 Address. 146 ICMP fields: 148 Code 3 for Service Solicitation. 150 Extensions: 152 Service-Information 153 One or more qualifiers, in order of importance. 155 In the unlikely event that not all extensions fit in a single 156 solicitation, as constrained by the MTU of the link, the remaining 157 extensions are removed. 159 1.2. Advertisement 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | Type | Code | Checksum | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | Sequence Number | LifeTime | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | Extensions ... 167 +-+-+-+-+-+-+-+-+-+-+-+- 169 Type 34 171 Code Up-to-date values are specified in the most recent 172 "Assigned Numbers" [RFC-1310]. Current values are 173 assigned as follows: 175 0 RESERVED 176 1 General 177 2 Router 178 3 Service 179 4 Local Redirect 180 5 Remote Redirect 182 Checksum The ICMP Checksum. 184 Sequence Number Contains the number of Advertisement messages sent 185 since the node was initialized. This number MUST 186 include this advertisement. That is, the first 187 Advertisement contains the value one, and the value 188 zero indicates that the number has rolled over. 190 LifeTime Indicates the seconds remaining before the 191 advertised information is considered expired. The 192 maximum time is approximately 18.2 hours. 194 Extensions This field is variable in length and contains zero 195 or more Extensions. These Extensions are described 196 in a later section. 198 1.2.1. General Advertisement 200 The General Advertisement MUST contain at least the following values: 202 IPv6 Header: 204 Destination the Source specified in the solicitation. 206 Source the Destination specified in the solicitation. 208 ICMP fields: 210 Code 1 for General Advertisement. 212 Lifetime the interface's configured AdvertisementLifetime. 214 Extensions: 216 Media-Access for interfaces which are not point-to-point 217 links. 219 Other-Identifier for each of that node's known IPv6 Addresses 220 other than the IPv6 Address specified in the IPv6 221 Source field. The prefix size is set to zero. 223 System-Heard for each Router Advertisement that has been 224 heard, in order of preference. 226 In the unlikely event that not all extensions fit in a single 227 advertisement, as constrained by the MTU of the link, the 228 remaining extensions are removed. 230 1.2.2. Router Advertisement 232 The Router Advertisement MUST contain at least the following values: 234 IPv6 Header: 236 Destination the all-nodes multicast. The scope is set to 237 intra-link. 239 Source the primary IPv6 Address of the node. 241 The same IPv6 Address is used for all interfaces. 242 When a router has more than one interface on the 243 same link, or a multi-homed host can hear the 244 same router on more than one link, it is 245 necessary to unambiguously know which router sent 246 this advertisement. The individual routing 247 prefixes for the links are distinguished in the 248 Routing Information extension. 250 ICMP fields: 252 Code 2 for Router Advertisement. 254 Lifetime the interface's configured AdvertisementLifetime. 256 Extensions: 258 Media-Access for interfaces which are not point-to-point 259 links. 261 Routing-Information 262 for each of that interface's associated IPv6 263 Addresses whose Advertise flags are TRUE. 265 Change-Identifier for each of that interface's recently changed 266 IPv6 Addresses. 268 Other-Identifier for each of that node's other IPv6 Addresses 269 which have not already been included through 270 prefix subsumption. 272 System-Heard for each Router Advertisement that has been 273 heard, in order of preference. 275 In the unlikely event that not all extensions fit in a single 276 advertisement, as constrained by the MTU of the link, multiple 277 advertisements are sent, with each except the last containing as 278 many extensions as can fit. 280 1.2.3. Service Advertisement 282 The Service Advertisement MUST contain at least the following values: 284 IPv6 Header: 286 Destination the all-nodes multicast. The scope is set by 287 administrative policy. 289 Source any IPv6 Address associated with the sending 290 node. 292 ICMP fields: 294 Code 3 for Service Advertisement. 296 Lifetime the interface's configured AdvertisementLifetime. 298 Extensions: 300 Media-Access for interfaces which are not point-to-point 301 links. 303 Other-Identifier for each of that node's known IPv6 Addresses 304 other than the IPv6 Address specified in the IPv6 305 Source field. The prefix size is set to zero. 307 Service-Information 308 One or more qualifiers, in order of importance. 310 System-Heard for each Router Advertisement that has been 311 heard, in order of preference. 313 In the unlikely event that not all extensions fit in a single 314 advertisement, as constrained by the MTU of the link, multiple 315 advertisements are sent, with each except the last containing as 316 many extensions as can fit. 318 1.2.4. Local Redirect 320 The Local Redirect MUST contain at least the following values: 322 IPv6 Header: 324 Destination the Source specified in the packet being 325 redirected. 327 Source the primary IPv6 Address associated with the 328 sending node. 330 ICMP fields: 332 Code 4 for Local Redirect. 334 Sequence the last Sequence from the target node 335 Advertisement. 337 Lifetime the remaining Lifetime from the target node 338 Advertisement. 340 Extensions: 342 Media-Access for interfaces which are not point-to-point 343 links, the Media-Access extension from the target 344 node Advertisement. 346 Other-Identifier for each IPv6 Address associated with the target 347 node. The metric is set to zero. 349 When the redirect applies to an entire cluster, 350 the prefix size is set to the size of the cluster 351 prefix. 353 Transit-Information 354 one or more, when the redirect is limited to a 355 specific Quality of Service. The metric is set 356 to zero. 358 Redirected-Header The target header. 360 In the unlikely event that not all extensions fit in a single 361 redirect, as constrained by the MTU of the link, the remaining 362 extensions are removed. Only a single redirect is sent. 364 The Local Redirect is used by a router to redirect a host to another 365 router, or to another host on the same link. These uses are 366 indistinguishable. 368 1.2.5. Remote Redirect 370 The Remote Redirect MUST contain at least the following values: 372 IPv6 Header: 374 Destination the Source specified in the packet being 375 redirected. 377 Source the primary IPv6 Address associated with the 378 sending node. 380 An Authentication Header is required. 382 ICMP fields: 384 Code 5 for Remote Redirect. 386 Sequence the last Sequence from the target node 387 Advertisement. 389 Lifetime the remaining Lifetime from the target node 390 Advertisement. 392 Extensions: 394 Change-Identifier when the IPv6 Destination of the redirected 395 packet is changing. The Prefix Size is set to 396 zero. 398 Other-Identifier for each IPv6 Address associated with the target 399 node. The metric is set to zero, and the prefix 400 size is set to zero. 402 Redirected-Header The target header. 404 In the unlikely event that not all extensions fit in a single 405 redirect, as constrained by the MTU of the link, the remaining 406 extensions are removed. Only a single redirect is sent. 408 The Remote Redirect is primarily used to support Mobility. 410 1.3. Mobile Registration Request 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | Type | Code | Checksum | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | unused | LifeTime | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | | 418 + Identification + 419 | | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | | 422 ~ Home Agent ~ 423 | | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | | 426 ~ Care-Of-Address ~ 427 | | 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 | Extensions ... 430 +-+-+-+-+-+-+-+-+-+-+-+- 432 IPv6 Header: 434 Destination The IPv6 Address of the Agent, when known. 436 When the IPv6 Address is unknown (the agent was 437 discovered via a link-layer protocol), the "all 438 Mobile Agents" multicast address. The link-layer 439 unicast address is used to deliver the datagram 440 to the correct Agent. 442 Source An IPv6 Address belonging to the interface on 443 which this message is sent. 445 A Mobile Node MUST use the transient Care-Of- 446 Address when assigned; otherwise, the Home- 447 Address is used. 449 ICMP fields: 451 Type 35 453 Code Bitmask of optional capabilities: 455 1 - retain prior registrations 456 2 - registering through Foreign Agent 458 LifeTime The seconds remaining before the registration is 459 considered expired. A value of zero indicates a 460 request for de-registration. A value of all ones 461 indicates infinity. 463 Home Agent The IPv6 Address of a Home Agent. 465 Care-Of-Address The IPv6 Address for the decapsulation end of a 466 tunnel. 468 Identification A sequence number assigned by the Mobile Node. 469 This is used to assist in matching Requests with 470 Replies. 472 A Network Time Protocol [RFC-1305] formatted 473 value is preferred. The low-order 32 bits of the 474 NTP format represent fractional seconds, and 475 those bits which are not available from a time 476 source SHOULD be generated from a good source of 477 randomness. 479 A battery-backed clock is the usual source of 480 this value. In more robust implementations, 481 Global Positioning System or authenticated NTP 482 values MAY be used. The elapsed time since 483 system startup or another such monotonically 484 increasing counter MAY be used, but is considered 485 less secure, as it could repeat each time the 486 machine is restarted, or when a poor source of 487 randomness is used for the low-order bits. See 488 [Eastlake, et alia] for a discussion of sources 489 of randomness. 491 It is possible to use an entirely random 492 "nonce" in this field, or to generate nonces 493 from previous registration exchanges. We have 494 not standardized this procedure because of 495 intellectual property concerns. It is also 496 incompatible with the expected venue of the 497 protocol, and presents difficulties with 498 interoperability and security validation. 500 The value MUST NOT be the same as an immediately 501 preceeding request, and SHOULD NOT repeat during 502 the lifetime of the Mobility Security Association 503 between the Mobile Node and the Home Agent. 505 Extensions: 507 Other-Identifier required. Contains the Home-Address of the 508 Mobile Node. The metric is set to zero. 510 Mobile-Home Authentication 511 required. Immediately follows all non- 512 authentication extensions. 514 When forwarded by a Foreign Agent, extensions which are specific to 515 the Foreign Agent are removed. All others are copied without 516 modification. 518 1.4. Mobile Registration Reply 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 521 | Type | Code | Checksum | 522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 523 | unused | LifeTime | 524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 525 | | 526 + Identification + 527 | | 528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 529 | Extensions ... 530 +-+-+-+-+-+-+-+-+-+-+-+- 532 IPv6 Header: 534 The Source and Destination of the Request message are swapped for 535 the Reply message. 537 Note that the Source of the original Mobile Registration Request 538 must be saved in order for a Foreign Agent to return the reply to 539 the correct Mobile Node. 541 ICMP fields: 543 Type 36 545 Code One of the following codes: 547 0 service will be provided. 549 denied by Foreign Agent, 550 16 reason unspecified. 551 17 administratively prohibited. 552 18 insufficient resources. 553 19 Mobile Node failed authentication. 554 20 Home Agent failed authentication. 555 21 Request LifeTime too long. 557 denied by Home Agent, 558 32 reason unspecified. 559 33 administratively prohibited. 560 34 insufficient resources. 561 35 Mobile Node failed authentication. 562 36 Foreign Agent failed authentication. 564 Up-to-date values of the Code field are specified 565 in the most recent "Assigned Numbers" [RFC-1310]. 567 LifeTime The seconds remaining before the registration is 568 considered expired. A value of zero confirms a 569 request for de-registration. A value of all ones 570 indicates infinity. 572 Identification Copied from the Request message. 574 Extensions: 576 Other-Identifier required. Contains the Home-Address of the 577 Mobile Node. The metric is set to zero. 579 Mobile-Home Authentication 580 required. Immediately follows all non- 581 authentication extensions. 583 Note that the Care-Of-Address and Home Agent are 584 not present in the message. This provides a 585 separate calculation value for mutual 586 authentication. 588 When forwarded by a Foreign Agent, extensions which are specific to 589 the Foreign Agent are removed. All others are copied without 590 modification. 592 2. Extensions 594 Extensions allow variable amounts of information to be carried within 595 each Solicitation or Advertisement packet. Some extensions are 596 common to both packet types. 598 The end of the list of Extensions is indicated by the Payload Length 599 of the IPv6 packet. 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 602 | Extension | Length | Data ... 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 605 Extension This document concerns the following values: 607 0 Single Pad (no length field) 608 1 Multiple Pads (with length field) 609 2 Change-Identifier 610 3 Other-Identifier 611 4 System-Heard 612 5 Routing-Information 613 6 Service-Information 614 7 Transit-Information 615 8 Redirected-Header 616 14 Maximum-Receive-Unit 617 15 Media-Access 618 16 Mobility (obsolete) 619 17 Home-Address (obsolete) 620 32 Mobile-Home Authentication 621 64 Minimal Encapsulation 622 65 GRE Encapsulation 624 Up-to-date values are specified in the most recent 625 "Assigned Numbers" [RFC-1310]. 627 Length Indicates the length of the Data field which has 628 been used. The Length does not include the 629 Extension and Length octets. The Single Pad 630 (extension 0) is a special case, which has no Length 631 field. 633 Data This field is zero or more octets and contains the 634 value(s) for this Extension. The format and length 635 of the Data field is determined by the Extension and 636 Length fields. 638 When an extension is encountered which is not recognized, it is 639 ignored. The length field is used to skip the data field in 640 searching for the next extension. 642 Every extension is aligned such that internal fields fall on natural 643 boundaries, except that fields larger than 64-bits need only be 644 aligned to 64-bit boundaries. 646 Any unused portion of the datagram between such Extensions is padded 647 as appropriate. The final Extension in a datagram does not require 648 trailing padding. 650 2.1. Single Pad 652 +-+-+-+-+-+-+-+-+ 653 | Extension | 654 +-+-+-+-+-+-+-+-+ 656 Extension 0 658 2.2. Multiple Pads 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 661 | Extension | Length | Data ... 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 664 Extension 1 666 Length Indicates the length of the Data field. 668 Data This field is zero or more bytes of zeroes. 670 2.3. Change-Identifier 672 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 673 | Extension | Length | unused | Prefix Size | 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 | unused | 676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 | | 678 ~ Old IPv6 Address ~ 679 | | 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 | | 682 ~ New IPv6 Address ~ 683 | | 684 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 Extension 2 688 Length 22 690 Prefix Size Indicates the number of bits in both IPv6 Addresses 691 which define the cluster prefix width for the link. 692 The value ranges from 0 to 126. 694 Old IPv6 Address Depending on the Prefix Size, it may indicate a 695 cluster, or a single IPv6 Address. 697 New IPv6 Address Depending on the Prefix Size, it may indicate a 698 cluster, or a single IPv6 Address. 700 For advertisements, this allows changing a prefix for every node on a 701 router's interface. 703 For redirects, this allows changing a single target IPv6 Address. 705 2.4. Other-Identifier 707 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 708 | Extension | Length | | Prefix Size | 709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 710 | Metric | 711 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 712 | | 713 ~ IPv6 Address ~ 714 | | 715 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 Extension 3 719 Length 14 721 Prefix Size Indicates the number of bits in the IPv6 Address 722 which define the cluster prefix width for the link. 723 The value ranges from 0 to 126. 725 If the IPv6 Address does not indicate a valid 726 prefix, the value is zero. 728 Non-routers MUST set this field to zero. 730 Metric Indicates the preference level for use of this node 731 to forward packets to the IPv6 Address. Lower 732 values indicate greater preference. 734 Non-routers MUST set this field to zero. 736 IPv6 Address Contains one of the IPv6 Addresses for this node. 737 This may be another IPv6 Address for the same 738 interface that sent the message, or may identify 739 another interface on the same node which sent the 740 message. 742 This supports multiple IPv6 Addresses per interface, as well as 743 multi-homed nodes. 745 When a number of interfaces, such as point-to-point interfaces, may 746 be aggregated with the same prefix, only one extension need be 747 included. 749 For advertisements, this enables the recipient node to determine the 750 best next-hop without sending a Solicitation when the next-hop is on 751 another interface attached to the same advertising node. 753 For redirects, this enables the recipient node to determine the best 754 next-hop without multiple redirects for each cluster. 756 2.5. System-Heard 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 | Extension | Length | | Prefix Size | 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 | Sequence Number | Remaining LifeTime | 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 763 | | 764 ~ IPv6 Address ~ 765 | | 766 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 767 | MRU | | Speed | 768 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 769 | Quality | 770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 771 | Advertisement Count | 772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 773 | Error Count | 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 776 Extension 4 778 Length 30 780 Prefix Size Indicates the number of bits in the IPv6 Address 781 which define the cluster prefix width for the link. 782 The value ranges from 0 to 126. 784 If the IPv6 Address does not indicate a valid 785 prefix, the value is zero. 787 Sequence Number Contains the last heard sequence number from the 788 node. 790 Remaining LifeTime 791 Indicates the seconds remaining before the entry is 792 considered expired. 794 IPv6 Address Contains the primary IPv6 Address for the node, 795 taken from the Source field of the Advertisement 796 heard. 798 MRU Indicates the maximum size packet that the node will 799 receive over the link. 801 Speed Indicates the speed of the link over which the 802 advertisement or solicitation was heard. Higher 803 values indicate greater speed. The speed value is 804 related to int( 10 * ln( speed / 100 ) ) in bits per 805 second. 807 0 link is down 808 1 - 9 reserved 809 10 300 or less 810 24 1,200 96 1,544,000 T1 811 31 2,400 99 2,048,000 E1 812 38 4,800 106 4,000,000 Token Ring 813 42 7,200 110 6,312,000 T2 814 45 9,600 115 10,000,000 Ethernet 815 49 14,400 119 16,000,000 Token Ring 816 52 19,200 817 56 28,800 130 44,736,000 T3 818 59 38,400 142 155,520,000 STS-3,STM-1 819 63 57,600 202 622,080,000 STS-12,STM-4 820 64 64,000 216 2,488,320,000 STS-48,STM-16 821 71 128,000 822 73 153,600 823 78 256,000 825 Quality Contains an indication of the signal quality 826 received from this node. Higher values indicate 827 greater quality. 829 Advertisement Count 830 Indicates the number of advertisements that have 831 been heard from the identified node. 833 Error Count Indicates the number of errors which have been 834 detected on the link with the identified node. 836 This extension is included in the Advertisement message to indicate a 837 node which has been heard. 839 The MRU, Speed, Quality, Advertisement Count, and Error Count are 840 primarily used for selecting among multiple paths in a wireless 841 environment. 843 2.6. Routing-Information 845 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 846 | Extension | Length |C|F| | Prefix Size | 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 848 | | Preference | 849 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 | | 851 ~ IPv6 Address ~ 852 | | 853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 Extension 5 857 Length 14 859 C Cluster bit. When this bit is set to 1, the IPv6 860 Cluster is entirely confined to the link. When 861 forwarding, a node MAY use the prefix to determine 862 whether a target node is on the link. 864 F Foreign Agent bit. When this bit is set to 1, 865 Mobile Registration through the Foreign Agent is 866 required, even when the Mobile Node has acquired a 867 transient Care-Of-Address. 869 Prefix Size Indicates the number of bits in the IPv6 Address 870 which define the cluster prefix width for the link. 871 The value ranges from 0 to 126. 873 If the IPv6 Address does not indicate a valid 874 prefix, the value is zero. 876 Preference Indicates the preference level for use of this node 877 to forward packets to the IPv6 Address. Higher 878 values indicate greater preference. 880 IPv6 Address Contains one of the IPv6 Addresses for this 881 interface. 883 This extension is sent only by Routers. 885 2.7. Service-Information 887 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 888 | Extension | Length | Service | 889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 890 | Data ... 891 +-+-+-+-+-+-+-+-+-+-+-+- 893 Extension 6 895 Length >= 2 897 Service The value of this field is usually the same as the 898 well-known port number. Up-to-date values are 899 specified in the most recent "Assigned Numbers" 900 [RFC-1310]. 902 Data This field is variable in length and contains 903 Attribute information specific to the service. 905 2.8. Transit-Information 907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 908 | Extension | Length | | QoS | 909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 910 | Metric | 911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 913 Extension 7 915 Length 6 917 QoS Indicates a quality of service for which transit 918 will be accepted. 920 Metric Indicates the preference level for use of this link 921 to forward packets of the indicated Quality of 922 Service. Lower values indicate greater preference. 924 For advertisements, this indicates that a router will accept transit 925 traffic for the service. If this extension is not included, other 926 routers will treat the link as a stub cluster. 928 For redirects, this indicates that the redirect is limited to only 929 the particular service. If this extension is not included, the 930 redirect includes all services. 932 2.9. Redirected-Header 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 | Extension | Length | IPv6 Header ... 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 938 Extension 8 940 Length 54 942 IPv6 Header 48 octets. 944 This extension is included in the Local or Remote Redirect to verify 945 the traffic that is being redirected. 947 2.10. Maximum-Receive-Unit 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 | Extension | Length | MRU | 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 953 Extension 14 955 Length 2 957 MRU Indicates the maximum size packet that the node will 958 receive over the link. 960 The Maximum-Receive-Unit extension MUST be included in those messages 961 sent from an interface for which there is no dependable MTU, such as 962 Frame-Relay or Asynchronous Transfer Mode. 964 It MUST NOT be included in messages such as the Remote Redirect which 965 pass through intermediate nodes. 967 2.11. Media-Access 969 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 970 | Extension | Length | Media Type | 971 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 972 | Media Address ... 973 +-+-+-+-+-+-+-+-+-+-+-+- 975 Extension 15 977 Length >= 2 979 Media Type The value of this field is the same as the Hardware 980 Type used in ARP. Up-to-date values are specified 981 in the most recent "Assigned Numbers" [RFC-1310]. 983 Media Address This field is variable in length and contains the 984 media address which is used to access this node. 986 The Media Address is always specified in Canonical 987 order. 989 The Media-Access extension MUST be included in those messages sent 990 from an interface on a multi-access media. 992 It MUST NOT be included in a message sent from a point-to-point 993 interface, or in messages such as the Remote Redirect which pass 994 through intermediate nodes. 996 2.12. Mobile-Home Authentication Extension 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 | Extension | Length | Authenticator ... 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 Extension 32 1004 Length The number of data bytes in the Extension (16 when 1005 MD5 is used). 1007 Authenticator Variable length (128 bits for MD5). 1009 A hash value taken over a stream of bytes consisting 1010 of the shared secret, followed by (concatenated 1011 with) the fields in the Mobile Registration message 1012 beginning with the Type field, including all prior 1013 extensions, and the Type and Length of this 1014 extension, but not including the Authenticator field 1015 itself. 1017 This Authentication Extension is found in all Mobile Registration 1018 Requests and Replies. 1020 The value differs depending on the direction the message is sent, 1021 since the Mobile Registration Request and Reply have different 1022 fields. 1024 2.13. Minimal Encapsulation Extension 1026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1027 | Extension | Length | 1028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1030 Extension 64 1032 Length 0 1034 The Minimal Encapsulation Extension is found in Router Advertisements 1035 and Mobile Registration Requests. 1037 Security Considerations 1039 References 1041 [Eastlake] 1043 [IPv6-ICMP] 1045 [RFC-1305] 1047 [RFC-1310] 1049 Acknowledgements 1051 Extensive review by Alex Conta (DEC), and Dan McDonald (NRL). 1053 Author's Address 1055 Questions about this memo can also be directed to: 1057 William Allen Simpson 1058 Daydreamer 1059 Computer Systems Consulting Services 1060 1384 Fontaine 1061 Madison Heights, Michigan 48071 1063 Bill.Simpson@um.cc.umich.edu 1064 bsimpson@MorningStar.com 1065 Table of Contents 1067 1. Additional ICMP Packets ............................... 1 1068 1.1 Solicitation .................................... 2 1069 1.1.1 General Solicitation ............................ 3 1070 1.1.2 Router Solicitation ............................. 4 1071 1.1.3 Service Solicitation ............................ 5 1072 1.2 Advertisement ................................... 6 1073 1.2.1 General Advertisement ........................... 7 1074 1.2.2 Router Advertisement ............................ 8 1075 1.2.3 Service Advertisement ........................... 10 1076 1.2.4 Local Redirect .................................. 11 1077 1.2.5 Remote Redirect ................................. 13 1078 1.3 Mobile Registration Request ..................... 14 1079 1.4 Mobile Registration Reply ....................... 17 1081 2. Extensions ............................................ 19 1082 2.1 Single Pad ...................................... 20 1083 2.2 Multiple Pads ................................... 20 1084 2.3 Change-Identifier ............................... 21 1085 2.4 Other-Identifier ................................ 22 1086 2.5 System-Heard .................................... 23 1087 2.6 Routing-Information ............................. 25 1088 2.7 Service-Information ............................. 26 1089 2.8 Transit-Information ............................. 27 1090 2.9 Redirected-Header ............................... 28 1091 2.10 Maximum-Receive-Unit ............................ 29 1092 2.11 Media-Access .................................... 30 1093 2.12 Mobile-Home Authentication Extension ............ 31 1094 2.13 Minimal Encapsulation Extension ................. 32 1096 SECURITY CONSIDERATIONS ...................................... 33 1098 REFERENCES ................................................... 33 1100 ACKNOWLEDGEMENTS ............................................. 33 1102 AUTHOR'S ADDRESS ............................................. 33