RFC Errata
RFC 6006, "Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths", September 2010
Note: This RFC has been obsoleted by RFC 8306
Source of RFC: pce (rtg)See Also: RFC 6006 w/ inline errata
Errata ID: 4868
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: DHRUV DHODY
Date Reported: 2016-11-16
Verifier Name: Deborah Brungard
Date Verified: 2016-11-16
Section 3.5 says:
<PCRep Message>::= <Common Header> <response> <response>::=<RP> [<end-point-path-pair-list>] [<NO-PATH>] [<attribute-list>] where: <end-point-path-pair-list>::= [<END-POINTS>]<path>[<end-point-path-pair-list>] <path> ::= (<ERO>|<SERO>) [<path>] <attribute-list>::=[<OF>] [<LSPA>] [<BANDWIDTH>] [<metric-list>] [<IRO>]
It should say:
<PCRep Message>::= <Common Header> <response-list> where: <response-list>::=<response>[<response-list>] <response>::=<RP> [<end-point-path-pair-list>] [<NO-PATH>] [<UNREACH-DESTINATION>] [<attribute-list>] <end-point-path-pair-list>::= [<END-POINTS>]<path>[<end-point-path-pair-list>] <path> ::= (<ERO>|<SERO>) [<path>] where: <attribute-list>::=[<OF>] [<LSPA>] [<BANDWIDTH>] [<metric-list>] [<IRO>]
Notes:
o Update the RBNF for Reply message format:
* Update PCEP allows for the bundling of multiple path computation
responses within a single Path Computation Reply (PCRep) message.
* Update UNREACH-DESTINATION in PCRep message. This object was
missed in [RFC6006].
Refer: https://datatracker.ietf.org/doc/draft-palleti-pce-rfc6006bis/?include_text=1