TRILL: RBridge Channel Tunnel Protocol
draft-eastlake-trill-channel-tunnel-00
| Document | Type |
Replaced Internet-Draft
(trill WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Donald E. Eastlake 3rd , Yizhou Li | ||
| Last updated | 2013-11-13 (Latest revision 2013-10-21) | ||
| Replaced by | draft-ietf-trill-channel-tunnel | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-trill-channel-tunnel | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The IETF TRILL (Transparent Interconnection of Lots of Links) protocol includes an optional mechanism, called RBridge Channel, 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.
Authors
Donald E. Eastlake 3rd
Yizhou Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)