Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 13 April 2023 12:15 UTC
Return-Path: <jie.dong@huawei.com>
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 61181C140675 for <idr@ietfa.amsl.com>; Thu, 13 Apr 2023 05:15:03 -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_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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 GThI1kReHeVh for <idr@ietfa.amsl.com>; Thu, 13 Apr 2023 05:14:59 -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 38375C151B0C for <idr@ietf.org>; Thu, 13 Apr 2023 05:14:59 -0700 (PDT)
Received: from lhrpeml100003.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Pxz5J18l4z67L8m for <idr@ietf.org>; Thu, 13 Apr 2023 20:13:56 +0800 (CST)
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 13 Apr 2023 13:14:54 +0100
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi500017.china.huawei.com (7.221.188.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 13 Apr 2023 20:14:52 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2507.023; Thu, 13 Apr 2023 20:14:52 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>, "idr@ietf.org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
Thread-Index: AdlL+RJPqJsgTki3TX6JUXZxZXhGxAcyl6IlAU5QisA=
Date: Thu, 13 Apr 2023 12:14:52 +0000
Message-ID: <bdce022823774a3db669ffe5f1c4088d@huawei.com>
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com> <869041475.26224.1680811512321@mail.yahoo.com>
In-Reply-To: <869041475.26224.1680811512321@mail.yahoo.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.49.87]
Content-Type: multipart/alternative; boundary="_000_bdce022823774a3db669ffe5f1c4088dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6p_BxQcXd34bhVUa0AHwfdHtmgM>
Subject: Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2023 12:15:03 -0000
Hi Boris, Thanks for your support and comments. Sorry for the delayed response. Regarding the comments from Gyan and Dhruv, we will address them in next update. The first reason of associating NRP with SR policy CP is that the CP is the granularity of SR policy signaling in BGP, and each CP could become active according to the path selection rules. The second reason is that although it is recommended to have all the CPs associated with the same NRP, in some special cases the active and backup CPs may belong to different NRP. Hope this helps. Best regards, Jie From: Idr <idr-bounces@ietf.org> On Behalf Of Boris Hassanov Sent: Friday, April 7, 2023 4:05 AM To: idr@ietf.org; Susan Hares <shares@ndzh.com> Subject: Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14) Hi Sue and all, I read it and support the adoption of this draft. But with some comments. First of all agree with previous questions from Gyan and Dhruv (not only BGP use case but PCEP too, SR Algo and NRP, Section 3 definitely with MUST). Secondly, about association of NRP with SR Policy or a CP. As per RFC 9256 we have only one active CP in SR Policy, so what is the point for having other different NRPs for non active CPs? Thank you. SY, Boris On Wednesday, March 1, 2023 at 07:49:19 AM GMT+3, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote: This begins a 2 week WG adoption call for draft-dong-idr-sr-policy-nrp https://datatracker.ietf.org/doc/draft-dong-idr-sr-policy-nrp/ Each of the authors should respond to this message with an email indicating if they know of any IPR regarding this draft. The draft specifies an extension to BGP SR policy to Specify the NRP (network partition resources) that Than an SR Policy candidate path is associated with. In your discussion consider if this is a useful addition to the SR Policy candidate path. Cheerily, Sue =========== Full description from the draft Segment Routing (SR) Policy is a set of candidate paths, each consisting of one or more segment lists and the associated information. The header of a packet steered in an SR Policy is augmented with an ordered list of segments associated with that SR Policy. A Network Resource Partition (NRP) is a subset of network resources allocated in the underlay network which can be used to support one or a group of IETF network slice services. In networks where there are multiple NRPs, an SR Policy may be associated with a particular NRP. The association between SR Policy and NRP needs to be specified, so that for service traffic which is steered into the SR Policy, the header of the packets can be augmented with the information associated with the NRP. An SR Policy candidate path can be distributed using BGP SR Policy. This document defines the extensions to BGP SR policy to specify the NRP which the SR Policy candidate path is associated with. _______________________________________________ Idr mailing list Idr@ietf.org<mailto:Idr@ietf.org> https://www.ietf.org/mailman/listinfo/idr
- [Idr] Adoption call for - draft-dong-idr-sr-polic… Susan Hares
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Huzhibo
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Zhuangshunwan
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dongjie (Jimmy)
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… 庞冉(联通集团本部)
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Giuseppe Fioccola
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Chongfeng Xie
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… peng.shaofu
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… duzongpeng@foxmail.com
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Zhangka
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Gyan Mishra
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dhruv Dhody
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dongjie (Jimmy)
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dhruv Dhody
- [Idr] Clarifications on draft-ietf-idr-segment-ro… li_zhenqiang@hotmail.com
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… Ketan Talaulikar
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Boris Hassanov
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… li_zhenqiang@hotmail.com
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… Ketan Talaulikar
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… tanzhen (A)
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… Robert Raszuk
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dongjie (Jimmy)
- Re: [Idr] Adoption call for - draft-dong-idr-sr-p… Dongjie (Jimmy)
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… tanzhen (A)
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… Robert Raszuk
- Re: [Idr] Clarifications on draft-ietf-idr-segmen… li_zhenqiang@hotmail.com