Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
"庞冉(联通集团本部)" <pangran@chinaunicom.cn> Mon, 06 March 2023 13:20 UTC
Return-Path: <pangran@chinaunicom.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 4B3C2C14F6EC for <idr@ietfa.amsl.com>; Mon, 6 Mar 2023 05:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level:
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, 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=no 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 gj2cJ7EkFBsm for <idr@ietfa.amsl.com>; Mon, 6 Mar 2023 05:20:52 -0800 (PST)
Received: from senda.mailex.chinaunicom.cn (senda.mailex.chinaunicom.cn [123.138.59.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B349FC1516E0 for <idr@ietf.org>; Mon, 6 Mar 2023 05:20:39 -0800 (PST)
Received: from M10-XA-MLCEN01.MailSrv.cnc.intra (unknown [10.236.3.197]) by senda.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4PVfPd3b8wz6RC9t for <idr@ietf.org>; Mon, 6 Mar 2023 21:22:13 +0800 (CST)
Received: from smtpbg.qq.com (10.237.2.99) by M10-XA-MLCEN01.MailSrv.cnc.intra (10.236.3.197) with Microsoft SMTP Server id 15.0.1497.42; Mon, 6 Mar 2023 21:20:29 +0800
X-QQ-mid: Ymail-xx24b003-t1678108827tox
Received: from DESKTOP-TS2O28F (unknown [10.172.212.178]) by smtp.qq.com (ESMTP) with id ; Mon, 06 Mar 2023 21:20:27 +0800 (CST)
X-QQ-SSF: 01900000000000J0ZF10000A0000000
X-QQ-GoodBg: 0
From: "庞冉(联通集团本部)" <pangran@chinaunicom.cn>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>
Date: Mon, 06 Mar 2023 21:20:28 +0800
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.20.259[cn]
MIME-Version: 1.0
Message-ID: <202303062119525271164@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart777452427767_=----"
X-QQ-SENDSIZE: 520
Feedback-ID: Ymail-xx:chinaunicom.cn:mail-xx:mail-xx24b003-zhyw47w
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/HaIKzI8vYS8lXGQZRkHgvfkV544>
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: Mon, 06 Mar 2023 13:20:53 -0000
Hi Sue, As a coauthor, I support the adoption of this document. I’m not aware of any IPR that applies to it. Best regards, Pang Ran. From: Susan Hares<mailto:shares@ndzh.com> Date: 2023-03-01 12:48 To: idr@ietf.org<mailto: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. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.
- [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