IETF Logo Mail Archive

[trill] 答复: TRILL Resilient Distribution Trees, who have read it?

"Guyingjie (Yingjie)" <guyingjie@huawei.com> Wed, 05 December 2012 06:31 UTC

Return-Path: <guyingjie@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 8840021F8C60 for <trill@ietfa.amsl.com>; Tue, 4 Dec 2012 22:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.55
X-Spam-Level:
X-Spam-Status: No, score=-97.55 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345, 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 Kmjx2jis4qyP for <trill@ietfa.amsl.com>; Tue, 4 Dec 2012 22:31:10 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD4521F8C5E for <trill@ietf.org>; Tue, 4 Dec 2012 22:31:08 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AME60070; Wed, 05 Dec 2012 06:31:06 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 5 Dec 2012 06:30:15 +0000
Received: from SZXEML426-HUB.china.huawei.com (10.72.61.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 5 Dec 2012 06:30:42 +0000
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.138]) by szxeml426-hub.china.huawei.com ([10.72.61.34]) with mapi id 14.01.0323.003; Wed, 5 Dec 2012 14:30:24 +0800
From: "Guyingjie (Yingjie)" <guyingjie@huawei.com>
To: "Pathangi_Janardhanan@Dell.com" <Pathangi_Janardhanan@Dell.com>, "ayabaner@gmail.com" <ayabaner@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] TRILL Resilient Distribution Trees, who have read it?
Thread-Index: Ac3O0ux4S0JhVhpwS56Ahgx4dyNymwCtjLeAACASioAAFc/pAAAURs9Q
Date: Wed, 05 Dec 2012 06:30:24 +0000
Message-ID: <A27496C192613C44A82D819E1B98DB57477F6F0C@SZXEML511-MBS.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E732132977@SZXEML507-MBS.china.huawei.com> <CA+-tSzzp08kcd31qZtz0Kf73tnktuTv-spxfdfheuztED51wcQ@mail.gmail.com> <CAHD03N_vTBCtbrEPY5+POvPN81_OCPX156F_0FCWtGU019HS8w@mail.gmail.com> <D5A6F3355F664C40AFB65BB1277D8D450185BC09C1@MAAX7MCDC101.APAC.DELL.COM>
In-Reply-To: <D5A6F3355F664C40AFB65BB1277D8D450185BC09C1@MAAX7MCDC101.APAC.DELL.COM>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.109.101]
Content-Type: multipart/alternative; boundary="_000_A27496C192613C44A82D819E1B98DB57477F6F0CSZXEML511MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [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: Wed, 05 Dec 2012 06:31:10 -0000

I read it and Support it.


On Fri, Nov 30, 2012 at 12:18 AM, Mingui Zhang <zhangmingui@huawei.com<mailto:zhangmingui@huawei.com>> wrote:
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<mailto:trill@ietf.org>
https://www.ietf.org/mailman/listinfo/trill


_______________________________________________
trill mailing list
trill@ietf.org<mailto:trill@ietf.org>
https://www.ietf.org/mailman/listinfo/trill

v2.23.0 | Report a Bug | By Email