RFC 7379: Problem Statement and Goals for Active-Active Connection at the Transparent Interconnection of Lots of Links (TRILL) Edge
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 with rapid failover for both unicast and multi-destination traffic in networks with arbitrary topology. Active-active connection at the TRILL edge is the extension of these characteristics to end stations that are multiply connected to a TRILL campus. This informational document discusses the high-level problems and goals when providing active-active connection at the TRILL edge.
Document record
- Document ID
- RFC7379
- Published
- October 2014
- Authors
- Y. Li; W. Hao; R. Perlman; J. Hudson; H. Zhai
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7382Template for a Certification Practice Statement (CPS) for the Resource PKI (RPKI)Current
April 2015
- RFC 7385IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code PointsUpdated
October 2014
- RFC 7387A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) NetworkCurrent
October 2014
- RFC 7370Updates to the IS-IS TLV Codepoints RegistryUpdated
September 2014
- RFC 7369GMPLS RSVP-TE Extensions for Ethernet Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
October 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 7392Explicit Path Routing for Dynamic Multi-Segment PseudowiresCurrent
December 2014
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?