Skip to main content

VLAN based Tree Selection for Multi-destination Frames
draft-yizhou-trill-tree-selection-01

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Yizhou Li , Hao Weiguo , Radia Perlman , Naveen Nimmu , Somnath Chatterjee
Last updated 2013-01-04 (Latest revision 2012-07-03)
Replaced by draft-ietf-trill-tree-selection, RFC 7968
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

TRILL uses distribution trees for multi-destination traffic. Multiple trees can be used by an ingress RBridge. Different ingress RBridges may choose different distribution trees for the same VLAN and/or multicast group traffic. Distribution trees are normally pruned based on VLAN. For any RBridge RBn, if RBn has downstream receivers of VLAN x in a distribution tree t, there will be an entry of (t, x, port list) in the multicast forwarding table on RBn. If there are n trees and m VLANs, the multicast forwarding table size on RBn is typically n*m entries. The value of m is up to 4096 and n is the total number of distribution trees in the campus. If finer granularity filtering such as L2/L3 multicast address is used, then the multicast forwarding table size further increases dramatically. TRILL multicast forwarding table size is limited by hardware and L3 multicasting may share the same table with it in hardware implementations. Therefore multicast table entry is a precious resource. This document specifies a VLAN based tree selection mechanism to reduce the TRILL multicast forwarding table size. No data plane change is required.

Authors

Yizhou Li
Hao Weiguo
Radia Perlman
Naveen Nimmu
Somnath Chatterjee

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