The following errata report has been submitted for RFC6006, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6006&eid=3830 -------------------------------------- Type: Editorial Reported by: Udayasree <[email protected]> Section: 3.15 Original Text ------------- To indicate P2MP message fragmentation errors associated with a P2MP path request, a new Error-Type (17) and subsequent error-values are defined as follows for inclusion in the PCEP-ERROR object: Corrected Text -------------- To indicate P2MP message fragmentation errors associated with a P2MP path request, a new Error-Type (18) and subsequent error-values are defined as follows for inclusion in the PCEP-ERROR object: Notes ----- 17 P2MP END-POINTS Error 18 P2MP Fragmentation Error It should be 18 in this statement Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6006 (draft-ietf-pce-pcep-p2mp-extensions-11) -------------------------------------- Title : Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths Publication Date : September 2010 Author(s) : Q. Zhao, Ed., D. King, Ed., F. Verhaeghe, T. Takeda, Z. Ali, J. Meuric 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
