RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 5440, "Path Computation Element (PCE) Communication Protocol (PCEP)", March 2009

Note: This RFC has been updated by RFC 7896, RFC 8253, RFC 8356, RFC 9488

Source of RFC: pce (rtg)
See Also: RFC 5440 w/ inline errata

Errata ID: 4956
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Adrian Farrel
Date Reported: 2017-03-01
Verifier Name: Deborah Brungard
Date Verified: 2017-03-02

Section 9.3 says:


This section does not tell IANA the range for the Object-Types to be registered for each Object-Class, nor what to do with the values not assigned in this document.

IANA has correctly recognised that the top value is 15, and that the values between those shown here and 15 should be marked as "Unassigned."

However, there is confusion over the value 0 for an Object-Type. The old entries (arising from RFC 5440) do not mention 0. Newer entries for RFC 7470 and several I-Ds in the pipe mark 0 as Unassigned.

For consistency, ALL 0 Object-Types should be marked "Reserved".

(This might need an Errata Report against some other RFCs if you are particularly fussy, but I think we can do it all on this report.)

Report New Errata

Advanced Search