%% You should probably cite draft-ietf-trill-clear-correct instead of this I-D.
@techreport{eastlake-trill-rbridge-clear-correct-03,
    number =    {draft-eastlake-trill-rbridge-clear-correct-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-eastlake-trill-rbridge-clear-correct/03/},
    author =    {Donald E. Eastlake 3rd and Mingui Zhang and Anoop Ghanwani and Ayan Banerjee and Vishwas Manral},
    title =     {{TRILL: Clarifications, Corrections, and Updates}},
    pagetotal = 29,
    year =      2012,
    month =     jan,
    day =       8,
    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 topology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Since the TRILL base protocol was approved in March 2010, active development of TRILL has revealed a few errata in the original RFC 6325 and some cases that could use clarifications or updates. RFCs 6327, RFC 6439, and RFC XXXX, provide clarifications with respect to Adjacency, Appointed Forwarders, and the TRILL ESADI protocol. This document provide other known clarifications, corrections, and updates to RFCs 6325, 6327, and 6439.},
}