Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information

Introduction Segment Routing Policy for Traffic Engineering details the concepts of SR Policy and approaches to steering traffic into an SR Policy. In particular, it describes the SR Candidate Path as a collection of one or more Segment Lists. The current PCEP standards only allow for signaling of one Segment List per Candidate Path. The PCEP extension to support Segment Routing Policy Candidate Paths specifically avoids defining how to signal multiple Segment Lists. This document defines the required extensions that allow the signaling of multipath information via PCEP. Although these extensions are motivated by the SR Policy use case, they are also applicable to other data plane types.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Terminology The following terms are used in this document: ECMP:

Equal Cost Multi Path, equally distributing traffic among multiple paths/links, where each path/link gets the same share of traffic as others.

W-ECMP:

Weighted ECMP, unequally distributing traffic among multiple paths/links, where some paths/links get more traffic than others.

Motivation This extension is motivated by the use-cases described below.

Signaling Multiple Segment Lists of an SR Candidate Path The Candidate Path of an SR Policy is the unit of signaling in PCEP, see . Each Candidate Path can contain multiple Segment Lists and each Segment List is encoded by one Explicit Route Object (ERO). However, each PCEP LSP can contain only a single ERO, which prevents the encoding of multiple Segment Lists within the same SR Candidate Path.

Splitting of Requested Bandwidth A PCC may request a path with 80 Gbps of bandwidth, but all links in the network have only 60 Gbps capacity. The PCE can return two paths, that can together carry 80 Gbps. The PCC can then equally or unequally split the incoming 80 Gbps of traffic among the two paths. introduces a new TLV that carries the path weight that facilitates control of load-balancing of traffic among the multiple paths.

Reverse Path Information Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs) defines a mechanism in PCEP to associate two opposite direction SR Policy Candidate Paths. However, within each Candidate Path there can be multiple Segment Lists, and does not define a mechanism to specify mapping between Segment Lists of the forward and reverse Candidate Paths. Certain applications such as Circuit Style SR Policy , require the knowledge of reverse path(s) per Segment List, not just per Candidate Path. For example, when the headend knows the reverse Segment List for each forward Segment List, then PM/BFD can run a separate session on every Segment List, by imposing a double stack (forward stack followed by reverse stack) onto the packet. If the reverse Segment List is co-routed with the forward Segment List, then the PM/BFD session would traverse the same links in the forward and reverse directions, thus allowing detection of link/node failures in both directions.

Protocol Extensions

PATH-ATTRIB Object This document defines the PATH-ATTRIB object that is used to carry per-path information and to act as a separator between several ERO/RRO objects in the <intended-path>/<actual-path> RBNF element. The PATH-ATTRIB object always precedes the ERO/RRO that it applies to. If multiple ERO/RRO objects are present, then each ERO/RRO object MUST be preceded by an PATH-ATTRIB object that describes it. The PATH-ATTRIB Object-Class value is 45. The PATH-ATTRIB Object-Type value is 1.

PATH-ATTRIB object format Flags (32 bits):

O (Operational - 3 bits): operational state of the path, same values as the identically named field in the LSP object .
R (Reverse - 1 bit): Indicates this path is reverse, i.e., it originates on the LSP destination and terminates on the LSP source (usually the PCC headend itself). Paths with this flag set serve only informational purpose to the PCC.
Unassigned bits MUST be set to 0 on transmission and MUST be ignored on receipt.

Path ID (32 bits): 4-octet identifier that identifies a path (encoded in the ERO/RRO) within the set of multiple paths under the PCEP LSP. See for details.

METRIC Object The PCEP METRIC object can continue to be used at the LSP level. The metric value encoded into the LSP level METRIC object SHOULD be the maximum value of all the per PATH metrics. Per-path metrics are outside the scope of this document and would require further extensions.

MULTIPATH-WEIGHT TLV New MULTIPATH-WEIGHT TLV is optional in the PATH-ATTRIB object.

MULTIPATH-WEIGHT TLV format Type (16 bits): 61 for "MULTIPATH-WEIGHT" TLV. Length (16 bits): 4. Weight (32 bits): weight of this path within the multipath, if W-ECMP is desired. The fraction of flows a specific ERO/RRO carries is derived from the ratio of its weight to the sum of the weights of all other paths. When the MULTIPATH-WEIGHT TLV is absent from the PATH-ATTRIB object, or the PATH-ATTRIB object is absent from the <intended-path>/<actual-path>, then the Weight of the corresponding path is taken to be 1.

