<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-trill-vendor-channel" target="https://datatracker.ietf.org/doc/html/draft-ietf-trill-vendor-channel-01">
   <front>
      <title>Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol</title>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         <organization>Huawei</organization>
      </author>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei</organization>
      </author>
      <author initials="H." surname="Weiguo" fullname="Hao Weiguo">
         <organization>Huawei</organization>
      </author>
      <author initials="A." surname="Banerjee" fullname="Ayan Banerjee">
         <organization>Cisco</organization>
      </author>
      <date month="March" day="9" year="2018" />
      <abstract>
	 <t>The IETF TRILL (Transparent Interconnection of Lots of Links) protocol is implemented by devices called TRILL switches or RBridges (Routing Bridges).  TRILL includes a general mechanism, called an RBridge Channel, for the transmission of typed messages between RBridges in the same campus and between RBridges and end stations on the same link.  This document specifies a method to send vendor-specific messages over the RBridge Channel facility.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-trill-vendor-channel-01" />
   
</reference>
