draft-ietf-manet-tlv-naming-01.txt   draft-ietf-manet-tlv-naming-02.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: August 15, 2015 February 11, 2015 Expires: November 8, 2015 May 7, 2015
TLV Naming in the MANET Generalized Packet/Message Format TLV Naming in the MANET Generalized Packet/Message Format
draft-ietf-manet-tlv-naming-01 draft-ietf-manet-tlv-naming-02
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 2, line 12 skipping to change at page 2, line 12
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 August 15, 2015. This Internet-Draft will expire on November 8, 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
skipping to change at page 5, line 5 skipping to change at page 5, line 5
for values of the LINK_STATUS TLV.) Thus the name LINK_STATUS should for values of the LINK_STATUS TLV.) Thus the name LINK_STATUS should
be attached to that specific type extension for that type, i.e., to be attached to that specific type extension for that type, i.e., to
the full type, and not to the TLV type when used with all other type the full type, and not to the TLV type when used with all other type
extensions therefore. This was, however, not done as part of the extensions therefore. This was, however, not done as part of the
initial registration of this TLV type. Effectively, this leaves, for initial registration of this TLV type. Effectively, this leaves, for
the LINK_STAUS TLV type, the type extensions 1-255 either unavailable the LINK_STAUS TLV type, the type extensions 1-255 either unavailable
for allocation (if applying strictly the interpretation that they for allocation (if applying strictly the interpretation that they
must relate to a LINK_STATUS), or counterintuitively named for their must relate to a LINK_STATUS), or counterintuitively named for their
intended function. intended function.
The purpose of this document is to change how these names are The purpose of this document is to change how names of the second
applied, and recorded in IANA registries, and to provide guidelines form are applied, and recorded in IANA registries, and to provide
and instructions for future TLV type allocations. This is to guidelines and instructions for future TLV type allocations. This is
facilitate the addition of new TLVs using type extensions other than to facilitate the addition of new TLVs using type extensions other
0, but without them having inappropriate names attached. So, for than 0, but without them having inappropriate names attached. So,
example, LINK_STATUS will become the name of the full type (as for example, LINK_STATUS will become the name of the full type (as
composed by the TLV type 3 and the TLV type extension 0), and will composed by the TLV type 3 and the TLV type extension 0), and will
cease being the name of the TLV type 3. This leaves the question of cease being the name of the TLV type 3. This leaves the question of
how to name the type. As it is not clear what other TLVs might be how to name the type. As it is not clear what other TLVs might be
defined for other type extensions of the same type, it is proposed to defined for other type extensions of the same type, it is proposed to
leave the type currently unnamed, specified only by number. leave the type currently unnamed, specified only by number.
This document also updates the Expert Review guidelines from This document also updates the Expert Review guidelines from
[RFC5444], so as to establish a policy for consisteng naming of [RFC5444], so as to establish a policy for consisteng naming of
future TLV type and type extension allocations. future TLV type and type extension allocations.
skipping to change at page 7, line 5 skipping to change at page 6, line 47
Extensions", with XX replaced by the numerical value of the TLV Extensions", with XX replaced by the numerical value of the TLV
Type. Type.
* For Address Block TLV Types, that the Type Extension registry, * For Address Block TLV Types, that the Type Extension registry,
created for the TLV Type, be named "Type XX Address Block TLV created for the TLV Type, be named "Type XX Address Block TLV
Type Extensions", with XX replaced by the numerical value of Type Extensions", with XX replaced by the numerical value of
the TLV Type. the TLV Type.
* That each Type Extension be given a name when allocated. * That each Type Extension be given a name when allocated.
Note that the former case is unchanged by this specification, this
currently includes TLV types named ICV, TIMESTAMP and LINK_METRIC.
3.2. Updated IANA Registries 3.2. Updated IANA Registries
The following changes all apply to the IANA registry "Mobile Ad hoc The following changes all apply to the IANA registry "Mobile Ad hoc
NETwork (MANET) Parameters". NETwork (MANET) Parameters". For clarity, registries that are
unchanged, including those that define all type extensions of a TLV
type, are listed as unchanged.
The IANA registry "Packet TLV Types" is unchanged. The IANA registry "Packet TLV Types" is unchanged.
The IANA Registry "ICV Packet TLV Type Extensions" is unchanged. The IANA Registry "ICV Packet TLV Type Extensions" is unchanged.
The IANA Registry "TIMESTAMP Packet TLV Type Extensions" is The IANA Registry "TIMESTAMP Packet TLV Type Extensions" is
unchanged. unchanged.
The IANA Registry "Message TLV Types" is changed to Table 1. The IANA Registry "Message TLV Types" is changed to Table 1.
 End of changes. 6 change blocks. 
10 lines changed or deleted 15 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/