[Idr] Re: continue discussion //Re: draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pre-Adoption Shepherd's review
chen.ran@zte.com.cn Wed, 22 May 2024 01:21 UTC
Return-Path: <chen.ran@zte.com.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9BFC1CAF29 for <idr@ietfa.amsl.com>; Tue, 21 May 2024 18:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ElBXIH3OztHF for <idr@ietfa.amsl.com>; Tue, 21 May 2024 18:21:15 -0700 (PDT)
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 66FF6C1C3D78 for <idr@ietf.org>; Tue, 21 May 2024 18:21:11 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (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 4VkYR81zYxz8XsKt for <idr@ietf.org>; Wed, 22 May 2024 09:21:08 +0800 (CST)
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 mxct.zte.com.cn (FangMail) with ESMTPS id 4VkYQZ1Kptz50yRQ; Wed, 22 May 2024 09:20:38 +0800 (CST)
Received: from njb2app07.zte.com.cn ([10.55.22.95]) by mse-fl2.zte.com.cn with SMTP id 44M1KMWX034403; Wed, 22 May 2024 09:20:22 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid203; Wed, 22 May 2024 09:20:23 +0800 (CST)
Date: Wed, 22 May 2024 09:20:23 +0800
X-Zmail-TransId: 2afb664d48573a1-272a8
X-Mailer: Zmail v1.0
Message-ID: <20240522092023567jbqQd0nnSJlDskhiwWxcY@zte.com.cn>
In-Reply-To: <CAH6gdPxRA87BdZ6hJ6aBuq0B9UhxAECxewgaBUcrsychuUuuVQ@mail.gmail.com>
References: 20240517181507045AVpCyOpqoPDnHY9vuMgYO@zte.com.cn,20240521161822843VME6LXy2t3jtHmRkLEvS4@zte.com.cn,CAH6gdPxRA87BdZ6hJ6aBuq0B9UhxAECxewgaBUcrsychuUuuVQ@mail.gmail.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: ketant.ietf@gmail.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 44M1KMWX034403
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 664D4884.000/4VkYR81zYxz8XsKt
Message-ID-Hash: BUXTXOQ4O66XNWGZ3C7R76EANCIXTUQK
X-Message-ID-Hash: BUXTXOQ4O66XNWGZ3C7R76EANCIXTUQK
X-MailFrom: chen.ran@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: shares@ndzh.com, idr@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: continue discussion //Re: draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pre-Adoption Shepherd's review
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Hi Ketan, Thanks! We will consider writing the new SR policy NRP document in the SPRING WG, or adding this part to the existing document. Best Regards, Ran Original From: KetanTalaulikar <ketant.ietf@gmail.com> To: 陈然00080434; Cc: shares@ndzh.com <shares@ndzh.com>;jmh@joelhalpern.com <jmh@joelhalpern.com>;idr@ietf.org <idr@ietf.org>; Date: 2024年05月22日 01:48 Subject: Re: continue discussion //Re: draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pre-Adoption Shepherd's review Hi Ran, Regarding applicability of NRP to SR Policies, there are two drafts in IDR (BGP SR Policy SAFI and BGP-LS) and another one in PCEP. Clearly, these details that we are discussing do not belong to either BGP or PCEP and are better covered in a SPRING document. The draft has an informative reference to draft-ietf-teas-nrp-scalability but I could not find any text there that describes exactly how NRP is used for SR Policy. There is clearly need for a standards track SPRING document that can be normatively referred to by these BGP and PCEP protocol extensions for SR Policy NRP. Thanks, Ketan On Tue, May 21, 2024 at 1:48 PM <chen.ran@zte.com.cn> wrote: Hi Sue,Joel &Ketan, Thank you very much for your valuable comments on 5/20/2024 IDR interim. Please see below. 1. Sue's comment on why the headend needs to report the configuration and the states of an SR Policy carrying NRP information. [Ran] The controller collects the resources occupied by the SR policy by the reported association between the NRP ID and the SR policy from the head node. The controller can use this information to visualize paths, verify consistency, calculate other SR policy paths that may share or bypass specific nodes or links, etc. One of the most important functions is to verify consistency, for example, SR policy with associated NRP-ID can be configured statically by the headend, or the association between NRP-ID and SR policy can be distributed to the headend by [I-D.ietf-idr-sr-policy-nrp]. The headend reports the association between NRP-ID and SR pilicy candidate path, indicating the association takes effect. 2. Joel's comment on clarifying this draft's relationship to draft-ietf-spring-resource-aware-segments-09, [Ran] In the resource SID scenario, The headend node does not have information about the relationship between CP and NRP ID, so it currently does not consider reporting the relationship between CP and NRP ID. The current draft is only for the scenario where data packets carry NRP ID, The NRP ID is used with the normal SRv6 SID as the resource used will be indicated by the NRP-ID. An SR Policy candidate path (CP) may be instantiated with a specific NRP on the headend node via a local configuration, PCEP, or BGP SR Policy signaling. Then the state and attributes of the NRP associated with the candidate path of SR policy can be distributed to the controller. For SR Policy with IPv6 data plane, the approach to encapsulate the NRP ID in IPv6 Hop-by-Hop Options header is defined in [I-D.ietf-6man-enhanced-vpn-vtn-id]. I will communicate with Jie about how to specify the relationship with SRv6 in the [I-D.ietf-6man-enhanced-vpn-vtn-id]. and clarify the scope in draft-chen-idr-bgp-ls-sr-policy-nrp. Is this ok? 3. Ketan's comment on how does the tail node of SR policy know to remove NRP-ID? [Ran] Since the tail node of the SR policy is the final destination, the IPv6 header will be removed, and the NRP ID carried in the IPv6 Hop-by-Hop Options header will naturally also be removed. Best Regards, Ran Original From: 陈然00080434 To: SusanHares <shares@ndzh.com>; Cc: idr@ietf.org <idr@ietf.org>;Dongjie (Jimmy) <jie.dong@huawei.com>;赵德涛10132546;龚立艳 <gongliyan@chinamobile.com>;zhuyq8@chinatelecom.cn <zhuyq8@chinatelecom.cn>; Date: 2024年05月17日 18:15 Subject: Re: draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pre-Adoption Shepherd's review Hi Sue & WG, We would like to request a presentation on 5/20/2024 IDR interim. Problem 1: Authors need to provide additional information on the following comment in section 1: “This document defines a new TLV to enable the headend to report the configuration and the states of an SR Policy carrying the NRP information by using BGP-LS”. The authors should indicate why: 1. The headend needs to report the configuration and the states of an SR Policy carrying NRP information. [Ran]: As defined in [I-D.ietf-idr-bgp-ls-sr-policy], SR policy information can be used by external components for path computation, re-optimization, service placement, network visualization, etc. A Network Resource Partition (NRP) is a network resource attribute associated with the SR policy. It is also an important attribute of the SR policy and needs to be reported to the external components. The notification of SR policy with NRP information is also used for the same function. 2. Why BGP-LS in BGP is the best protocol to pass this state. [Ran]: When reporting SR Policy information, the corresponding protocol is BGP-LS. As an attribute of SR Policy, NRP is reported together with the SR Policy information. Problem 2: Why the security considerations in this draft are sufficient when they only reference RFC9552 and RFC4271. [Ran]: A Network Resource Partition (NRP) also an important attribute of the SR policy and needs to be reported to the external components. The security considerations of BGP-LS SR policy [I-D.ietf-idr-bgp-ls-sr-policy] also apply to this document. Will update it. Best Regards, Ran From: SusanHares <shares@ndzh.com> To: idr@ietf.org <idr@ietf.org>; Cc: 陈然00080434;Dongjie (Jimmy) <jie.dong@huawei.com>;赵德涛10132546;龚立艳 <gongliyan@chinamobile.com>;zhuyq8@chinatelecom.cn <zhuyq8@chinatelecom.cn>; Date: 2024年05月15日 10:19 Subject: draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pre-Adoption Shepherd's review Draft: draft-chen-idr-bgp-ls-sr-policy-nrp-05 Status: Almost ready for adoption TEAS checks: The concept of NRP – has been OKed by TEAS. The IDR chairs will validate section 1 with the TEAS and MPLS chairs prior to adopting the draft. Problem 1: Authors need to provide additional information on the following comment in section 1: “This document defines a new TLV to enable the headend to report the configuration and the states of an SR Policy carrying the NRP information by using BGP-LS”. The authors should indicate why: The headend needs to report the configuration and the states of an SR Policy carrying NRP information. Why BGP-LS in BGP is the best protocol to pass this state. Problem 2: Why the security considerations in this draft are sufficient when they only reference RFC9552 and RFC4271. The IDR chairs welcome a presentation on this draft at the 5/20/2024 interim. Cheerily, Susan Hares
- [Idr] draft-chen-idr-bgp-ls-sr-policy-nrp-05 - Pr… Susan Hares
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-05 … chen.ran
- [Idr] continue discussion //Re: draft-chen-idr-bg… chen.ran
- [Idr] Re: continue discussion //Re: draft-chen-id… Joel Halpern
- [Idr] Re: continue discussion //Re: draft-chen-id… chen.ran
- [Idr] Re: continue discussion //Re: draft-chen-id… Dongjie (Jimmy)
- [Idr] Re: continue discussion //Re: draft-chen-id… Ketan Talaulikar
- [Idr] Re: continue discussion //Re: draft-chen-id… chen.ran
- [Idr] Re: continue discussion //Re: draft-chen-id… Dongjie (Jimmy)