PCEP extensions for p2mp sr policy

The draft defines a variant of the SR Policy that uses for constructing a P2MP segment to support multicast service delivery. A Point-to-Multipoint (P2MP) Policy connects a Root node to a set of Leaf nodes, optionally through a set of intermediate replication nodes. A Replication segment , corresponds to the state of a P2MP segment on a particular node and provide forwarding instructions for the segment. A P2MP Policy is relevant on the root of the P2MP Tree and it contains candidate paths. The candidate paths are made of path-instances and each path-instance is constructed via replication segments. These replication segments are programmed on the root, leaves and optionally intermediate replication nodes. Replication segments MAY be connected to each other directly, or they MAY be connected or steered via unicast SR segments or a segment list. For a P2MP Tree, a controller may be used to compute paths from a Root node to a set of Leaf nodes, optionally via a set of replication nodes. A packet is replicated at the root node and optionally on Replication nodes towards each Leaf node. There are two types of a P2MP Tree: Spray and Replication. A Point-to-Multipoint service delivery could be via Ingress Replication, known as Spray. The root unicasts individual copies of traffic to each leaf. The corresponding P2MP Policy consists of replication segments only for the root and the leaves and they are connected via a unicast SR Segment. A Point-to-Multipoint service delivery could also be via Downstream Replication, known as Replication Tree. The root and some downstream replication nodes replicate the traffic along the tree as it traverses closer to the leaves. The PCE discovers the root and the leaves via different methods. As an example, the leaves and the root can be explicitly configured on the PCE or PCC can update the PCE with the identity of the root and the leaves when it discovers them via multicast protocols like MP-BGP and MVPN procedures or PIM. The controller can calculate the P2MP Policy and any of its associated replication segments from the root to the leaves with these info and any additional Service Leave Agreements (SLAs) that is used to construct the tree. This document defines PCEP objects, TLVs and the procedures to instantiate a P2MP Policy and Replication Segments.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

After discovering the root and the leaves the PCE programs the PCCs with relevant information needed to create a P2MP Tree. As per draft a P2MP Policy is defined by Root-ID, Tree-ID and a set of leaves. A P2MP policy is a variant of SR policy as such it uses the same concept as draft . A P2MP policy is composed of a collection of SR P2mp Candidate Paths. Candidate paths are computed by the PCE and can be used for P2MP Tree redundancy. Only a single candidate path may be active at each time. Each candidate paths can be globally optimized, therefore it is consists of multiple path-instances. A path-instance can be considered as a P2MP LSP. If a candidate path needs to be globally optimized two path-instances can be programmed from the root the leaves and via make before break procedures the candidate path can be switched from path-instance 1 to the 2nd path-instance. The forwarding states of these path-instances are build via replication segments, in short each path-instance initiated on the root has its own set of replication segments on the Root, Transit and Leaf nodes. A replication segment is set of forwarding instructions on a specific node. Each instruction may be a PUSH or SWAP operation before forwarding out of an interface, or a POP action on bud and leaf nodes. PCE could also calculate and download additional information for the replication segments, such as protections next-hops for link protection (FRR).

SR P2MP Policy Is only relevant on the Root of the P2MP tree and is a policy on PCE. It is downloaded only on the root node and is identified via <Root-ID, Tree-ID> It contains the following information: Root node of the P2MP Segment Set of Leaf nodes of the P2MP Segment Tree-ID, which is a unique identifier of the P2MP tree on the Root A set of Candidate paths belonging to the policy Optional Constraints used to build these candidate paths Candidate Path: Is used for P2MP Tree redundancy where the candidate path with the highest preference is the active path. Each Candidate Path can contain two path-instance for global optimization procedures (i.e. make before break) Contains information regarding originator, discriminator, preference, path-instances Path-instance: Is used for global optimization of the candidate path. Multiple path-instance can be present under a candidate path but only a single path instance is active at a time. A path instance is identified via <Root-ID, Tree-ID, Instance-ID> Replication Segment: Is the forwarding information needed on each replication node for building the forwarding path for each path-instance of the P2MP Candidate path. Explained further in upcoming sections, there are 2 ways to identify the replication segment, depending on the type of replication segment (shared replication segment or non-shared replication segment) It is identified via Tree-ID and Root-ID and path-instance for non-shared replication segment. It is identified via Node-ID, Replication-ID, for shared replication segment. As per a shared replication segment is not associated to a tree and is used for constructing by-pass tunnels. Contains forwarding instructions, in the form of a list of outgoing segments each of which may be a segment list or a single replication segment with next-hop information. On the forwarding plane the Replication Segment is identified via the incoming Replication SID. Replication segment information is downloaded on any node that is replicating the packet on the path of the tree including the Root, Transit and Leaf nodes respectively.

This document attempts to leverage existing IETF draft and RFC documents which define PCEP objects, to update the PCE with Root and Leaves information when PCC Initiated method is used. Similarly, existing documents are utilized where feasible to update the PCC with relevant information to build the P2MP Policy and its Replication Segments. This document introduces new TLVs and Objects specific to a programing P2MP policy and its replication segment.

