<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-sr-p2mp-policy" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-p2mp-policy-00">
   <front>
      <title>Advertising p2mp policies in BGP</title>
      <author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
         <organization>Nokia</organization>
      </author>
      <author initials="D." surname="Voyer" fullname="Daniel Voyer">
         <organization>Bell Canada</organization>
      </author>
      <author initials="A." surname="Stone" fullname="Andrew Stone">
         <organization>Nokia</organization>
      </author>
      <author initials="R." surname="Parekh" fullname="Rishabh Parekh">
         <organization>Cisco System, Inc.</organization>
      </author>
      <author initials="S." surname="Krier" fullname="Serge Krier">
         <organization>Cisco System, Inc.</organization>
      </author>
      <author initials="S." surname="Agrawal" fullname="Swadesh Agrawal">
         <organization>Cisco System, Inc.</organization>
      </author>
      <date month="May" day="27" year="2022" />
      <abstract>
	 <t>   SR P2MP policies are set of policies that enable architecture for
   P2MP service delivery.

   A P2MP policy consists of candidate paths that connects the Root of
   the Tree to a set of Leaves.  The P2MP policy is composed of
   replication segments.  A replication segment is a forwarding
   instruction for a candidate path which is downloaded to the Root,
   transit nodes and the leaves.

   This document specifies a new BGP SAFI with a new NLRI in order to
   advertise P2MP policy from a controller to a set of nodes.

   This document introduces three new route types within this NLRI, one
   for P2MP policy and its candidate paths that need to be programmed on
   the Root node, one for the replication segment incoming SID which
   uniquely will identify the cross connect and another for each
   outgoing interface that the packets get replicated to.  The last two
   route types are forwarding instructions that needs to be programmed
   on the Root, and optionally on Transit and Leaf nodes.

   It should be noted that this document does not specify how the Root
   and the Leaves are discovered on the controller, it only describes
   how the P2MP Policy and Replication Segments are programmed from the
   controller to the nodes.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-sr-p2mp-policy-00" />
   
</reference>
