IETF Logo Mail Archive

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

Huzhibo <huzhibo@huawei.com> Fri, 03 March 2023 09:15 UTC

Return-Path: <huzhibo@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 E47A8C151B06 for <idr@ietfa.amsl.com>; Fri, 3 Mar 2023 01:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 z68I4mYQq_l7 for <idr@ietfa.amsl.com>; Fri, 3 Mar 2023 01:15:55 -0800 (PST)
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 97ECDC14F744 for <idr@ietf.org>; Fri, 3 Mar 2023 01:15:55 -0800 (PST)
Received: from lhrpeml500003.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PShz21l2Gz67PjK for <idr@ietf.org>; Fri, 3 Mar 2023 17:10:54 +0800 (CST)
Received: from canpemm500009.china.huawei.com (7.192.105.203) by lhrpeml500003.china.huawei.com (7.191.162.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Fri, 3 Mar 2023 09:15:52 +0000
Received: from canpemm500009.china.huawei.com (7.192.105.203) by canpemm500009.china.huawei.com (7.192.105.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Fri, 3 Mar 2023 17:15:50 +0800
Received: from canpemm500009.china.huawei.com ([7.192.105.203]) by canpemm500009.china.huawei.com ([7.192.105.203]) with mapi id 15.01.2507.021; Fri, 3 Mar 2023 17:15:50 +0800
From: Huzhibo <huzhibo@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+RJPqJsgTki3TX6JUXZxZXhGxABt4gRQ
Date: Fri, 03 Mar 2023 09:15:50 +0000
Message-ID: <7d34375fdfa1480c954e1894fd357545@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.202.45]
Content-Type: multipart/alternative; boundary="_000_7d34375fdfa1480c954e1894fd357545huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/JVBkPrp3y1eAmgoANrQdMKtOa2M>
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: Fri, 03 Mar 2023 09:15:57 -0000

Hi Sue,

As a coauthor I support the adoption of this document. I'm not aware of any undisclosed IPR.

Thanks

Zhibo Hu

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