The bases for a stateful PCE, and reuses the following objects or a variant of them <SRP Object> <LSP Object> A variation of the LSP identifier TLV is defined in this draft, to support P2MP LSP Identifier P2MP capabilities advertisement Candidate paths for P2MP Policy is used for Tree Redundancy. As an example, a P2MP Policy can have multiple candidate paths. Each protecting the primary candidate path. The active path is chosen via the preference of the candidate path. Defines the instance-ID, instance-ID is used for global optimization of a candidate path with in a P2MP policy. Each Candidate path can have 2 path-instances. These path-instances are equivalent to sub-lsps (instance-IDs). There are used for MBB and global optimization procedures. instance-ID is equivalent to LSP ID Segment-list, used for connecting two non-adjacent replication policy via a unicast binding SID or Segment-list. P2MP End Point objects, used for the PCC to update the PCE with discovered Leaves. for programming and identifying the Replication Segment. A new PCE CC Capability sub Tlv is introduced to indicated the support to handle PCE CC based label download for SR P2MP. Forwarding instruction for a P2MP LSP is defined by a set of SR-ERO sub-objects in the ERO object, ERO-ATTRIBUTES object and MULTIPATH-BACKUP TLV as defined in this draft. SR-ERO Sub Object used in the multipath. It should be noted that the can provide further details of the high level P2MP Policy Model.

A P2MP Policy and its candidate path can be identified on the root via the P2MP LSP Object. This Object is a variation of the LSP ID Object defined in and is as follow: PLSP-ID: , is assigned by PCC and is unique per candidate path. It is constant for the lifetime of a PCEP session. Stand-by candidate paths will be assigned a new PLSP-ID by PCC. Stand-by candidate paths can co-exist with the active candidate path. Root-ID: is equivalent to the first node on the P2MP path, as per , Section 4.6.2.1 Tree-ID: is equivalent to Tunnel Identifier color which identifies a unique P2MP Policy at a ROOT and is advertised via the PTA in the BGP AD route or can be assigned manually on the root. Tree-ID needs to be unique on the root. Instance-ID: LSP ID Identifier as defined in RFC 3209, is the path-instance identifier and is assigned by the PCE. The candidate path can have up to two path-instance for global optimization. Instance-IDs are assigned by PCE per path-instance, they are unique within the P2MP Policy. Two or more P2MP policy can reuse the same Instance-ID assigned to their corresponding path-instances. A path-instance for a candidate path of a P2MP policy should program same Instance-ID on the root, transit and leaf nodes when it is programing its replication segments on the PCC.

The key to identify a replication segment is also a P2MP LSP Object. With varying encoding rules for the SR-P2MP-LSP- IDENTIFIER TLV which will be explained in later sections.

PCECC and a variant of CCI object is used in Replication Segment to identify a cross connect. A cross connect is a incoming SID and set of outgoing interfaces and their corresponding SID or SID List. The CCI objects contains the incoming SID and the outgoing interfaces which are presented via the ERO objects, which each may contain a segment list.

A P2MP policy can be instantiated via the PCC or the PCE depending on how the root and the leaves are discovered. This document describes two way to discover the root and the leaves: They can be configured and identified on the controller and are considered PCE initiated. They can be discovered on the PCC via MVPN procedures or legacy multicast protocols like PIM or IGMP etc... and are considered PCC initiated.

PCE is informed of the P2MP request through its API or configuration mechanism to instantiate a P2MP tunnel. PCE will be programmed with the Root and a set of leaf nodes. PCE will initiate the P2MP Policy for the request, by sending a PCInitiate message to the Root. The PCInitiate message will be programmed with a unique Instance-ID for the path-instance (P2MP tunnel) within the P2MP Policy. For the root PCInitiate message ONLY the tree-id should be set to 0 by the PCE, for transit and leaf nodes the PCE can set the tree-id same as the tree-id assigned by the PCC root. Note in PCE initiate the endpoint-object can be added optionally to the PCInitiate message for providing the leaf list to the PCC. Root in response to the PCInitiate message, will generate PLSP-ID for the candidate paths and will use the instantiated Instance-ID from the PCE for the Path-Instance (LSP-ID) contained with in the candidate path. The tree-id for the P2MP Policy are filled by the PCC root node as well. PCC will reports back the PLSP-ID and tree-id with PCE assigned Instance-ID via PCRpt message Optionally, the Root can add any additional leaves that were discovered by multicast procedures in this PCRpt message. PCE will send a PCInitiate message to the Root, Transit and the Leaf nodes to download the Replication Segment information. These messages will utilize the CCI object to identify the p2mp cross connect and encode the forwarding instruction information. PCE will then send a PCUpdate to the root indicating the association information (Candidate path) , and implicitly indicate it to bind to the latest CCI information downloaded.

Root node (PCC) discovers the leaves (as an example via MVPN Procedures or other mechanism), the following communication happens between the PCE and PCCs Root sends a PCRpt message for P2MP policy to PCE including the Root-ID, Tree-ID, PLSP-ID, symbolic-path-name, and any leaves discovered until then. This PCRpt message also includes a association object. In addition: Since the instance-id is set by the PCE, the root will set the instance-id to value to 0 in the RCRpt message For the association object, root will fill the association type according to the association type defined in this draft. The association ID SHOULD be set to value 1 as done in . The association source is set to the Root PCC Address. PCE on receiving of this report, will generate a Instance-ID for this path-instance of the candidate path and compute the P2MP Policy and its replication segments. PCE will send a PCInitiate message to the Root, Transit and the Leaf nodes to download the Replication Segment information. These messages will utilize the CCI object to encode the forwarding instruction information. PCE will then send a PCUpdate to the root indicating the association information (Candidate path) , and implicitly indicate it to bind to the latest CCI information downloaded.

