IETF Logo Mail Archive

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

Chongfeng Xie <xiechf@chinatelecom.cn> Wed, 08 March 2023 05:48 UTC

Return-Path: <xiechf@chinatelecom.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 D892FC14CEED for <idr@ietfa.amsl.com>; Tue, 7 Mar 2023 21:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 ZAJLJMCGnKTk for <idr@ietfa.amsl.com>; Tue, 7 Mar 2023 21:48:44 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id F1343C14F74E for <idr@ietf.org>; Tue, 7 Mar 2023 21:48:43 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.188:36745.844613435
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-10.133.8.238 (unknown [172.18.0.188]) by chinatelecom.cn (HERMES) with SMTP id AA3722800D2; Wed, 8 Mar 2023 13:48:39 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([10.133.8.238]) by app0023 with ESMTP id d6f40735245f45ebbba51b3b0bff0c8f for shares@ndzh.com; Wed, 08 Mar 2023 13:48:41 CST
X-Transaction-ID: d6f40735245f45ebbba51b3b0bff0c8f
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 10.133.8.238
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Wed, 08 Mar 2023 13:48:39 +0800
From: Chongfeng Xie <xiechf@chinatelecom.cn>
To: Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
Message-ID: <202303081348392136066@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart368522087265_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/R3w0pOeP37Eh7TSqRxS8uuaJoiA>
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: Wed, 08 Mar 2023 05:48:46 -0000

Hi Sue,
 
I’ve read this document and support its adoption. It provides a useful mechanism to associate the SR policy candidate path with an NRP.
 
Best regards,

Chongfeng Xie

 
From: Susan Hares
Date: 2023-03-01 12:48
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