RFC 8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
In plain English — editorial summary, not part of the RFC
RFC 5444 specifies a generalized Mobile Ad Hoc Network (MANET) packet/message format and describes an intended use for multiplexed MANET routing protocol messages; this use is mandated by RFC 5498 when using the MANET port or protocol number that it specifies. This document updates RFC 5444 by providing rules and recommendations for how the multiplexer operates and how protocols can use the packet/message format. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals and that would have led to interoperability problems, to the impediment of protocol extension development, and/or to an inability to use optional generic parsers.
Document record
- Document ID
- RFC8245
- Published
- October 2017
- Authors
- T. Clausen; C. Dearlove; U. Herberg; H. Rogge
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
- Updates:
- RFC 5444
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8218Multipath Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
August 2017
- RFC 8116Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
May 2017
- RFC 7985Security Threats to Simplified Multicast Forwarding (SMF)Current
November 2016
- RFC 7939Definition of Managed Objects for the Neighborhood Discovery ProtocolCurrent
August 2016
- RFC 7859Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing ProtocolsCurrent
May 2016
- RFC 8703Dynamic Link Exchange Protocol (DLEP) Link Identifier ExtensionCurrent
February 2020
- RFC 7779Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2)Current
April 2016
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
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?