The following procedures are the same for PCE or PCC Init. PCE will download the replication segments for the Candidate-path's path-instances to all the leaves and transit nodes using PCInitiate message with the same Instance-ID that was assigned for the path-instance on the root, PLSP-ID = 0, symbolic path name, Root-address, Tree-id(assigned by the root an obtained via P2MP Policy creation). This PCInitiate message includes the EROs needed for the replication segments. These messages will utilize the CCI object to encode the forwarding instruction information. Any new candidate path for the P2MP Policy is downloaded by PCE to the Root by sending a PCInitiate message it should be noted, PLSP-ID, Path-Instance ID are generated by the PCC for these new candidate paths and their Path-instances Any update to the Candidate Paths or Replication Segments is done via the PCUpd message. Association object need to be present for Candidate Path PCUpdate and PCRpt message. CCI object needs to be present the replication segment updates. The PCE will also download the necessary replication segment for the candidate path and its path-instances to the root, leaves and the transit nodes via a PCInit message New leaves can be discovered via Multicast procedures, and new replication segments can be instantiated or existing one updated to reach these leaves If these leaves reside on routers that are part of the P2MP LSP path, then PCUpd is sent from PCE to necessary PCCs (LEAVES, TRANSIT or ROOT) with the correct PLSP-ID, Instance-ID, Tree-ID and CC-ID. If the new leaves are residing on routers that are not part of the P2MP Tree yet, then a PCInitiate message is sent from PCE to these new leaves with PLSP- ID=0 and Instance-ID that the PCE has reserved for that path-instance and end to end P2MP tree. The active candidate-path is indicated by the PCC through the operational bits(Up/Active) of the LSP object in the PCRpt message. If a candidate path needs to be removed, PCE sends PC Initiate message, setting the R-flag in the LSP object and R bit in the SRP-object. To remove the entire P2MP-LSP, PCE needs to send PCInitiate remove messages for every candidate path of the P2MP POLICY to the root and send PCInitiate remove messages for every Replication Segment on all the PCCs on the P2MP Tree. The R bit in the LSP Object as defined in , refers to the removal of the LSP as identified by the SR-P2MP-INSTANCE-ID-TLV (defined in this document). An all zero (SR-P2MP-LSP-ID-TLV defines to remove all the state of the corresponding PLSP-ID. A candidate path is made active based on the preference of the path. If the Root is programed with multiple candidate paths from different sources, as an example PCE and CLI, based on its tie-breaking rules, if it selects the CLI path, it will send a report to PCE for the PCE path indicating the status of label-download and sets operational bit of the LSP object to UP and Not Active . At any instance, only one path will be active

When a P2MP LSP needs to be optimized for any reason (i.e. it is taking a FRR tunnel or new routers are added to the network) a global optimization of the candidate path is possible. Each Candidate Path can contain two Path-Instances. The current unoptimized Path-Instance is the active instance and its replication segments are forwarding the multicast PDUs from the root to the leaves. However the second optimized Path-Instance will be setup with its own unique replication segments throughout the network, from the Root to the leaves. These two Path-Instances can co-exist. The two Path-Instances are uniquely identified by their Instance-ID in the SR-P2MP-INSTANCE-ID-TLV (defined in this document). After the optimized LSP has been downloaded successfully PCC MUST send two reports, reporting UP of the new path indicating the new LSP-ID, and a second reporting the tear down of the old path with the R bit of the LSP Object SET with the old Instance-ID in the SR-P2MP-INSTANCE-ID-TLV. This MBB procedure will move the multicast PDUs to the optimized Path-Instance. The leaf should be able to accept traffic from both Path-Instances to minimize the traffic outage by the Make Before Break process.

When one of the PCCs involved in the LSP lacks the capability to support more than one instance, the possibility of achieving global MBB (make before break) is compromised. However, with knowledge of the PCCs' advertised capabilities, the PCE can detect this limitation and instead opt for local re-optimization of the candidate path. In such cases, the PCE can compute the optimized LSP but send the PCUpd message using the existing Instance for candidate path, specifically targeting the PCCs where the optimized LSP triggers a change in forwarding state.

Currently this draft identifies the Facility FRR procedures. In addition, only LINK Protection procedures are defined. How the Facility Path is built and instantiated is beyond the scope of this document.

As an example, in figure 1 both R and T are configured with replication segments. There are two interface between R and T. One can be used as primary and second as a bypass in case the primary interface is down. There can be 2 method to protect the primary interface. The two replication segments on R and T can take advantage of unicast SR to connect to each other. In this case the LFA of unicast SR can be utilize to protect the primary interface between R and T. The replication segment provides protection nexthop, the protection nexthop can be programmed to take the alternate interface between R and T to protect the primary interface. As a second example, in figure 2, R and T connected directly and via network F1..F2. In this example as per example 1 unicast SR can be used to connect the two replication segments and in this case the unicast SR LFA or R-LFA or TI-LFA can be used to protect the direct link between R-T via F1. That said if there is no unicast SR available with in the network, the PCE optionally can setup a shared replication point on F1 and F2 and protect all path-instances that are traversing R-T via this shared replication segment. In addition, PHP procedure and implicit null label on the bypass path can be implemented to reduce the PCE programming on the MP PCC.

There could be nodes between two replication segment that do not support P2MP Policy or Replication segment. It is possible to connect two non-adjacent Replication segments via a unicast segment routing path and SID list. The SID list can be comprised of any IGP supported segment types (ex: Binding, Adjacency, Node). This information is encoded via the SR-ERO sub-objects and ERO-attributes objects. The last segment in an encoding SID list MUST be a replication segment

SR P2MP Policy can be constructed via the following objects

::=

