IETF Logo Mail Archive

Re: [trill] Working group LC on draft-ietf-trill-multi-topology-04 (9/27

Liyizhou <liyizhou@huawei.com> Tue, 26 December 2017 05:57 UTC

Return-Path: <liyizhou@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 C58B7126C83 for <trill@ietfa.amsl.com>; Mon, 25 Dec 2017 21:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 h9yPtJsCMRIu for <trill@ietfa.amsl.com>; Mon, 25 Dec 2017 21:57:25 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967BF1200F3 for <trill@ietf.org>; Mon, 25 Dec 2017 21:57:25 -0800 (PST)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 583D251285E61 for <trill@ietf.org>; Tue, 26 Dec 2017 05:57:22 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 26 Dec 2017 05:57:22 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0361.001; Tue, 26 Dec 2017 13:57:15 +0800
From: Liyizhou <liyizhou@huawei.com>
To: Radia Perlman <radiaperlman@gmail.com>, R Parameswaran <parameswaran.r7@gmail.com>
CC: Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] Working group LC on draft-ietf-trill-multi-topology-04 (9/27
Thread-Index: AQHTeJCCak8YJ7np/0eV/T0CvgFXqaNVKwRA
Date: Tue, 26 Dec 2017 05:57:14 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8FA6B33DAD@nkgeml513-mbs.china.huawei.com>
References: <CAGeBGG6ZsdV93EoULj=uPpMOvu9wzXtarfDFrMAzZJSDMxOC9A@mail.gmail.com> <CAFOuuo5C7Uvpw7XxYQDUysY3Swv8HdYj52vHN4A_Od25EG3NcA@mail.gmail.com>
In-Reply-To: <CAFOuuo5C7Uvpw7XxYQDUysY3Swv8HdYj52vHN4A_Od25EG3NcA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.186.229]
Content-Type: multipart/alternative; boundary="_000_D408889639FC5E4FADB4E00A3E01FA8FA6B33DADnkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/PsJw9QO-K08xr22DEqb-G1m-hWA>
Subject: Re: [trill] Working group LC on draft-ietf-trill-multi-topology-04 (9/27
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Dec 2017 05:57:28 -0000

I support its publication. The document is well shaped to follow and is potentially a useful feature for scalable DC.

Thanks,
Yizhou

From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Radia Perlman
Sent: Tuesday, December 19, 2017 2:13 PM
To: R Parameswaran <parameswaran.r7@gmail.com>
Cc: Donald Eastlake <d3e3e3@gmail.com>; trill@ietf.org
Subject: Re: [trill] Working group LC on draft-ietf-trill-multi-topology-04 (9/27

I too support the publication of this document.  The document seems well written.  Although I get nervous about features that can create loops if misconfigured, this is not a problem with using this feature for TRILL any more than using IS-IS for IP.  Since people seem to have it successfully deployed for IP, and find it useful, it should be equally useful for TRILL.

I think the draft is ready for publication.

Radia

On Sun, Oct 15, 2017 at 5:57 PM, R Parameswaran <parameswaran.r7@gmail.com<mailto:parameswaran.r7@gmail.com>> wrote:


Hi,

I support the adoption/standardization of this draft. Comments  inline.

thanks,

Ramkumar


This begins a 2 week WG LC on draft-ietf-trill-multi-topology-04.txt.

During this WG last call please include comment on the following three

things in addition to your normal comments:



1)      Does this draft support the things you desire to support multiple

topology routing of unicast and multi-destination traffic in TRILL?

[RP]: Yes.

 2)      Do you think this draft is read for publication?

[RP]: Yes, quick look-through, seems correct.



3)      Do you think that multi-topology trill has a place in the data

center deployments of TRILL?

[RP] Yes.

 Sue Hares and Jon Hudson



Co-chairs 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