Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
RFC 8245
| Document | Type |
RFC - Proposed Standard
(October 2017; No errata)
Updates RFC 5444
|
|
|---|---|---|---|
| Authors | Thomas Clausen , Christopher Dearlove , Ulrich Herberg , Henning Rogge | ||
| Last updated | 2017-10-20 | ||
| Replaces | draft-clausen-manet-rfc5444-usage | ||
| 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 2016-05-30) | ||
| IESG | IESG state | RFC 8245 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alvaro Retana | ||
| Send notices to | "Justin Dean" <bebemaster@gmail.com>, aretana@cisco.com | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) T. Clausen
Request for Comments: 8245 Ecole Polytechnique
Updates: 5444 C. Dearlove
Category: Standards Track BAE Systems
ISSN: 2070-1721 U. Herberg
H. Rogge
Fraunhofer FKIE
October 2017
Rules for Designing Protocols Using
the Generalized Packet/Message Format from RFC 5444
Abstract
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.
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 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8245.
Clausen, et al. Standards Track [Page 1]
RFC 8245 Usage of RFC 5444 October 2017
Copyright Notice
Copyright (c) 2017 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
(https://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.
Clausen, et al. Standards Track [Page 2]
RFC 8245 Usage of RFC 5444 October 2017
Table of Contents
1. Introduction ....................................................4
1.1. History and Purpose ........................................4
1.2. Features of RFC 5444 .......................................4
1.2.1. Packet/Message Format ...............................5
1.2.2. Multiplexing and Demultiplexing .....................7
1.3. Status of This Document ....................................8
2. Terminology .....................................................8
3. Applicability Statement .........................................9
4. Information Transmission ........................................9
4.1. Where to Record Information ................................9
4.2. Message and TLV Type Allocation ...........................10
4.3. Message Recognition .......................................11
4.4. Message Multiplexing and Packets ..........................11
4.4.1. Packet Transmission ................................12
4.4.2. Packet Reception ...................................13
4.5. Messages, Addresses, and Attributes .......................15
4.6. Addresses Require Attributes ..............................16
4.7. TLVs ......................................................18
4.8. Message Integrity .........................................19
5. Structure ......................................................19
6. Message Efficiency .............................................20
6.1. Address Block Compression .................................21
6.2. TLVs ......................................................22
6.3. TLV Values ................................................23
7. Security Considerations ........................................24
8. IANA Considerations ............................................24
9. References .....................................................25
Show full document text