RFC 8385: Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLS
In plain English — editorial summary, not part of the RFC
This document specifies methods to interconnect multiple TRILL (Transparent Interconnection of Lots of Links) sites with an intervening MPLS network using existing TRILL and VPLS (Virtual Private LAN Service) standards. This document addresses two problems: 1) providing connection between more than two TRILL sites that are separated by an MPLS provider network and 2) providing a single logical virtualized TRILL network for different tenants that are separated by an MPLS provider network.
Document record
- Document ID
- RFC8385
- Published
- June 2018
- Authors
- M. Umair; S. Kingston Smiler; D. Eastlake 3rd; L. Yong
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 7152Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)Current
March 2014
- RFC 6718Pseudowire RedundancyCurrent
August 2012
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 4665Service Requirements for Layer 2 Provider-Provisioned Virtual Private NetworksCurrent
September 2006
- RFC 8384Transparent Interconnection of Lots of Links (TRILL) Smart EndnodesCurrent
July 2018
- RFC 8383Transparent Interconnection of Lots of Links (TRILL): Address Flush MessageCurrent
May 2018
- RFC 8388Usage and Applicability of BGP MPLS-Based Ethernet VPNCurrent
May 2018
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?