Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol
RFC 8381
|
| Document |
Type |
|
RFC - Proposed Standard
(May 2018; No errata)
|
|
Last updated |
|
2018-05-21
|
|
Replaces |
|
draft-eastlake-trill-vendor-channel
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Susan Hares
|
|
Shepherd write-up |
|
Show
(last changed 2018-02-20)
|
| IESG |
IESG state |
|
RFC 8381 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alia Atlas
|
|
Send notices to |
|
Susan Hares <shares@ndzh.com>
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 8381 Y. Li
Category: Standards Track W. Hao
ISSN: 2070-1721 Huawei
A. Banerjee
Cisco
May 2018
Transparent Interconnection of Lots of Links (TRILL):
Vendor-Specific RBridge Channel Protocol
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 an
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8381.
Eastlake, et al. Standards Track [Page 1]
RFC 8381 TRILL: Vendor Channel May 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
1.1. Terminology and Acronyms ...................................3
2. Vendor Channel Packet Format ....................................3
3. Vendor Channel Errors ...........................................6
3.1. Sending an Error Response ..................................7
4. IANA Considerations .............................................9
5. Security Considerations .........................................9
6. References .....................................................10
6.1. Normative References ......................................10
6.2. Informative References ....................................10
Authors' Addresses ................................................11
1. Introduction
The IETF TRILL (Transparent Interconnection of Lots of Links)
protocol [RFC6325] [RFC7780] is implemented by devices called TRILL
switches or RBridges (Routing Bridges). It provides efficient least-
cost transparent routing in multi-hop networks with arbitrary
topologies and link technologies, using link-state routing and a hop
count.
The TRILL protocol includes an RBridge Channel facility [RFC7178] to
support typed message transmission between RBridges in the same
campus and between RBridges and end stations on the same link. This
document specifies a method of sending messages specified by a
particular organization, indicated by OUI (Organizationally Unique
Identifier) [RFC7042] or CID (Company Identifier) [802], over the
RBridge Channel facility. Such organization-specific messages could,
for example, be used for vendor-specific diagnostic or control
messages.
Eastlake, et al. Standards Track [Page 2]
RFC 8381 TRILL: Vendor Channel May 2018
However, note that a range of RBridge Channel protocol numbers are
available based on RFC publication. Those intending to use the
RBridge Channel facility are encouraged to document their use in an
RFC and to use RBridge Channel protocol numbers based on such RFC
publication.
1.1. Terminology and Acronyms
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
Show full document text