draft-ietf-manet-tlv-naming-00.txt   draft-ietf-manet-tlv-naming-01.txt 
Mobile Ad hoc Networking (MANET) C. Dearlove Mobile Ad hoc Networking (MANET) C. Dearlove
Internet-Draft BAE Systems ATC Internet-Draft BAE Systems ATC
Updates: 5444 (if approved) T. Clausen Updates: 5444 (if approved) T. Clausen
Intended status: Standards Track LIX, Ecole Polytechnique Intended status: Standards Track LIX, Ecole Polytechnique
Expires: July 9, 2015 January 5, 2015 Expires: August 15, 2015 February 11, 2015
TLV Naming in the MANET Generalized Packet/Message Format TLV Naming in the MANET Generalized Packet/Message Format
draft-ietf-manet-tlv-naming-00 draft-ietf-manet-tlv-naming-01
Abstract Abstract
TLVs (type-length-value structures) as defined by RFC5444 have both a TLVs (type-length-value structures) as defined by RFC5444 have both a
type (one octet) and a type extension (one octet), together forming a type (one octet) and a type extension (one octet), together forming a
full type (of two octets). RFC5444 sets up IANA registries for TLV full type (of two octets). RFC5444 sets up IANA registries for TLV
types, specifying that an allocation of a TLV type entails creation types, specifying that an allocation of a TLV type entails creation
of an IANA registry for the corresponding type extensions. of an IANA registry for the corresponding type extensions.
In some cases, reserving all 256 type extensions for use for a common In some cases, reserving all 256 type extensions for use for a common
skipping to change at page 1, line 40 skipping to change at page 1, line 40
name for all the type extensions for a TLV type in the corresponding name for all the type extensions for a TLV type in the corresponding
IANA registries. Rather, it is appropriate to record an individual IANA registries. Rather, it is appropriate to record an individual
name per full type. name per full type.
This document reorganizes the naming of already allocated TLV types This document reorganizes the naming of already allocated TLV types
and type extensions in those registries to use names appropriately. and type extensions in those registries to use names appropriately.
It has no consequences in terms of any protocol implementation. It has no consequences in terms of any protocol implementation.
This document also updates the Expert Review guidelines from RFC5444, This document also updates the Expert Review guidelines from RFC5444,
so as to establish a policy for consistent naming of future TLV type so as to establish a policy for consistent naming of future TLV type
and type extension allocations. and type extension allocations. It makes no other changes to
RFC5444.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 9, 2015. This Internet-Draft will expire on August 15, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
 End of changes. 4 change blocks. 
4 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/