(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 an optimization to improve the selection of routing MPRs. The optimization retains full interoperability between implementations of OLSRv2 with and without this optimization.
(2) Document Announcement Write-Up.
The abstract of this document is included below.
This specification updates the Optimized Link State Routing Protocol version 2 (OLSRv2) with an optimization to improve the selection of routing MPRs. The optimization retains full interoperability between implementations of OLSRv2 with and without this optimization.
Working Group Summary
There was consensus to publish the document.
There is one publicly known implementation this extension to OLSRv2:
o Ecole Polytechnique, France
(Contact: Thomas Clausen)
The Document Shepherd is Ulrich Herberg (email@example.com); 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
(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). The RFC-to-be is listed on the title page header, listed in the abstract, and discussed in the introduction.
(17) There is no IANA consideration in the document.
(18) There is no IANA consideration in the document.
(19) The Document Shepherd has run the idnits tool against the document; the remaining warning will be resolved in a new revision to be submitted by the authors after the IETF LC.