The following errata report has been submitted for RFC5786,
"Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) 
Extensions".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5786&eid=2085

--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <[email protected]>

Section: 6.

Original Text
-------------
   IANA has assigned the Node Attribute TLV (value 5) type from the
   range 3-32767 as specified in [RFC3630], from the top level types in
|  TE LSAs registry maintained by IANA at http://www.iana.org.

   IANA has created and now maintains the registry for the sub-TLVs of
|   the Node Attribute TLV.  Value 1 is reserved for Node IPv4 Local
|  Address sub-TLV and value 2 for Node IPv6 Local Address sub-TLV.

   [...]

      o  Types in the range 32778-65535 are not to be assigned at this
         time.  Before any assignments can be made in this range, there
         MUST be a Standards Track RFC that specifies IANA
|        Considerations that covers the range being assigned.


Corrected Text
--------------
   IANA has assigned the Node Attribute TLV (value 5) type from the
   range 3-32767 as specified in [RFC3630], from the top level types in
|  the TE LSAs registry maintained by IANA at http://www.iana.org.

   IANA has created and now maintains the registry for the sub-TLVs of
|  the Node Attribute TLV.  Value 1 is assigned to the Node IPv4 Local
|  Address sub-TLV and value 2 to the Node IPv6 Local Address sub-TLV.

   [...]

      o  Types in the range 32778-65535 are not to be assigned at this
         time.  Before any assignments can be made in this range, there
         MUST be a Standards Track RFC that specifies IANA
|        Considerations that cover the range being assigned.


Notes
-----
Rationale:
a)  missing article
b)  confusing use of "reserved"; IANA has _assigned_ these 2 values
c)  singular/plural mismatch

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5786 (draft-ietf-ospf-te-node-addr-07)
--------------------------------------
Title               : Advertising a Router's Local Addresses in OSPF Traffic 
Engineering (TE) Extensions
Publication Date    : March 2010
Author(s)           : R. Aggarwal, K. Kompella
Category            : PROPOSED STANDARD
Source              : Open Shortest Path First IGP
Area                : Routing
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
OSPF mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ospf

Reply via email to