%% You should probably cite draft-sajassi-bess-rfc8317bis-03 instead of this revision.
@techreport{sajassi-bess-rfc8317bis-00,
    number =    {draft-sajassi-bess-rfc8317bis-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-sajassi-bess-rfc8317bis/00/},
    author =    {Ali Sajassi and Jorge Rabadan and John Drake and Arivudainambi Appachi Gounder and Aaron Bamberger},
    title =     {{Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)}},
    pagetotal = 29,
    year =      2023,
    month =     apr,
    day =       1,
    abstract =  {The MEF Forum (MEF) has defined a rooted-multipoint Ethernet service known as Ethernet-Tree (E-Tree). A solution framework for supporting this service in MPLS networks is described in {[}RFC7387{]}, "A Framework for Ethernet-Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network". This document discusses how those functional requirements can be met with a solution based on RFC 7432, "BGP MPLS Based Ethernet VPN (EVPN)", with some extensions and a description of how such a solution can offer a more efficient implementation of these functions than that of {[}RFC7796{]}, "Ethernet- Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)". This document makes use of the most significant bit of the Tunnel Type field (in the P-Multicast Service Interface (PMSI) Tunnel attribute) governed by the IANA registry created by {[}RFC7385{]}; hence, it updates {[}RFC7385{]} accordingly.},
}