Re: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)

"Xialiang (Frank)" <frank.xialiang@huawei.com> Tue, 02 December 2014 11:14 UTC

Return-Path: <frank.xialiang@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6304B1A1A98 for <trill@ietfa.amsl.com>; Tue, 2 Dec 2014 03:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level:
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FS_REPLICA=0.994, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVn6fodDfehl for <trill@ietfa.amsl.com>; Tue, 2 Dec 2014 03:14:54 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1A61A1AA0 for <trill@ietf.org>; Tue, 2 Dec 2014 03:14:53 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMG87241; Tue, 02 Dec 2014 11:14:52 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 2 Dec 2014 11:14:47 +0000
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.198]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0158.001; Tue, 2 Dec 2014 19:14:43 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)
Thread-Index: AdAJPrZvprDf4VONRLaFpaqqxF/Xdpx5543MgAAGw2CccCy7wA==
Date: Tue, 2 Dec 2014 11:14:42 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12AD27BC2@SZXEMA502-MBS.china.huawei.com>
References: <023e01d0093e$f076bc40$d16434c0$@ndzh.com> <DD5FC8DE455C3348B94340C0AB5517334F82087D@nkgeml501-mbs.china.huawei.com>, <EA360A7AB9D90D4B9E9173B6D27C371E752C1A1A@MTKMBS61N1.mediatek.inc> <DD5FC8DE455C3348B94340C0AB5517334F820976@nkgeml501-mbs.china.huawei.com> <06FF377397785A4781BD13272EBF3D586655B2334B@HQ1-EXCH02.corp.brocade.com>
In-Reply-To: <06FF377397785A4781BD13272EBF3D586655B2334B@HQ1-EXCH02.corp.brocade.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.42.200]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12AD27BC2SZXEMA502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/IHnV4gSYkosrAxgWYbTeyWPNQEY
Subject: Re: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2014 11:14:58 -0000

I have reviewed this draft and think it is a good solution for solving an important issue in active-active scenario:  incorrect packet drop by RPF check failure.
And this draft is well organized in describing the solution.

So, I support adoption of this draft!

B.R.
Frank

From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Muhammad Durrani
Sent: Monday, December 01, 2014 9:09 AM
To: trill@ietf.org
Cc: Haoweiguo
Subject: Re: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)

This draft provides optimized way to forward BUM traffic via centralized replication mechanism which in fact makes it simpler to use legacy multicast RPF algorithm for loop prevention with min BUM distribution tree states which in turn addresses control plane scalability issues and also maximizes the usage of all available bandwidth using VLAN and Flow based load balancing,  this makes trill implementation more robust to fit for high to hyper scale data centers.


I support adaption of this draft !



Regards,

Muhammad



________________________________
From: Andrew Qu [andrew.qu@mediatek.com]
Sent: Saturday, November 29, 2014 14:04
To: shares@ndzh.com<mailto:shares@ndzh.com>
Cc: trill@ietf.org<mailto:trill@ietf.org>
Subject: Re: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)
Hi Sue



This draft bring forth a solution to have less number of trees but not compromise RPF checking on data plane.

This helps active-active implementation without scalability issue in managing potential large number of distribution trees

in control plane.



I support such draft.



Thanks,



Andrew



________________________________
From: Susan Hares [shares@ndzh.com]
Sent: Wednesday, November 26, 2014 14:05
To: trill@ietf.org<mailto:trill@ietf.org>
Cc: 'Donald Eastlake'; trill-chairs@tools.ietf.org<mailto:trill-chairs@tools.ietf.org>
Subject: [trill] 2 WG adoption call for draft-hao-trill-centralized-replication-02 (11/26 to 12/12)
This begins a 2 week adoption call for draft-hao-trill-centralized-replication-02.txt
(Centralized Replication for BUM traffic in active-active edge) which can be found at:
http://datatracker.ietf.org/doc/draft-hao-trill-centralized-replication/

This draft is another in our active-active drafts.  Please debate the technical merits of the draft, and include in the discussion "support" or "no support" for this draft as a WG draft.

Sue



************* Email Confidentiality Notice ********************

The information contained in this e-mail message (including any

attachments) may be confidential, proprietary, privileged, or otherwise

exempt from disclosure under applicable laws. It is intended to be

conveyed only to the designated recipient(s). Any use, dissemination,

distribution, printing, retaining or copying of this e-mail (including its

attachments) by unintended recipient(s) is strictly prohibited and may

be unlawful. If you are not an intended recipient of this e-mail, or believe

that you have received this e-mail in error, please notify the sender

immediately (by replying to this e-mail), delete any and all copies of

this e-mail (including any attachments) from your system, and do not

disclose the content of this e-mail to any other person. Thank you!