RFC 7781: Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active Access
In plain English — editorial summary, not part of the RFC
The IETF TRILL (Transparent Interconnection of Lots of Links) protocol provides support for flow-level multipathing for both unicast and multi-destination traffic in networks with arbitrary topology. Active-active access at the TRILL edge is the extension of these characteristics to end stations that are multiply connected to a TRILL campus as discussed in RFC 7379. In this document, the edge RBridge (Routing Bridge, or TRILL switch) group providing active-active access to such an end station is represented as a virtual RBridge. Based on the concept of the virtual RBridge, along with its pseudo-nickname, this document specifies a method for TRILL active-active access by such end stations.
Document record
- Document ID
- RFC7781
- Published
- February 2016
- Authors
- H. Zhai; T. Senevirathne; R. Perlman; M. Zhang; Y. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7926Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered NetworksCurrent
July 2016
- RFC 6472Recommendation for Not Using AS_SET and AS_CONFED_SET in BGPObsoleted
December 2011
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 6769Simple Virtual Aggregation (S-VA)Current
October 2012
- RFC 6768ATM-Based xDSL Bonded Interfaces MIBCurrent
February 2013
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
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?