Re: [trill] WG Adoption of draft-hao-idr-ls-trill-02.txt - 8/18 to 9/1

Andrew Qu <andrew.qu@mediatek.com> Wed, 19 August 2015 01:07 UTC

Return-Path: <andrew.qu@mediatek.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 337251A21A0; Tue, 18 Aug 2015 18:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_BAD_LINEBREAK=0.5, MIME_BASE64_TEXT=1.741, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=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 W9idq8Wfh5zY; Tue, 18 Aug 2015 18:07:30 -0700 (PDT)
Received: from mailgw02.mediatek.com (mailgw02.mediatek.com [69.46.227.142]) by ietfa.amsl.com (Postfix) with ESMTP id E41671A6EF2; Tue, 18 Aug 2015 18:07:28 -0700 (PDT)
X-Listener-Flag: 11101
Received: from mtkcas64.mediatek.inc [(172.29.17.144)] by mailgw02.mediatek.com (envelope-from <andrew.qu@mediatek.com>) (Cellopoint E-mail Firewall v3.9.12 Build 0312 with TLS) with ESMTP id 527573591; Tue, 18 Aug 2015 21:04:10 -0500
Received: from MTKMBS61N1.mediatek.inc ([fe80::2898:86df:e627:42ee]) by MTKCAS64.mediatek.inc ([::1]) with mapi id 14.03.0181.006; Tue, 18 Aug 2015 21:07:24 -0400
From: Andrew Qu <andrew.qu@mediatek.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] WG Adoption of draft-hao-idr-ls-trill-02.txt - 8/18 to 9/1
Thread-Index: AdDZut6Bol+RUVQHQm+jVgUCbJKDVwAX71xg
Date: Wed, 19 Aug 2015 01:07:23 +0000
Message-ID: <EA360A7AB9D90D4B9E9173B6D27C371EE3F8007C@MTKMBS61N1.mediatek.inc>
References: <014001d0d9bb$5d47c240$17d746c0$@ndzh.com>
In-Reply-To: <014001d0d9bb$5d47c240$17d746c0$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.17.249]
x-tm-as-product-ver: SMEX-10.2.0.3176-8.000.1202-21752.005
x-tm-as-result: No--46.194100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_EA360A7AB9D90D4B9E9173B6D27C371EE3F8007CMTKMBS61N1media_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/6W63LmM50VlS3uwInA7AQ2MQz1c>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, 'Haoweiguo' <haoweiguo@huawei.com>
Subject: Re: [trill] WG Adoption of draft-hao-idr-ls-trill-02.txt - 8/18 to 9/1
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: <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: Wed, 19 Aug 2015 01:07:32 -0000

Hi Sue,

I am supporting this proposal.  customers may have small trill cloud (due to
many reasons of network design, or SW capacity etc),  inter-connecting multiple
TRILL clouds become inevitable requirements.  the control plane like this will definitely
become helpful for those vendors to provide inter-connecting approach.

Of course, there are cases where DCI also need such control plane to support if
TRILL domain to be connected.

Thanks,

Andrew

From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, August 18, 2015 6:40 AM
To: idr@ietf.org; trill@ietf.org
Cc: 'Donald Eastlake'; 'Haoweiguo'
Subject: [trill] WG Adoption of draft-hao-idr-ls-trill-02.txt - 8/18 to 9/1

This begins a 2 week WG Adoption call for draft-hao-idr-ls-trill-02.txt as IDR WG document.  At IETF 93 by the TRILL WG indicated support for the as supporting TRILL.  This WG adoption call for IDR is being cross-posted to TRILL WG.

The authors should indicate whether they know of any IPR on this document.

The IDR and TRILL WG members should indicate whether;


1)      TRILL information is necessary to pass in BGP in deployments?

2)      Does this use of ls-distribution mechanisms make sense?

3)      Do you see any technical flaws with the document?

Sue Hares