MULTIPATH-BACKUP TLV New MULTIPATH-BACKUP TLV is optional in the PATH-ATTRIB object. This TLV is used to specify protecting standby path(s), for each ECMP path within a PCEP LSP. This is similar to path protection, but works at the ECMP path level instead of at the PCEP LSP level. This functionality is not part of the SR Policy Architecture , but is something optional that may be implemented for certain specialized use cases. One such use case is the Point-to-Multipoint (P2MP) SR Policy . Support for the MULTIPATH-BACKUP TLV is currently defined only for P2MP paths. Support for Point-to-Point (P2P) paths is out of scope for this document. If needed in the future, support for P2P paths using the MULTIPATH-BACKUP TLV can be defined in future documents. Future documents that extend this TLV to support P2P paths SHOULD also define explicit capability exchange mechanisms to allow PCEP peers to negotiate support for MULTIPATH-BACKUP with P2P paths.

MULTIPATH-BACKUP TLV format Type (16 bits): 62 for "MULTIPATH-BACKUP" TLV Length (16 bits): 4 + (N * 4) (where N is the Backup Path Count) Backup Path Count (16 bits): Number of backup path(s). Flags (16 bits):

B: If set, indicates a pure backup path. This is a path that only carries rerouted traffic after the protected path fails. If this flag is not set, or if the MULTIPATH-BACKUP TLV is absent, then the path is assumed to be primary that carries normal traffic.
Unassigned bits MUST be set to 0 on transmission and MUST be ignored on receipt.

Backup Path ID(s): a series of 4-octet identifier(s) that identify the backup path(s) in the set that protect this primary path. If a PCEP speaker receives a MULTIPATH-BACKUP TLV applied to a P2P path, it SHOULD reject the path and send a PCError message with Error-Type = 19 ("Invalid Operation") and Error-Value = 20 ("Not supported path backup").

MULTIPATH-OPPDIR-PATH TLV New MULTIPATH-OPPDIR-PATH TLV is optional in the PATH-ATTRIB object. Multiple instances of the TLV are allowed in the same PATH-ATTRIB object. This TLV encodes a many-to-many mapping between forward and reverse paths. Many-to-many mapping means that a single forward path MAY map to multiple reverse paths and conversely that a single reverse path MAY map to multiple forward paths. Many-to-many mapping can happen for an SR Policy, when a Segment List contains Node Segment(s) which traverse parallel links at the midpoint. The reverse of this Segment List may not be able to be expressed as a single Reverse Segment List, but requires multiple Reverse Segment Lists to cover all the parallel links at the midpoint.

MULTIPATH-OPPDIR-PATH TLV format Type (16 bits): 63 for "MULTIPATH-OPPDIR-PATH" TLV Length (16 bits): 16. Reserved: This field MUST be set to zero on transmission and MUST be ignored on receipt. Flags (16 bits):

N (Node co-routed): If set, indicates this path is node co-routed with its opposite direction path, specified in this TLV. Two opposite direction paths are node co-routed if they traverse the same nodes, but MAY traverse different links.
L (Link co-routed): If set, indicates this path is link co-routed with its opposite directions path, specified in this TLV. Two opposite direction paths are link co-routed if they traverse the same links (but in opposite directions).
Unassigned bits MUST be set to 0 on transmission and MUST be ignored on receipt.

Opposite Direction Path ID (32 bits): Identifies a path that goes in the opposite direction to this path. If no such path exists, then this field MUST be set to 0, a value reserved to indicate the absence of a Path ID. Multiple instances of this TLV present in the same PATH-ATTRIB object indicate that there are multiple opposite-direction paths corresponding to the given path. This allows for many-to-many relationship among the paths of two opposite direction LSPs. Whenever path A references another path B as being the opposite-direction path, then path B MUST also reference path A as its own opposite-direction path. Furthermore, their values of the R-flag (Reverse) in the PATH-ATTRIB object MUST have opposite values. If a PCEP speaker receives an opposite-direction path mapping that is asymmetric or where the R-flags are inconsistent, it MUST treat this as an error. The PCEP speaker MUST send a PCError message with Error-Type = 19 ("Invalid Operation") and Error-Value = TBD4 ("Invalid opposite-direction path mapping"). See for an example of usage.

