idnits 2.17.1 draft-ietf-manet-tlv-naming-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5444, but the abstract doesn't seem to directly say this. It does mention RFC5444 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5444, updated by this document, for RFC5378 checks: 2006-03-01) -- 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 (May 7, 2015) is 3276 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mobile Ad hoc Networking (MANET) C. Dearlove 3 Internet-Draft BAE Systems ATC 4 Updates: 5444 (if approved) T. Clausen 5 Intended status: Standards Track LIX, Ecole Polytechnique 6 Expires: November 8, 2015 May 7, 2015 8 TLV Naming in the MANET Generalized Packet/Message Format 9 draft-ietf-manet-tlv-naming-02 11 Abstract 13 TLVs (type-length-value structures) as defined by RFC5444 have both a 14 type (one octet) and a type extension (one octet), together forming a 15 full type (of two octets). RFC5444 sets up IANA registries for TLV 16 types, specifying that an allocation of a TLV type entails creation 17 of an IANA registry for the corresponding type extensions. 19 In some cases, reserving all 256 type extensions for use for a common 20 purpose for a given TLV is meaningful, and thus it makes sense to 21 record a common name for such a TLV type (and all of its type 22 extensions) in the corresponding IANA registries. An example of such 23 is a LINK_METRIC TLV Type, with its type extensions reserved for use 24 to be indicating the "kind" of metric expressed by the value of the 25 TLV. 27 In some other cases, there may not be 256 full types that share a 28 common purpose and, as such, it is not meaningful to record a common 29 name for all the type extensions for a TLV type in the corresponding 30 IANA registries. Rather, it is appropriate to record an individual 31 name per full type. 33 This document reorganizes the naming of already allocated TLV types 34 and type extensions in those registries to use names appropriately. 35 It has no consequences in terms of any protocol implementation. 37 This document also updates the Expert Review guidelines from RFC5444, 38 so as to establish a policy for consistent naming of future TLV type 39 and type extension allocations. It makes no other changes to 40 RFC5444. 42 Status of this Memo 44 This Internet-Draft is submitted in full conformance with the 45 provisions of BCP 78 and BCP 79. 47 Internet-Drafts are working documents of the Internet Engineering 48 Task Force (IETF). Note that other groups may also distribute 49 working documents as Internet-Drafts. The list of current Internet- 50 Drafts is at http://datatracker.ietf.org/drafts/current/. 52 Internet-Drafts are draft documents valid for a maximum of six months 53 and may be updated, replaced, or obsoleted by other documents at any 54 time. It is inappropriate to use Internet-Drafts as reference 55 material or to cite them other than as "work in progress." 57 This Internet-Draft will expire on November 8, 2015. 59 Copyright Notice 61 Copyright (c) 2015 IETF Trust and the persons identified as the 62 document authors. All rights reserved. 64 This document is subject to BCP 78 and the IETF Trust's Legal 65 Provisions Relating to IETF Documents 66 (http://trustee.ietf.org/license-info) in effect on the date of 67 publication of this document. Please review these documents 68 carefully, as they describe your rights and restrictions with respect 69 to this document. Code Components extracted from this document must 70 include Simplified BSD License text as described in Section 4.e of 71 the Trust Legal Provisions and are provided without warranty as 72 described in the Simplified BSD License. 74 Table of Contents 76 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 77 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 78 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 79 3.1. Expert Review: Evaluation Guidelines . . . . . . . . . . . 6 80 3.2. Updated IANA Registries . . . . . . . . . . . . . . . . . 7 81 4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 82 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 83 6. Normative References . . . . . . . . . . . . . . . . . . . . . 15 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 86 1. Introduction 88 This document reorganizes and rationalizes the naming of TLVs (type- 89 length-value structures), defined by [RFC5444] and recorded by IANA 90 in the Mobile Ad hoc NETwork (MANET) Parameters registries "Packet 91 TLV Types", "Message TLV Types", and "Address Block TLV Types". 93 This document reorganizes the naming of already allocated Packet, 94 Message and Address Block TLV types, and their corresponding Type 95 Extensions, and updates corresponding IANA registries. 97 TLVs have a type (one octet) and a type extension (one octet) which 98 together form a full type (of two octets). A TLV may omit the type 99 extension when it is zero, but that applies only to its 100 representation, it still has a type extension of zero. A TLV type 101 defines an IANA registry of type extensions for that type. 103 There have been two forms of TLV allocation. 105 The first, but less common, form of allocation has been that 106 allocation of the type has immediately defined (but not necessarily 107 allocated) all the corresponding type extensions for versions of that 108 type. This applies, for example, to the Address Block TLV 109 LINK_METRIC specified in [RFC7181]. The LINK_METRIC type extensions 110 are all available for allocation for different definitions of link 111 metric. It is appropriate in this case to apply the name LINK_METRIC 112 to the type, and also to all the full types corresponding to that 113 type, as has been done. Type extensions can then be individually 114 named, or can be simply referred to by their number. 116 The second, more common, form of allocation has been that for a TLV 117 type, only type extension 0, and possibly the type extension 1, are 118 defined. An example is the Address Block TLV LINK_STATUS defined in 119 [RFC6130], where only type extension 0 is allocated. It is not 120 reasonable to assume that the remaining 255 type extensions will be 121 allocated to forms of LINK_STATUS. (Other forms of link status are 122 already catered to by the introduction, in [RFC7188], of a registry 123 for values of the LINK_STATUS TLV.) Thus the name LINK_STATUS should 124 be attached to that specific type extension for that type, i.e., to 125 the full type, and not to the TLV type when used with all other type 126 extensions therefore. This was, however, not done as part of the 127 initial registration of this TLV type. Effectively, this leaves, for 128 the LINK_STAUS TLV type, the type extensions 1-255 either unavailable 129 for allocation (if applying strictly the interpretation that they 130 must relate to a LINK_STATUS), or counterintuitively named for their 131 intended function. 133 The purpose of this document is to change how names of the second 134 form are applied, and recorded in IANA registries, and to provide 135 guidelines and instructions for future TLV type allocations. This is 136 to facilitate the addition of new TLVs using type extensions other 137 than 0, but without them having inappropriate names attached. So, 138 for example, LINK_STATUS will become the name of the full type (as 139 composed by the TLV type 3 and the TLV type extension 0), and will 140 cease being the name of the TLV type 3. This leaves the question of 141 how to name the type. As it is not clear what other TLVs might be 142 defined for other type extensions of the same type, it is proposed to 143 leave the type currently unnamed, specified only by number. 145 This document also updates the Expert Review guidelines from 146 [RFC5444], so as to establish a policy for consisteng naming of 147 future TLV type and type extension allocations. 149 For clarity, all currently allocated TLVs in [RFC5497], [RFC6130], 150 [RFC7181] and [RFC7182] will be listed in the IANA considerations 151 section of this document, indicating no change when that is 152 appropriate (such as the LINK_METRIC TLV). The only changes are of 153 naming. 155 Note that nothing in this draft changes the operation of any 156 protocol. This naming is already used, in effect, in [RFC6130] and 157 [RFC7181], currently the main users of allocated TLVs. For example 158 the former indicates that all usage of LINK_STATUS refers to that TLV 159 with type extension 0. 161 2. Terminology 163 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 164 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 165 "OPTIONAL" in this document are to be interpreted as described in 166 [RFC2119]. 168 All references to elements such as packet, message and TLV in this 169 document refer to those defined in [RFC5444]. 171 3. IANA Considerations 173 This document updates the Expert Review evaluation guidelines for 174 Packet TLV Type, Message TLV Type, and Address Block TLV Type 175 allocations, from [RFC5444], and updates the registries for already 176 made allocations to follow these guidelines. 178 3.1. Expert Review: Evaluation Guidelines 180 For registration from the registries for Packet TLV Types, Message 181 TLV Types, and Address Block TLV Types, the following guidelines 182 apply, in addition to those given in section 6.1 in [RFC5444]: 184 o If the reguested TLV Type immediately defines (but not necessarily 185 allocates) all the corresponding type extensions for versions of 186 that type, then a common name SHOULD be assigned for the TLV type. 188 o Otherwise, if the reguested TLV Type does not immediately define 189 all the corresponding type extensions for versions of that type, 190 then a common name SHOULD NOT be assigned for that TLV type. 191 Instead, it is RECOMMENDED that: 193 * The "description" for the allocated TLV type be "Defined by 194 Type Extension"; 196 * For Packet TLV Types, that the Type Extension registry, created 197 for the TLV Type, be named "Type XX Packet TLV Type 198 Extensions", with XX replaced by the numerical value of the TLV 199 Type. 201 * For Message TLV Types, that the Type Extension registry, 202 created for the TLV Type, be named "Type XX Message TLV Type 203 Extensions", with XX replaced by the numerical value of the TLV 204 Type. 206 * For Address Block TLV Types, that the Type Extension registry, 207 created for the TLV Type, be named "Type XX Address Block TLV 208 Type Extensions", with XX replaced by the numerical value of 209 the TLV Type. 211 * That each Type Extension be given a name when allocated. 213 Note that the former case is unchanged by this specification, this 214 currently includes TLV types named ICV, TIMESTAMP and LINK_METRIC. 216 3.2. Updated IANA Registries 218 The following changes all apply to the IANA registry "Mobile Ad hoc 219 NETwork (MANET) Parameters". For clarity, registries that are 220 unchanged, including those that define all type extensions of a TLV 221 type, are listed as unchanged. 223 The IANA registry "Packet TLV Types" is unchanged. 225 The IANA Registry "ICV Packet TLV Type Extensions" is unchanged. 227 The IANA Registry "TIMESTAMP Packet TLV Type Extensions" is 228 unchanged. 230 The IANA Registry "Message TLV Types" is changed to Table 1. 232 +---------+-------------------------------+-----------+ 233 | Type | Description | Reference | 234 +---------+-------------------------------+-----------+ 235 | 0 | Defined by Type Extension | [RFC5497] | 236 | 1 | Defined by Type Extension | [RFC5497] | 237 | 2-4 | Unassigned | | 238 | 5 | ICV | [RFC7182] | 239 | 6 | TIMESTAMP | [RFC7182] | 240 | 7 | Defined by Type Extension | [RFC7181] | 241 | 8 | Defined by Type Extension | [RFC7181] | 242 | 9-223 | Unassigned | | 243 | 224-255 | Reserved for Experimental Use | [RFC5444] | 244 +---------+-------------------------------+-----------+ 246 Table 1: Message TLV Types 248 The IANA Registry "INTERVAL_TIME Message TLV Type Extensions" is 249 renamed as "Type 0 Message TLV Type Extensions" and changed to 250 Table 2. 252 +-----------+---------------+---------------------------+-----------+ 253 | Type | Name | Description | Reference | 254 | Extension | | | | 255 +-----------+---------------+---------------------------+-----------+ 256 | 0 | INTERVAL_TIME | The maximum time before | [RFC5497] | 257 | | | another message of the | | 258 | | | same type as this message | | 259 | | | from the same originator | | 260 | | | should be received | | 261 | 1-223 | | Unassigned | | 262 | 224-255 | | Reserved for Experimental | [RFC5497] | 263 | | | Use | | 264 +-----------+---------------+---------------------------+-----------+ 266 Table 2: Type 0 Message TLV Type Extensions 268 The IANA Registry "VALIDITY_TIME Message TLV Type Extensions" is 269 renamed as "Type 1 Message TLV Type Extensions" and changed to 270 Table 3. 272 +-----------+---------------+---------------------------+-----------+ 273 | Type | Name | Description | Reference | 274 | Extension | | | | 275 +-----------+---------------+---------------------------+-----------+ 276 | 0 | VALIDITY_TIME | The time from receipt of | [RFC5497] | 277 | | | the message during which | | 278 | | | the information contained | | 279 | | | in the message is to be | | 280 | | | considered valid | | 281 | 1-223 | | Unassigned | | 282 | 224-255 | | Reserved for Experimental | [RFC5497] | 283 | | | Use | | 284 +-----------+---------------+---------------------------+-----------+ 286 Table 3: Type 1 Message TLV Type Extensions 288 The IANA Registry "ICV Message TLV Type Extensions" is unchanged. 290 The IANA Registry "TIMESTAMP Message TLV Type Extensions" is 291 unchanged. 293 The IANA Registry "MPR_WILLING Message Type Extensions" is renamed as 294 "Type 7 Message TLV Type Extensions" and changed to Table 4. 296 +-----------+-------------+-----------------------------+-----------+ 297 | Type | Name | Description | Reference | 298 | Extension | | | | 299 +-----------+-------------+-----------------------------+-----------+ 300 | 0 | MPR_WILLING | Bits 0-3 specify the | [RFC7181] | 301 | | | originating router's | | 302 | | | willingness to act as a | | 303 | | | flooding MPR; bits 4-7 | | 304 | | | specify the originating | | 305 | | | router's willingness to act | | 306 | | | as a routing MPR | | 307 | 1-223 | | Unassigned | | 308 | 224-255 | | Reserved for Experimental | [RFC7181] | 309 | | | Use | | 310 +-----------+-------------+-----------------------------+-----------+ 312 Table 4: Type 7 Message TLV Type Extensions 314 The IANA Registry "CONT_SEQ_NUM Message Type Extensions" is renamed 315 as "Type 8 Message TLV Type Extensions" and changed to Table 5. 317 +-----------+--------------+----------------------------+-----------+ 318 | Type | Name | Description | Reference | 319 | Extension | | | | 320 +-----------+--------------+----------------------------+-----------+ 321 | 0 | CONT_SEQ_NUM | Specifies a content | [RFC7181] | 322 | | (COMPLETE) | sequence number for this | | 323 | | | complete message | | 324 | 1 | CONT_SEQ_NUM | Specifies a content | [RFC7181] | 325 | | (INCOMPLETE) | sequence number for this | | 326 | | | incomplete message | | 327 | 2-223 | | Unassigned | | 328 | 224-255 | | Reserved for Experimental | [RFC7181] | 329 | | | Use | | 330 +-----------+--------------+----------------------------+-----------+ 332 Table 5: Type 8 Message TLV Type Extensions 334 The IANA Registry "Address Block TLV Types" is changed to Table 6. 336 +---------+-------------------------------+-----------+ 337 | Type | Description | Reference | 338 +---------+-------------------------------+-----------+ 339 | 0 | Defined by Type Extension | [RFC5497] | 340 | 1 | Defined by Type Extension | [RFC5497] | 341 | 2 | Defined by Type Extension | [RFC6130] | 342 | 3 | Defined by Type Extension | [RFC6130] | 343 | 4 | Defined by Type Extension | [RFC6130] | 344 | 5 | ICV | [RFC7182] | 345 | 6 | TIMESTAMP | [RFC7182] | 346 | 7 | LINK_METRIC | [RFC7181] | 347 | 8 | Defined by Type Extension | [RFC7181] | 348 | 9 | Defined by Type Extension | [RFC7181] | 349 | 10 | Defined by Type Extension | [RFC7181] | 350 | 11-223 | Unassigned | | 351 | 224-255 | Reserved for Experimental Use | [RFC5444] | 352 +---------+-------------------------------+-----------+ 354 Table 6: Address Block TLV Types 356 The IANA Registry "INTERVAL_TIME Address Block TLV Type Extensions" 357 is renamed as "Type 0 Address Block TLV Type Extensions" and changed 358 to Table 7. 360 +-----------+---------------+---------------------------+-----------+ 361 | Type | Name | Description | Reference | 362 | Extension | | | | 363 +-----------+---------------+---------------------------+-----------+ 364 | 0 | INTERVAL_TIME | The maximum time before | [RFC5497] | 365 | | | another message of the | | 366 | | | same type as this message | | 367 | | | from the same originator | | 368 | | | and containing this | | 369 | | | address should be | | 370 | | | received | | 371 | 1-223 | | Unassigned | | 372 | 224-255 | | Reserved for Experimental | [RFC5497] | 373 | | | Use | | 374 +-----------+---------------+---------------------------+-----------+ 376 Table 7: Type 0 Address Block TLV Type Extensions 378 The IANA Registry "VALIDITY_TIME Address Block Type Extensions" is 379 renamed as "Type 1 Address Block TLV Type Extensions" and changed to 380 Table 8. 382 +-----------+---------------+---------------------------+-----------+ 383 | Type | Name | Description | Reference | 384 | Extension | | | | 385 +-----------+---------------+---------------------------+-----------+ 386 | 0 | VALIDITY_TIME | The time from receipt of | [RFC5497] | 387 | | | the address during which | | 388 | | | the information regarding | | 389 | | | this address is to be | | 390 | | | considered valid | | 391 | 1-223 | | Unassigned | | 392 | 224-255 | | Reserved for Experimental | [RFC5497] | 393 | | | Use | | 394 +-----------+---------------+---------------------------+-----------+ 396 Table 8: Type 1 Address Block TLV Type Extensions 398 The IANA Registry "LOCAL_IF Address Block Type Extensions" is renamed 399 as "Type 2 Address Block TLV Type Extensions" and changed to Table 9. 401 +-----------+----------+-----------------------+--------------------+ 402 | Type | Name | Description | Reference | 403 | Extension | | | | 404 +-----------+----------+-----------------------+--------------------+ 405 | 0 | LOCAL_IF | This value is to be | [RFC7188][RFC6130] | 406 | | | interpreted according | | 407 | | | to the registry | | 408 | | | [LOCAL_IF TLV Values] | | 409 | 1-223 | | Unassigned | | 410 | 224-255 | | Reserved for | [RFC6130] | 411 | | | Experimental Use | | 412 +-----------+----------+-----------------------+--------------------+ 414 Table 9: Type 2 Address Block TLV Type Extensions 416 The IANA Registry "LINK_STATUS Address Block Type Extensions" is 417 renamed as "Type 3 Address Block TLV Type Extensions" and changed to 418 Table 10. 420 +-----------+-------------+--------------------+--------------------+ 421 | Type | Name | Description | Reference | 422 | Extension | | | | 423 +-----------+-------------+--------------------+--------------------+ 424 | 0 | LINK_STATUS | This value is to | [RFC7188][RFC6130] | 425 | | | be interpreted | | 426 | | | according to the | | 427 | | | registry | | 428 | | | [LINK_STATUS TLV | | 429 | | | Values] | | 430 | 1-223 | | Unassigned | | 431 | 224-255 | | Reserved for | [RFC6130] | 432 | | | Experimental Use | | 433 +-----------+-------------+--------------------+--------------------+ 435 Table 10: Type 3 Address Block TLV Type Extensions 437 The IANA Registry "OTHER_NEIGHB Address Block Type Extensions" is 438 renamed as "Type 4 Address Block TLV Type Extensions" and changed to 439 Table 11. 441 +-----------+--------------+-------------------+--------------------+ 442 | Type | Name | Description | Reference | 443 | Extension | | | | 444 +-----------+--------------+-------------------+--------------------+ 445 | 0 | OTHER_NEIGHB | This value is to | [RFC7188][RFC6130] | 446 | | | be interpreted | | 447 | | | according to the | | 448 | | | registry | | 449 | | | [OTHER_NEIGHB TLV | | 450 | | | Values] | | 451 | 1-223 | | Unassigned | | 452 | 224-255 | | Reserved for | [RFC6130] | 453 | | | Experimental Use | | 454 +-----------+--------------+-------------------+--------------------+ 456 Table 11: Type 4 Address Block TLV Type Extensions 458 The IANA Registry "ICV Address Block TLV Type Extensions" is 459 unchanged. 461 The IANA Registry "TIMESTAMP Address Block TLV Type Extensions" is 462 unchanged. 464 The IANA Registry "LINK_METRIC Address Block TLV Type Extensions" is 465 unchanged. 467 The IANA Registry "MPR Address Block Type Extensions" is renamed as 468 "Type 8 Address Block TLV Type Extensions" and changed to Table 12. 470 +-----------+------+---------------------------+--------------------+ 471 | Type | Name | Description | Reference | 472 | Extension | | | | 473 +-----------+------+---------------------------+--------------------+ 474 | 0 | MPR | This value is to be | [RFC7188][RFC7181] | 475 | | | interpreted according to | | 476 | | | the registry [MPR TLV Bit | | 477 | | | Values] | | 478 | 1-223 | | Unassigned | | 479 | 224-255 | | Reserved for Experimental | This Document | 480 | | | Use | | 481 +-----------+------+---------------------------+--------------------+ 483 Table 12: Type 8 Address Block TLV Type Extensions 485 The IANA Registry "NBR_ADDR_TYPES Address Block Type Extensions" is 486 renamed as "Type 9 Address Block TLV Type Extensions" and changed to 487 Table 13. 489 +-----------+----------------+-----------------+--------------------+ 490 | Type | Name | Description | Reference | 491 | Extension | | | | 492 +-----------+----------------+-----------------+--------------------+ 493 | 0 | NBR_ADDR_TYPES | This value is | [RFC7188][RFC7181] | 494 | | | to be | | 495 | | | interpreted | | 496 | | | according to | | 497 | | | the registry | | 498 | | | [NBR_ADDR_TYPE | | 499 | | | Address Block | | 500 | | | TLV Bit Values] | | 501 | 1-223 | | Unassigned | | 502 | 224-255 | | Reserved for | This Document | 503 | | | Experimental | | 504 | | | Use | | 505 +-----------+----------------+-----------------+--------------------+ 507 Table 13: Type 9 Address Block TLV Type Extensions 509 The IANA Registry "GATEWAY Address Block Type Extensions" is renamed 510 as "Type 10 Address Block TLV Type Extensions" and changed to 511 Table 14. 513 +-----------+---------+------------------------+--------------------+ 514 | Type | Name | Description | Reference | 515 | Extension | | | | 516 +-----------+---------+------------------------+--------------------+ 517 | 0 | GATEWAY | Specifies that a given | [RFC7188][RFC7181] | 518 | | | network address is | | 519 | | | reached via a gateway | | 520 | | | on the originating | | 521 | | | router, with value | | 522 | | | equal to the number of | | 523 | | | hops | | 524 | 1-223 | | Unassigned | | 525 | 224-255 | | Reserved for | This Document | 526 | | | Experimental Use | | 527 +-----------+---------+------------------------+--------------------+ 529 Table 14: Type 10 Address Block TLV Type Extensions 531 Note: This document adds reservations for experimental use, omitted 532 in [RFC7181], to the last three tables. 534 4. Security Considerations 536 As this document is concerned only with how entities are named, those 537 names being used only in documents such as this and IANA registries, 538 this document has no security considerations. 540 5. Acknowledgments 542 The authors would like to thank Adrian Farrel for having pointed out 543 the need for reorganization and rationalization the naming of TLVs 544 (type-length-value structures), defined by [RFC5444]. 546 6. Normative References 548 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 549 Requirement Levels", BCP 14, RFC 2119, March 1997. 551 [RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, 552 "Generalized MANET Packet/Message Format", RFC 5444, 553 February 2009. 555 [RFC5497] Clausen, T. and C. Dearlove, "Representing Multi-Value 556 Time in Mobile Ad Hoc Networks (MANETs)", RFC 5497, 557 March 2009. 559 [RFC6130] Clausen, T., Dean, J., and C. Dearlove, "Mobile Ad Hoc 560 Network (MANET) Neighborhood Discovery Protocol (NHDP)", 561 RFC 6130, April 2011. 563 [RFC7181] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, 564 "The Optimized Link State Routing Protocol version 2", 565 RFC 7181, April 2014. 567 [RFC7182] Herberg, U., Clausen, T., and C. Dearlove, "Integrity 568 Check Value and Timestamp TLV Definitions for Mobile Ad 569 Hoc Networks (MANETs)", RFC 7182, April 2014. 571 [RFC7188] Dearlove, C. and T. Clausen, "Optimized Link State Routing 572 Protocol version 2 (OLSRv2) and MANET Neighborhood 573 Discovery Protocol (NHDP) Extension TLVs", RFC 7188, 574 April 2014. 576 Authors' Addresses 578 Christopher Dearlove 579 BAE Systems Advanced Technology Centre 580 West Hanningfield Road 581 Great Baddow, Chelmsford 582 United Kingdom 584 Phone: +44 1245 242194 585 Email: chris.dearlove@baesystems.com 586 URI: http://www.baesystems.com/ 587 Thomas Heide Clausen 588 LIX, Ecole Polytechnique 590 Phone: +33 6 6058 9349 591 Email: T.Clausen@computer.org 592 URI: http://www.ThomasClausen.org/