TRILL: Vendor Specific TRILL Channel Protocol
draft-eastlake-trill-vendor-channel-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Donald E. Eastlake 3rd , Yizhou Li , Hao Weiguo , Ayan Banerjee | ||
| Last updated | 2014-03-03 (Latest revision 2013-08-19) | ||
| Replaced by | draft-ietf-trill-vendor-channel, draft-ietf-trill-vendor-channel | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 is implemented by devices called TRILL switches or RBridges (Routing Bridges). TRILL includes a general mechanism, called 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 how to send vendor specific messages over the RBridge Channel facility.
Authors
Donald E. Eastlake 3rd
Yizhou Li
Hao Weiguo
Ayan Banerjee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)