Re: [trill] draft-ietf-trill-over-ip WG Last Call (11/15 - 12/6)

Lucy yong <lucy.yong@huawei.com> Mon, 02 January 2017 17:48 UTC

Return-Path: <lucy.yong@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 EA08B1296D8 for <trill@ietfa.amsl.com>; Mon, 2 Jan 2017 09:48:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.32
X-Spam-Level:
X-Spam-Status: No, score=-7.32 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, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] 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 vuZHDrrN3jb7 for <trill@ietfa.amsl.com>; Mon, 2 Jan 2017 09:48:26 -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 1F2651296DF for <trill@ietf.org>; Mon, 2 Jan 2017 09:48:25 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DDR21575; Mon, 02 Jan 2017 17:48:23 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 2 Jan 2017 17:48:22 +0000
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0301.000; Mon, 2 Jan 2017 09:48:16 -0800
From: Lucy yong <lucy.yong@huawei.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: RE:[trill] draft-ietf-trill-over-ip WG Last Call (11/15 - 12/6)
Thread-Index: AdJlIF6tD+PHp0VKQOmMqwT+0nWv6Q==
Date: Mon, 2 Jan 2017 17:48:16 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57B9BE55@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.146.166]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57B9BE55dfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.586A9268.0080, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 59330b83549f650507fc56625121d1b6
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/GZu4r0BMr9GFCrng-sNnKhec-Dg>
Subject: Re: [trill] draft-ietf-trill-over-ip WG Last Call (11/15 - 12/6)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 02 Jan 2017 17:48:29 -0000

Support publishing.

One comment:  In section 8.1 ,    d. Use of a "Managed Circuit Breaker" for the TRILL traffic as
      described in [circuit-breaker].
CB can't serve this purpose.  Please look at the congestion consideration text in
 https://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-19

Lucy

On behalf of the Chairs, this message begins a three week WG Last Call on
https://datatracker.ietf.org/doc/draft-ietf-trill-over-ip/
There are no IPR declarations filed with the IETF on this draft.

The call is three weeks rather than the usual two due to overlap with the IETF meeting when people are usually pretty busy.

In your response please include answers to the following questions:

Is this draft ready for publication?
Are there any significant aspects of TRILL over IP that are omitted from the draft?
Is the encapsulation agreement method provided in the draft necessary and sufficient for good support of TRILL over IP?

Thanks,
Donald (TRILL WG Secretary)