[Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026)

Weiqiang Cheng <chengweiqiang@chinamobile.com> Mon, 11 May 2026 02:31 UTC

Return-Path: <chengweiqiang@chinamobile.com>
X-Original-To: pce@mail2.ietf.org
Delivered-To: pce@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5B913EC42E65; Sun, 10 May 2026 19:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778466706; bh=yi5MeHJRR9RDkz0M5UwFJI/lXUx5jQTBZndNA/0VGrI=; h=Date:From:To:Subject:References; b=y107BYbahLMFDPcuOWvC/MNxWZn/j2DJJDOE5VgZOEIjRq+zUbRb6SiC1+Uyal8xX VcLXfuMf2FQ/ZT3MWucxe305OPoAy8NbAOz22ilddrMRyaEJyRYsjcdIBACi8pSI59 P+k4gZNHbHXYkrnub6xobqmyZ/7lRmpRDCOMy0Nw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.687
X-Spam-Level:
X-Spam-Status: No, score=-1.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=chinamobile.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 E2Xzq72Ypn0U; Sun, 10 May 2026 19:31:42 -0700 (PDT)
Received: from cmccmta8.chinamobile.com (cmccmta8.chinamobile.com [111.22.67.151]) by mail2.ietf.org (Postfix) with ESMTP id DF229EC42E4E; Sun, 10 May 2026 19:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chinamobile.com; s=default; l=0; h=from:subject:message-id:to:mime-version; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=fKxnxO8WITW1EDf3PLRqUP4gw4sBL9TGNsELLW97rthXm/qpNbB7YPCWpz6Hm9tz24O/OqHBBY3Iu HCKn2sYj5/pGw/Rbt+Kq+u+BydISETm6csE5WQ0JKaOMj/wmHNtfbCdssQv4Lx7kFNgGvuLAbIsqhJ YPqucPZyrYpn2EvM=
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app06-12006 (RichMail) with SMTP id 2ee66a013f7f685-84080; Mon, 11 May 2026 10:31:28 +0800 (CST)
X-RM-TRANSID: 2ee66a013f7f685-84080
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from chengweiqiang (unknown[10.2.146.19]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee46a013f7fc0e-34191; Mon, 11 May 2026 10:31:28 +0800 (CST)
X-RM-TRANSID: 2ee46a013f7fc0e-34191
Date: Mon, 11 May 2026 10:31:26 +0800
From: Weiqiang Cheng <chengweiqiang@chinamobile.com>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>, spring <spring@ietf.org>, pce <pce@ietf.org>
References: <DM8PR08MB741323A62687BDCE44A2951DB33B2@DM8PR08MB7413.namprd08.prod.outlook.com>
X-Priority: 3
X-GUID: F10882C9-006B-46D2-BA6D-F817F21F7CB8
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.489[cn]
Mime-Version: 1.0
Message-ID: <2026051110312601484238@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart303803730755_=----"
Message-ID-Hash: 4FPWZTQU43YR6AIUD3YUOBCPXK3ORILO
X-Message-ID-Hash: 4FPWZTQU43YR6AIUD3YUOBCPXK3ORILO
X-MailFrom: chengweiqiang@chinamobile.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/l4SjXZloI6HKyrYjO7xHnc5wduE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>

Hi Sue and all,
I am not aware of any IPR associated with this document.
As a co-author, I support the publication of the document.

Thanks,
Weiqiang Cheng

 
From: Susan Hares
Date: 2026-05-11 03:46
To: idr@ietf. org; spring; Path Computation Element Discussion List
Subject: [Idr] WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026)
Greetings: 
 
This is a 3-week WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026).  The authors of draft-ietf-idr-sr-policy-seglist-id-09.txt should respond to this email with IPR statements.   
 
This IDR WG LC is being cross-posted to Spring, PCE, and SRv6ops.  This document’s WG LC needs input from these 3 WGs. 
 
IDR WG members should discuss this draft and include in their discussion an indication of “support” or “no Support”.   IDR members should consider the following: 
1) Is this document ready for publication? 
2) Does the segment list identifier specified at the candidate path (CP) scope help deployments? 
3) Are there any technical flaws in this document? 
 
Appendix A of this draft contains a “cross-WG” information regarding Spring and PCE.   This WG LC includes Spring and PCE to validate the cross-WG information.  In addition, SRV6ops will be informed of the WG LC. 
 
This draft limits the scope of the segment list identifier to a candidate path.  During January – March,  the spring WG discussed whether this should be limited to just the Candidate Path or whether the scope of Segment List ID as unique within the headend node.  The discussion is at: 
https://mailarchive.ietf.org/arch/msg/spring/JVzsniFIj3sSQ93HT4Sl4fbJDpE/
 
Spring WG – please review the author's decision to limit the BGP mechanism to a candidate path.  Does this limitation align with Spring’s view on the segment list identifier?   
 
PCE WG -  please check that the reference material related to draft-ietf-pce-multipath are correct and valid. 
 
Thank you, Susan Hares 
 
PS – the SRv6ops is an operational WG – so I will send notification and summarize results.