optionally a list of end-point can be added. This is true weather it is PCC initiated or PCE initiated [} ]]>

Replication segment can be constructed via the following objects:

::= (| (

)) ::= [] ::= (() []) ]]>

Path-attribute as per

The new objects and TLV's defined in this document can be included in PCRpt, PcInitiate and PcUpd messages. It should be noted that every PcRpt, PcInitiate and PCUpd messages will contain full list of the Leaves and segment and forwarding information that is needed to build the Candidate path and its Replication segments. They will never send the delta information related to the new leaves or forwarding information that need to be added or updated. This is necessary to ensure that PCE or any new PCE is in sync with the PCC.

This draft uses to identify each out-going interface in the replication segment. In addition each out-going interface can be protected by a backup path. The Path Attributes Object is used to provide the relation between the primary path and its backup path as per draft . Note: Multipath weight TLV MUST not be used and should be ignored when revived. Composite Candidate Path TLV SHOULD NOt be present and ignored if present. When a replication segment is being updated or new out-going interfaces are added to a specific replication segment, the PCRpt, PCInitiate and PCUpd messages sent via PCEP maintains the previous ERO Path IDs and generates new Path IDs for new instructions. The PATH IDs are maintained for each specific forwarding instructions until the instructions are deleted. For example: When the first leaf is added, the PCE will update with Path ID 1 to the PCC. When the second leaf is added, according to the path calculated, PCE might just append the existing instruction Path ID 1 with a new Path ID 2 to construct the new PCUpd message.

The CCI Object is used to identify the entire cross connect of incoming segment and the set of outgoing Interfaces and their corresponding SIDs/SIDList. Any modification to the cross connect should use this CCI ID to identify the cross connect uniquely. Leaves and their corresponding Path IDs can be removed from the cross connect identified via the CCI. The CC-ID is assigned by the PCE. The Central Control Instructions (CCI) Object used by the PCE to specify the controller instructions is defined in . defines CCI object-type for SR-MPLS. This document redefines a new version of the SR-MPLS CCI object-type for SR P2MP Policy in upcoming sections.

A PCE does not advertise its P2MP capability during discovery, PCEP should be used to allow a PCC to discover, during the Open Message Exchange, which PCEs are capable of supporting SR P2MP path computation. To satisfy this requirement, we extend the PCEP OPEN object by defining an optional TLV to indicate the PCE's capability to perform SR P2MP path computations. This new TLV is called SR-P2MP-POLICY-CAPABILITY. The inclusion of this TLV in an OPEN object indicates that the sender can perform SR P2MP path computations. The capability TLV is meaningful only for a PCE, so it will typically appear only in one of the two Open messages during PCE session establishment. However, in the case of PCE cooperation (e.g., inter-domain), when a PCE behaving as a PCC initiates a PCE session. it SHOULD also indicate its path computation capabilities. This draft defines a new SR-P2MP capability TLV with type TBD

Number of Instances 16 bits - Number of instances the advertising PCEP speaker supports. This is meaningful for PCEs. PCEs can determine the least number of instances that could be created for a SR P2MP policy. Number of replication 16 bits - number of out going interfaces that the system is capable of having per multicast state. Flags 16 bits - Not used currently Upon the receipt of an Open message, the receiving PCEP peer MUST determine whether the suggested PCEP session characteristics (leaf-types) are acceptable. If the suggested leaf-types are not acceptable to the receiving peer, it MUST send an PCEP Error message (PCErr) with Error-Type=2 (Capability not supported) and error-value X (new error type assigned by IANA incompatible SR P2MP leaf types) (See Section 4.5.2 for leaf-types)

If a PCEP speaker advertises SR P2MP Policy Capability then it MUST include the PST = 1 in the PATH-SETUP-TYPE-CAPABILITY TLV as per

A Assoc-Type-List TLV as per section 3.4 should be send via PCEP open object with following association type

OP-CONF-Assoc-RANGE (Operator-configured Association Range)should not be set for this association type and must be ignored.

This document reuses symbolic path name from section 7.3.2. For P2MP Policy a symbolic path is unique for a Candidate Path of the P2MP Policy on the PCC. It is recommended for the symbolic path name to be root-id+tree-id+cp discriminator.

Two ASSOCIATION object types for IPv4 and IPv6 are defined in . The ASSOCIATION object includes "Association type" indicating the type of the association group. This document adds a new Association type. Association type = TBD1 "P2MP SR Policy Association Type" for SR Policy Association Group (P2MP SRPAG). NOTE: for PCC initiate the Association object is present in the first PCRpt message that is send by the PCC to PCE to indicate the initiation of the P2MP policy and its candidate path, this first PCRpt message does not have a corresponding PCUpdate message but it does include the Association object accordingly. NOTE: The Association Source should be set to the root address of the P2MP tree. In par with section 4.2, P2MP policy reuses the four TLVs used in the SRPA object. P2MP policy also redefines the extended association ID TLV: SRPOLICY-POL-NAME TLV: (optional) encodes P2MP SR Policy Name SRPOLICY-CPATH-ID TLV: (mandatory) encodes P2MP SR Policy Candidate path Identifier SRPOLICY-CPATH-NAME TLV: (optional) encodes P2MP SR Policy Candidate path name. SRPOLICY-CPATH-PREFRENCE TLV: (optional) encodes P2MP SR Policy Candidate path preference value. In addition to above the extended association ID TLV has been modified to address the P2MP Policy

In par with the Extended Association ID TLV MUST be included and it MUST be in the following format for the P2MP Policy

