RFC Errata
Found 1 record.
Status: Held for Document Update (1)
RFC 5786, "Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions", March 2010
Note: This RFC has been updated by RFC 6827, RFC 8687
Source of RFC: ospf (rtg)
Errata ID: 2085
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-03-21
Held for Document Update by: Stewart Bryant
Section 6. says:
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.
It should say:
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