RFC 7782: Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments
In plain English — editorial summary, not part of the RFC
TRILL (Transparent Interconnection of Lots of Links) active-active service provides end stations with flow-level load balance and resilience against link failures at the edge of TRILL campuses, as described in RFC 7379. This document specifies a method by which member RBridges (also referred to as Routing Bridges or TRILL switches) in an active-active edge RBridge group use their own nicknames as ingress RBridge nicknames to encapsulate frames from attached end systems. Thus, remote edge RBridges (who are not in the group) will see one host Media Access Control (MAC) address being associated with the multiple RBridges in the group. Such remote edge RBridges are required to maintain all those associations (i.e., MAC attachments) and to not flip-flop among them (as would occur prior to the implementation of this specification). The design goals of this specification are discussed herein.
Document record
- Document ID
- RFC7782
- Published
- February 2016
- Authors
- M. Zhang; R. Perlman; H. Zhai; M. Durrani; S. Gupta
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- RFC 7781Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active AccessCurrent
February 2016
- RFC 7783Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL)Current
February 2016
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7784Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIBCurrent
February 2016
- RFC 7779Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2)Current
April 2016
- RFC 7777Advertising Node Administrative Tags in OSPFCurrent
March 2016
- RFC 7775IS-IS Route Preference for Extended IP and IPv6 ReachabilityCurrent
February 2016
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?