IETF Logo Mail Archive

Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)

Zhangka <zhangka@huawei.com> Thu, 30 March 2023 03:30 UTC

Return-Path: <zhangka@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 897C3C151700 for <idr@ietfa.amsl.com>; Wed, 29 Mar 2023 20:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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=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 AXIFk5GJ--Ee for <idr@ietfa.amsl.com>; Wed, 29 Mar 2023 20:30:15 -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 891F4C15171B for <idr@ietf.org>; Wed, 29 Mar 2023 20:30:15 -0700 (PDT)
Received: from lhrpeml100003.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Pn85X4Dbmz6J7Qk for <idr@ietf.org>; Thu, 30 Mar 2023 11:28:32 +0800 (CST)
Received: from kwepemi100008.china.huawei.com (7.221.188.57) 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.21; Thu, 30 Mar 2023 04:30:11 +0100
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by kwepemi100008.china.huawei.com (7.221.188.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 30 Mar 2023 11:30:09 +0800
Received: from kwepemi500004.china.huawei.com ([7.221.188.17]) by kwepemi500004.china.huawei.com ([7.221.188.17]) with mapi id 15.01.2507.021; Thu, 30 Mar 2023 11:30:09 +0800
From: Zhangka <zhangka@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
Thread-Index: AdlL+RJPqJsgTki3TX6JUXZxZXhGxAWvclXw
Date: Thu, 30 Mar 2023 03:30:09 +0000
Message-ID: <19ee2cc2fcac45c7a656d67d22d1f22b@huawei.com>
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.153.199]
Content-Type: multipart/alternative; boundary="_000_19ee2cc2fcac45c7a656d67d22d1f22bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VDjbRxq9UBXOHDB9UuQzQND4TzM>
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, 30 Mar 2023 03:30:19 -0000

Hi, all

NRP is an important attribute of SR Policy, and the headend node of SR Policy candidate path need this to information to steer the traffic to the specified NRP.
So I support the adoption call of this draft.

Regards,
Ka



From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, March 1, 2023 12:49 PM
To: idr@ietf.org
Subject: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)

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.

v2.23.0 | Report a Bug | By Email