%% You should probably cite rfc8317 instead of this I-D.
@techreport{ietf-bess-evpn-etree-13,
    number =    {draft-ietf-bess-evpn-etree-13},
    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-bess-evpn-etree/13/},
    author =    {Ali Sajassi and Samer Salam and John Drake and Jim Uttaro and Sami Boutros and Jorge Rabadan},
    title =     {{E-TREE Support in EVPN \& PBB-EVPN}},
    pagetotal = 22,
    year =      2017,
    month =     aug,
    day =       29,
    abstract =  {The Metro Ethernet 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 RFC7432, BGP MPLS Based Ethernet VPN (EVPN), with some extensions and how such a solution can offer a more efficient implementation of these functions than that of RFC7796, E-Tree Support in Virtual Private LAN Service (VPLS). This document makes use of the most significant bit of the "Tunnel Type" field (in PMSI Tunnel Attribute) governed by the IANA registry created by RFC7385, and hence updates RFC7385 accordingly.},
}