--- 1/draft-ietf-manet-nhdp-olsrv2-tlv-extension-00.txt 2014-01-23 09:14:36.864633158 -0800 +++ 2/draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.txt 2014-01-23 09:14:36.892633894 -0800 @@ -1,21 +1,21 @@ Mobile Ad hoc Networking (MANET) C. Dearlove Internet-Draft BAE Systems ATC Updates: RFC6130, OLSRv2 T. Clausen (if approved) LIX, Ecole Polytechnique -Intended status: Standards Track September 19, 2013 -Expires: March 23, 2014 +Intended status: Standards Track January 23, 2014 +Expires: July 27, 2014 Optimized Link State Routing Protocol version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs - draft-ietf-manet-nhdp-olsrv2-tlv-extension-00 + draft-ietf-manet-nhdp-olsrv2-tlv-extension-01 Abstract This specification describes extensions to definitions of TLVs used by the Optimized Link State Routing Protocol version 2 (OLSRv2) and the MANET Neighborhood Discovery Protocol (NHDP), to increase their abilities to accommodate protocol extensions. This document updates OLSRv2 and RFC6130. Status of this Memo @@ -26,25 +26,25 @@ 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 March 23, 2014. + This Internet-Draft will expire on July 27, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 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 (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 @@ -58,21 +58,21 @@ 4. TLV Values . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Unrecognized TLV Values . . . . . . . . . . . . . . . . . 4 4.2. TLV Value Lengths . . . . . . . . . . . . . . . . . . . . 5 4.3. Undefined TLV Values . . . . . . . . . . . . . . . . . . . 5 4.3.1. NHDP TLVs: LOCAL_IF, LINK_STATUS and OTHER_NEIGHB . . 6 4.3.2. OLSRv2 TLVs: MPR and NBR_ADDR_TYPE . . . . . . . . . . 6 4.3.3. Unspecified TLV Values . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5.1. Address Block TLVs . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 - 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 + 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction The MANET Neighborhood Discovery Protocol (NHDP) [RFC6130] and the Optimized Link State Routing Protocol, version 2 (OLSRv2) [OLSRv2] are protocols for use in mobile ad hoc networks (MANETs) [RFC2501], @@ -168,26 +168,26 @@ [OLSRv2], except with regard to not allowing this to be a reason for rejection of a message. [RFC6130] or [OLSRv2] are specified in terms such as "if an address is associated with a value of LOST by a LINK_STATUS TLV". Association with an unrecognized value has no effect on any implementation strictly following such a specification. 4.2. TLV Value Lengths The TLVs specified in [RFC6130] and [OLSRv2] may be either single- - value or multi-value TLVs. In either case, the length of the - information encoded in the TLV Value field is the "single-length", + value or multi-value TLVs. In either case, the length of each item + of information encoded in the TLV Value field is the "single-length", defined and calculated as in section 5.4.1 in [RFC5444]. All TLVs - specified in [RFC6130] and [OLSRv2] describe TLVs with one or two - octet TLV Value field single-length. These are considered the - expected values of single-length for a received TLV. + specified in [RFC6130] and [OLSRv2] have a one or two octet single- + length. These are considered the expected single-lengths of such a + received TLV. Other single-length TLV Value fields may be introduced by extensions to [RFC6130] and [OLSRv2]. This document specifies how implementations of [RFC6130] and [OLSRv2], or extensions thereof, MUST behave on receiving TLVs of the TLV types defined in [RFC6130] and [OLSRv2], but with TLV Value fields with other single-length values. The following principles apply: @@ -246,51 +246,54 @@ the individual bits in these bitfields, with initial registrations for values defined and used by [OLSRv2] - see Section 5. Other TLVs defined by [OLSRv2] are not affected by this specification. 4.3.3. Unspecified TLV Values The registries defined in Section 5 for the LOCAL_IF, LINK_STATUS and OTHER_NEIGHB TLVs each include an additional TLV Value UNSPECIFIED. - This TLV Value represents a value that MUST NOT be defined in any - extension of [RFC6130]. Such a TLV Value MAY be used to enable the - creation of more efficient multivalue Address Block TLVs, or to - simplify an implementation. + This TLV Value represents a defined value that, like currently + undefined TLV Values, indicates that no information is associated + with this address, but will always have this meaning. Such a TLV + Value may be used to enable the creation of more efficient multivalue + Address Block TLVs, or to simplify an implementation. The similar requirement for the MPR and NBR_ADDR_TYPES TLVs is already satisfied by the TLV Value zero, provided that each bit in the TLV Value is defined as set ('1') when indicating the presence of an attribute, or clear ('0') when indicating the absence of an - attribute; this is therefore REQUIRED for registrations from the + attribute; this is therefore required for registrations from the relevant registries, see Section 5. For the LINK_METRIC TLV, this is already possible by clearing the most significant bits (0 to 3) of the first octet of the TLV Value. It is RECOMMENDED that in this case the remaining bits of the TLV Value are either all clear ('0') or all set ('1'). 5. IANA Considerations Note: Values defined as "Unallocated: Expert Review" mean that these values may be allocated according to the expert review guidelines specified in [RFC6130] and [OLSRv2]. In two cases a constraint on - future allocation is specified. + future allocation is specified. IANA tables referenced are from + "Mobile Ad hoc NETwork (MANET) Parameters". 5.1. Address Block TLVs IANA is requested to create a registry associated with the Address Block TLV with name LOCAL_IF (Type = 2, Type Extension = 0) defined in [RFC6130], specifying the meaning of its single values. This - replaces the Description column in Table 6 in [RFC6130] by a - reference to this table. + replaces the Description column in IANA table "LOCAL_IF Address Block + TLV Type Extensions" (from Table 6 in [RFC6130]) by a reference to + this table. +---------+-------------+-------------------------------------------+ | Value | Name | Description | +---------+-------------+-------------------------------------------+ | 0 | THIS_IF | The network address is associated with | | | | this local interface of the sending | | | | router | | 1 | OTHER_IF | The network address is associated with | | | | another local interface of the sending | | | | router | @@ -298,21 +301,22 @@ | 224-254 | | Experimental Use | | 255 | UNSPECIFIED | No information about this network address | | | | is provided | +---------+-------------+-------------------------------------------+ Table 1: LOCAL_IF TLV Values IANA are requested to create a registry associated with the Address Block TLV with name LINK_STATUS (Type = 3, Type Extension = 0) defined in [RFC6130], specifying the meaning of its single values. - This replaces the Description column in Table 7 in [RFC6130] by a + This replaces the Description column in the IANA table "LINK_STATUS + Address Block TLV Type Extensions" (from Table 7 in [RFC6130]) by a reference to this table. +---------+-------------+-------------------------------------------+ | Value | Name | Description | +---------+-------------+-------------------------------------------+ | 0 | LOST | The link on this interface from the | | | | router with that network address has been | | | | lost | | 1 | SYMMETRIC | The link on this interface from the | | | | router with that network address has the | @@ -324,22 +328,23 @@ | 224-254 | | Experimental Use | | 255 | UNSPECIFIED | No information about this network address | | | | is provided | +---------+-------------+-------------------------------------------+ Table 2: LINK_STATUS TLV Values IANA are requested to create a registry associated with the Address Block TLV with name OTHER_NEIGHB (Type = 4, Type Extension = 0) defined in [RFC6130], specifying the meaning of its single values. - This replaces the Description column in Table 8 in [RFC6130] by a - reference to this table. + This replaces the Description column in Table 8 in the IANA table + "OTHER_NEIGHB Address Block TLV Type Extensions" (from [RFC6130]) by + a reference to this table. +---------+-------------+-------------------------------------------+ | Value | Name | Description | +---------+-------------+-------------------------------------------+ | 0 | LOST | The neighbor relationship with the router | | | | with that network address has been lost | | 1 | SYMMETRIC | The neighbor relationship with the router | | | | with that network address is symmetric | | 2-223 | | Unallocated: Expert Review | | 224-254 | | Experimental Use | @@ -347,22 +352,23 @@ | | | is provided | +---------+-------------+-------------------------------------------+ Table 3: OTHER_NEIGHB TLV Values IANA are requested to create a registry associated with the Address Block TLV with name MPR (Type = 8, Type Extension = 0) defined in [OLSRv2], specifying the meaning of its single values in terms of the values of each bit of the value, from bit 0 (most significant) to bit 7 (least significant). If multiple bits are set then each applies. - This replaces the Description column in Table 14 in [OLSRv2] by a - reference to this table. + This replaces the Description column in the (not yet created) IANA + table "MPR Address Block TLV Type Extensions" (from Table 14 in + [OLSRv2]) by a reference to this table. +-------+-------+----------+----------------------------------------+ | Value | Value | Name | Description | | Bit | | | | +-------+-------+----------+----------------------------------------+ | 7 | 1 | FLOODING | The neighbor with that network address | | | | | has been selected as flooding MPR | | 6 | 2 | ROUTING | The neighbor with that network address | | | | | has been selected as flooding MPR | | 0-5 | | | Unallocated: Expert Review | @@ -376,22 +382,23 @@ future allocations, the Expert Review MUST ensure that allocated bits MUST use the unset bit (0) to indicates no information, so that the case Value = 0 will always indicate that no information about this network address is provided. IANA are requested to create a registry associated with the Address Block TLV with name NBR_ADDR_TYPE (Type = 9, Type Extension = 0) defined in [OLSRv2], specifying the meaning of its single values in terms of the values of each bit of the value, from bit 0 (most significant) to bit 7 (least significant). If multiple bits are set - then each applies. This replaces the Description column in Table 15 - in [OLSRv2] by a reference to this table. + then each applies. This replaces the Description column in the (not + yet created) IANA table "NBR_ADDR_TYPE Address Block TLV Type + Extensions" (from Table 15 in [OLSRv2]) by a reference to this table. +-------+-------+------------+--------------------------------------+ | Value | Value | Name | Description | | Bit | | | | +-------+-------+------------+--------------------------------------+ | 7 | 1 | ORIGINATOR | The network address is an originator | | | | | address reachable via the | | | | | originating router | | 6 | 2 | ROUTABLE | The network address is a routable | | | | | address reachable via the |