draft-ietf-manet-nhdp-olsrv2-tlv-extension-04.txt   draft-ietf-manet-nhdp-olsrv2-tlv-extension-05.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 March 4, 2014 Intended status: Standards Track March 5, 2014
Expires: September 5, 2014 Expires: September 6, 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-04 draft-ietf-manet-nhdp-olsrv2-tlv-extension-05
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 September 5, 2014. This Internet-Draft will expire on September 6, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Applicability Statement . . . . . . . . . . . . . . . . . . . 3 3. Applicability Statement . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5.1. LOCAL_IF Address Block TLVs . . . . . . . . . . . . . . . 7 5.1. LOCAL_IF Address Block TLVs . . . . . . . . . . . . . . . 8
5.1.1. Create New Registry . . . . . . . . . . . . . . . . . 7 5.1.1. Create New Registry . . . . . . . . . . . . . . . . . 8
5.1.2. Modification to Existing Registry . . . . . . . . . . 8 5.1.2. Modification to Existing Registry . . . . . . . . . . 9
5.2. LINK_STATUS Address Block TLVs . . . . . . . . . . . . . . 9 5.2. LINK_STATUS Address Block TLVs . . . . . . . . . . . . . . 10
5.2.1. Create New Registry . . . . . . . . . . . . . . . . . 9 5.2.1. Create New Registry . . . . . . . . . . . . . . . . . 10
5.2.2. Modification to Existing Registry . . . . . . . . . . 10 5.2.2. Modification to Existing Registry . . . . . . . . . . 11
5.3. OTHER_NEIGHB Address Block TLVs . . . . . . . . . . . . . 11 5.3. OTHER_NEIGHB Address Block TLVs . . . . . . . . . . . . . 12
5.3.1. Create New Registry . . . . . . . . . . . . . . . . . 11 5.3.1. Create New Registry . . . . . . . . . . . . . . . . . 12
5.3.2. Modification to Existing Registry . . . . . . . . . . 12 5.3.2. Modification to Existing Registry . . . . . . . . . . 13
5.4. MPR Address Block TLVs . . . . . . . . . . . . . . . . . . 12 5.4. MPR Address Block TLVs . . . . . . . . . . . . . . . . . . 13
5.4.1. Create New Registry . . . . . . . . . . . . . . . . . 12 5.4.1. Create New Registry . . . . . . . . . . . . . . . . . 13
5.4.2. Modification to Existing Registry . . . . . . . . . . 13 5.4.2. Modification to Existing Registry . . . . . . . . . . 14
5.5. NBR_ADDR_TYPE Address Block TLVs . . . . . . . . . . . . . 14 5.5. NBR_ADDR_TYPE Address Block TLVs . . . . . . . . . . . . . 15
5.5.1. Create New Registry . . . . . . . . . . . . . . . . . 14 5.5.1. Create New Registry . . . . . . . . . . . . . . . . . 15
5.5.2. Modification to Existing Registry . . . . . . . . . . 15 5.5.2. Modification to Existing Registry . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 16 8.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
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],
based on the Generalized Mobile Ad Hoc Network (MANET) Packet/Message based on the Generalized Mobile Ad Hoc Network (MANET) Packet/Message
Format [RFC5444]. Format [RFC5444].
This document updates [RFC6130] and [OLSRv2], specifically their use This document updates [RFC6130] and [OLSRv2], specifically their use
skipping to change at page 5, line 7 skipping to change at page 5, line 7
"invalid for processing" for other reasons (Section 12.1 of [RFC6130] "invalid for processing" for other reasons (Section 12.1 of [RFC6130]
and Section 16.3.1 of [OLSRv2]). These sections could be interpreted and Section 16.3.1 of [OLSRv2]). These sections could be interpreted
as allowing rejection of a message because a TLV Value field is as allowing rejection of a message because a TLV Value field is
unrecognized. This specification removes that latitude: unrecognized. This specification removes that latitude:
o An implementation MUST NOT reject a message because it contains an o An implementation MUST NOT reject a message because it contains an
unrecognized TLV value. Instead, any unrecognised TLV Value field unrecognized TLV value. Instead, any unrecognised TLV Value field
MUST be processed or ignored by an unextended implementation of MUST be processed or ignored by an unextended implementation of
NHDP or OLSRv2, as described in the following sections. NHDP or OLSRv2, as described in the following sections.
o Hence, this specification removes the 7th, 10th, and 11th bullets
in Section 12.1 of [RFC6130].
It should be stressed that this is not a change to [RFC6130] or It should be stressed that this is not a change to [RFC6130] or
[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-
 End of changes. 6 change blocks. 
28 lines changed or deleted 31 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/