idnits 2.17.1 draft-ietf-manet-packetbb-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 21. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1687. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1698. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1705. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1711. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 437 has weird spacing: '...-length is a ...' == Line 446 has weird spacing: '...-length is a ...' == Line 454 has weird spacing: '...-length is a ...' == Line 554 has weird spacing: '...ex-stop are v...' == Line 581 has weird spacing: '...-values is a ...' -- 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 (June 20, 2007) is 6153 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. '3' Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mobile Ad hoc Networking (MANET) T. Clausen 3 Internet-Draft LIX, Ecole Polytechnique, France 4 Intended status: Standards Track C. Dearlove 5 Expires: December 22, 2007 BAE Systems Advanced Technology 6 Centre 7 J. Dean 8 Naval Research Laboratory 9 C. Adjih 10 INRIA Rocquencourt 11 June 20, 2007 13 Generalized MANET Packet/Message Format 14 draft-ietf-manet-packetbb-06 16 Status of this Memo 18 By submitting this Internet-Draft, each author represents that any 19 applicable patent or other IPR claims of which he or she is aware 20 have been or will be disclosed, and any of which he or she becomes 21 aware will be disclosed, in accordance with Section 6 of BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on December 22, 2007. 41 Copyright Notice 43 Copyright (C) The IETF Trust (2007). 45 Abstract 47 This document specifies a multi-message packet format that may be 48 used by mobile ad hoc network routing and other protocols. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 3. Applicability Statement . . . . . . . . . . . . . . . . . . . 6 55 4. Protocol Overview and Functioning . . . . . . . . . . . . . . 7 56 5. Signaling Framework . . . . . . . . . . . . . . . . . . . . . 8 57 5.1. Packets . . . . . . . . . . . . . . . . . . . . . . . . . 8 58 5.2. Messages . . . . . . . . . . . . . . . . . . . . . . . . . 9 59 5.2.1. Address Blocks . . . . . . . . . . . . . . . . . . . . 11 60 5.3. TLVs and TLV Blocks . . . . . . . . . . . . . . . . . . . 13 61 5.3.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 13 62 5.3.2. Constraints . . . . . . . . . . . . . . . . . . . . . 16 63 5.4. Padding . . . . . . . . . . . . . . . . . . . . . . . . . 16 64 6. TLV specification . . . . . . . . . . . . . . . . . . . . . . 17 65 6.1. Address Block TLV Specification . . . . . . . . . . . . . 17 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 67 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 20 71 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 21 72 A.1. Address Block Examples . . . . . . . . . . . . . . . . . . 21 73 A.2. TLV Examples . . . . . . . . . . . . . . . . . . . . . . . 22 74 Appendix B. Illustrations . . . . . . . . . . . . . . . . . . . 25 75 Appendix B.1. Packet . . . . . . . . . . . . . . . . . . . . . . . 25 76 Appendix B.2. Message and Padding . . . . . . . . . . . . . . . . 27 77 Appendix B.3. Message Body . . . . . . . . . . . . . . . . . . . . 33 78 Appendix B.4. Address Block . . . . . . . . . . . . . . . . . . . 34 79 Appendix B.5. TLV Block . . . . . . . . . . . . . . . . . . . . . 36 80 Appendix B.6. TLV . . . . . . . . . . . . . . . . . . . . . . . . 36 81 Appendix C. Complete Example . . . . . . . . . . . . . . . . . . 39 82 Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 41 83 Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 42 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 85 Intellectual Property and Copyright Statements . . . . . . . . . . 44 87 1. Introduction 89 This document specifies the syntax of a general purpose multi-message 90 packet format for information exchange between MANET routers. 91 Messages consist of a message header, which is designed for control 92 of message dissemination, and a message body, which contains protocol 93 information. Only the syntax of the message body is specified. All 94 syntactical entities, including messages and packets, are specified 95 using regular expressions. 97 This document specifies: 99 o A packet format, allowing zero or more messages to be contained 100 within a single transmission, and optionally including a packet 101 header. A packet with zero messages may be sent in case the only 102 information to exchange is contained in the packet header (such as 103 a "keep alive" sequence number). 105 o A message format, where a message is composed of a message header 106 and a message body. 108 o A message header format which allows a node to make forwarding 109 decisions based on the node's present state and the message 110 header, without inspecting and processing the message body, and 111 independently of the TTL or hop limit information in the IP 112 header. Message header information permits single- and multi-hop 113 message diffusion. 115 o A message body format, containing attributes associated with the 116 message or the originator of the message, as well as blocks of 117 addresses with associated attributes. 119 o An address block format, where an address block represents sets of 120 addresses in a compact (compressed) form. 122 o A generalized type-length-value (TLV) format representing 123 attributes. Multiple TLVs can be included and associated with a 124 packet, a message, an address, or a set of addresses. 126 The specification has been explicitly designed with the following 127 properties, listed in no particular order, in mind: 129 Parsing logic - the regular expression specification facilitates 130 generic, protocol independent, parsing logic. 132 Extensibility - packets and messages defined by a protocol using 133 this specification are extensible through defining new message 134 types and new TLVs. Existing protocol specifications using this 135 specification will be able to correctly identify and skip such new 136 message types and TLVs, while correctly parsing the remainder of 137 the packet and message. 139 Efficiency - when reported addresses share common bit sequences 140 (e.g. prefixes or IPv6 interface identifiers) the address block 141 representation allows for a compact representation. Compact 142 message headers are ensured through permitting inclusion of only 143 required message header elements. 145 Separation of forwarding and processing - duplicate detection and 146 controlled scope message forwarding decisions can be made using 147 information contained in the message header, without processing 148 the message body. 150 2. Terminology 152 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 153 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 154 document are to be interpreted as described in RFC 2119. [1]. 156 Additionally, this document uses the following terminology: 158 Packet - the top level entity in this specification. Packets are 159 transmitted over a single logical hop and are not forwarded. A 160 packet contains zero or more messages, and may contain a packet 161 header. 163 Message - the fundamental entity carrying protocol information, in 164 the form of addresses and TLVs. Messages are transmitted in 165 packets, and may be forwarded based on their header information. 167 Address - an address of the same length as the source IP address in 168 the IP datagram carrying the packet. 170 TLV - a Type-Length-Value structure. This is a generic way in which 171 an attribute can be represented and correctly parsed, without the 172 parser having to understand the attribute. 174 element - a syntactic entity defined in the regular expression 175 specification, represented using the notation . 177 - if is an 8 or 16 bit field then is also used to 178 represent the value of that field. 180 ? - zero or one occurrences of the preceding element. 182 * - zero or more occurrences of the preceding element. 184 bar - a variable, usually obtained through calculations based on the 185 value(s) of field(s). Variables are introduced into the 186 specification solely as a means to clarify the description. 188 address-length - a variable whose value is the length of an address 189 in octets, it is 4 if using IPv4, 16 if using IPv6. 191 3. Applicability Statement 193 This specification describes a generic multi-message packet format, 194 for carrying MANET routing protocol signals. The specification has 195 been developed from that used by OLSR (The Optimized Link State 196 Routing Protocol) [4]. 198 The specification is designed specifically with IP (IPv4/IPv6) in 199 mind. All addresses within a control message are assumed to be of 200 the same size, deduced from IP. In the case of mixed IPv6 and IPv4 201 addresses, IPv4 addresses are represented as IPv4-mapped IPv6 202 addresses as specified in [2]. 204 The messages defined by this specification are designed to carry 205 routing protocol signals between MANET routers, and to support scope 206 limited diffusion, as well as point to point signaling in a multi-hop 207 network. 209 The packets defined by this specification are designed to carry a 210 number of messages between in a single transmission. The packets may 211 be unicast or multicast and may use any transport protocol (TCP, UDP, 212 ...) appropriate to the protocol using this specification and may 213 travel over a single logical hop which might consist of one or more 214 IP hops. When the diffusion mechanism enabled by this specification 215 is employed, UDP may be most appropriate. 217 This specification is particularly appropriate for extensible 218 protocols. It offers external extensibility in the form of new 219 message types. It offers internal extensibility in the form of TLVs, 220 which may be added to existing message types. 222 A protocol using the multi-message packet format defined by this 223 specification may constrain the syntax (for example requiring a full 224 message header) and features (for example specifying the suggested 225 diffusion mechanism) that the protocol will employ. 227 4. Protocol Overview and Functioning 229 This specification does not describe a protocol. It describes a 230 packet format, which may be used by any mobile ad hoc network routing 231 or other protocol. 233 5. Signaling Framework 235 This section provides syntactical specification of a packet, 236 represented by the element and the elements from which it is 237 composed. The specification is given in the form of regular 238 expressions. Illustrations of specified elements are given in 239 Appendix B. 241 The length of a is obtained as the size of the payload of 242 the transport protocol employed. 244 5.1. Packets 246 is defined by: 248 = {*}? 249 {*}* 251 where is defined in Section 5.2, and is defined 252 in Section 5.4. Successful parsing is terminated when all octets are 253 used. 255 is defined by: 257 = 258 259 ? 260 ? 262 where: 264 is an 8 bit field with all bits cleared ('0'). This field 265 serves to identify that the packet starts with a packet header. 267 is an 8 bit field, specifying the composition of 268 the packet header: 270 bit 0 (pnoseqnum): if cleared ('0'), then the packet header 271 contains a . If set ('1'), then the packet 272 header does not include a . 274 bit 1 (ptlv): if cleared ('0'), then the packet header does not 275 include a TLV block. If set ('1'), then the packet header 276 includes a TLV block. 278 bits 2-7: are RESERVED, and MUST each be cleared ('0') to be in 279 conformance with this version of the specification. 281 is omitted if the pnoseqnum bit is set ('1'), 282 otherwise is a 16 bit field, specifying a packet sequence number. 284 is omitted if the ptlv bit is cleared ('0'), and is 285 otherwise defined in Section 5.3. 287 Note that since the message type zero is reserved (see Section 7), 288 the presence or absence of a packet header can be determined by 289 inspecting the first octet of the packet. 291 5.2. Messages 293 Information is carried through messages. Messages contain: 295 o A message header. 297 o A message TLV block that contains zero or more TLVs, associated 298 with the whole message. 300 o Zero or more address blocks, each containing one or more 301 addresses. 303 o A TLV block, containing zero or more TLVs, following each address 304 block. 306 is defined by: 308 = 309 310 {}* 312 = 313 314 315 317 = ? 318 ? 319 ? 320 ? 322 where: 324 is defined in Section 5.3. 326 is defined in Section 5.2.1. 328 is an 8 bit field, specifying the type of message. A 329 type with all bits cleared ('0') MUST NOT be used. 331 is an 8 bit field, specifying the interpretation of 332 the remainder of the message header: 334 bit 0 (noorig): If cleared ('0'), then is 335 included in the . If set ('1'), then 336 is not included in the . 338 bit 1 (nohoplimit): If cleared ('0'), then is 339 included in the . If set ('1'), then is not included in the . 342 bit 2 (nohopcount): If cleared ('0'), then is 343 included in the . If set ('1'), then is not included in the 346 bit 3 (noseqnum): If cleared ('0'), then is 347 included in the . If set ('1'), then is not included in the . 350 bit 4 (typedep): If cleared ('0'), then the message sequence 351 number in the message is type-independent. If set ('1'), then 352 the message sequence number contained in the message is type 353 dependent (the message originator maintains a sequence number 354 specific to ). This bit MUST be cleared ('0') if the 355 noorig bit is set ('1'). 357 bits 5-7: are RESERVED and MUST each be cleared ('0') to be in 358 conformance with this version of the specification. 360 If bit 0 (noorig) and bit 3 (noseqnum) are both cleared, then the 361 message header provides for duplicate suppression. 363 If bit 1 (nohoplimit) and bit 2 (nohopcount) are both cleared, 364 then the message header provides for scope-delimited forwarding. 366 is a 16 bit field, specifying the size of the , 367 counted in octets. 369 is an identifier of length equal to address- 370 length, which serves to uniquely identify the node that originated 371 the message. 373 is an 8 bit field, which contains the maximum number of 374 logical hops a message should be further transmitted. 376 is an 8 bit field, which contains the number of logical 377 hops a message has traveled. 379 is a 16 bit field, which contains a unique number, 380 generated by the originator node. The , , and, if the typedep bit in the field 382 is set, the of a message serves to uniquely identify 383 the message in the network. 385 5.2.1. Address Blocks 387 An address is specified as a sequence of address-length octets of the 388 form head:mid:tail. An address block is an ordered set of addresses 389 sharing the same head and tail, and having individual mids. Network 390 addresses may be represented using the PREFIX_LENGTH TLV defined in 391 Section 6. 393
is defined by: 395 = 396 397 ? 398 ? 399 ? 400 ? 401 * 403 where: 405 is an 8 bit field containing the number of addresses 406 represented in the address block, which MUST NOT be zero. 408 is an 8 bit field specifying the interpretation of 409 the remainder of the address block: 411 bit 0 (nohead): if cleared ('0'), then is included 412 in , and may be included in . If set ('1'), then and are not 414 included in . 416 bit 1 (notail) and bit 2 (zerotail): MUST NOT both be set ('1'). 417 Otherwise, they are interpreted according to Table 1. 419 +--------+----------+---------------+-----------------+ 420 | notail | zerotail | | | 421 +--------+----------+---------------+-----------------+ 422 | 0 | 0 | included | may be included | 423 | | | | | 424 | 0 | 1 | included | not included | 425 | | | | | 426 | 1 | 0 | not included | not included | 427 +--------+----------+---------------+-----------------+ 429 Table 1 431 bits 3-7: are RESERVED and MUST each be cleared ('0') to be in 432 accordance with this version of the specification. 434 if present is an 8 bit field, which contains the total 435 length (in octets) of the head of all of the addresses. 437 head-length is a variable, defined to equal if 438 present, or 0 otherwise. 440 is omitted if head-length == 0, otherwise it is a field of 441 the head-length leftmost octets of all the addresses. 443 if present is an 8 bit field, which contains the total 444 length (in octets) of the tail of all of the addresses. 446 tail-length is a variable, defined to equal if 447 present, or 0 otherwise. 449 is omitted if tail-length == 0 or if the zerotail bit is set 450 ('1'), otherwise it is a field of the tail-length rightmost octets 451 of all the addresses. If the zerotail bit is set ('1') then the 452 tail-length rightmost octets of all the addresses are all 0. 454 mid-length is a variable, which MUST be non-negative, defined by: 456 * mid-length = address-length - head-length - tail-length 458 is omitted if mid-length == 0, otherwise each is a field 459 of length mid-length octets, representing the mid of the 460 corresponding address in the address block. 462 5.3. TLVs and TLV Blocks 464 A TLV block is defined by: 466 = 467 * 469 where: 471 is a 16 bit field, which contains the total length (in 472 octets) of all of the immediately following elements. 474 is defined in Section 5.3.1. 476 5.3.1. TLVs 478 There are three kinds of TLV, each represented by an element : 480 o A packet TLV, included in a packet header. 482 o A message TLV, included in a message before all address blocks. 484 o An address block TLV, included in a TLV block following an address 485 block. An address block TLV applies to: 487 * all addresses in the address block; OR 489 * any continuous sequence of addresses in the address block; OR 491 * a single address in the address block. 493 is defined by: 495 = 496 497 ? 498 ? 499 ? 500 ? 502 where: 504 is an 8 bit field, specifying the type of the TLV, 505 specific to the TLV kind (i.e. packet, message, or address block 506 TLV). 508 is an 8 bit field specifying the interpretation of 509 the remainder of the TLV: 511 bit 0 (extended) and bit 1 (novalue): MUST NOT both be set ('1'). 512 Otherwise, they are interpreted according to Table 2. 514 +----------+---------+--------------+--------------+ 515 | extended | novalue | | | 516 +----------+---------+--------------+--------------+ 517 | 0 | 0 | 8 bits | included | 518 | | | | | 519 | 0 | 1 | not included | not included | 520 | | | | | 521 | 1 | 0 | 16 bits | included | 522 +----------+---------+--------------+--------------+ 524 Table 2 526 bit 2 (noindex) and bit 3 (singleindex): MUST NOT both be set 527 ('1'). The former MUST be set ('1') and the latter MUST be 528 cleared ('0') for packet or message TLVs. They are interpreted 529 according to Table 3. 531 +---------+-------------+---------------+--------------+ 532 | noindex | singleindex | | | 533 +---------+-------------+---------------+--------------+ 534 | 0 | 0 | included | included | 535 | | | | | 536 | 0 | 1 | included | not included | 537 | | | | | 538 | 1 | 0 | not included | not included | 539 +---------+-------------+---------------+--------------+ 541 Table 3 543 bit 4 (multivalue): this bit serves to specify how the 544 field is interpreted, as specified below. This bit MUST be 545 cleared ('0') for packet or message TLVs, if the singleindex 546 bit is set ('1'), or if the novalue bit is set ('1'). 548 bits 5-7: are RESERVED and MUST each be cleared ('0') to be in 549 accordance with this version of the specification. 551 and when present are each an 8 bit field, 552 interpreted as follows: 554 index-start and index-stop are variables, defined according to 555 Table 4. The variable end-index is defined as follows: 557 + For message and packet TLVs: 559 - end-index = 0 561 + For address block TLVs: 563 - end-index = - 1 565 +---------+-------------+---------------+---------------+ 566 | noindex | singleindex | index-start = | index-stop = | 567 +---------+-------------+---------------+---------------+ 568 | 0 | 0 | | | 569 | | | | | 570 | 0 | 1 | | | 571 | | | | | 572 | 1 | 0 | 0 | end-index | 573 +---------+-------------+---------------+---------------+ 575 Table 4 577 For an address block TLV, the TLV applies to the addresses from 578 position index-start to position index-stop (inclusive) in the 579 address block, where the first address has position zero. 581 number-values is a variable, defined by: 583 + number-values = index-stop - index-start + 1 585 is omitted or is a 8 or 16 bit field according to Table 2. 586 If present it MUST NOT be zero. If the multivalue bit is set 587 ('1') then MUST be an integral multiple of number-values, 588 and the variable single-length is defined by: 590 * single-length = / number-values 592 If the multivalue bit is cleared ('0'), then the variable single- 593 length is defined by: 595 * single-length = 597 if present (see Table 2) is a field of length 598 octets. In an address block TLV, is associated with the 599 addresses from index-start to index-stop, inclusive. If the 600 multivalue bit is cleared ('0') then the whole of this field is 601 associated with each of the indicated addresses. If the 602 multivalue bit is set ('1') then this field is divided equally 603 into number-values fields, each of length single-length octets and 604 these are associated, in order, with the indicated addresses. 606 5.3.2. Constraints 608 TLVs in the same TLV block MUST be sorted in ascending TLV type 609 order. 611 Two or more TLVs of the same type associated with the same address 612 block MUST NOT both cover any address. 614 TLVs of the same type associated with the same address block MUST be 615 sorted in ascending index-start order. 617 5.4. Padding 619 Packet headers and messages MAY be padded to ensure 32 bit alignment 620 of each message contained within the packet and of the overall packet 621 length. 623 All elements are an integer multiple of octets, hence padding can be 624 accomplished by inserting an integer number of elements 625 after the element that is to be 32 bit aligned. 627 The number of elements required to achieve this 32 bit 628 alignment is the smallest number (0 to 3) that, when added to the 629 size of the preceding elements, produces an integer multiple of 4. 631 is an 8 bit field with all bits cleared ('0'). 633 There is no need to indicate if padding is included, since a will always precede either a message or the end of the packet. 635 In the former case, the start of a message is indicated by the next 636 non-zero octet parsed. 638 The padding after a message may be freely changed when a message is 639 forwarded without affecting the message. 641 6. TLV specification 643 This document specifies one address block TLV, which is included to 644 allow a standardized way of representing network addresses. 646 6.1. Address Block TLV Specification 648 +----------------------+------+--------+----------------------------+ 649 | Name | Type | Length | Value | 650 +----------------------+------+--------+----------------------------+ 651 | PREFIX_LENGTH | 0 | 8 bits | Indicates that the address | 652 | | | | is a network address, | 653 | | | | rather than a host | 654 | | | | address. The value is the | 655 | | | | length of the | 656 | | | | prefix/netmask, in bits. | 657 +----------------------+------+--------+----------------------------+ 659 Table 5 661 An address in an address block without an associated PREFIX_LENGTH 662 TLV may be considered to have a prefix length equal to the address 663 length in bits (i.e. address-length times 8). 665 7. IANA Considerations 667 A new registry for message types must be created with initial 668 assignments as specified in Table 6. Future values in the range 669 5-127 can be allocated using standards action [3]. Additionally, 670 values in the range 128-255 are reserved for private/local use. 672 +-------+----------------------------------------+ 673 | Value | Description | 674 +-------+----------------------------------------+ 675 | 0 | MUST NOT be allocated. | 676 | | | 677 | 1-4 | RESERVED | 678 +-------+----------------------------------------+ 680 Table 6 682 Message type 0 MUST NOT be allocated because a zero-octet signifies a 683 packet header and zero-octets are used for padding. Message types 1 684 to 4 are reserved because they are used by OLSR [4], which uses a 685 compatible packet/message header format. 687 A new registry for packet TLV types must be created, with no initial 688 assignments. Future values in the range 0-127 can be allocated using 689 standards action [3]. Additionally, values in the range 128-255 are 690 reserved for private/local use. 692 A new registry for message TLV types must be created with no initial 693 assignments. Future values in the range 0-127 can be allocated using 694 standards action [3]. Additionally, values in the range 128-255 are 695 reserved for private/local use. 697 A new registry for address block TLV types must be created with 698 initial assignments as specified in Table 7. Future values in the 699 range 1-127 can be allocated using standards action [3]. 700 Additionally, values in the range 128-255 are reserved for private/ 701 local use. 703 +--------------------+-------+--------------------------------------+ 704 | Mnemonic | Value | Description | 705 +--------------------+-------+--------------------------------------+ 706 | PREFIX_LENGTH | 0 | Indicates that associated addresses | 707 | | | are network addresses, with given | 708 | | | prefix length, in bits. | 709 +--------------------+-------+--------------------------------------+ 711 Table 7 713 8. Security Considerations 715 Messages are designed to be carriers of protocol information and MAY, 716 at each hop, be forwarded and/or processed according to the 717 information in the message header by the protocol using this 718 specification. 720 For forwarded messages where the message is unchanged by forwarding 721 nodes, then end-to-end security MAY be implemented, between nodes 722 with an existing security association, by including a suitable 723 message TLV containing a cryptographic signature in the message. 724 Since and are the only fields that may be 725 modified when such a message is forwarded in this manner, this 726 signature can be calculated based on the entire message, including 727 the message header, with the and fields set 728 to zero ('0') if present. 730 Packets are designed to carry a number of messages between 731 neighboring nodes in a single transmission and over a single logical 732 hop. Hop-by-hop packet level security MAY be implemented, between 733 nodes with an existing security association, by including a suitable 734 packet TLV containing a cryptographic signature to the packet. Since 735 packets are received as transmitted, this signature can be calculated 736 based on the entire packet, or on parts thereof as appropriate. 738 9. References 740 9.1. Normative References 742 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 743 Levels", RFC 2119, BCP 14, March 1997. 745 [2] Hinden, R. and S. Deering, "IP Version 6 Addressing 746 Architecture", RFC 4291, February 2006. 748 [3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 749 Considerations Section in RFCs", October 1998. 751 9.2. Informative References 753 [4] Clausen, T. and P. Jacquet, "The Optimized Link State Routing 754 Protocol", RFC 3626, October 2003. 756 Appendix A. Examples 758 This appendix contains some examples of parts of this specification. 760 A.1. Address Block Examples 762 The following examples illustrate how some combinations of addresses 763 may be efficiently included in address blocks. These examples are 764 for IPv4, with address-length equal to 4. a, b, c etc. represent 765 distinct, non-zero, octet values. 767 Note that it is permissible to use a less efficient representation, 768 in particular one in which the nohead and notail bits of the 769 semantics octet are set, and hence head-length = 0, tail-length = 0, 770 mid-length = address-length, and the address block consists of the 771 number of addresses, the semantics octet with value 3, and a list of 772 the uncompressed addresses. This is also the most efficient way to 773 represent a single address, and the only way to represent, for 774 example, a.b.c.d and e.f.g.h in one address block. 776 Examples: 778 o To include a.b.c.d, a.b.e.f and a.b.g.h: 780 * head-length = 2; 782 * tail-length = 0; 784 * mid-length = 2; 786 * has notail set (value 2); 788 * and are omitted. 790 The address block is then 3 2 2 a b c d e f g h (11 octets). 792 o To include a.b.c.g and d.e.f.g: 794 * head-length = 0; 796 * tail-length = 1; 798 * mid-length = 3; 800 * has nohead set (value 1); 802 * and are omitted. 804 The address block is then 2 1 1 g a b c d e f (10 octets). 806 o To include a.b.d.e and a.c.d.e: 808 * head-length = 1; 810 * tail-length = 2; 812 * mid-length = 1; 814 * = 0. 816 The address block is then 2 0 1 a 2 d e b c (9 octets). 818 o To include a.b.0.0, a.c.0.0, and a.d.0.0: 820 * head-length = 1; 822 * tail-length = 2; 824 * mid-length = 1; 826 * has zerotail set (value 4); 828 * is omitted. 830 The address block is then 3 4 1 a 2 b c d (8 octets). 832 o To include a.b.0.0 and c.d.0.0: 834 * head-length = 0; 836 * tail-length = 2; 838 * mid-length = 2; 840 * has nohead and zerotail set (value 5); 842 * and are omitted. 844 The address block is then 2 5 2 a b c d (7 octets). 846 A.2. TLV Examples 848 If network addresses a.b.0.0/16, c.d.0.0/16, c.d.e.0/24 and 849 c.d.e.f/32 are to be represented using a single address block 850 containing a.b.0.0, c.d.0.0, c.d.e.0 and c.d.e.f, with the prefix 851 lengths added using one or more address block TLVs of type 852 PREFIX_LENGTH (0), then this can be done in a number of ways. 853 Possible examples are: 855 o Using one multivalue TLV covering all of the addresses: 857 * has noindex and multivalue set (value 20); 859 * and are omitted; 861 * = 4 (single-length = 1). 863 * The TLV is then 0 20 4 16 16 24 32 (7 octets). 865 o Using one multivalue TLV omitting the last address (a prefix 866 length of 32 is the default): 868 * has multivalue set (value 16); 870 * = 0; 872 * = 2 874 * = 3 (single-length = 1). 876 * The TLV is then 0 16 0 2 3 16 16 24 (8 octets). 878 o Using two single value TLVs, omitting the last address. First: 880 * = 0; 882 * = 0; 884 * = 1; 886 * = 1; 888 * = 16. 890 * The TLV is then 0 0 0 1 1 16 (6 octets). 892 Second: 894 * has singlevalue set (value 8); 896 * = 2; 898 * is omitted; 899 * = 1; 901 * = 24. 903 * The TLV is then 0 8 2 1 24 (5 octets). 905 Total length of TLVs is 11 octets. 907 In this case the first of these is the most efficient. In other 908 cases patterns such as the others may be preferred. Regardless of 909 efficiency, any of these may be used. 911 Assuming the definition of an address block TLV with type EXAMPLE 912 which has no value (it is sufficient to simply indicate which 913 addresses are examples), for the same address block, with the second 914 and third addresses being examples, this can be indicated with a 915 single TLV: 917 o has novalue set (value 2); 919 o = 1; 921 o = 2; 923 o and are omitted. 925 o The TLV is then EXAMPLE 2 1 2 (4 octets). 927 Assuming the definition of a message TLV with type DATA which can 928 take a value field of any length, for such a message TLV with 8 929 octets of data (a to h): 931 o has noindex set (value 4); 933 o and are omitted; 935 o = 8. 937 o The TLV is then DATA 4 8 a b c d e f g h (11 octets). 939 If, in this example, the number of data octets were 256 or greater 940 then would also have extended set and have value 5. The 941 length would require two octets (most significant first). The TLV 942 length would be 4 + N octets, where N is the number of data octets 943 (it can be 3 + N octets if N is 255 or less). 945 Appendix B. Illustrations 947 This informative appendix illustrates the elements, which are 948 normatively specified in Section 5 using regular expressions. 950 Bits labeled Reserved, Resv, or Rsv are cleared ('0'). Bits labeled 951 N and M may be cleared ('0') or set ('1'). Octets labeled Padding 952 are cleared ('0'), and are optional. 954 Appendix B.1. Packet 956 0 1 2 3 957 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 958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 959 |0 0 0 0 0 0 0 0| Reserved |0|0| Packet Sequence Number | 960 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 961 | | 962 | Message + Padding | 963 | | 964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 965 | | 966 : ... : 967 | | 968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 969 | | 970 | Message + Padding | 971 | | 972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 974 0 1 2 3 975 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 976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 977 |0 0 0 0 0 0 0 0| Reserved |0|1| Padding | 978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 979 | | 980 | Message + Padding | 981 | | 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 | | 984 : ... : 985 | | 986 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 987 | | 988 | Message + Padding | 989 | | 990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 0 1 2 3 992 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 993 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 994 |0 0 0 0 0 0 0 0| Reserved |1|0| Packet Sequence Number | 995 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 996 | | 997 | Packet TLV Block | 998 | | 999 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1000 | | Padding | 1001 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 | | 1003 | Message + Padding | 1004 | | 1005 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1006 | | 1007 : ... : 1008 | | 1009 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1010 | | 1011 | Message + Padding | 1012 | | 1013 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1015 0 1 2 3 1016 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 1017 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1018 |0 0 0 0 0 0 0 0| Reserved |1|1| | 1019 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1020 | | 1021 | Packet TLV Block | 1022 | | 1023 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1024 | | Padding | 1025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1026 | | 1027 | Message + Padding | 1028 | | 1029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1030 | | 1031 : ... : 1032 | | 1033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1034 | | 1035 | Message + Padding | 1036 | | 1037 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1038 0 1 2 3 1039 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 1040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1041 | | 1042 | Message + Padding | 1043 | | 1044 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1045 | | 1046 : ... : 1047 | | 1048 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1049 | | 1050 | Message + Padding | 1051 | | 1052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 Appendix B.2. Message and Padding 1056 0 1 2 3 1057 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 1058 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1059 | Message Type | Rsv |N|0|0|0|0| Message Size | 1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 | Originator Address | 1062 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1063 | Hop Limit | Hop Count | Message Sequence Number | 1064 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1065 | | 1066 | Message Body | 1067 | | 1068 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1069 | | Padding | 1070 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1072 0 1 2 3 1073 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 1074 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1075 | Message Type | Rsv |0|0|0|0|1| Message Size | 1076 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1077 | Hop Limit | Hop Count | Message Sequence Number | 1078 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1079 | | 1080 | Message Body | 1081 | | 1082 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1083 | | Padding | 1084 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1085 0 1 2 3 1086 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 1087 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1088 | Message Type | Rsv |N|0|0|1|0| Message Size | 1089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1090 | Originator Address | 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1092 | Hop Count | Message Sequence Number | | 1093 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1094 | | 1095 | Message Body | 1096 | | 1097 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1098 | | Padding | 1099 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1101 0 1 2 3 1102 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 1103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1104 | Message Type | Rsv |0|0|0|1|1| Message Size | 1105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1106 | Hop Count | Message Sequence Number | | 1107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1108 | | 1109 | Message Body | 1110 | | 1111 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1112 | | Padding | 1113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1115 0 1 2 3 1116 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 1117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1118 | Message Type | Rsv |N|0|1|0|0| Message Size | 1119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1120 | Originator Address | 1121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1122 | Hop Limit | Message Sequence Number | | 1123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1124 | | 1125 | Message Body | 1126 | | 1127 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1128 | | Padding | 1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1130 0 1 2 3 1131 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 1132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1133 | Message Type | Rsv |N|0|1|0|1| Message Size | 1134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1135 | Hop Limit | Message Sequence Number | | 1136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1137 | | 1138 | Message Body | 1139 | | 1140 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1141 | | Padding | 1142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1144 0 1 2 3 1145 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 1146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1147 | Message Type | Rsv |N|0|1|1|0| Message Size | 1148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1149 | Originator Address | 1150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1151 | Message Sequence Number | | 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1153 | | 1154 | Message Body | 1155 | | 1156 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1157 | | Padding | 1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1160 0 1 2 3 1161 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 1162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1163 | Message Type | Rsv |N|0|1|1|1| Message Size | 1164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1165 | Message Sequence Number | | 1166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1167 | | 1168 | Message Body | 1169 | | 1170 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1171 | | Padding | 1172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1173 0 1 2 3 1174 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 1175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1176 | Message Type | Rsv |N|1|0|0|0| Message Size | 1177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1178 | Originator Address | 1179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1180 | Hop Limit | Hop Count | | 1181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1182 | | 1183 | Message Body | 1184 | | 1185 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 | | Padding | 1187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1189 0 1 2 3 1190 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 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | Message Type | Rsv |N|1|0|0|1| Message Size | 1193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1194 | Hop Limit | Hop Count | | 1195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1196 | | 1197 | Message Body | 1198 | | 1199 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1200 | | Padding | 1201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1203 0 1 2 3 1204 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 1205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1206 | Message Type | Rsv |N|1|0|1|0| Message Size | 1207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1208 | Originator Address | 1209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1210 | Hop Count | | 1211 +-+-+-+-+-+-+-+-+ | 1212 | Message Body | 1213 | | 1214 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1215 | | Padding | 1216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1217 0 1 2 3 1218 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 1219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1220 | Message Type | Rsv |N|1|0|1|1| Message Size | 1221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1222 | Hop Count | | 1223 +-+-+-+-+-+-+-+-+ | 1224 | Message Body | 1225 | | 1226 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1227 | | Padding | 1228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1230 0 1 2 3 1231 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 1232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1233 | Message Type | Rsv |N|1|1|0|0| Message Size | 1234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1235 | Originator Address | 1236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1237 | Hop Limit | | 1238 +-+-+-+-+-+-+-+-+ | 1239 | Message Body | 1240 | | 1241 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1242 | | Padding | 1243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1245 0 1 2 3 1246 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 1247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1248 | Message Type | Rsv |N|1|1|0|1| Message Size | 1249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1250 | Hop Limit | | 1251 +-+-+-+-+-+-+-+-+ | 1252 | Message Body | 1253 | | 1254 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1255 | | Padding | 1256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1257 0 1 2 3 1258 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 1259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1260 | Message Type | Rsv |N|1|1|1|0| Message Size | 1261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1262 | Originator Address | 1263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1264 | | 1265 | Message Body | 1266 | | 1267 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1268 | | Padding | 1269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1271 0 1 2 3 1272 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 1273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1274 | Message Type | Rsv |N|1|1|1|0| Message Size | 1275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1276 | | 1277 | Message Body | 1278 | | 1279 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1280 | | Padding | 1281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1283 Appendix B.3. Message Body 1285 0 1 2 3 1286 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 1287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1288 | | 1289 | Message TLV Block | 1290 | +-+-+-+-+-+-+-+-+ 1291 | | | 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1293 | | 1294 | Address Block | 1295 | | 1296 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1297 | | | 1298 +-+-+-+-+-+-+-+-+ | 1299 | Address TLV Block | 1300 | | 1301 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1302 | | | 1303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1304 | | 1305 : ... : 1306 | | 1307 | +-+-+-+-+-+-+-+-+ 1308 | | | 1309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1310 | | 1311 | Address Block | 1312 | | 1313 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1314 | | | 1315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1316 | | 1317 | Address TLV Block | 1318 | | 1319 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1320 | | 1321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1323 Appendix B.4. Address Block 1325 0 1 2 3 1326 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 1327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1328 | Number Addrs | Resv |0|0|0| Head Length | Head | 1329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1330 | Head (cont) | Tail Length | Tail | 1331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1332 | Mid | | 1333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1334 | | 1335 : ... : 1336 | | 1337 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1338 | | Mid | 1339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1341 0 1 2 3 1342 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 1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1344 | Number Addrs | Resv |0|0|1| Tail Length | Tail | 1345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1346 | Tail (cont) | Mid | | 1347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1348 | | 1349 : ... : 1350 | | 1351 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1352 | | Mid | 1353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1355 0 1 2 3 1356 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 1357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1358 | Number Addrs | Resv |0|1|0| Head Length | Head | 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | Head (cont) | Mid | | 1361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1362 | | 1363 : ... : 1364 | | 1365 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1366 | | Mid | 1367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1368 0 1 2 3 1369 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 1370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1371 | Number Addrs | Resv |0|1|1| Mid | 1372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1373 | Mid (cont) | | 1374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1375 | | 1376 : ... : 1377 | | 1378 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1379 | | Mid | 1380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1381 | Mid (cont) | 1382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 0 1 2 3 1385 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 1386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1387 | Number Addrs | Resv |1|0|0| Head Length | Head | 1388 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1389 | Head (cont) | Tail Length | Mid | 1390 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1391 | | 1392 : ... : 1393 | | 1394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1395 | Mid | 1396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1398 0 1 2 3 1399 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 1400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1401 | Number Addrs | Resv |1|0|1| Tail Length | Mid | 1402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1403 | Mid (cont) | | 1404 +-+-+-+-+-+-+-+-+ | 1405 | | 1406 : ... : 1407 | | 1408 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1409 | | Mid | 1410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1412 Appendix B.5. TLV Block 1414 0 1 2 3 1415 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 1416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1417 | Length | | 1418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1419 | | 1420 | TLV | 1421 | +-+-+-+-+-+-+-+-+ 1422 | | | 1423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1424 | | 1425 : ... : 1426 | | 1427 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1428 | | | 1429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1430 | | 1431 | TLV | 1432 | +-+-+-+-+-+-+-+-+ 1433 | | 1434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1436 Appendix B.6. TLV 1438 0 1 2 3 1439 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 1440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1441 | Type |Resv |M|0|0|0|0| Index Start | Index Stop | 1442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1443 | Length | | 1444 +-+-+-+-+-+-+-+-+ | 1445 | Value | 1446 | | 1447 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1448 | | 1449 +-+-+-+-+-+-+-+-+ 1450 0 1 2 3 1451 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 1452 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1453 | Type |Resv |M|0|0|0|1| Index Start | Index Stop | 1454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1455 | Length | | 1456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1457 | | 1458 | Value | 1459 | | 1460 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1461 | | 1462 +-+-+-+-+-+-+-+-+ 1464 0 1 2 3 1465 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 1466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1467 | Type |Resv |0|0|0|1|0| Index Start | Index Stop | 1468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1470 0 1 2 3 1471 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 1472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1473 | Type |Resv |M|0|1|0|0| Length | | 1474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1475 | | 1476 | Value | 1477 | | 1478 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1479 | | 1480 +-+-+-+-+-+-+-+-+ 1482 0 1 2 3 1483 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 1484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1485 | Type |Resv |M|0|1|0|1| Length | 1486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1487 | | 1488 | Value | 1489 | | 1490 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1491 | | 1492 +-+-+-+-+-+-+-+-+ 1493 0 1 2 3 1494 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 1495 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1496 | Type |Resv |0|0|1|1|0| 1497 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1499 0 1 2 3 1500 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 1501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1502 | Type |Resv |0|1|0|0|0| Index Start | Length | 1503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1504 | | 1505 | Value | 1506 | | 1507 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1508 | | 1509 +-+-+-+-+-+-+-+-+ 1511 0 1 2 3 1512 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 1513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1514 | Type |Resv |0|1|0|0|1| Index Start | Length | 1515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1516 | Length (cont) | | 1517 +-+-+-+-+-+-+-+-+ | 1518 | | 1519 | Value | 1520 | | 1521 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1522 | | 1523 +-+-+-+-+-+-+-+-+ 1525 0 1 2 3 1526 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 1527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1528 | Type |Resv |0|1|0|1|0| Index Start | 1529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1531 Appendix C. Complete Example 1533 An example packet, using IPv4 addresses (length four octets) is 1534 shown. This packet has a header, indicated by the initial octet 0. 1535 The packet header has semantics octet 0, and hence has a packet 1536 sequence number, but no packet TLV block. 1538 The packet contains a single message. This message has semantics 1539 octet 0, and hence has a complete message header, including 1540 originator address, hop limit, hop count and message sequence number 1541 (which is type independent). The message has a message TLV block 1542 with content length 9 octets, containing a single TLV. This TLV has 1543 the noindex bit of its semantics octet 4 set, and has value length 6 1544 octets. The message then has two address blocks each with a 1545 following TLV block. 1547 The first address block contains 3 addresses. It has the notail bit 1548 of its semantics octet 2 set, and has head length 2 octets, hence mid 1549 length two octets. It is followed by a TLV block, with content 1550 length 9 octets, containing two TLVs. The first of these TLVs has 1551 the noindex bit of its semantics octet 4 set, and has a single value 1552 of length 2 octets, which applies to all of the addresses in the 1553 address block. The second of these TLVs has the novalue bit of its 1554 semantics octet 2 set, and hence has no length or value fields. It 1555 does have index fields, which indicate those addresses this TLV 1556 applies to. 1558 The second address block contains 2 addresses. It has the nohead and 1559 zerotail bits of its semantics octet 5 set, and has tail length 2 1560 octets, hence mid length two octets. The two tail octets of each 1561 address are zero. It is followed by a TLV block with content length 1562 5 octets. This TLV block contains a single TLV of type PREFIX_LENGTH 1563 that has the multivalue and noindex bits of its semantics octet 20 1564 set, and a value field length of 2 octets, indicating two values each 1565 of one octet length. There is one final padding octet 0 that is not 1566 included in the message length of 59 octets. 1568 0 1 2 3 1569 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 1570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1571 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0| Packet Sequence Number | 1572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1573 | Message Type |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 1 1 1 0 1 1| 1574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1575 | Originator Address | 1576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1577 | Hop Limit | Hop Count | Message Sequence Number | 1578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1579 |0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| TLV Type |0 0 0 0 0 1 0 0| 1580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1581 |0 0 0 0 0 1 1 0| Value | 1582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1583 | Value (cont) |0 0 0 0 0 0 1 1| 1584 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1585 |0 0 0 0 0 0 1 0|0 0 0 0 0 0 1 0| Head | 1586 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1587 | Mid | Mid | 1588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1589 | Mid |0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1| 1590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1591 | TLV Type |0 0 0 0 0 1 0 0|0 0 0 0 0 0 1 0| Value | 1592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1593 | Value (cont) | TLV Type |0 0 0 0 0 0 1 0| Index Start | 1594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1595 | Index Stop |0 0 0 0 0 0 1 0|0 0 0 0 0 1 0 1|0 0 0 0 0 0 1 0| 1596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1597 | Mid | Mid | 1598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1599 |0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1| PREFIX_LENGTH |0 0 0 1 0 1 0 0| 1600 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1601 |0 0 0 0 0 0 1 0| Value0 | Value1 |0 0 0 0 0 0 0 0| 1602 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1604 Appendix D. Contributors 1606 This specification is the result of the joint efforts of the 1607 following contributors from the OLSRv2 Design Team -- listed 1608 alphabetically. 1610 o Cedric Adjih, INRIA, France, 1612 o Emmanuel Baccelli, Hitachi Labs Europe, France, 1613 1615 o Thomas Heide Clausen, LIX, Ecole Polytechnique, France, 1616 1618 o Justin W. Dean, NRL, USA 1620 o Christopher Dearlove, BAE Systems, UK, 1621 1623 o Satoh Hiroki, Hitachi SDL, Japan, 1625 o Philippe Jacquet, INRIA, France, 1627 o Monden Kazuya, Hitachi SDL, Japan, 1629 Appendix E. Acknowledgements 1631 The authors would like to acknowledge the team behind OLSRv1, as 1632 specified in RFC 3626, including Anis Laouiti, Pascale Minet, Laurent 1633 Viennot (all at INRIA, France), and Amir Qayyum (Center for Advanced 1634 Research in Engineering, Pakistan) for their contributions. 1636 The authors would like to gratefully acknowledge the following people 1637 for intense technical discussions, early reviews and comments on the 1638 specification and its components: Joe Macker (NRL), Alan Cullen (BAE 1639 Systems), Ian Chakeres (Boeing), Charlie E. Perkins (Nokia), Andreas 1640 Schjonhaug (LIX), Florent Brunneau (LIX), Yasunori Owada (Niigata 1641 University) and the entire IETF MANET working group. 1643 Authors' Addresses 1645 Thomas Heide Clausen 1646 LIX, Ecole Polytechnique, France 1648 Phone: +33 6 6058 9349 1649 Email: T.Clausen@computer.org 1650 URI: http://www.thomasclausen.org/ 1652 Christopher M. Dearlove 1653 BAE Systems Advanced Technology Centre 1655 Phone: +44 1245 242194 1656 Email: chris.dearlove@baesystems.com 1657 URI: http://www.baesystems.com/ 1659 Justin W. Dean 1660 Naval Research Laboratory 1662 Phone: +1 202 767 3397 1663 Email: jdean@itd.nrl.navy.mil 1664 URI: http://pf.itd.nrl.navy.mil/ 1666 Cedric Adjih 1667 INRIA Rocquencourt 1669 Phone: +33 1 3963 5215 1670 Email: Cedric.Adjih@inria.fr 1671 URI: http://menetou.inria.fr/~adjih/ 1673 Full Copyright Statement 1675 Copyright (C) The IETF Trust (2007). 1677 This document is subject to the rights, licenses and restrictions 1678 contained in BCP 78, and except as set forth therein, the authors 1679 retain all their rights. 1681 This document and the information contained herein are provided on an 1682 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1683 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1684 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1685 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1686 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1687 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1689 Intellectual Property 1691 The IETF takes no position regarding the validity or scope of any 1692 Intellectual Property Rights or other rights that might be claimed to 1693 pertain to the implementation or use of the technology described in 1694 this document or the extent to which any license under such rights 1695 might or might not be available; nor does it represent that it has 1696 made any independent effort to identify any such rights. Information 1697 on the procedures with respect to rights in RFC documents can be 1698 found in BCP 78 and BCP 79. 1700 Copies of IPR disclosures made to the IETF Secretariat and any 1701 assurances of licenses to be made available, or the result of an 1702 attempt made to obtain a general license or permission for the use of 1703 such proprietary rights by implementers or users of this 1704 specification can be obtained from the IETF on-line IPR repository at 1705 http://www.ietf.org/ipr. 1707 The IETF invites any interested party to bring to its attention any 1708 copyrights, patents or patent applications, or other proprietary 1709 rights that may cover technology that may be required to implement 1710 this standard. Please address the information to the IETF at 1711 ietf-ipr@ietf.org. 1713 Acknowledgment 1715 Funding for the RFC Editor function is provided by the IETF 1716 Administrative Support Activity (IASA).