draft-ietf-manet-nhdp-olsrv2-tlv-extension-00.txt | draft-ietf-manet-nhdp-olsrv2-tlv-extension-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: RFC6130, OLSRv2 T. Clausen | Updates: RFC6130, OLSRv2 T. Clausen | |||
(if approved) LIX, Ecole Polytechnique | (if approved) LIX, Ecole Polytechnique | |||
Intended status: Standards Track September 19, 2013 | Intended status: Standards Track January 23, 2014 | |||
Expires: March 23, 2014 | Expires: July 27, 2014 | |||
Optimized Link State Routing Protocol version 2 (OLSRv2) and MANET | Optimized Link State Routing Protocol version 2 (OLSRv2) and MANET | |||
Neighborhood Discovery Protocol (NHDP) Extension TLVs | Neighborhood Discovery Protocol (NHDP) Extension TLVs | |||
draft-ietf-manet-nhdp-olsrv2-tlv-extension-00 | draft-ietf-manet-nhdp-olsrv2-tlv-extension-01 | |||
Abstract | Abstract | |||
This specification describes extensions to definitions of TLVs used | This specification describes extensions to definitions of TLVs used | |||
by the Optimized Link State Routing Protocol version 2 (OLSRv2) and | by the Optimized Link State Routing Protocol version 2 (OLSRv2) and | |||
the MANET Neighborhood Discovery Protocol (NHDP), to increase their | the MANET Neighborhood Discovery Protocol (NHDP), to increase their | |||
abilities to accommodate protocol extensions. This document updates | abilities to accommodate protocol extensions. This document updates | |||
OLSRv2 and RFC6130. | OLSRv2 and RFC6130. | |||
Status of this Memo | Status of this Memo | |||
skipping to change at page 1, line 37 | skipping to change at page 1, line 37 | |||
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 March 23, 2014. | This Internet-Draft will expire on July 27, 2014. | |||
Copyright Notice | 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. | 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 | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
skipping to change at page 2, line 23 | skipping to change at page 2, line 23 | |||
4. TLV Values . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 4. TLV Values . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
4.1. Unrecognized TLV Values . . . . . . . . . . . . . . . . . 4 | 4.1. Unrecognized TLV Values . . . . . . . . . . . . . . . . . 4 | |||
4.2. TLV Value Lengths . . . . . . . . . . . . . . . . . . . . 5 | 4.2. TLV Value Lengths . . . . . . . . . . . . . . . . . . . . 5 | |||
4.3. Undefined TLV Values . . . . . . . . . . . . . . . . . . . 5 | 4.3. Undefined TLV Values . . . . . . . . . . . . . . . . . . . 5 | |||
4.3.1. NHDP TLVs: LOCAL_IF, LINK_STATUS and OTHER_NEIGHB . . 6 | 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.2. OLSRv2 TLVs: MPR and NBR_ADDR_TYPE . . . . . . . . . . 6 | |||
4.3.3. Unspecified TLV Values . . . . . . . . . . . . . . . . 6 | 4.3.3. Unspecified TLV Values . . . . . . . . . . . . . . . . 6 | |||
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | |||
5.1. Address Block TLVs . . . . . . . . . . . . . . . . . . . . 7 | 5.1. Address Block TLVs . . . . . . . . . . . . . . . . . . . . 7 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 | |||
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 | 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 | 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 | |||
8.2. Informative References . . . . . . . . . . . . . . . . . . 11 | 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
1. Introduction | 1. Introduction | |||
The MANET Neighborhood Discovery Protocol (NHDP) [RFC6130] and the | The MANET Neighborhood Discovery Protocol (NHDP) [RFC6130] and the | |||
Optimized Link State Routing Protocol, version 2 (OLSRv2) [OLSRv2] | Optimized Link State Routing Protocol, version 2 (OLSRv2) [OLSRv2] | |||
are protocols for use in mobile ad hoc networks (MANETs) [RFC2501], | are protocols for use in mobile ad hoc networks (MANETs) [RFC2501], | |||
skipping to change at page 5, line 14 | skipping to change at page 5, line 14 | |||
[OLSRv2], except with regard to not allowing this to be a reason for | [OLSRv2], except with regard to not allowing this to be a reason for | |||
rejection of a message. [RFC6130] or [OLSRv2] are specified in terms | 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 | such as "if an address is associated with a value of LOST by a | |||
LINK_STATUS TLV". Association with an unrecognized value has no | LINK_STATUS TLV". Association with an unrecognized value has no | |||
effect on any implementation strictly following such a specification. | effect on any implementation strictly following such a specification. | |||
4.2. TLV Value Lengths | 4.2. TLV Value Lengths | |||
The TLVs specified in [RFC6130] and [OLSRv2] may be either single- | The TLVs specified in [RFC6130] and [OLSRv2] may be either single- | |||
value or multi-value TLVs. In either case, the length of the | value or multi-value TLVs. In either case, the length of each item | |||
information encoded in the TLV Value field is the "single-length", | 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 | defined and calculated as in section 5.4.1 in [RFC5444]. All TLVs | |||
specified in [RFC6130] and [OLSRv2] describe TLVs with one or two | specified in [RFC6130] and [OLSRv2] have a one or two octet single- | |||
octet TLV Value field single-length. These are considered the | length. These are considered the expected single-lengths of such a | |||
expected values of single-length for a received TLV. | received TLV. | |||
Other single-length TLV Value fields may be introduced by extensions | Other single-length TLV Value fields may be introduced by extensions | |||
to [RFC6130] and [OLSRv2]. This document specifies how | to [RFC6130] and [OLSRv2]. This document specifies how | |||
implementations of [RFC6130] and [OLSRv2], or extensions thereof, | implementations of [RFC6130] and [OLSRv2], or extensions thereof, | |||
MUST behave on receiving TLVs of the TLV types defined in [RFC6130] | MUST behave on receiving TLVs of the TLV types defined in [RFC6130] | |||
and [OLSRv2], but with TLV Value fields with other single-length | and [OLSRv2], but with TLV Value fields with other single-length | |||
values. | values. | |||
The following principles apply: | The following principles apply: | |||
skipping to change at page 6, line 44 | skipping to change at page 6, line 44 | |||
the individual bits in these bitfields, with initial registrations | the individual bits in these bitfields, with initial registrations | |||
for values defined and used by [OLSRv2] - see Section 5. | for values defined and used by [OLSRv2] - see Section 5. | |||
Other TLVs defined by [OLSRv2] are not affected by this | Other TLVs defined by [OLSRv2] are not affected by this | |||
specification. | specification. | |||
4.3.3. Unspecified TLV Values | 4.3.3. Unspecified TLV Values | |||
The registries defined in Section 5 for the LOCAL_IF, LINK_STATUS and | The registries defined in Section 5 for the LOCAL_IF, LINK_STATUS and | |||
OTHER_NEIGHB TLVs each include an additional TLV Value UNSPECIFIED. | OTHER_NEIGHB TLVs each include an additional TLV Value UNSPECIFIED. | |||
This TLV Value represents a value that MUST NOT be defined in any | This TLV Value represents a defined value that, like currently | |||
extension of [RFC6130]. Such a TLV Value MAY be used to enable the | undefined TLV Values, indicates that no information is associated | |||
creation of more efficient multivalue Address Block TLVs, or to | with this address, but will always have this meaning. Such a TLV | |||
simplify an implementation. | 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 | The similar requirement for the MPR and NBR_ADDR_TYPES TLVs is | |||
already satisfied by the TLV Value zero, provided that each bit in | 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 | the TLV Value is defined as set ('1') when indicating the presence of | |||
an attribute, or clear ('0') when indicating the absence of an | 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. | relevant registries, see Section 5. | |||
For the LINK_METRIC TLV, this is already possible by clearing the | 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. | 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 | It is RECOMMENDED that in this case the remaining bits of the TLV | |||
Value are either all clear ('0') or all set ('1'). | Value are either all clear ('0') or all set ('1'). | |||
5. IANA Considerations | 5. IANA Considerations | |||
Note: Values defined as "Unallocated: Expert Review" mean that these | Note: Values defined as "Unallocated: Expert Review" mean that these | |||
values may be allocated according to the expert review guidelines | values may be allocated according to the expert review guidelines | |||
specified in [RFC6130] and [OLSRv2]. In two cases a constraint on | 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 | 5.1. Address Block TLVs | |||
IANA is requested to create a registry associated with the Address | IANA is requested to create a registry associated with the Address | |||
Block TLV with name LOCAL_IF (Type = 2, Type Extension = 0) defined | Block TLV with name LOCAL_IF (Type = 2, Type Extension = 0) defined | |||
in [RFC6130], specifying the meaning of its single values. This | in [RFC6130], specifying the meaning of its single values. This | |||
replaces the Description column in Table 6 in [RFC6130] by a | replaces the Description column in IANA table "LOCAL_IF Address Block | |||
reference to this table. | TLV Type Extensions" (from Table 6 in [RFC6130]) by a reference to | |||
this table. | ||||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| Value | Name | Description | | | Value | Name | Description | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| 0 | THIS_IF | The network address is associated with | | | 0 | THIS_IF | The network address is associated with | | |||
| | | this local interface of the sending | | | | | this local interface of the sending | | |||
| | | router | | | | | router | | |||
| 1 | OTHER_IF | The network address is associated with | | | 1 | OTHER_IF | The network address is associated with | | |||
| | | another local interface of the sending | | | | | another local interface of the sending | | |||
| | | router | | | | | router | | |||
skipping to change at page 7, line 47 | skipping to change at page 7, line 50 | |||
| 224-254 | | Experimental Use | | | 224-254 | | Experimental Use | | |||
| 255 | UNSPECIFIED | No information about this network address | | | 255 | UNSPECIFIED | No information about this network address | | |||
| | | is provided | | | | | is provided | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
Table 1: LOCAL_IF TLV Values | Table 1: LOCAL_IF TLV Values | |||
IANA are requested to create a registry associated with the Address | IANA are requested to create a registry associated with the Address | |||
Block TLV with name LINK_STATUS (Type = 3, Type Extension = 0) | Block TLV with name LINK_STATUS (Type = 3, Type Extension = 0) | |||
defined in [RFC6130], specifying the meaning of its single values. | 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. | reference to this table. | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| Value | Name | Description | | | Value | Name | Description | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| 0 | LOST | The link on this interface from the | | | 0 | LOST | The link on this interface from the | | |||
| | | router with that network address has been | | | | | router with that network address has been | | |||
| | | lost | | | | | lost | | |||
| 1 | SYMMETRIC | The link on this interface from the | | | 1 | SYMMETRIC | The link on this interface from the | | |||
| | | router with that network address has the | | | | | router with that network address has the | | |||
skipping to change at page 8, line 28 | skipping to change at page 8, line 30 | |||
| 224-254 | | Experimental Use | | | 224-254 | | Experimental Use | | |||
| 255 | UNSPECIFIED | No information about this network address | | | 255 | UNSPECIFIED | No information about this network address | | |||
| | | is provided | | | | | is provided | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
Table 2: LINK_STATUS TLV Values | Table 2: LINK_STATUS TLV Values | |||
IANA are requested to create a registry associated with the Address | IANA are requested to create a registry associated with the Address | |||
Block TLV with name OTHER_NEIGHB (Type = 4, Type Extension = 0) | Block TLV with name OTHER_NEIGHB (Type = 4, Type Extension = 0) | |||
defined in [RFC6130], specifying the meaning of its single values. | defined in [RFC6130], specifying the meaning of its single values. | |||
This replaces the Description column in Table 8 in [RFC6130] by a | This replaces the Description column in Table 8 in the IANA table | |||
reference to this table. | "OTHER_NEIGHB Address Block TLV Type Extensions" (from [RFC6130]) by | |||
a reference to this table. | ||||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| Value | Name | Description | | | Value | Name | Description | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
| 0 | LOST | The neighbor relationship with the router | | | 0 | LOST | The neighbor relationship with the router | | |||
| | | with that network address has been lost | | | | | with that network address has been lost | | |||
| 1 | SYMMETRIC | The neighbor relationship with the router | | | 1 | SYMMETRIC | The neighbor relationship with the router | | |||
| | | with that network address is symmetric | | | | | with that network address is symmetric | | |||
| 2-223 | | Unallocated: Expert Review | | | 2-223 | | Unallocated: Expert Review | | |||
| 224-254 | | Experimental Use | | | 224-254 | | Experimental Use | | |||
skipping to change at page 8, line 51 | skipping to change at page 9, line 6 | |||
| | | is provided | | | | | is provided | | |||
+---------+-------------+-------------------------------------------+ | +---------+-------------+-------------------------------------------+ | |||
Table 3: OTHER_NEIGHB TLV Values | Table 3: OTHER_NEIGHB TLV Values | |||
IANA are requested to create a registry associated with the Address | IANA are requested to create a registry associated with the Address | |||
Block TLV with name MPR (Type = 8, Type Extension = 0) defined in | Block TLV with name MPR (Type = 8, Type Extension = 0) defined in | |||
[OLSRv2], specifying the meaning of its single values in terms of the | [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 | 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. | 7 (least significant). If multiple bits are set then each applies. | |||
This replaces the Description column in Table 14 in [OLSRv2] by a | This replaces the Description column in the (not yet created) IANA | |||
reference to this table. | table "MPR Address Block TLV Type Extensions" (from Table 14 in | |||
[OLSRv2]) by a reference to this table. | ||||
+-------+-------+----------+----------------------------------------+ | +-------+-------+----------+----------------------------------------+ | |||
| Value | Value | Name | Description | | | Value | Value | Name | Description | | |||
| Bit | | | | | | Bit | | | | | |||
+-------+-------+----------+----------------------------------------+ | +-------+-------+----------+----------------------------------------+ | |||
| 7 | 1 | FLOODING | The neighbor with that network address | | | 7 | 1 | FLOODING | The neighbor with that network address | | |||
| | | | has been selected as flooding MPR | | | | | | has been selected as flooding MPR | | |||
| 6 | 2 | ROUTING | The neighbor with that network address | | | 6 | 2 | ROUTING | The neighbor with that network address | | |||
| | | | has been selected as flooding MPR | | | | | | has been selected as flooding MPR | | |||
| 0-5 | | | Unallocated: Expert Review | | | 0-5 | | | Unallocated: Expert Review | | |||
skipping to change at page 9, line 31 | skipping to change at page 9, line 36 | |||
future allocations, the Expert Review MUST ensure that allocated bits | future allocations, the Expert Review MUST ensure that allocated bits | |||
MUST use the unset bit (0) to indicates no information, so that the | MUST use the unset bit (0) to indicates no information, so that the | |||
case Value = 0 will always indicate that no information about this | case Value = 0 will always indicate that no information about this | |||
network address is provided. | network address is provided. | |||
IANA are requested to create a registry associated with the Address | IANA are requested to create a registry associated with the Address | |||
Block TLV with name NBR_ADDR_TYPE (Type = 9, Type Extension = 0) | Block TLV with name NBR_ADDR_TYPE (Type = 9, Type Extension = 0) | |||
defined in [OLSRv2], specifying the meaning of its single values in | 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 | 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 | significant) to bit 7 (least significant). If multiple bits are set | |||
then each applies. This replaces the Description column in Table 15 | then each applies. This replaces the Description column in the (not | |||
in [OLSRv2] by a reference to this table. | 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 | | | Value | Value | Name | Description | | |||
| Bit | | | | | | Bit | | | | | |||
+-------+-------+------------+--------------------------------------+ | +-------+-------+------------+--------------------------------------+ | |||
| 7 | 1 | ORIGINATOR | The network address is an originator | | | 7 | 1 | ORIGINATOR | The network address is an originator | | |||
| | | | address reachable via the | | | | | | address reachable via the | | |||
| | | | originating router | | | | | | originating router | | |||
| 6 | 2 | ROUTABLE | The network address is a routable | | | 6 | 2 | ROUTABLE | The network address is a routable | | |||
| | | | address reachable via the | | | | | | address reachable via the | | |||
End of changes. 15 change blocks. | ||||
26 lines changed or deleted | 33 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |