RFC 7978: Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7978
- Published
- September 2016
- Authors
- D. Eastlake 3rd; M. Umair; Y. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
- Updates:
- RFC 7178
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 5512The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation AttributeObsoleted
April 2009
- RFC 2637Point-to-Point Tunneling Protocol (PPTP)Current
July 1999
- RFC 8926Geneve: Generic Network Virtualization EncapsulationCurrent
November 2020
- RFC 9638Network Virtualization over Layer 3 (NVO3) Encapsulation ConsiderationsCurrent
September 2024
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?