TRILL: Vendor Specific TRILL Channel Protocol
draft-eastlake-trill-vendor-channel-04
Document | Type |
Replaced Internet-Draft
(candidate for trill WG)
Expired & archived
|
|
---|---|---|---|
Authors | Donald E. Eastlake 3rd , Yizhou Li , Hao Weiguo , Ayan Banerjee | ||
Last updated | 2018-01-14 | ||
Replaced by | draft-ietf-trill-vendor-channel | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-trill-vendor-channel | |
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 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 a method 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.)