RFC 8383: Transparent Interconnection of Lots of Links (TRILL): Address Flush Message
In plain English — editorial summary, not part of the RFC
The TRILL (Transparent Interconnection of Lots of Links) protocol, by default, learns end station addresses from observing the data plane. In particular, it learns local Media Access Control (MAC) addresses and the edge switch port of attachment from the receipt of local data frames and learns remote MAC addresses and the edge switch port of attachment from the decapsulation of remotely sourced TRILL Data packets. This document specifies a message by which a TRILL switch can explicitly request other TRILL switches to flush certain MAC reachability learned through the decapsulation of TRILL Data packets. This is a supplement to the TRILL automatic address forgetting (see Section 4.8.3 of RFC 6325) and can assist in achieving more rapid convergence in case of topology or configuration change.
Document record
- Document ID
- RFC8383
- Published
- May 2018
- Authors
- W. Hao; D. Eastlake 3rd; Y. Li; M. Umair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8355Resiliency Use Cases in Source Packet Routing in Networking (SPRING) NetworksCurrent
March 2018
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7176Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISCurrent
May 2014
- RFC 7172Transparent Interconnection of Lots of Links (TRILL): Fine-Grained LabelingCurrent
May 2014
- RFC 9722Fast Recovery for EVPN Designated Forwarder ElectionCurrent
May 2025
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 4719Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3)Updated
November 2006
- RFC 8384Transparent Interconnection of Lots of Links (TRILL) Smart EndnodesCurrent
July 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?