[trill] Ingress replication for multicast forwarding states reduction
Mingui Zhang <zhangmingui@huawei.com> Tue, 19 June 2012 07:41 UTC
Return-Path: <zhangmingui@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9F621F8625 for <trill@ietfa.amsl.com>; Tue, 19 Jun 2012 00:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.102
X-Spam-Level:
X-Spam-Status: No, score=-6.102 tagged_above=-999 required=5 tests=[AWL=-0.498, BAYES_00=-2.599, FS_REPLICA=0.994, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aM-rCPCFhl5I for <trill@ietfa.amsl.com>; Tue, 19 Jun 2012 00:41:10 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2607421F8615 for <trill@ietf.org>; Tue, 19 Jun 2012 00:41:10 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHA61069; Tue, 19 Jun 2012 03:41:09 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 19 Jun 2012 00:40:59 -0700
Received: from SZXEML438-HUB.china.huawei.com (10.72.61.73) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 19 Jun 2012 00:40:58 -0700
Received: from SZXEML507-MBS.china.huawei.com ([169.254.7.154]) by szxeml438-hub.china.huawei.com ([10.72.61.73]) with mapi id 14.01.0323.003; Tue, 19 Jun 2012 15:40:52 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "'trill@ietf.org'" <trill@ietf.org>
Thread-Topic: Ingress replication for multicast forwarding states reduction
Thread-Index: AQHNSeGZQy8G0zb9VE+whwG5f16PPQ==
Date: Tue, 19 Jun 2012 07:40:51 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E731FA55C1@SZXEML507-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.103.7]
Content-Type: multipart/alternative; boundary="_000_4552F0907735844E9204A62BBDD325E731FA55C1SZXEML507MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [trill] Ingress replication for multicast forwarding states reduction
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 07:41:11 -0000
Hi WG members, In TRILL, distribution trees are pruned per VLAN. The number of multicast states maintained on TRILL switches may be very large. If RBridges advertise in LSPs that VLANs with _sparse_ multicast receivers would rather use ingress replication, then distribution trees need not be pruned and maintained for these VLANs. Since they are sparse, the bandwidth consumption of them will be low. Given sparse multicast groups may have a high proportion in all multicast groups, the states on RBridges can be greatly reduced. So, whether it's possible to use ingress replication in combination with distribution trees in TRILL? Thanks, Mingui
- [trill] Ingress replication for multicast forward… Mingui Zhang