[Teas] Review on draft-ietf-teas-yang-te-21
"Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com> Wed, 10 April 2019 10:12 UTC
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B20E1201F3; Wed, 10 Apr 2019 03:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 twQaR_cDRqco; Wed, 10 Apr 2019 03:12:51 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 4F7A812021F; Wed, 10 Apr 2019 03:12:51 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7DC0419A35D3066C12FB; Wed, 10 Apr 2019 11:12:49 +0100 (IST)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Apr 2019 11:12:49 +0100
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 10 Apr 2019 11:12:48 +0100
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Wed, 10 Apr 2019 11:12:48 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.130]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0415.000; Wed, 10 Apr 2019 18:12:34 +0800
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com>
To: "draft-ietf-teas-yang-te@ietf.org" <draft-ietf-teas-yang-te@ietf.org>
CC: "'teas@ietf.org'" <teas@ietf.org>
Thread-Topic: Review on draft-ietf-teas-yang-te-21
Thread-Index: AdTvheHjf7TOdpIpTw6de+pLrBcGbg==
Date: Wed, 10 Apr 2019 10:12:33 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B7B600A@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.57.78.212]
Content-Type: multipart/related; boundary="_004_E0C26CAA2504C84093A49B2CAC3261A43B7B600Adggeml511mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/-PqaAXfTyo6ancjGGN8mvP9uxnI>
Subject: [Teas] Review on draft-ietf-teas-yang-te-21
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 10:12:53 -0000
Hi, Tarek, Authors, I have reviewed the latest version of draft-ietf-teas-yang-te (-21) with following considerations, please take a look and decide whether to address in future work. 1. Status Consideration: Currently we are having two parameters describing the status: operational-state and provisioning-state. By using the current states we can specify whether an LSP has been successfully planned or established, but cannot specify whether an LSP has been successfully revised or tear down. Refer more details to https://mailarchive.ietf.org/arch/msg/teas/iKL2TYV9M3B5z825EzCZnMMnFWg; BTW, I don’t quite understand why we change the ‘administrative-state’ into ‘operational-state’ but still keep the description as ‘TE tunnel administrative state’ in page 72. And the description on P68 about provisioning-state is also misleading. 2. Renaming ‘tp-’ with ‘ttp’ for some cases: Now we are having te-tp-id to describe the LTP information, and having src-tp-id, dst-tp-id describing the TTP information. The abbreviation ‘tp-’ is confusing. The proposal is to keep ‘tp-’ stand for LTP and use ’ttp-’ to indicating TTP, i.e., rename the ‘src-tp-id’ to ‘src-ttp-id’ and ‘dst-tp-id’ to ‘dst-ttp-id’. 3. About WTR: currently we are having two different WTRs both referencing RFC4427. The ‘wait-to-revert’ is used for protection, while the ‘wait-to-revert’ and the ‘wait-to-restore’ are used for restoration. However in RFC 4427, there is only definition for wait-to-restore as a part of protection (the definition for wait-to-restore is also consistent with ITU-T G.808.1), therefore it is suggested to use ‘wait-to-restore’ rather than ‘wait-to-revert’ under protection. Moreover, it is not clear why there are two different WTR for restoration and how they are used in different ways, shall we combine them into one? Thank you. Best wishes, Haomian Network Research Department Fixed Network Business Unit Huawei Technologies Co., LTD. Xiliu Beipo Village, Huanhu Road, Songshan Lake, Dongguan, 523808 P.R.China Tel: +86-13066975206 ________________________________ 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo]
- [Teas] Review on draft-ietf-teas-yang-te-21 Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)
- Re: [Teas] Review on draft-ietf-teas-yang-te-21 Igor Bryskin