Re: [trill] TRILL Resilient Distribution Trees, who have read it?
hu.fangwei@zte.com.cn Fri, 07 December 2012 06:54 UTC
Return-Path: <hu.fangwei@zte.com.cn>
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 39FD921F8965; Thu, 6 Dec 2012 22:54:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.395
X-Spam-Level:
X-Spam-Status: No, score=-98.395 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1mSiIkwoani; Thu, 6 Dec 2012 22:54:58 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 66DC321F8989; Thu, 6 Dec 2012 22:54:58 -0800 (PST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 6EDAB126DA8D; Fri, 7 Dec 2012 14:56:37 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id qB76scgK001243; Fri, 7 Dec 2012 14:54:38 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
In-Reply-To: <4552F0907735844E9204A62BBDD325E732132977@SZXEML507-MBS.china.huawei.com>
To: Mingui Zhang <zhangmingui@huawei.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.4 June 01, 2004
Message-ID: <OF36E5FC50.EA4FE953-ON48257ACD.00252D55-48257ACD.0025F553@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Fri, 07 Dec 2012 14:54:30 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-07 14:54:38, Serialize complete at 2012-12-07 14:54:38
Content-Type: multipart/alternative; boundary="=_alternative 0025F54E48257ACD_="
X-MAIL: mse01.zte.com.cn qB76scgK001243
Cc: trill-bounces@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] TRILL Resilient Distribution Trees, who have read it?
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: Fri, 07 Dec 2012 06:54:59 -0000
I have read the draft. The draft provides to build backup distribution tree for link protection, which mininizes the serive disruption for multicast data forwarding. If there is a WG adoption polling, I support it. Mingui Zhang <zhangmingui@huawei.com> 发件人: trill-bounces@ietf.org 2012-11-30 16:18 收件人 "trill@ietf.org" <trill@ietf.org> 抄送 主题 [trill] TRILL Resilient Distribution Trees, who have read it? Hi all, When customers deploy TRILL in their networks, they concern much about minimizing the disruption of their multicast service. So failure protection mechanisms are desired. Protection solutions for IP Multicast service have been developed and standardized. However, unlike unicast, multicast protection solutions cannot be reused by TRILL because TRILL-multicast is customized for TRILL. Therefore we composed the draft to provide the multicast protection suitable for TRILL. As we know, TRILL can intrinsically calculate multiple distribution trees. In the draft, this ability is leveraged to achieve multicast protection in a way that the pay is insignificant. We believe this work deserves our exploration. So, we would like to know, who have read this draft? The draft TRILL Resilient Distribution Trees http://datatracker.ietf.org/doc/draft-zhang-trill-resilient-trees/ Thanks, Mingui _______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill
- [trill] TRILL Resilient Distribution Trees, who h… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… gayle noble
- Re: [trill] TRILL Resilient Distribution Trees, w… Anoop Ghanwani
- Re: [trill] TRILL Resilient Distribution Trees, w… Ayan Banerjee
- [trill] 答复: TRILL Resilient Distribution Trees, w… Haoweiguo
- Re: [trill] TRILL Resilient Distribution Trees, w… Pathangi_Janardhanan
- [trill] 答复: TRILL Resilient Distribution Trees, w… Guyingjie (Yingjie)
- Re: [trill] TRILL Resilient Distribution Trees, w… Linda Dunbar
- Re: [trill] TRILL Resilient Distribution Trees, w… Sam Aldrin
- Re: [trill] TRILL Resilient Distribution Trees, w… zhai.hongjun
- Re: [trill] TRILL Resilient Distribution Trees, w… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… Sam Aldrin
- [trill] 答复: TRILL Resilient Distribution Trees, w… Zhangxudong
- Re: [trill] TRILL Resilient Distribution Trees, w… gayle noble
- Re: [trill] TRILL Resilient Distribution Trees, w… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… gayle noble
- Re: [trill] TRILL Resilient Distribution Trees, w… hu.fangwei
- Re: [trill] TRILL Resilient Distribution Trees, w… Thomas Narten
- Re: [trill] TRILL Resilient Distribution Trees, w… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… Thomas Narten
- Re: [trill] TRILL Resilient Distribution Trees, w… Mingui Zhang
- Re: [trill] TRILL Resilient Distribution Trees, w… Donald Eastlake