RFC 7631: TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7631
- Published
- September 2015
- Authors
- C. Dearlove; T. Clausen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7859Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing ProtocolsCurrent
May 2016
- RFC 7188Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVsUpdated
April 2014
- RFC 2501Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation ConsiderationsCurrent
January 1999
- RFC 2734IPv4 over IEEE 1394Current
December 1999
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 7779Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2)Current
April 2016
- RFC 7466An Optimization for the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Current
March 2015
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?