Composite Candidate Path SR Policy Architecture defines the concept of a Composite Candidate Path. A regular SR Policy Candidate Path outputs traffic to a set of Segment Lists, while an SR Policy Composite Candidate Path outputs traffic recursively to a set of SR Policies on the same headend. In PCEP, the Composite Candidate Path still consists of PATH-ATTRIB objects, but ERO is replaced by Color of the recursively used SR Policy. To signal the Composite Candidate Path, we make use of the COLOR TLV, defined in . For a Composite Candidate Path, the COLOR TLV is included in the PATH-ATTRIB Object, thus allowing each Composite Candidate Path to do ECMP/W-ECMP among SR Policies identified by its constituent Colors. Only one COLOR TLV MUST be included into the PATH-ATTRIB object. If multiple COLOR TLVs are contained in the PATH-ATTRIB object, only the first one MUST be processed and the others MUST be ignored. An ERO object MUST be included as per the existing RBNF, this ERO MUST contain no sub-objects. This empty ERO serves as a placeholder to maintain compatibility with existing implementations based on the RBNF defined in . If the head-end receives a non-empty ERO for a Composite Candidate Path, it MUST send a PCError message with Error-Type = 19 ("Invalid Operation") and Error-Value = 21 ("Non-empty path"). See for an example of the encoding.

Per-Flow Candidate Path Per-Flow Candidate Path builds on top of the concept of the Composite Candidate Path. Each Path in a Per-Flow Candidate Path is assigned a 3-bit forward class value, which allows Quality of Service (QoS) classified traffic to be steered depending on the forward class. New MULTIPATH-FORWARD-CLASS TLV is optional in the PATH-ATTRIB object.

MULTIPATH-FORWARD-CLASS TLV format Type (16 bits): TBD1 for "MULTIPATH-FORWARD-CLASS" TLV. Length (16 bits): 4. Reserved: This field MUST be set to zero on transmission and MUST be ignored on receipt. FC (3 bits): Forward class value that is given by the QoS classifier to traffic entering the given Candidate Path. Different classes of traffic that enter the given Candidate Path can be differentially steered into different Colors.

Operation

Capability Negotiation

Multipath Capability TLV New MULTIPATH-CAP TLV is defined. This TLV MAY be present in the OPEN object during PCEP session establishment.

MULTIPATH-CAP TLV format Type (16 bits): 60 for "MULTIPATH-CAP" TLV. Length (16 bits): 4. Number of Multipaths (16 bits): When sent from a PCC, it indicates how many multipaths the PCC can install in forwarding. From a PCE, it indicates how many multipaths the PCE can compute. The value 255 indicates an unlimited number. The value 0 is reserved. Flags (16 bits):

W-flag: whether MULTIPATH-WEIGHT TLV is supported.
B-flag: whether MULTIPATH-BACKUP TLV is supported.
O-flag: whether MULTIPATH-OPPDIR-PATH TLV is supported and requested. If this flag is set, the PCE SHOULD tell the PCC the reverse path information, if it is able to.
F-flag: whether MULTIPATH-FORWARD-CLASS TLV is supported.
C-flag: whether Composite Candidate Path () is supported.
Unassigned bits MUST be set to 0 on transmission and MUST be ignored on receipt.