Length: 4 byte Tree-ID: Tree ID that the replication segment is part of as per draft-ietf-spring-sr-p2mp-policy

In order for the Root to indicate operations of its leaves(Add/Remove/Replace-all), the PC Report message is extended to include P2MP End Point <P2MP End-points> Object which is defined in It SHOULD be noted, the absence of the P2MP-END-POINTS Object means that there is no change in the leaf endpoint of the policy. The format of the PC Report message is as follow: <Common Header> [<SRP>] <LSP> [<association-list>] [<end-points-list>]

Leaf Types (derived from section 3.3.2) : New leaves to add (leaf type = 1) Old leaves to remove (leaf type = 2) the entire pce leaf list is overwritten and replaced with the new leaf list (leaf type = 5) Note a PCE speaking node MUST NOT combine leaf type 1 and 2 with leaf type 5. Note a PCE speaking node SHOULD NOT have the same node present in the leaf type 1 and 2 if both leaf types are present. A given P2MP END-POINTS object gathers the leaves of a given type. Note that a P2MP report can mix the different types of leaves by including several P2MP END-POINTS objects. The END-POINTS object body has a variable length. These are multiples of 4 bytes for IPv4, multiples of 16 bytes, plus 4 bytes, for IPv6.

As it was mentioned previously both P2MP Policy and Replication Segment are identified via the LSP object and more precisely via the SR-P2MP-LSPID-TLV The P2MP Policy uses the PLSP-ID to identify the Candidate Paths and the Instance-ID to identify a Path-Instance with in the Candidate path. On other hand the Replication Segment uses the SR-P2MP-LSPID-TLV to identify and correlate a Replication Segment to a P2MP Policy As it was noted previously on the Root, the P2MP Policy and the Replication Segment is downloaded via the same PCUpd message.

The LSP Object is defined in Section 7.3 of . It specifies the PLSP-ID to uniquely identify an LSP that is constant for the life time of a PCEP session. Similarly, for a P2MP tunnel, the PLSP-ID identify a Candidate Path uniquely with in the P2MP policy. The LSP Object MUST include the new SR-P2MP-INSTANCE-ID-TLV (IPV4/IpV6) defined in this document below. This is a variation to the P2MP object defined in

The type (16-bit) of the TLV is TBD (need allocation by IANA). Root: Source Router IP Address Tree-ID: Unique Identifier of this P2MP LSP on the Root. Instance-ID : Contains 32 Bit instance ID. Instance-id 0 is reserved. Reserved: 8 bits reserved for future use Flags: 8 bits, A - Activate the Instance-ID, R - Remove the Instance-ID At any given time, only one instance SHOULD be active. Activating one instance entails deactivating all other instances, with the condition that the active instance MUST have a non-zero value. The (A) flag is meaningful for Root PCC and PCEs. PCE MUST be setting (A) flag in the PCupd containing SR-P2MP-INSTANCE-ID TLV for activating the instance. The decision regarding when to set the (A) flag can be made locally on the PCE. E.g., this decision can be based on factors such as receiving PCRpt messages from all PCCs for the new instance or utilizing a timer-based approach to ensure that the data plane is completely configured on all PCCs. It's important to note that determining the appropriate timing for activating the new instance is not within the scope of this document. After the activation of the P2MP Policy any PCUpd MUST include the (A) flag in the P2MP-Instance TLV. Root PCC MUST set the (A) flag in the PCRpt as a response to receiving a PCupd message with the (A) flag set. If a PCE receives a PCRpt with the (A) flag set in response to a PCUpd message that did not have the (A) flag set, then PCE MUST treat this as an error. In such a case, PCE MUST send an PCEP Error message (PCErr) with Error-Type=10 (Reception of an Invalid Object) and error-value (X) (Invalid active instance). For transit or leaf PCCs, receipt of a PCUpd message with the (A) flag MUST be treated as an error. Transit or leaf PCCs MUST send an PCEP Error message (PCErr) with Error-Type=19 (Invalid Operation) and error-value (X) (Attempted activating instance on Transit or leaf PCC).

As per a replication segment has a next-hop-group which MAY contain a single outgoing replication SID or a list of SIDs (sr-policy-sid-list) In either case there needs to be a replication SID identifying the replication state on a downstream replication node. This means two replication segments can be directly connected or connected via a unicast SR domain.

The format of a Replication Segment message encoding is similar to P2MP Policy. However, the P2MP Policy contains the association object and the replication segment message does not contain the association object. In addition the replication segment uses the CCI object to identify a P2MP cross connect. The replication segment is downloaded individually to the root, transit and leaf nodes without the P2MP Policy. The P2MP Policy is a Root Concept. The replication segment uses SR-P2MP-LSPID-TLV as its identifier. The TLV is coded differently for shared and non-shared case

The CCI Object as defined in is used to identify a forwarding instruction in the Replication Segment. A forwarding instruction is incoming SID and a set of outgoing branches. The CCI Object-Type of 1 is used for the MPLS Label. The label in the CCI Object is the incoming SID. The outgoing SIDs are defined by the ERO Objects. The CCI Object can be include in Reports, initiate and Update messages for Replication Segments. The PCInitiate message defined in and extended in is further extended to support SR-P2MP replication segment based central control instructions.

::=

Where: is defined in "RFC5440" ::= [] ::= (| | ) ::= (| (

)) ::= [] ::= (() []) Where: and are as per [RFC8281]. ]]>

The LSP and SRP object is defined in . The <intended-path> is as per (PATH-ATTRIB and ERO).

::=

Where: ::= [] ::= (| ) ::= []

