%% You should probably cite draft-ietf-bier-pim-signaling-12 instead of this revision. @techreport{ietf-bier-pim-signaling-00, number = {draft-ietf-bier-pim-signaling-00}, 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-bier-pim-signaling/00/}, author = {Hooman Bidgoli and Andrew Dolganow and Jayant Kotalwar and Fengman Xu and IJsbrand Wijnands and Mankamana Prasad Mishra}, title = {{PIM Signaling Through BIER Core}}, pagetotal = 12, year = 2018, month = feb, day = 23, abstract = {Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. Neither does BIER require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. Such header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the according set of bits switched on in BIER packet header. This document describes the procedure needed for PIM Joins and Prunes to be signaled through a BIER core. Allowing PIM routers to run traditional PIM multicast services through a BIER core.}, }