TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
RFC 7631
Document | Type |
RFC - Proposed Standard
(September 2015; No errata)
Updated by RFC 7722
Updates RFC 5444
|
|
---|---|---|---|
Authors | Christopher Dearlove , Thomas Clausen | ||
Last updated | 2018-12-20 | ||
Replaces | draft-dearlove-manet-tlv-naming | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Justin Dean | ||
Shepherd write-up | Show (last changed 2015-05-11) | ||
IESG | IESG state | RFC 7631 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) C. Dearlove Request for Comments: 7631 BAE Systems ATC Updates: 5444 T. Clausen Category: Standards Track LIX, Ecole Polytechnique ISSN: 2070-1721 September 2015 TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format Abstract This document reorganizes the naming of already-allocated TLV (type- length-value) types and type extensions in the "Mobile Ad hoc NETwork (MANET) Parameters" registries defined by RFC 5444 to use names appropriately. It has no consequences in terms of any protocol implementation. This document also updates the Expert Review guidelines in RFC 5444, so as to establish a policy for consistent naming of future TLV type and type extension allocations. It makes no other changes to RFC 5444. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7631. Dearlove & Clausen Standards Track [Page 1] RFC 7631 TLV Naming September 2015 Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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. Table of Contents 1. Introduction ....................................................3 2. Terminology .....................................................4 3. IANA Considerations .............................................4 3.1. Expert Review: Evaluation Guidelines .......................5 3.2. Updated IANA Registries ....................................6 4. Security Considerations ........................................13 5. References .....................................................13 5.1. Normative References ......................................13 5.2. Informative References ....................................14 Acknowledgments ...................................................15 Authors' Addresses ................................................15 Dearlove & Clausen Standards Track [Page 2] RFC 7631 TLV Naming September 2015 1. Introduction This document reorganizes and rationalizes the naming of TLVs (type- length-value structures) defined by [RFC5444] and recorded by IANA in the following subregistries of the "Mobile Ad hoc NETwork (MANET) Parameters" registry: "Packet TLV Types", "Message TLV Types", and "Address Block TLV Types". This document reorganizes the naming of already-allocated Packet, Message, and Address Block TLV types, and their corresponding type extensions. It also updates the corresponding IANA registries. TLVs have a type (one octet) and a type extension (one octet) that together form a full type (of two octets). A TLV may omit the type extension when it is zero. However, that applies only to its representation; it still has a type extension of zero. A TLV type defines an IANA registry of type extensions for that type. There have been two forms of TLV allocation. The first, but less common, form of allocation has been that allocation of the TLV type has defined (but not necessarily allocated) all the type extensions for that TLV type. This applies, for example, to the Address Block TLV LINK_METRIC specified in [RFC7181]. The LINK_METRIC type extensions are all available for allocation for different definitions of link metric. It is appropriate in this case to apply the name LINK_METRIC to the type, and also to all the full types corresponding to that type, as has been done. Type extensions can then be individually named or can be simply referred to by their number.Show full document text