<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-trill-channel-tunnel" target="https://datatracker.ietf.org/doc/html/draft-ietf-trill-channel-tunnel-06">
   <front>
      <title>TRILL: RBridge Channel Tunnel Protocol</title>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         </author>
      <author initials="M." surname="Umair" fullname="Mohammed Umair">
         </author>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         </author>
      <date month="June" day="15" year="2015" />
      <abstract>
	 <t>   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol includes an optional mechanism, called RBridge Channel, that
   is specified in RFC 7178, for the transmission of typed messages
   between TRILL switches in the same campus and between TRILL switches
   and end stations on the same link. This document specifies two
   optional extensions to the RBridge Channel protocol: (1) A standard
   method to tunnel a variety of payload types by encapsulating them in
   an RBridge Channel message; and (2) A method to support security
   facilities for RBridge Channel messages. This document updates RFC
   7178.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-trill-channel-tunnel-06" />
   
</reference>
