RFC 8171: Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance Mechanisms
In plain English — editorial summary, not part of the RFC
This document describes mechanisms for providing directory service to TRILL (Transparent Interconnection of Lots of Links) edge switches. The directory information provided can be used in reducing multi-destination traffic, particularly ARP / Neighbor Discovery (ND) and unknown unicast flooding. It can also be used to detect traffic with forged source addresses.
Document record
- Document ID
- RFC8171
- Published
- June 2017
- Authors
- D. Eastlake 3rd; L. Dunbar; R. Perlman; Y. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 55
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 7357Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) ProtocolCurrent
September 2014
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8297An HTTP Status Code for Indicating HintsCurrent
December 2017
- RFC 8030Generic Event Delivery Using HTTP PushCurrent
December 2016
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 8765DNS Push NotificationsCurrent
June 2020
- RFC 8169Residence Time Measurement in MPLS NetworksCurrent
May 2017
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?