[Pce] Re: [Internet][spring] WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026)
"wisdomtan(谭智)" <wisdomtan@tencent.com> Tue, 19 May 2026 12:43 UTC
Return-Path: <wisdomtan@tencent.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 03175F0B18D4; Tue, 19 May 2026 05:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779194596; bh=SE5XSjHMSYoL1bD2KjVeF0Qq21/GENAGIyMJcqvN3cY=; h=From:To:Subject:Date; b=dYt6MgUd2o+GA/dZmGQ1w0eoS55qZd6Ii0xMMUZqNGf42UKM4O30x0MY1QPhJVYPj 6CLN8naeg76dpFZQQIZPHsHSPpK3+apzHqxqzvy9qTPEUW0SUoSN8JwDn+sxoO1e3r y4k7H19riQzW+7/go+zGLNJIr1sBBNdAT/WD7IRQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 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, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=tencent.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 a5DXrtONa7d5; Tue, 19 May 2026 05:43:11 -0700 (PDT)
Received: from smtpbgbr1.qq.com (smtpbgbr1.qq.com [54.207.19.206]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CFDE6F0B18C9; Tue, 19 May 2026 05:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tencent.com; s=s201512; t=1779194565; bh=/NU4zf2Ids9cf2I9eLFcHwZzGA5PfTLWBW8Lyo6+wkI=; h=From:To:Subject:Mime-Version:Date:Message-ID; b=RM1l479oCzBLQTp4VJRu9Y9OvaOiTowNFpbcyREDSapgJZnNPT+ct34ThL4KYNkW0 t/ACFCAWhTu3WxMcnWyH1WmcVnYuT2IAhLs8twRjhYW922PPEfNIJnGgfOw4OLBI7s oV1Uu/MuAF+9xGhlzJm2vHxegf/k6dcMLoHGoEpw=
EX-QQ-RecipientCnt: 4
X-QQ-FEAT: D4aqtcRDiqR+OAhJ48GeF84p35fTYJCpaPbxx7Rfw/Q=
X-QQ-SSF: 0040000000000020
X-QQ-WAPMAIL: 1
X-QQ-BUSINESS-ORIGIN: 2
X-QQ-Originating-IP: qlN22U20LRCZduk3IwUB2qtL20gOVGvEVLzMD9/iTkE=
X-Originating-IP: 114.244.197.172
X-QQ-STYLE:
X-QQ-mid: lv2gz3a-1t1779194558tec296578
From: "wisdomtan(谭智)" <wisdomtan@tencent.com>
To: Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>, spring <spring@ietf.org>, Path ComputationElement Discussion List <pce@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_6A0C5ABE_2799F3A0_538BD08C"
Content-Transfer-Encoding: 8bit
Date: Tue, 19 May 2026 20:42:38 +0800
X-Priority: 3
Message-ID: <tencent_143AA21343B39EAF3A687EF0@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-BIZMAIL-ID: 15634231280246974411
X-Address-Ticket: version=;type=;ticket_id=;id_list=;display_name=;session_id=;
X-QQ-SENDSIZE: 520
Received: from qq.com (unknown [127.0.0.1]) by smtp.qq.com (ESMTP) with SMTP id ; Tue, 19 May 2026 20:42:39 +0800 (CST)
Feedback-ID: lv:tencent.com:qybglogicsvrgz:qybglogicsvrgz3a-0
X-QQ-XMAILINFO: NMe51Z/yYga7Izyq43oJrCl6CIpKWkx+LsZQawi/S7LwWXHswR1H6T7r okp5W1NxCMu738Z4GKqjtLmrxh6I8K25CMxYuNXwrGVlcXaxM04kR0W5F3nsSCBHM8m+Wyx cbuF+MRpybtoTzkDepfS11d0ENfxXUYHv4s4cs8DsMMlWp8JiJzU6qFiDFD+TVz7PgPj+Q+ QcY7jfrHWDZ/6l2KIu525hsD5qIZrxIHlN2ThcNwFu8OjruUEeCAlzbLQBxPt6os5ca5X5k JCmE1q96VHTX3AOwoAhZcSsGWiiO0UTbwgciYgF5Ch1NXZ3/SECqQuHnPhoqIVEPDqOAUhg Gx6oNZGvI/mHENP95BZgepgX5HARJqL5Pu7ayBUCnjZViXWyDT0ucTde49V7I6MAEJuxlnz h4ZTJVlc4Vh6Tb90OglS68TJqyIY6exd2OK6/Xdit/sbblDybVVk6ZFTw+hvysGNdoaoZga 8h0CcCnyozdL8StSsWdQdv3Ibk9b7cSsjBITQjLXvjvBBj53Z1bM/Hu5pWISr8gJjoMV2LE uPpef29BADxL3BbUS5sm2iq7TC070Y66FrZ63UE4Gu1cyP+Qa38zuPa57EKAFiteamiTRFF bVBl8fJqG7OIP+Y490vpAyATW9+dm6EYF7AhLYE6gD1waoNVpyLqG/Z44g1RlBx3XnKA+z7 M9Oa0TvK2gx1q1drLI0Jk3GRY4ELKX7DOPpfk9AlkdqVschg+IF4ypDX9HfEg/cNKgihBN4 sTorTuG0cWFkZ+5LlPJKDfxt/fmY98WKoyAhk+a0tDWLkL8KWgT6SQTprbbjAQxKumsTeWL hifeQFMWeUNCYk8B1yv6w3G1aOv6FY4kAvDbRtcGiT2PFidTL7xsvhnAW12RK8hN1g01tgn RPrDgoZ2my/KyE4i0Gg1Id18emKiTamqVRK9nEYfApWYCtkiD5WU9tw4VaS25eE8hOPdodY Wr/XmKDJXASYHrla5o2E5FeULiK53BnK4HLQiWA3QNv0nhVJpT8Trs72qep2QJ7xf8aRCo8 a7hwpomNjA6IO5wrT+Ob1VRIEpEsPmLgtWpige2E/KPI8HwIyF5tNHvAolEiLaIF+XYrr7X JRMFwV/BNHge4m3larRSIk=
X-QQ-XMRINFO: OD9hHCdaPRBwH5bRRRw8tsiH4UAatJqXfg==
X-QQ-RECHKSPAM: 0
Message-ID-Hash: 3UIWVHELTOW2FSRBP24ULROFHQF2AU5T
X-Message-ID-Hash: 3UIWVHELTOW2FSRBP24ULROFHQF2AU5T
X-MailFrom: wisdomtan@tencent.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: [Internet][spring] 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/5OMInPi7aNFut5h1UsZNIJRiXns>
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 this document.
My responses to the three questions are provided below:
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?
Not found.
Thanks,
wisdom
腾讯
wisdomtan
wisdomtan@tencent.com
----------Reply to Message----------
On Mon, May 11, 2026 03:49 AM Susan Hares<shares@ndzh.com> wrote:
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.
- [Pce] WG LC for draft-ietf-idr-sr-policy-seglist-… Susan Hares
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… liu.yao71
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Weiqiang Cheng
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Yisong Liu
- [Pce] 回复: WG LC for draft-ietf-idr-sr-policy-segl… Zhanghaiyang
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… yimi zhang
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… zhang.zheng
- [Pce] Re: [spring] WG LC for draft-ietf-idr-sr-po… xiao.min2
- [Pce] [Idr] Re: [Idr] WG LC for draft-ietf-idr-sr… linchangwang
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… allan michael
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Alex Lee
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… Liurubing
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Nat Kao
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… zhuyq8@chinatelecom.cn
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… 高星(联通集团本部)
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Susan Hares
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… Yujia Gao
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… Dongjie (Jimmy)
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… linchangwang
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… Liurubing
- [Pce] Re: [Idr] WG LC for draft-ietf-idr-sr-polic… 汪江波
- [Pce] Re: [Internet][spring] WG LC for draft-ietf… wisdomtan(谭智)
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… Hongwei Li
- [Pce] Re: WG LC for draft-ietf-idr-sr-policy-segl… Susan Hares