TRILL: Data Label based Tree Selection for Multi-destination Data

Document Type Replaced Internet-Draft (individual)
Authors Yizhou Li  , Donald Eastlake  , Hao Weiguo  , Hao Chen  , Radia Perlman  , Naveen Nimmu  , Somnath Chatterjee  , Sunny Rajagopalan 
Last updated 2015-03-02
Replaced by RFC 7968
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-trill-tree-selection
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


TRILL uses distribution trees to deliver multi-destination frames. Multiple trees can be used by an ingress 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 VLAN and/or FGL and/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 tree; however, there is a limited 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 group thus reducing the total amount of pruning information so that it can more easily be accommodated by fast path hardware.


Yizhou Li (
Donald Eastlake (
Hao Weiguo (
Hao Chen (
Radia Perlman (
Naveen Nimmu (
Somnath Chatterjee (
Sunny Rajagopalan (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)