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

Liyizhou <liyizhou@huawei.com> Sat, 29 August 2015 00:32 UTC

Return-Path: <liyizhou@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 7675C1A1A7E; Fri, 28 Aug 2015 17:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 SG5sxhmr1O8w; Fri, 28 Aug 2015 17:32:02 -0700 (PDT)
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 9C21C1B3307; Fri, 28 Aug 2015 17:32:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CAN88529; Sat, 29 Aug 2015 00:32:00 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sat, 29 Aug 2015 01:31:57 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.207]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0235.001; Sat, 29 Aug 2015 08:31:44 +0800
From: Liyizhou <liyizhou@huawei.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+jVgUCbJKDVwINvkhA
Date: Sat, 29 Aug 2015 00:31:43 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8F838FA5BB@nkgeml503-mbx.china.huawei.com>
References: <014001d0d9bb$5d47c240$17d746c0$@ndzh.com>
In-Reply-To: <014001d0d9bb$5d47c240$17d746c0$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.180.237]
Content-Type: multipart/alternative; boundary="_000_D408889639FC5E4FADB4E00A3E01FA8F838FA5BBnkgeml503mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/SbbUVmxcoRLxYi5s0Ko1yx0WMic>
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: Sat, 29 Aug 2015 00:32:04 -0000

Support. I believe it is a useful feature for TRILL domain interconnection.

Thanks,
Yizhou

From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, August 18, 2015 9:40 PM
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