@misc{rfc8317,
    series =    {Request for Comments},
    number =    8317,
    howpublished =  {RFC 8317},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8317},
    url =       {https://www.rfc-editor.org/info/rfc8317},
    author =    {Ali Sajassi and Samer Salam and John Drake and Jim Uttaro and Sami Boutros and Jorge Rabadan},
    title =     {{Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)}},
    pagetotal = 23,
    year =      2018,
    month =     jan,
    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 RFC 7387, "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 RFC 7796, "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 RFC 7385; hence, it updates RFC 7385 accordingly.},
}