TRILL: Vendor Specific TRILL Channel Protocol
draft-eastlake-trill-vendor-channel-04

Document Type Replaced Internet-Draft (candidate for trill WG)
Last updated 2018-01-14
Replaced by draft-ietf-trill-vendor-channel
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-trill-vendor-channel
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-eastlake-trill-vendor-channel-04.txt

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 Eastlake (d3e3e3@gmail.com)
Li Yizhou (liyizhou@huawei.com)
Hao Weiguo (haoweiguo@huawei.com)
Ayan Banerjee (ayabaner@cisco.com)

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