<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.perlman-trill-rbridge-data-encoding" target="https://datatracker.ietf.org/doc/html/draft-perlman-trill-rbridge-data-encoding-10">
   <front>
      <title>RBridges: TRILL Link Data Optimizations</title>
      <author initials="R." surname="Perlman" fullname="Radia Perlman">
         <organization>EMC</organization>
      </author>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         <organization>Futurewei Technologies</organization>
      </author>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="A." surname="Ghanwani" fullname="Anoop Ghanwani">
         <organization>Dell</organization>
      </author>
      <date month="May" day="1" year="2023" />
      <abstract>
	 <t>   TRILL (TRansparent Interconnection of Lots of Links) Data frames can
   be encoded so as to make more efficient use of communications links
   under certain circumstances.  This document specifies two such
   optional optimizations.  One, called Compact Format, improves the
   compactness of encoding where a TRILL link is a point-to-point
   Ethernet link.  The other, called Specific Addressing, optionally
   decreases the burden on multi-access TRILL links for multi-
   destination TRILL Data frames.  This document updates RFC 6325.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-perlman-trill-rbridge-data-encoding-10" />
   
</reference>
