Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension
RFC 7978
| Document | Type |
RFC - Proposed Standard
(September 2016; No errata)
Updates RFC 7178
|
|
|---|---|---|---|
| Authors | Donald Eastlake , Mohammed Umair , Li Yizhou | ||
| Last updated | 2016-09-30 | ||
| Replaces | draft-eastlake-trill-channel-tunnel | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Susan Hares | ||
| Shepherd write-up | Show (last changed 2016-02-08) | ||
| IESG | IESG state | RFC 7978 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alia Atlas | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 7978 Huawei
Updates: 7178 M. Umair
Category: Standards Track IPinfusion
ISSN: 2070-1721 Y. Li
Huawei
September 2016
Transparent Interconnection of Lots of Links (TRILL):
RBridge Channel Header Extension
Abstract
The IETF TRILL (Transparent Interconnection of Lots of Links)
protocol includes an optional mechanism (specified in RFC 7178)
called RBridge Channel for the transmission of typed messages between
TRILL switches in the same campus and the transmission of such
messages between TRILL switches and end stations on the same link.
This document specifies extensions to the RBridge Channel protocol
header to support two features as follows: (1) a standard method to
tunnel payloads whose type can be indicated by Ethertype through
encapsulation in RBridge Channel messages; and (2) a method to
support security facilities for RBridge Channel messages. This
document updates RFC 7178.
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
http://www.rfc-editor.org/info/rfc7978.
Eastlake, et al. Standards Track [Page 1]
RFC 7978 TRILL: RBridge Channel Extension September 2016
Copyright Notice
Copyright (c) 2016 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
(http://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.
Eastlake, et al. Standards Track [Page 2]
RFC 7978 TRILL: RBridge Channel Extension September 2016
Table of Contents
1. Introduction ....................................................4
1.1. Terminology and Acronyms ...................................4
2. RBridge Channel Header Extension Format .........................5
3. Extended RBridge Channel Payload Types ..........................8
3.1. Null Payload ...............................................8
3.2. Ethertyped Payload .........................................9
3.2.1. RBridge Channel Message as the Payload ..............9
3.2.2. TRILL Data Packet as the Payload ...................10
3.2.3. TRILL IS-IS Packet as the Payload ..................10
3.3. Ethernet Frame ............................................11
4. Extended RBridge Channel Security ..............................13
4.1. Derived Keying Material ...................................14
4.2. SType None ................................................14
4.3. IS-IS CRYPTO_AUTH-Based Authentication ....................15
4.4. DTLS Pairwise Security ....................................17
4.5. Composite Security ........................................18
5. Extended RBridge Channel Errors ................................18
5.1. SubERRs ...................................................19
5.2. Secure Nested RBridge Channel Errors ......................19
6. IANA Considerations ............................................19
6.1. Extended RBridge Channel Protocol Number ..................19
6.2. RBridge Channel Protocol Subregistries ....................20
6.2.1. RBridge Channel Error Codes ........................20
6.2.2. RBridge Channel SubError Codes .....................20
6.2.3. Extended RBridge Channel Payload Types
Subregistry ........................................20
6.2.4. Extended RBridge Channel Security Types
Subregistry ........................................21
Show full document text