Note that F-flag and C-flag can be set independently, i.e., F-flag can be set, but C-flag not set, etc. When PCE computes the LSP path, it MUST NOT return more forward multipaths than the corresponding value of "Number of Multipaths" from the MULTIPATH-CAP TLV. If this TLV is absent (from both OPEN and LSP objects), then the "Number of Multipaths" is assumed to be 1. From the PCC, the MULTIPATH-CAP TLV MAY also be present in the LSP object for each individual LSP, to specify per-LSP values. The PCC MUST NOT include this TLV in the LSP object if the TLV was not present in the OPEN objects of both PCEP peers. TLV values in the LSP object override the session default values in the OPEN object. If a PCEP speaker receives a PATH-ATTRIB object but the multipath capability was not successfully negotiated during session establishment, it MUST treat this as an error. The PCEP speaker MUST send a PCError message with Error-Type = 10 ("Reception of an invalid object") and Error-Value = TBD2 ("Unexpected PATH-ATTRIB object"). Additionally, if a PCEP speaker receives a TLV within the PATH-ATTRIB object (such as MULTIPATH-WEIGHT, MULTIPATH-BACKUP, MULTIPATH-OPPDIR-PATH, or MULTIPATH-FORWARD-CLASS) but the corresponding capability flag was not set in the negotiated MULTIPATH-CAP TLV, it MUST treat this as an error. The PCEP speaker MUST send a PCError message with Error-Type = 19 ("Invalid Operation") and Error-Value = TBD3 ("Unsupported multipath capability"). For example, the PCC includes this TLV in the OPEN object at session establishment, setting "Number of Multipaths" to 4 and "O-flag" to 0. The PCC also includes this TLV in the LSP object for a particular LSP, setting "Number of Multipaths" to 16 and "O-flag" to 1. This indicates that the PCC only wants to receive the reverse path information for that particular LSP and that this LSP can have up to 16 multipaths, while other LSPs can only have up to 4 multipaths.

Path ID The Path ID uniquely identifies a Path within the context of an LSP. Note that when the LSP is an SR Policy Candidate Path, the Paths within that LSP are the Segment Lists. Value 0 indicates an unallocated Path ID. The value of 0 MAY be used when this Path is not referenced and the allocation of a Path ID is not necessary. Path IDs are allocated by the PCEP peer that owns the LSP. If the LSP is delegated to the PCE, then the PCE allocates the Path IDs and sends them in the PCReply/PCUpd/PCInitiate messages. If the LSP is locally computed on the PCC, then the PCC allocates the Path IDs and sends them in the PCReq/PCRpt messages. If a PCEP speaker detects that there are two Paths with the same Path ID, then the PCEP speaker MUST send PCError message with Error-Type = 1 ("Reception of an invalid object") and Error-Value = 38 ("Conflicting Path ID").

Signaling Multiple Paths for Loadbalancing The PATH-ATTRIB object can be used to signal multiple path(s) and indicate (un)equal loadbalancing amongst the set of multipaths. In this case, the PATH-ATTRIB is populated for each ERO as follows:

The PCE MAY assign a unique Path ID to each ERO path and populate it inside the PATH-ATTRIB object. The Path ID is unique within the context of a PLSP (when non-zero).
The MULTIPATH-WEIGHT TLV MAY be carried inside the PATH-ATTRIB object. A weight is populated to reflect the relative loadshare that is to be carried by the path. If the MULTIPATH-WEIGHT is not carried inside a PATH-ATTRIB object, the default weight 1 MUST be assumed when computing the loadshare.
The fraction of flows carried by a specific primary path is derived from the ratio of its weight to the sum of all other multipath weights.

Signaling Multiple Paths for Protection The PATH-ATTRIB object can be used to describe a set of backup path(s) protecting a primary path within a PCEP LSP. This capability is currently defined only for P2MP paths. Support for P2P paths with the MULTIPATH-BACKUP TLV is out of scope for this document. In this case, the PATH-ATTRIB is populated for each ERO as follows:

The PCE assigns a unique Path ID to each ERO path and populates it inside the PATH-ATTRIB object. The Path ID is unique within the context of a PLSP.
The MULTIPATH-BACKUP TLV MAY be added inside the PATH-ATTRIB object for each ERO that is protected. The backup path ID(s) are populated in the MULTIPATH-BACKUP TLV to reflect the set of backup paths protecting the primary path. The Length field and Backup Path Count in the MULTIPATH-BACKUP are updated according to the number of backup path ID(s) included.
The MULTIPATH-BACKUP TLV MAY be added inside the PATH-ATTRIB object for each ERO that is unprotected. In this case, MULTIPATH-BACKUP does not carry any backup path IDs in the TLV. If the path acts as a pure backup i.e., the path only carries rerouted traffic after the protected path(s) fail then the B flag MUST be set.

