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

Liurubing <liurubing@h3c.com> Wed, 13 May 2026 07:32 UTC

Return-Path: <liurubing@h3c.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 41B80ED96417; Wed, 13 May 2026 00:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778657523; bh=ETtrVoCAdq1QrDDfKudqvElR2v0DoTJHaoJJ4hV7B2U=; h=From:To:Subject:Date:References:In-Reply-To; b=eYGpFCo3kHMofjrntx2Dt6Vah3HVv3cK8XEPcslPtDGCHwsQ7yy3Tck8t5I29YqDh dXBZyHChQ4dch7Ly1YBVVXOulfTm9HTeYl5pDHN8oKI7k31CgOZnzTWHSJdm/pFHGE hMwvv+Si5SZSyEiX1vStX6fSlngggzgEJ/vi0f0o=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.803
X-Spam-Level:
X-Spam-Status: No, score=0.803 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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] autolearn=ham autolearn_force=no
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 iF6xNijqIeyG; Wed, 13 May 2026 00:31:59 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (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 99246ED9640C; Wed, 13 May 2026 00:31:55 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 64D7VVFh049356; Wed, 13 May 2026 15:31:31 +0800 (+08) (envelope-from liurubing@h3c.com)
Received: from DAG6EX12-BJD.srv.huawei-3com.com (unknown [10.153.34.14]) by mail.maildlp.com (Postfix) with ESMTP id 04B4020045B5; Wed, 13 May 2026 15:43:34 +0800 (CST)
Received: from DAG6EX10-BJD.srv.huawei-3com.com (10.153.34.12) by DAG6EX12-BJD.srv.huawei-3com.com (10.153.34.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Wed, 13 May 2026 15:31:31 +0800
Received: from DAG6EX10-BJD.srv.huawei-3com.com ([fe80::ade6:b219:16f8:9aa8]) by DAG6EX10-BJD.srv.huawei-3com.com ([fe80::ade6:b219:16f8:9aa8%6]) with mapi id 15.02.1258.027; Wed, 13 May 2026 15:31:31 +0800
From: Liurubing <liurubing@h3c.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>, spring <spring@ietf.org>, Path Computation Element Discussion List <pce@ietf.org>
Thread-Topic: WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026)
Thread-Index: AdzgsmfagOaVAvKURLK/er3r9lwPOwB95nzg
Date: Wed, 13 May 2026 07:31:31 +0000
Message-ID: <212ffcbc2af643b1aaf5c85f63dd8093@h3c.com>
References: <DM8PR08MB741323A62687BDCE44A2951DB33B2@DM8PR08MB7413.namprd08.prod.outlook.com>
In-Reply-To: <DM8PR08MB741323A62687BDCE44A2951DB33B2@DM8PR08MB7413.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.209.9]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_212ffcbc2af643b1aaf5c85f63dd8093h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 64D7VVFh049356
Message-ID-Hash: JP5R6UQ4FX2ECDHGXUK7S3U56655TGLS
X-Message-ID-Hash: JP5R6UQ4FX2ECDHGXUK7S3U56655TGLS
X-MailFrom: liurubing@h3c.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: 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/mBgIGT7lPRW7OwoPU4GML_sQqtY>
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>

I support the publication of the document.

My answers to the three questions are:
1) Is this document ready for publication?
Yes.
2) Does the segment list identifier specified at the candidate path (CP) scope help deployments?
Yes.
3) Are there any technical flaws in this document?
No.

From: Susan Hares <shares@ndzh.com>
Sent: Monday, May 11, 2026 3:47 AM
To: idr@ietf. org <idr@ietf.org>; spring <spring@ietf.org>; Path Computation Element Discussion List <pce@ietf.org>
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.


-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出的个人或群组。
禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。
如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited.
If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!