%% You should probably cite draft-ietf-bess-bgp-multicast-controller-12 instead of this revision. @techreport{ietf-bess-bgp-multicast-controller-01, number = {draft-ietf-bess-bgp-multicast-controller-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-multicast-controller/01/}, author = {Zhaohui (Jeffrey) Zhang and Robert Raszuk and Dante Pacella and Arkadiy Gulko}, title = {{Controller Based BGP Multicast Signaling}}, pagetotal = 13, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {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' 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' 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.}, }