Primary paths which do not include the MULTIPATH-BACKUP TLV are assumed to be protected by all the backup paths. I.e., omitting the TLV is equivalent to including the TLV with all the backup path IDs filled in. Note that a given PCC may not support certain backup combinations, such as a backup path that is itself protected by another backup path, etc. If a PCC does not support a requested backup scenario, the PCC MUST send a PCError message with Error-Type = 19 ("Invalid Operation") and Error-Value = 20 ("Not supported path backup"). Additionally, if a P2P path is sent with a MULTIPATH-BACKUP TLV, the PCC or PCE SHOULD reject it with the same PCError as above.

PCEP Message Extensions The RBNF of PCRpt and PCUpd messages, as defined in , use a combination of <intended-path> and/or <actual-path>. PCReq and PCRep messages, as defined in and extended by , directly include ERO and RRO objects within their respective message structures rather than encapsulating them within <intended-path> or <actual-path> constructs. As specified in Section 6.1 of , within the context of messages that use these constructs, <intended-path> is represented by the ERO object and <actual-path> is represented by the RRO object: ::=

::= ]]>

This document updates to allow multiple ERO/RRO objects to be present in the <intended-path>/<actual-path>: ::= (| () []) ::= (| () []) ]]> Similarly, this document updates to allow multiple paths in the PCInitiate message by allowing multiple ERO objects with their associated path attributes. The PCE-initiated LSP instantiation format is updated to: ::= [] [] ]]> where <intended-path> follows the recursive definition above, allowing multiple paths to be signaled in a single PCInitiate message. Each path is preceded by a PATH-ATTRIB object that describes it.

Examples

SR Policy Candidate Path with Multiple Segment Lists Consider the following sample SR Policy, taken from
. Candidate Path CP1 Preference 200 Weight W1, SID-List1 Weight W2, SID-List2 Candidate Path CP2 Preference 100 Weight W3, SID-List3 Weight W4, SID-List4 ]]> As specified in , CP1 and CP2 are signaled as separate state-report elements and each has a unique PLSP-ID, assigned by the PCC. For this example, PLSP-ID 100 is assigned to CP1 and PLSP-ID 200 to CP2. The state-report for CP1 can be encoded as: =

> ]]>

The state-report for CP2 can be encoded as: =

> ]]>

The above sample state-report elements only specify the minimum mandatory objects, of course other objects like SRP, LSPA, METRIC, etc., are allowed to be inserted. Note that the syntax > ]]> means that this is PATH-ATTRIB object with Path ID field set to 1 and with a MULTIPATH-WEIGHT TLV carrying weight of "W1".

Two Primary Paths Protected by One Backup Path Suppose there are 3 paths: A, B, C. Where A and B are primary and C is to be used only when A or B fail. Suppose the Path IDs for A, B, C are respectively 1, 2, 3. This would be encoded in a state-report as: =

> ]]>

Note that the syntax > ]]> means that this is PATH-ATTRIB object with Path ID field set to 1 and with a MULTIPATH-BACKUP TLV that has B-flag cleared and contains a single backup path with Backup Path ID of 3.

Composite Candidate Path Consider the following Composite Candidate Path, taken from
. Candidate Path CP1 Preference 200 Weight W1, SR policy Weight W2, SR policy ]]> This is signaled in PCEP as:

> ]]>

Opposite Direction Tunnels Consider the two opposite-direction SR Policies between endpoints H1 and E1. Candidate Path CP1 Preference 200 Bidirectional Association = A1 SID-List = SID-List = Candidate Path CP2 Preference 100 Bidirectional Association = A2 SID-List = SID-List = SR policy POL2 Candidate Path CP1 Preference 200 Bidirectional Association = A1 SID-List = SID-List = Candidate Path CP2 Preference 100 Bidirectional Association = A2 SID-List = ]]> The state-report for POL1, CP1 can be encoded as: =

> > > > > > > > ]]>

The state-report for POL1, CP2 can be encoded as: =

> > > > > > ]]>

The state-report for POL2, CP1 can be encoded as: =

> > > > > > > > ]]>

The state-report for POL2, CP2 can be encoded as: =

> > > > > > ]]>

Implementation Status Note to the RFC Editor - remove this section before publication, as well as remove the reference to . This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Cisco Systems

