%% You should probably cite draft-ietf-trill-esadi instead of this I-D.
@techreport{hu-trill-rbridge-esadi-04,
    number =    {draft-hu-trill-rbridge-esadi-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hu-trill-rbridge-esadi/04/},
    author =    {Hongjun Zhai and fangwei hu and Radia Perlman and Donald E. Eastlake 3rd},
    title =     {{TRILL: The ESADI Protocol}},
    pagetotal = 19,
    year =      2012,
    month =     apr,
    day =       11,
    abstract =  {The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides least cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topologies and link technologies. TRILL supports the multi-pathing of both unicast and multicast traffic. Devices that implement the TRILL protocol are called RBridges (Routing Bridges) or TRILL Switches. The ESADI (End System Address Distribution Information) protocol is a VLAN (Virtual Local Area Network) scoped way that TRILL switches can communicate end station addresses to each other. An RBridge announcing VLAN-x connectivity (normally a VLAN-x appointed forwarder) and running the TRILL ESADI protocol can receive remote address information and/or transmit local address information for VLAN-x to other such RBridges. This document updates RFC 6325, specifically the documentation of the ESADI protocol.},
}