Shepherd writeup
rfc7188-05

(1) The request is to publish this document as a Standards Track RFC,
and this is indicated in the document header.

The Optimized Link State Routing Protocol version 2 (OLSRv2) has been published as Standards Track. This extension updates the OLSRv2 RFC by defining extensions to definitions of TLVs used by OLSRv2 and the MANET Neighborhood Discovery Protocol (NHDP), to increase their abilities to accommodate protocol extensions.

(2) Document Announcement Write-Up.

Technical Summary

The abstract of this document is included below.

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.


Working Group Summary

There was consensus to publish the document. 


Document Quality

There is a number of independent implementations this extension to OLSRv2. Those
listed below have, explicitly, consented to be nominatively mentioned:

o Ecole Polytechnique, France
  (Contact: Thomas Clausen)

o BAE Systems Advanced Technology Centre, UK
  (Contact Christopher Dearlove)



Personnel

The Document Shepherd is Ulrich Herberg (ulrich@herberg.name); the
responsible Area Directors are Adrian Farrel and Stewart Bryant.

(3) The document Shepherd has participated in review both in the Working
Group, and has run the "idnits" tool against the draft.

(4) The Document Shepherd has no concerns about the reviews of the
document; they have been thorough.

(5) The authors do not believe that additional reviews are required,
aside from the usual directorate reviews during IETF last call.

(6) The Document Shepherd has no concerns with the document.

(7) All authors have confirmed that they are unaware of any IPR needing
disclosure; there are no known IPR claims related to this document.

(8) No IPR disclosures have been filed, as none are required.

(9) WG consensus appears to be strong.

(10) Nobody has threatened an appeal or otherwise indicated extreme discontent.

(11) Some ID nits were found, and should be addressed by the authors in the next revision. This can be done along with addressing other potential comments during IETF LC.

(12) Mib Doctor, media type, and URI reviews are not required.

(13) All references have been defined as either normative or
informative.

(14) No normative references exist to documents not ready for
advancement. Of the normative references, OLSRv2 is not yet an RFC, but has been approved for publication and is in the RFC editor queue.

(15) There are no normative downward references.

(16) Publication of this document will update OLSRv2 (no RFC number assigned yet) and RFC6130. The two references are listed on the title page header, listed in the abstract, and discussed in the introduction.

(17) The Document Shepherd has reviewed the IANA considerations section
of the document, and it appears wholly consistent with the body of said
document. Extensions are associated with the appropriate reservations in
IANA registries. All IANA registries have been clearly defined.

(18) Impact on IANA registries :

There are several new registries:
 - 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.
 - 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 reference to this table.
 - 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.
 - 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.
 - 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.

IANA Experts should be chosen amongst candidates with thorough knowledge of the existing NHDP and OLSRv2 registries. The experts for these existing tables are the MANET WG chairs; the shepherd recommends to select the WG chairs as IANA Experts for these new registries as well.


(19) The Document Shepherd has run the idnits tool against the document; two remaining warnings will be resolved in a new revision to be submitted by the authors after the IETF LC.
Back