Ciena Corp

Huawei Technologies

IANA Considerations

PCEP Object IANA is requested to confirm the following allocation in the "PCEP Objects" within the "Path Computation Element Protocol (PCEP) Numbers" registry group:

PCEP TLV IANA is requested to confirm the following allocations within the "PCEP TLV Type Indicators" within the "Path Computation Element Protocol (PCEP) Numbers" registry group: IANA is requested to make new allocations within the "PCEP TLV Type Indicators" within the "Path Computation Element Protocol (PCEP) Numbers" registry group:

PCEP-Error Object IANA is requested to confirm the following allocations within the "PCEP-ERROR Object Error Types and Values" within the "Path Computation Element Protocol (PCEP) Numbers" registry group: IANA is requested to make new allocations within the "PCEP-ERROR Object Error Types and Values" within the "Path Computation Element Protocol (PCEP) Numbers" registry group:

Flags in the MULTIPATH-CAP TLV IANA is requested to create a new sub-registry to manage the Flag field of the MULTIPATH-CAP TLV, called "Flags in MULTIPATH-CAP TLV" within the "Path Computation Element Protocol (PCEP) Numbers" registry group. New values are to be assigned by "IETF review"

Flags in the PATH-ATTRIB Object IANA is requested to create a new sub-registry to manage the Flag field of the PATH-ATTRIB object, called "Flags in PATH-ATTRIB Object" within the "Path Computation Element Protocol (PCEP) Numbers" registry group. New values are to be assigned by "IETF review"

Flags in the MULTIPATH-BACKUP TLV IANA is requested to create a new sub-registry to manage the Flag field of the MULTIPATH-BACKUP TLV, called "Flags in MULTIPATH-BACKUP TLV" within the "Path Computation Element Protocol (PCEP) Numbers" registry group. New values are to be assigned by "IETF review"

Flags in the MULTIPATH-OPPDIR-PATH TLV IANA is requested to create a new sub-registry to manage the flag fields of the MULTIPATH-OPPDIR-PATH TLV, called "Flags in the MULTIPATH-OPPDIR-PATH TLV" within the "Path Computation Element Protocol (PCEP) Numbers" registry group. New values are to be assigned by "IETF review"

Security Considerations The security considerations described in , , , , , and are applicable to this specification. As per , it is RECOMMENDED that these PCEP extensions can only be activated on authenticated and encrypted sessions across PCEs and PCCs belonging to the same administrative authority, using Transport Layer Security (TLS) as per the recommendations and best current practices in .

Manageability Considerations All manageability requirements and considerations listed in , , , and apply to the PCEP protocol extensions defined in this document. In addition, the requirements and considerations listed in this section apply.

Control of Function and Policy A PCEP speaker (PCC or PCE) implementation SHOULD allow an operator to enable or disable the multipath capabilities advertised in the MULTIPATH-CAP TLV (see ).

Information and Data Models It is expected that a future version of the PCEP YANG module will be extended to include the PCEP extensions defined in this document.

Liveness Detection and Monitoring The mechanisms defined in this document do not introduce any new liveness detection or monitoring requirements in addition to those already defined in and .

Verify Correct Operations In addition to the verification requirements in and , the following considerations apply:

An implementation SHOULD allow an operator to view the capabilities advertised in the MULTIPATH-CAP TLV by each PCEP peer for a session and for individual LSPs.
An implementation SHOULD allow an operator to view the PATH-ATTRIB object and all its associated TLVs for each path within an LSP. This includes the Path ID, weight, backup information, and opposite-direction path associations.
An implementation SHOULD provide a mechanism to log and display the new PCEP errors defined in this document

Requirements On Other Protocols The PCEP extensions defined in this document do not impose any new requirements on other protocols.

Impact On Network Operations The mechanisms in this document allow for more complex LSP structures with multiple paths. Network operators should be aware of the potential increase in PCEP message sizes and the additional state that must be maintained by PCEP speakers. The "Number of Multipaths" field in the MULTIPATH-CAP TLV can be used to control the scale of multipath computations and state.

Acknowledgement Thanks to Dhruv Dhody for ideas and discussion. Thanks to Yuan Yaping for review comments.

Contributors