::= [] (| (

)) ::= [] Where: is as per [RFC8231] and the LSP and SRP object are also defined in [RFC8231]. The is as per [draft-ietf-pce-multipath] (PATH-ATTRIB and ERO). ]]>

This document extends the use of PCUpd message with SR-P2MP CCI as follows:

::=

Where: ::= [] ::= (| ) ::=

::= (

) Where: is as per [RFC8231] and the LSP and SRP object are also defined in [RFC8231]. The is as per [draft-ietf-pce-multipath] (PATH-ATTRIB and ERO). ]]>

Any modification to the cross connect should use this CCI ID to As per [draft-ietf-spring-sr-replication-segment] a replication identify the cross connect uniquely. Leaves and their corresponding segment has a next-hop-group which MAY contain a single outgoing Path IDs can be removed from the cross connect identified via the replication SID or a list of SIDs (sr-policy-sid-list) In either case CCI. The CC-ID is assigned by the PCE. defines CCI object-type for SR-MPLS. This document redefines a new version of the SR-MPLS CCI object-type for SR P2MP Policy in upcoming sections.

Flags: The V and the L flags are defined as per The node action and role of ingress, transit, leaf or bud, is indicated via the 4 bit roles field Head, role type = 1 Transit, role type = 2 Leaf, role type = 3 Bud, role type = 4

Forwarding information of a replication segment can be configured and steered via many different mechanisms. RFC defines the NAI types. As an example a replication SID can be steered via: Replication SID steered with an IPv4/IPv6 directly connected nexthop (RFC 8664 NAI type 3, 4, 6 (adjacency)) In this case there will two SR-ERO in the ERO Object, with the Replication SID SR-ERO at the bottom and the IPv4/IPv6 SR-ERO on the top. Replication SID steered with an IPv4/IPv6 loopback address that reside on the directly connected router. (NAI type 1..2 (node)) In this case there will two SR-ERO in the ERO Object, with the Replication SID SR-ERO at the bottom and the IPv4/IPv6 SR-ERO on the top. Replication SID steered with unnumbered IPv4/IPv6 directly connected Interface (NAI type 5 (adjacency unnumbered) Replication SID steered via a SR adjacency or node SID In this case even a sid-list can be used to traffic engineer the path between two Replication Segment The Replication SID SR-ERO is at the bottom while the segments describing the path are on top in order.

The P2MP policy and its replication segment can be delete by the PCC or by the PCE. to delete the P2MP policy all the Candidate paths associated to that P2MP policy need to be deleted. The last Candidate path that is being deleted, will delete the P2MP Policy Instance as well on the PCE or PCC. To delete Candidate paths there are two methods: The Candidate paths can be deleted by deleting all the path-instances associated with them and the last path-instance that is deleted will trigger the Candidate path to be deleted. The Candidate path can be deleted entirely and this will delete all the associated path-instances for that candidate path as well. When PCE is deleting a Candidate path or a path instance it should delete all the replication segments of that Candidate path or path-instance as well before it moved to the next Candidate path or path instance.

For PCC to delete a Candidate path, Root send a PCRpt message with the R bit of the LSP object set and all the fields of the SR-P2MP- LSP-ID TLV set to 0(indicating to remove all state and path-instances associated with this P2MP tunnel). The PCE in response sends a PCInitiate message with R bit in the SRP object SET to all nodes along the path to indicate deletion of the entries. Note in this case the instance-id can be set 0 with the R bit set to indicate removing the entire Candidate path and all its path-instances. For PCC to delete a path-instance, Root send a PCRpt message with the R bit of the LSP object set and all the fields of the SR-P2MP- LSP-ID TLV set to 0 but the instance-id value (indicating to remove the specific path-instances associated with this P2MP tunnel). The PCE in response sends a PCInitiate message with R bit in the SRP object SET to all nodes along the path to indicate deletion of the entries. Note in this case the instance-id has to be set accordingly with the R bit set to indicate removing the specific path-instances. This is useful for the global optimization case where after downloading the optimize path-instance and ensuring the path-instance is operational the PCC removed that old path-instance.

For PCE to delete the Candidate path or path instance, the above can be implemented without the PCC PCRpt message.

The Fragmentation bit in the LSP object (F bit) can be used to indicate a fragmented PCEP message

This is an example of PCC initiated P2MP Policy. The PCC will send a Report message to the PCE to initiat a P2MP Policy with a set of leaves that are discovered via Next Generation MVPN procedures as per . In addition, since the PCC is initiating the P2MP Policy, it does populate the PLSP-ID for the candidate path. PCC will leave the instance-id for the Path-Instance to 0 and the instance-id is assigned by the PCE.

| PLSP-ID = 1 | A:1,D:1,N:1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=17 | Length=| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | symbolic path name | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root = A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Tree-ID = Y | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Instance-ID = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Leaf type = 5 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IPv4 address = A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IPv4 address = D | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IPv4 address = E | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ]]>

The following packet is the PCE creating the candidate path for the P2MP Policy and downloading the replication segment with the same message on the root. It should be noted combining the P2MP Policy candidate path creation and replication segment only is possible on the root. As such this message contains both association object and the CCI object. The CCI Object contains the incoming Binding SID and wraps all the Path Attribute messages and their corresponding EROs. The PLSP-ID are populated with the same ID as the previous PCC report message and the Instance-ID is assigned by the PCE.

