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/eid6012 -------------------------------------- Status: Verified Type: Editorial Reported by: Dhruv Dhody <[email protected]> Date Reported: 2020-03-10 Verified by: Deborah Brungard (IESG) Section: 5.8.3 Original Text ------------- If the PCC receives a PCUpd message for an LSP object identified with a PLSP-ID that does not exist on the PCC, it MUST generate a PCErr with Error-type=19 (Invalid Operation), error-value 3, (Attempted LSP Update Request for an LSP identified by an unknown PSP-ID) (see Section 8.5). Corrected Text -------------- If the PCC receives a PCUpd message for an LSP object identified with a PLSP-ID that does not exist on the PCC, it MUST generate a PCErr with Error-type=19 (Invalid Operation), error-value 3, (Attempted LSP Update Request for an LSP identified by an unknown PLSP-ID) (see Section 8.5). Notes ----- s/PSP-ID/PLSP-ID/ Thanks to Rebecca Vanrheenen from RFC Editor team for spotting this while editing another I-D. -------------------------------------- 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
