<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bier-pim-signaling" target="https://datatracker.ietf.org/doc/html/draft-ietf-bier-pim-signaling-13">
   <front>
      <title>PIM Signaling Through BIER Core</title>
      <author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
         <organization>Nokia</organization>
      </author>
      <author initials="F." surname="Xu" fullname="Fengman Xu">
         <organization>Verizon</organization>
      </author>
      <author initials="J." surname="Kotalwar" fullname="Jayant Kotalwar">
         <organization>Nokia</organization>
      </author>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         <organization>Cisco System</organization>
      </author>
      <author initials="M. P." surname="Mishra" fullname="Mankamana Prasad Mishra">
         <organization>Cisco System</organization>
      </author>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <date month="March" day="3" year="2025" />
      <abstract>
	 <t>   Consider large networks deploying traditional PIM multicast service.
   Typically, each portion of these large networks have their own
   mandates and requirements.  It might be desirable to deploy BIER
   technology in some part of these networks to replace traditional PIM
   services.  In such cases downstream PIM states need to be signaled
   over the BIER Domain toward the source.

   This document specifies the procedures to signal PIM Join and Prune
   messages through a BIER Domain using [RFC9739] , enabling the
   provisioning of traditional PIM services through a BIER Domain.
   These procedures are valid for forwarding PIM Join/Prune messages to
   the Source (SSM) or Rendezvous Point (ASM).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bier-pim-signaling-13" />
   
</reference>
