Re: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12

xiong.quan@zte.com.cn Wed, 17 January 2024 03:08 UTC

Return-Path: <xiong.quan@zte.com.cn>
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 9CA9BC151524; Tue, 16 Jan 2024 19:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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, UNPARSEABLE_RELAY=0.001, 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 hI2YPeVlWiGw; Tue, 16 Jan 2024 19:08:03 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BECBC151525; Tue, 16 Jan 2024 19:08:01 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4TF9mY6TzMz8XrRB; Wed, 17 Jan 2024 11:07:57 +0800 (CST)
Received: from njy2app08.zte.com.cn ([10.40.13.206]) by mse-fl2.zte.com.cn with SMTP id 40H37r8J058382; Wed, 17 Jan 2024 11:07:53 +0800 (+08) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid201; Wed, 17 Jan 2024 11:07:54 +0800 (CST)
Date: Wed, 17 Jan 2024 11:07:54 +0800
X-Zmail-TransId: 2aff65a7448a650-8a55d
X-Mailer: Zmail v1.0
Message-ID: <202401171107544074067@zte.com.cn>
In-Reply-To: <LV8PR11MB8511F30A9D563E3C37320876D3732@LV8PR11MB8511.namprd11.prod.outlook.com>
References: 202401151101276488103@zte.com.cn, LV8PR11MB8511F30A9D563E3C37320876D3732@LV8PR11MB8511.namprd11.prod.outlook.com
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: mkoldych@cisco.com
Cc: dd@dhruvdhody.com, draft-ietf-pce-segment-routing-policy-cp@ietf.org, pce@ietf.org, pce-chairs@ietf.org, mkoldych@proton.me
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 40H37r8J058382
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65A7448D.000/4TF9mY6TzMz8XrRB
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/OEAT4v2fxZb_r9OIqPU6inNiZvs>
Subject: Re: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12
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: Wed, 17 Jan 2024 03:08:07 -0000

Hi Mike,

Thanks for your reply!
I am not sure about this use case. From my understanding, serveral candidate paths may be associated to a SR policy in PCE environment, (if this may happen) but if all candidate paths are judged to invalid by PCE (for example as per draft-chen-pce-sr-policy-cp-validty), then the association should be removed. 
And another confusion about the "MBZ" in figure 3. May I know the full name of this abbreviation? Thanks!

Best Regards,
Quan

Original


From: MikeKoldychev(mkoldych) <mkoldych@cisco.com>
To: 熊泉00091065;dd@dhruvdhody.com <dd@dhruvdhody.com>;draft-ietf-pce-segment-routing-policy-cp@ietf.org <draft-ietf-pce-segment-routing-policy-cp@ietf.org>;
Cc: pce@ietf.org <pce@ietf.org>;pce-chairs@ietf.org <pce-chairs@ietf.org>;mkoldych@proton.me <mkoldych@proton.me>;
Date: 2024年01月17日 00:47
Subject: RE: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12



Hi Quan,
 
Thanks for your review! Comments inline with <MK></MK>.
 
Thanks,
Mike.
 

From: Pce <pce-bounces@ietf.org> On Behalf Of xiong.quan@zte.com.cn
 Sent: Sunday, January 14, 2024 10:01 PM
 To: dd@dhruvdhody.com; draft-ietf-pce-segment-routing-policy-cp@ietf.org
 Cc: pce@ietf.org; pce-chairs@ietf.org
 Subject: Re: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12


 
 
Hi PCE WG, Authors, I have reviewed the latest version in details and I feel this draft is good written and I support the progression to RFC.
And I have two minor suggestions.
A,I noticed the [I-D.ietf-idr-segment-routing-te-policy] and [I-D.ietf-pce-multipath] are in the Normative References. I am not sure if the two drafts should be moved to Informative References when progess to RFC.
<MK>
Good suggestion, thanks.
</MK>
B, AS per [RFC9256] section 8.1, an SR policy is invalid when all candidate paths are invalid and the SR policy should  transit to invalid state including removing the SR Policy and BSID and so.
Maybe it is better to consider or clarify that in the PCEP SR policy. Thanks!
<MK>
Sorry, what do you mean to clarify it? Isn’t it already clear from RFC9256?
</MK>
Best Regards,
Quan
 
<<Hi WG,   <<This email starts a 2-weeks working group last call for <<draft-ietf-pce-segment-routing-policy-cp-12.https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-policy-cp/Please indicate your support or concern for this <<<<draft. If you are opposed <<to the progression of the draft to RFC, please articulate your concern. If <<you support it, please indicate that you have read the latest version and <<it is ready for publication in your opinion. As always, review comments and <<nits are most welcome.   <<The WG LC will end on Monday 22nd January 2024.   <<A general reminder to the WG to be more vocal during the last-call/adoption.   <<Thanks, <<Dhruv & Julien