The following errata report has been verified for RFC8231, "Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6289 -------------------------------------- Status: Verified Type: Technical Reported by: Dhruv Dhody <[email protected]> Date Reported: 2020-09-14 Verified by: Deborah Brungard (IESG) Section: 7.3.2 Original Text ------------- Length (16 bits): indicates the total length of the TLV in octets and MUST be greater than 0. The TLV MUST be zero-padded so that the TLV is 4-octet aligned. Corrected Text -------------- Length (16 bits): indicates the length of the value portion of the TLV in octets and MUST be greater than 0. The TLV MUST be zero- padded so that the TLV is 4-octet aligned. Notes ----- The "total length of the TLV" is incorrect, as in PCEP the TLV formatting is as per RFC 5440 which requires the length to be of the value portion only. The other text such as "MUST be greater than 0", the padding rules along with "without a NULL terminator" also point to the fact that the intention of the authors/WG was not "total" (and it is simply a mistake). -------------------------------------- RFC8231 (draft-ietf-pce-stateful-pce-21) -------------------------------------- Title : Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Publication Date : September 2017 Author(s) : E. Crabbe, I. Minei, J. Medved, R. Varga Category : PROPOSED STANDARD Source : Path Computation Element Area : Routing Stream : IETF Verifying Party : IESG _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
