Rules for Designing Protocols Using the RFC 5444 Generalized Packet/ Message Format
draft-ietf-manet-rfc5444-usage-07

Document Type Active Internet-Draft (manet WG)
Last updated 2017-08-03 (latest revision 2017-07-18)
Replaces draft-clausen-manet-rfc5444-usage
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html 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 Ed Queue
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
RFC Editor RFC Editor state EDIT
Network Working Group                                         T. Clausen
Internet-Draft                                       Ecole Polytechnique
Updates: 5444 (if approved)                                  C. Dearlove
Intended status: Standards Track                             BAE Systems
Expires: January 19, 2018                                     U. Herberg

                                                                H. Rogge
                                                         Fraunhofer FKIE
                                                           July 18, 2017

  Rules for Designing Protocols Using the RFC 5444 Generalized Packet/
                             Message Format
                   draft-ietf-manet-rfc5444-usage-07

Abstract

   RFC 5444 specifies a generalized MANET packet/message format and
   describes an intended use for multiplexed MANET routing protocol
   messages that is mandated to use on the port or protocol specified by
   RFC 5498.  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 which would have led to interoperability problems, to
   the impediment of protocol extension development, and to an inability
   to use optional generic parsers.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 19, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the

Clausen, et al.         Expires January 19, 2018                [Page 1]
Internet-Draft               RFC 5444 Usage                    July 2017

   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
     1.1.  History and Purpose  . . . . . . . . . . . . . . . . . . .  3
     1.2.  RFC 5444 Features  . . . . . . . . . . . . . . . . . . . .  3
       1.2.1.  Packet/Message Format  . . . . . . . . . . . . . . . .  4
       1.2.2.  Multiplexing and Demultiplexing  . . . . . . . . . . .  6
     1.3.  Status of This Document  . . . . . . . . . . . . . . . . .  7
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  Applicability Statement  . . . . . . . . . . . . . . . . . . .  8
   4.  Information Transmission . . . . . . . . . . . . . . . . . . .  8
     4.1.  Where to Record Information  . . . . . . . . . . . . . . .  8
     4.2.  Message and TLV Type Allocation  . . . . . . . . . . . . .  9
     4.3.  Message Recognition  . . . . . . . . . . . . . . . . . . .  9
     4.4.  Message Multiplexing and Packets . . . . . . . . . . . . . 10
       4.4.1.  Packet Transmission  . . . . . . . . . . . . . . . . . 10
       4.4.2.  Packet Reception . . . . . . . . . . . . . . . . . . . 12
     4.5.  Messages, Addresses and Attributes . . . . . . . . . . . . 13
     4.6.  Addresses Require Attributes . . . . . . . . . . . . . . . 14
     4.7.  TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     4.8.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 17
   5.  Structure  . . . . . . . . . . . . . . . . . . . . . . . . . . 18
   6.  Message Efficiency . . . . . . . . . . . . . . . . . . . . . . 19
     6.1.  Address Block Compression  . . . . . . . . . . . . . . . . 19
     6.2.  TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     6.3.  TLV Values . . . . . . . . . . . . . . . . . . . . . . . . 21
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 22
Show full document text