RFC 7968: Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination Data
In plain English — editorial summary, not part of the RFC
TRILL (Transparent Interconnection of Lots of Links) uses distribution trees to deliver multi-destination frames. Multiple trees can be used by an ingress Routing Bridge (RBridge) for flows, regardless of the VLAN, Fine-Grained Label (FGL), and/or multicast group of the flow. Different ingress RBridges may choose different distribution trees for TRILL Data packets in the same VLAN, FGL, and/or multicast group. To avoid unnecessary link utilization, distribution trees should be pruned based on one or more of the following: VLAN, FGL, or multicast destination address. If any VLAN, FGL, or multicast group can be sent on any tree, for typical fast-path hardware, the amount of pruning information is multiplied by the number of trees, but there is limited hardware capacity for such pruning information. This document specifies an optional facility to restrict the TRILL Data packets sent on particular distribution trees by VLAN, FGL, and/or multicast groups, thus reducing the total amount of pruning information so that it can more easily be accommodated by fast-path hardware.
Document record
- Document ID
- RFC7968
- Published
- August 2016
- Authors
- Y. Li; D. Eastlake 3rd; W. Hao; H. Chen; S. Chatterjee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7176Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISCurrent
May 2014
- RFC 7900Extranet Multicast in BGP/IP MPLS VPNsUpdated
June 2016
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
- RFC 7716Global Table Multicast with BGP Multicast VPN (BGP-MVPN) ProceduresCurrent
December 2015
- RFC 8220Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)Current
September 2017
- RFC 8279Multicast Using Bit Index Explicit Replication (BIER)Current
November 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?