%% You should probably cite draft-eastlake-trill-link-security-06 instead of this revision.
@techreport{eastlake-trill-link-security-03,
    number =    {draft-eastlake-trill-link-security-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-link-security/03/},
    author =    {Donald E. Eastlake 3rd and Dacheng Zhang},
    title =     {{TRILL: Link Security}},
    pagetotal = 20,
    year =      2016,
    month =     apr,
    day =       12,
    abstract =  {The TRILL protocol supports arbitrary link technologies between TRILL switches, both point-to-point and broadcast links, and supports Ethernet links between edge TRILL switches and end stations. Communications links are constantly under attack by criminals and national intelligence agencies as discussed in RFC 7258. Link security is an important element of security in depth, particularly for links that are not entirely under the physical control of the TRILL network operator or that include device which may have been compromised. This document specifies link security recommendations for TRILL over Ethernet, PPP, and pseudowire links. It updates RFC 6325, RFC 6361, and RFC 7173. It requires that link encryption MUST be implemented and that all TRILL Data packets between TRILL switch ports capable of encryption at line speed MUST default to being encrypted. {[}This is a early partial draft.{]}},
}