%% You should probably cite rfc9960 instead of this I-D.
@techreport{ietf-pim-sr-p2mp-policy-17,
    number =    {draft-ietf-pim-sr-p2mp-policy-17},
    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-pim-sr-p2mp-policy/17/},
    author =    {Rishabh Parekh (editor) and Daniel Voyer and Clarence Filsfils and Hooman Bidgoli and Zhaohui (Jeffrey) Zhang},
    title =     {{Segment Routing Point-to-Multipoint Policy}},
    pagetotal = 22,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Point-to-Multipoint (P2MP) policy enables creation of P2MP trees for efficient multi-point packet delivery in a Segment Routing (SR) domain. A SR P2MP Policy consists of Candidate Paths (CP) which define the topology of P2MP tree instances of the Candidate Paths. A P2MP tree instance is instantiated by a set of Replication segments. This document specifies the architecture, signaling, and procedures for SR P2MP Policies within Segment Routing over MPLS (SR-MPLS) and Segment Routing over IPv6 (SRv6). It defines the P2MP Policy construct, the roles of the root and leaf nodes, Candidate Paths and how P2MP trees using Replication segments are instantiated and maintained. Additionally, it describes the required extensions for a controller to support P2MP path computation and provisioning.},
}