TRILL: RBridge Channel Tunnel Protocol
draft-ietf-trill-channel-tunnel-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (trill WG)
Last updated 2014-12-04 (latest revision 2014-06-02)
Replaces draft-eastlake-trill-channel-tunnel
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-trill-channel-tunnel-01.txt

Abstract

The IETF TRILL (Transparent Interconnection of Lots of Links) protocol includes an optional mechanism, called RBridge Channel and 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 optional extensions to RBridge Channel that provides three facilities: (1) A mechanism to send such messages between a TRILL switch and an end station in either direction, or between two end stations, when the two devices are in the same campus but not on the same link; (2) A method to support security facilities for RBridge Channel messages; and (3) A method to tunnel a variety of payload types by encapsulating them in an RBridge Channel message. This document updates RFC 7178.

Authors

Donald Eastlake (d3e3e3@gmail.com)
Li Yizhou (liyizhou@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)