| PLSP-ID = 1 | A:1,D:1,N:1,C:0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=17 | Length=| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | symbolic path name | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root =A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Tree-ID = Y | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Instance-ID = L1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Flags |0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Association type= SR-P2MP-PAG | Association ID = z | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv4 Association Source = | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=P2MP SR Policy ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root = A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TREE-ID = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=P2MP SR Policy Name | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ P2MP SR Policy Name ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Type=P2MP SR Pol Cand-path ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |ProtOrigin 10 | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Originator ASN | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Originator Address = | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator = 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Type=P2MP SR Pol Cand-path Name| Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ P2MP SR Policy Candidate Path Name ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Type=P2MP SR Pol Cand-Path Pre | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Preference = 100 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Leaf type = 5 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IPv4 address = A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IPv4 address = D | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IPv4 address = E | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CC-ID = X | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved1 | Flags |0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Label = 0 | Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Oper| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ERO-path Id = 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path Count = 1 | Flags |0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path ID 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=Node Role | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Role = ingress | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 1| Flags |0|0|1|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ipv4-address = NHD1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 0| Flags |0|1|0|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID = d1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Oper| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ERO-path Id = 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path Count = 0 | Flags |1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Role = ingress | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 1| Flags |0|0|1|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ipv4-address = NHD2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 0| Flags |0|1|0|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID = d2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ]]>

The following packet examples shows the replication segment initiation via a PCE on transit nodes and/or leaves node. Note: This packet is generated from PCE to instantiate the replication segment, as such the PLSP-ID is set to zero. PCC will assign these value and report them back to PCE. The instance-id was assigned by the PCE for the entire path-instance (P2MP tree) This is a replication segment instantiation as such there is no association object. The LSP Object Root A and Tree-ID Y associates this replication segment to the corresponding Candidate path and path instance on the root node. there is no association object present in the packet.

| PLSP-ID = 0 | A:1,D:1,N:1,C:0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=17 | Length=| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | symbolic path name | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root =A | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Tree-ID = Y | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Instance-ID = L1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CC-ID = X | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved1 | Flags |0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Label = d1 | Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Oper| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ERO-path Id = 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path Count = 1 | Flags |0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path ID 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Role | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 1| Flags |0|0|1|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ipv4-address = NHE1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 0| Flags |0|1|0|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID = e1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Oper| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ERO-path Id = 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Backup Path Count = 0 | Flags |1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Role | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 1| Flags |0|0|1|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ipv4-address = NHE2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type=36 | Length | NT= 0| Flags |0|1|0|0|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID = e2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ]]>

| PCECC LSP |PCC +--------+ | N=1,root-addr,tree-id=a, | SR-Policy | | | | instance-id =0, | Report to |Leaf | | | p2mp-end-points(LeafType=5)(optnl)| PCE +--------+ | | association-obj | | | | | | | |<--PCUpdate,PLSP-ID=1, SRP-ID =1, | Update | | | root-addr,tree-id=a,instance-id=b,| CP | | | p2mp-end-points, association-obj | | | | | | | |-------PCRpt,PLSP-ID=1, SRP-ID = 1,->| | | | root-addr,tree-id=a,instance-id=b,| | | | p2mp-end-points(LeafType=5) | | | | association-object | | | | | |<---------------PCInitiate,PLSP-ID=0, -------------| Download | | | root-addr,tree-id=a,instance-id=b,| Leaf | | | CC-ID=Z,C=0, | Replication | | | O=0,L=z,path-attribute,ERO,SR-ERO | Segment(RS) | | | | |---------------------PCRpt,PLSP-ID=1-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Z,Label=z,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | |<-------PCInitiate,PLSP-ID=0, -------------| Download | | | root-addr,tree-id=a,instance-id=b,| Transit | | | CC-ID=Y,C=0, | RS | | | O=0,L=y,path-attribute,ERO,SR-ERO | | | | | | |-------------PCRpt,PLSP-ID=2-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Y,Label=y,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | | |<--PCInitiate,PLSP-ID=1, | Download | | | root-addr,tree-id=a,instance-id=b,| Root | | | CC-ID=X,C=0, | RS | | | O=0,L=x,p2mp-end- | | | | points(LeafType=5),path-attribute,| | | | ERO,SR-ERO | | | | | | | |-------PCRpt,PLSP-ID=1-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=X,Label=x,O=0, | | | | p2mp-end-points(LeafType=5) | | | | path-attriute,ERO,SR-ERO | | | | | | | |<--PCUpdate,PLSP-ID=1, SRP-ID =2, | | | | root-addr,tree-id=a,instance-id=b,| Activate | | | p2mp-end-points | CP to last | | | | RS | | |-------PCRpt,PLSP-ID=1, SRP-ID =2, ->| | | | root-addr,tree-id=a,instance-id=b,| | | | p2mp-end-points(LeafType=5) | | | | | ]]> Note that on transit / leaf Initiate is with PLSP-ID = 0. Therefore PLSP-ID is locally unique to a node. It should be noted that the CC-ID does not need to be constant across all nodes that make up the path. PCE-Initiated workflow

