%% You should probably cite draft-ietf-trill-rbridge-af instead of this I-D.
@techreport{perlman-trill-rbridge-af-00,
    number =    {draft-perlman-trill-rbridge-af-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-perlman-trill-rbridge-af/00/},
    author =    {Radia Perlman and Donald E. Eastlake 3rd and Ayan Banerjee and fangwei hu},
    title =     {{RBridges: Appointed Forwarders}},
    pagetotal = 17,
    year =      2011,
    month =     mar,
    day =       29,
    abstract =  {The IETF TRILL protocol provides optimal pair-wise data forwarding without configuration, 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 link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called RBridges. TRILL supports multi-access LAN links that can have multiple end stations and RBridges attached. Where multiple RBridges are attached to a link, native traffic to and from end stations on that link is handled by a subset of those RBridges called Appointed Forwarders, with the intent that native traffic in each VLAN be handled by at most one RBridge. The purpose of this document is to improve the documentation of the Appointed Forwarder mechanism.},
}