RFC 8384: Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes
In plain English — editorial summary, not part of the RFC
This document addresses the problem of the size and freshness of the endnode learning table in edge Routing Bridges (RBridges), by allowing endnodes to volunteer for endnode learning and encapsulation/decapsulation. Such an endnode is known as a "Smart Endnode". Only the attached edge RBridge can distinguish a "Smart Endnode" from a "normal endnode". The Smart Endnode uses the nickname of the attached edge RBridge, so this solution does not consume extra nicknames. The solution also enables endnodes that are Fine-Grained Label (FGL) aware.
Document record
- Document ID
- RFC8384
- Published
- July 2018
- Authors
- R. Perlman; F. Hu; D. Eastlake 3rd; T. Liao
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- 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 8139Transparent Interconnection of Lots of Links (TRILL): Appointed ForwardersCurrent
June 2017
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- RFC 7178Transparent Interconnection of Lots of Links (TRILL): RBridge Channel SupportUpdated
May 2014
- RFC 7177Transparent Interconnection of Lots of Links (TRILL): AdjacencyUpdated
May 2014
- RFC 7173Transparent Interconnection of Lots of Links (TRILL) Transport Using PseudowiresCurrent
May 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?