%% You should probably cite rfc6327 instead of this I-D.
@techreport{ietf-trill-adj-07,
    number =    {draft-ietf-trill-adj-07},
    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-trill-adj/07/},
    author =    {Radia Perlman and Anoop Ghanwani and Vishwas Manral and Dinesh G. Dutt and Donald E. Eastlake 3rd},
    title =     {{Routing Bridges (RBridges): Adjacency}},
    pagetotal = 26,
    year =      2011,
    month =     apr,
    day =       29,
    abstract =  {The IETF TRILL (TRansparent Interconnection of Lots of Links) 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 (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called Routing Bridges (RBridges). TRILL supports multi-access LAN (Local Area Network) links that can have multiple end stations and RBridges attached. This document describes four aspects of the TRILL LAN Hello protocol used on such links, particularly adjacency, designated RBridge selection, and MTU (Maximum Transmission Unit) and pseudonode procedures, with state machines. There is no change for IS-IS point-to-point Hellos used on links configured as point-to-point in TRILL. {[}STANDARDS-TRACK{]}},
}