| | | | root-addr,tree-id=a,instance-id=b,| | | | p2mp-end-points(LeafType=5) | | | | association-object, | | | | | | | |<--PCUpdt,PLSP-ID=1, | Download | | | root-addr,tree-id=a,instance-id=b,| Root RS | | | CC-ID=X,C=0, | | | | O=0,L=x,p2mp-end- | | | | points(LeafType=5),path-attribute,| | | | ERO,SR-ERO | | | | | | | |-------PCRpt,PLSP-ID=1-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=X,Label=x,O=0, | | | | p2mp-end-points(LeafType=5) | | | | path-attriute,ERO,SR-ERO | | | | | |<---------------PCInitiate,PLSP-ID=0, -------------| Download | | | root-addr,tree-id=a,instance-id=b,| Leaf RS | | | CC-ID=Z,C=0, | | | | O=0,L=z,path-attribute,ERO,SR-ERO | | | | | |---------------------PCRpt,PLSP-ID=1-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Z,Label=z,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | |<-------PCInitiate,PLSP-ID=0, -------------| Download | | | root-addr,tree-id=a,instance-id=b,| Transit RS | | | CC-ID=Y,C=0, | | | | O=0,L=y,path-attribute,ERO,SR-ERO | | | | | | |-------------PCRpt,PLSP-ID=2-------------->| | | | root-addr,tree-id=a,instance-id=c,| | | | CC-ID=Y,Label=y,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | |<-------PCInitiate,PLSP-ID=0, -------------| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Y,C=0, | | | | O=0,L=y,path-attribute,ERO,SR-ERO | | | | | | |-------------PCRpt,PLSP-ID=2-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Y,Label=y,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | | |<--PCUpdate,PLSP-ID=1, SRP-ID =1, | Bind and | | | root-addr,tree-id=a,instance-id=b,| Activate | | | p2mp-end-points, | CP to last | | | | RS | | |-------PCRpt,PLSP-ID=1, SRP-ID = 1,->| | | | root-addr,tree-id=a,instance-id=b,| | | | p2mp-end-points(LeafType=5) | ]]> MBB Workflow:

| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Z1,Label=z1,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | |<-------PCInitiate,PLSP-ID=2, -------------| Download | | | root-addr,tree-id=a,instance-id=b,| new RS on | | | CC-ID=Y1,C=0, | Transit | | | O=0,L=y1,path-attribute,ERO,SR-ERO | | | | | | |-------------PCRpt,PLSP-ID=2-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Y1,Label=y1,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | | | |<--PCInitiate,PLSP-ID=1, | Download | | | root-addr,tree-id=a,instance-id=b,| new RS on | | | CC-ID=X1,C=0, | Root | | | O=0,L=x1,p2mp-end- | | | | points(LeafType=5),path-attribute,| | | | ERO,SR-ERO | | | | | | | |-------PCRpt,PLSP-ID=1-------------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=X1,Label=x1,O=0, | | | | p2mp-end-points(LeafType=5) | | | | path-attriute,ERO,SR-ERO | | | | | | | |<--PCUpdate,PLSP-ID=1, SRP-ID =1, | Bind and | | | root-addr,tree-id=a,instance-id=b,| Activate , | | | p2mp-end-points, | CP to last | | | | RS | | |-------PCRpt,PLSP-ID=1, SRP-ID = 1,->| | | | root-addr,tree-id=a,instance-id=b,| | | | p2mp-end-points(LeafType=5) | | | | | | | |<--PCInitiate,PLSP-ID=1,R=1 | Remove | | | root-addr,tree-id=a,instance-id=b,| the old RS | | | CC-ID=X1,C=0 | from Leaf | | | O=0,L=x1,p2mp-end- | | | | points(LeafType=5),path-attribute,| | | | ERO,SR-ERO | | | | | | | |-------PCRpt,PLSP-ID=1, R=1--------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=X1,Label=x1,O=0, | | | | p2mp-end-points(LeafType=5) | | | | path-attriute,ERO,SR-ERO | | | | | | |<-------PCInitiate,PLSP-ID=2, R=1----------| Remove the | | | root-addr,tree-id=a,instance-id=b,| old RS from | | | CC-ID=Y1,C=0, | Transit | | | O=0,L=y1,path-attribute,ERO,SR-ERO | | | | | | |-------------PCRpt,PLSP-ID=2, R=1--------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Y1,Label=y1,O=0, | | | | path-attribute,ERO,SR-ERO | | | | | |<---------------PCInitiate,PLSP-ID=1,R=1-----------| Remove the | | | root-addr,tree-id=a,instance-id=b,| old RS from | | | CC-ID=Z1,C=0, | Root | | | O=0,L=z1,path-attribute,ERO,SR-ERO | | | | | |---------------------PCRpt,PLSP-ID=1,R=1---------->| | | | root-addr,tree-id=a,instance-id=b,| | | | CC-ID=Z1,Label=z1,O=0, | | | | path-attribute,ERO,SR-ERO | ]]>

This draft defines a new Association type for P2MP SR Policy. IANA is requested to allocate a new value from the existing IANA Registry "ASSOCIATION TYPE FIELD".

This draft defines a new leaf-type for RFC8306 "P2MP- END-POINTS" object. IANA is requested to allocate a new value from the existing IANA Registry "Generalized Endpoint Types" The Authors are requesting value 5 for this new endpoint type.

This draft extends the PCEP OPEN object by defining a new optional TLV to indicate the PCE's capability to perform SR-P2MP path computation. IANA is requested to allocate a new value from the IANA Registry "PCEP TLV Type Indicators"

This draft defines two new TLVs for Identifying the P2MP Policy and the Replication segment with IPv4 or IPv6 root address. IANA is requested to allocate two new values from the IANA Registry "PCEP TLV Type Indicators"

This draft defines a new CCI Object type SR P2MP Policy. IANA is requested to allocate a new CCI Object type from the "CCI Object-Type" Class

TBD

The authors would like to thank Tanmoy Kundu and Stone Andrew at Nokia and Tarek Saad at Cisco for their feedback and major contribution to this draft.