<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-bgp-multicast-controller" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-multicast-controller-06">
   <front>
      <title>Controller Based BGP Multicast Signaling</title>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="R." surname="Raszuk" fullname="Robert Raszuk">
         <organization>NTT Network Innovations</organization>
      </author>
      <author initials="D." surname="Pacella" fullname="Dante Pacella">
         <organization>Verizon</organization>
      </author>
      <author initials="A." surname="Gulko" fullname="Arkadiy Gulko">
         <organization>Edward Jones Wealth Management</organization>
      </author>
      <date month="February" day="19" year="2021" />
      <abstract>
	 <t>   This document specifies a way that one or more centralized
   controllers can use BGP to set up a multicast distribution tree in a
   network.  In the case of labeled tree, the labels are assigned by the
   controllers either from the controllers&#x27; local label spaces, or from
   a common Segment Routing Global Block (SRGB), or from each routers
   Segment Routing Local Block (SRLB) that the controllers learn.  In
   case of labeled unidirectional tree and label allocation from the
   common SRGB or from the controllers&#x27; local spaces, a single common
   label can be used for all routers on the tree to send and receive
   traffic with.  Since the controllers calculate the trees, they can
   use sophisticated algorithms and constraints to achieve traffic
   engineering.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-bgp-multicast-controller-06" />
   
</reference>
