Rules For Designing Protocols Using the RFC5444 Generalized Packet/ Message Format
draft-clausen-manet-rfc5444-usage-00
| Document | Type | Replaced Internet-Draft (manet WG) | |
|---|---|---|---|
| Authors | Thomas Clausen , Christopher Dearlove , Ulrich Herberg , Henning Rogge | ||
| Last updated | 2015-10-14 (latest revision 2015-05-28) | ||
| Replaced by | RFC 8245 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-manet-rfc5444-usage | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-clausen-manet-rfc5444-usage-00.txt
Abstract
This document updates the generalized MANET packet/message format, specified in RFC5444, by providing prescriptive guidelines for how protocols can use that packet/message format. In particular, these mandatory guidelines prohibit a number of uses of RFC5444 that have been suggested in various proposals, and which would have lead to interoperability problems, to impediment of protocol extension development, and to inability to use generic RFC5444 parsers.
Authors
Thomas Clausen
(T.Clausen@computer.org)
Christopher Dearlove
(chris.dearlove@baesystems.com)
Ulrich Herberg
(ulrich@herberg.name)
Henning Rogge
(henning.rogge@fkie.fraunhofer.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)