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: 4867
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: DHRUV DHODY
Date Reported: 2016-11-16
Verifier Name: Deborah Brungard
Date Verified: 2017-03-13
Section 3.4 says:
<PCReq Message>::= <Common Header> <request> where: <request>::= <RP> <end-point-rro-pair-list> [<OF>] [<LSPA>] [<BANDWIDTH>] [<metric-list>] [<IRO>] [<LOAD-BALANCING>] where: <end-point-rro-pair-list>::= <END-POINTS>[<RRO-List>][<BANDWIDTH>] [<end-point-rro-pair-list>] <RRO-List>::=<RRO>[<BANDWIDTH>][<RRO-List>] <metric-list>::=<METRIC>[<metric-list>]
It should say:
<PCReq Message>::= <Common Header> [<svec-list>] <request-list> where: <svec-list>::=<SVEC> [<OF>] [<metric-list>] [<svec-list>] <request-list>::=<request>[<request-list>] <request>::= <RP> <end-point-rro-pair-list> [<OF>] [<LSPA>] [<BANDWIDTH>] [<metric-list>] [<IRO>|<BNC>] [<LOAD-BALANCING>] where: <end-point-rro-pair-list>::= <END-POINTS>[<RRO-List>[<BANDWIDTH>]] [<end-point-rro-pair-list>] <RRO-List>::=(<RRO>|<SRRO>)[<RRO-List>] <metric-list>::=<METRIC>[<metric-list>]
Notes:
o Update the Routing Backus-Naur Form (RBNF) [RFC5511] for Request
message format:
* Update the request message to allows for the bundling of
multiple path computation requests within a single Path
Computation Request (PCReq) message.
* Add <svec-list> in PCReq message. This object was missed in
[RFC6006].
* Add BNC object in PCReq message. This object is required to
support P2MP. It shares the same format as Include Route Object
(IRO) but it is a different object.
* Update the <RRO-List> format to also allow Secondary Record
Route object (SRRO). This object was missed in [RFC6006].
* Removed the BANDWIDTH Object followed by Record Route Object
(RRO) from <RRO-List>. As BANDWIDTH object doesn't need to follow
for each RRO in the <RRO-List>, there already exist BANDWIDTH
object follow <RRO-List> and is backward compatible with
[RFC5440].
* Update the <end-point-rro-pair-list> to allow optional BANDWIDTH
object only if <RRO-List> is included.
Refer https://datatracker.ietf.org/doc/draft-palleti-pce-rfc6006bis/?include_text=1