The following errata report has been submitted for RFC5440, "Path Computation Element (PCE) Communication Protocol (PCEP)".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5440&eid=4956 -------------------------------------- Type: Editorial Reported by: Adrian Farrel <afar...@juniper.net> Section: 9.3 Original Text ------------- Corrected Text -------------- Notes ----- 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.) Instructions: ------------- This erratum 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 can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5440 (draft-ietf-pce-pcep-19) -------------------------------------- Title : Path Computation Element (PCE) Communication Protocol (PCEP) Publication Date : March 2009 Author(s) : JP. Vasseur, Ed., JL. Le Roux, Ed. Category : PROPOSED STANDARD Source : Path Computation Element Area : Routing Stream : IETF Verifying Party : IESG _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
