[spring] Re: Call for adoption: draft-jiang-spring-sr-policy-nrp-05 (Ends 2026-02-02)

JinMing LI <lijinming1836@163.com> Mon, 26 January 2026 06:35 UTC

Return-Path: <lijinming1836@163.com>
X-Original-To: spring@mail2.ietf.org
Delivered-To: spring@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id CC752ACEFD3A; Sun, 25 Jan 2026 22:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=163.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vtvf2xPZlIPv; Sun, 25 Jan 2026 22:35:12 -0800 (PST)
Received: from m16.mail.163.com (m16.mail.163.com [220.197.31.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1E259ACEFD2B; Sun, 25 Jan 2026 22:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:To:Subject:Content-Type:MIME-Version: Message-ID; bh=tD5DU0sqH2v2u4KSgdv0QgM1MRbBp2jTD6MHFixwxKQ=; b=M +n2h+3A+oz8pscWYOWlTj0BmnCW6Q6g9TJj1Lx8fSMVzDFeTcMytWKXVFd1HMqAB ol5DJzQ2OLNOY5NjRNGPWJC7ps68Ug4xrelHX0ELBP9d1xjaWiyxCmkCo8EoFCUf AJpiOOPOaDeaJkP7sNGOb78/RUaAKy6g2ZWDca5M7k=
Received: from lijinming1836$163.com ( [117.133.22.26] ) by ajax-webmail-wzpm-k8s-gz (Coremail) ; Mon, 26 Jan 2026 14:34:56 +0800 (GMT+08:00)
X-Originating-IP: [117.133.22.26]
Date: Mon, 26 Jan 2026 14:34:56 +0800
From: JinMing LI <lijinming1836@163.com>
To: "spring@ietf.org" <spring@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2023.4-cmXT build 20250911(16116b36) MailMasterMac/4.17.24.1343_(26.2.0) Copyright (c) 2002-2026 www.mailtech.cn 163com
In-Reply-To: <176884532489.659941.6837288950663680017@dt-datatracker-865585c994-4fgh4>
References: <176884532489.659941.6837288950663680017@dt-datatracker-865585c994-4fgh4>
X-NTES-SC: AL_Qu2dC/ibtkoi4CGQY+kfmUgQge89W8uyuP4k1IZVN5B+jBjp3j8scVN8Jn3R3t+fNiOqvymdSyZh+8VrW4Rzb5Ah2liZHwV1YziQjmxYqx55Jg==
Content-Type: multipart/alternative; boundary="----=_Part_3101975_645637836.1769409296194"
MIME-Version: 1.0
Message-ID: <6f396ffd.bfc9e.19bf9033742.Coremail.lijinming1836@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD3z_AQC3dpFLZOAA--.58490W
X-CM-SenderInfo: polmx05plqwiqytwqiywtou0bp/xtbC2xD+wGl3CxCJ4AAA3Z
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: UKK4R5WEQQ7D63NCSKBT5CCSLTXEZ3OQ
X-Message-ID-Hash: UKK4R5WEQQ7D63NCSKBT5CCSLTXEZ3OQ
X-MailFrom: lijinming1836@163.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "draft-jiang-spring-sr-policy-nrp@ietf.org" <draft-jiang-spring-sr-policy-nrp@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: Call for adoption: draft-jiang-spring-sr-policy-nrp-05 (Ends 2026-02-02)
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/-xAUZ_y5jPeR4I7HKvtwO9bfAuI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>

hi wg,


I support the adoption of draft-jiang-spring-sr-policy-nrp-05 by the SPRING WG.


The document clearly defines the association between SR Policy and Network Resource Partitions (NRPs), which is essential for deterministic forwarding and network slicing. 


Best regards
jinming
|
JinMing LI
China Mobile
+8618810926581
lijinming@chinamobile.com
BeiJing China
|


---- Replied Message ----
| From | Alvaro Retana via Datatracker<noreply@ietf.org> |
| Date | 01/20/2026 01:55 |
| To | <spring@ietf.org> ,
<spring-chairs@ietf.org> ,
<draft-jiang-spring-sr-policy-nrp@ietf.org> |
| Subject | [spring] Call for adoption: draft-jiang-spring-sr-policy-nrp-05 (Ends 2026-02-02) |
This message starts a spring WG Call for Adoption of:
draft-jiang-spring-sr-policy-nrp-05

This Working Group Call for Adoption ends on 2026-02-02

Abstract:
Segment Routing (SR) Policy is a set of candidate paths, each
consisting of one or more segment lists and the associated
information.  A Network Resource Partition (NRP), is a subset of the
resources and associated policies in the underlay network.  In SR
networks with multiple NRPs, an SR Policy can be associated with a
particular NRP.  In that case, SR Policy can be used for steering and
forwarding traffic which is mapped to the NRP, so that the packets
can be processed with the subset of network resources and policy of
the NRP for guaranteed performance.  Thus the association between SR
Policy and NRP needs to be specified.

This document defines extensions to the SR Policy Architecture to
allow the association of the SR Policy candidate paths with NRPs.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the spring WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.


[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-jiang-spring-sr-policy-nrp/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-jiang-spring-sr-policy-nrp-05.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-jiang-spring-sr-policy-nrp-05

_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-leave@ietf.org