Re: [Pce] WG Adoption of draft-chen-pce-pcep-ifit-06

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 04 July 2022 13:19 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0B5C15A74B; Mon, 4 Jul 2022 06:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1f1oM95HtqJ5; Mon, 4 Jul 2022 06:19:37 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED2E6C15A750; Mon, 4 Jul 2022 06:19:36 -0700 (PDT)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Lc5rq6zB8z6H8XC; Mon, 4 Jul 2022 21:15:23 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Mon, 4 Jul 2022 15:19:33 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2375.024; Mon, 4 Jul 2022 15:19:33 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: 王 雪荣 <XuerongWang_ChinaTelecom@hotmail.com>, Dhruv Dhody <dd@dhruvdhody.com>, "pce@ietf.org" <pce@ietf.org>
CC: "draft-chen-pce-pcep-ifit@ietf.org" <draft-chen-pce-pcep-ifit@ietf.org>
Thread-Topic: WG Adoption of draft-chen-pce-pcep-ifit-06
Thread-Index: AQHYh6jQNKSAJlnK00OiUI3WP8k0U61t546AgAAlyKA=
Date: Mon, 04 Jul 2022 13:19:33 +0000
Message-ID: <42716823cf29430bad50d737b5098b90@huawei.com>
References: <CAP7zK5Zp6CWFvBTKHK53B8krYZWgZKvswjfd+hBek=DikVWc-Q@mail.gmail.com> <PSAPR01MB399286ACF72B36F022D82F7BE7BE9@PSAPR01MB3992.apcprd01.prod.exchangelabs.com>
In-Reply-To: <PSAPR01MB399286ACF72B36F022D82F7BE7BE9@PSAPR01MB3992.apcprd01.prod.exchangelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.223.9]
Content-Type: multipart/alternative; boundary="_000_42716823cf29430bad50d737b5098b90huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/llBlWmE7QiUHi8M5ryG1avFuRb4>
Subject: Re: [Pce] WG Adoption of draft-chen-pce-pcep-ifit-06
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2022 13:19:41 -0000

Hi Xuerong,
Thanks for the support and for the comments.
Please see my replies inline tagged as [GF].

Regards,

Giuseppe

From: 王 雪荣 <XuerongWang_ChinaTelecom@hotmail.com>
Sent: Monday, July 4, 2022 11:56 AM
To: Dhruv Dhody <dd@dhruvdhody.com>; pce@ietf.org
Cc: draft-chen-pce-pcep-ifit@ietf.org
Subject: 回复: WG Adoption of draft-chen-pce-pcep-ifit-06


Hi WG,



I support the adoption of this draft. I think this is an very useful extension.



There are several comments after reviewing the document:

1) It is mentioned the example of SR-MPLS and SRv6 in the draft. What about IPv6? Is it possible to add an example for IPv6 by leveraging draft-ietf-pce-pcep-extension-native-ip?

[GF]: Yes, this PCEP extension is general, therefore it can also be applied to the scenario of Native IP network. I can mention this point in the next revision of the draft.

2) What is the relation of the IFIT PCEP extension with the companion draft-ietf-idr-sr-policy-ifit which defines the BGP extension to enable IFIT methods for SR policy?

[GF]: For Segment Routing, both PCEP and BGP can be used to instantiate SR Policies, so it makes sense to have the same mechanism for PCEP and BGP. In particular, draft-ietf-idr-sr-policy-ifit simply extends the advertisement of SR Policies in BGP (draft-ietf-idr-segment-routing-te-policy) to include IFIT information. Therefore, this extension is limited to SR-Policy. While, for PCEP, the extension is general and the application to SR Policies is an example.

3) Section 2.1 is about “IFIT for SR Policies” and Section 6 is about “Example of application to SR Policy”. Since the PCEP Extension is general for all path types and SR Policy is just an example, why not merge section 2.1 in section 6?

[GF]: Sure, it can be possible to merge the two sections.



Thanks


Wangxuerong
+86 15323320217
XuerongWang_chinatelecom@hotmail.com/wangxr4@chinatelecom.cn<mailto:XuerongWang_chinatelecom@hotmail.com/wangxr4@chinatelecom.cn>

________________________________
发件人: Dhruv Dhody <dd@dhruvdhody.com<mailto:dd@dhruvdhody.com>>
发送时间: 2022年6月24日 16:58
收件人: pce@ietf.org<mailto:pce@ietf.org> <pce@ietf.org<mailto:pce@ietf.org>>
抄送: draft-chen-pce-pcep-ifit@ietf.org<mailto:draft-chen-pce-pcep-ifit@ietf.org> <draft-chen-pce-pcep-ifit@ietf.org<mailto:draft-chen-pce-pcep-ifit@ietf.org>>
主题: WG Adoption of draft-chen-pce-pcep-ifit-06

Hi WG,

This email begins the WG adoption poll for draft-chen-pce-pcep-ifit-06.

https://datatracker.ietf.org/doc/draft-chen-pce-pcep-ifit/

Should this draft be adopted by the PCE WG? Please state your reasons - Why / Why not? What needs to be fixed before or after adoption? Are you willing to work on this draft? Review comments should be posted to the list.

Please respond by Monday 11th July 2022.

Please be more vocal during WG polls!

Thanks!
Dhruv & Julien