[spring] Follow-up on IETF 124 Presentation of draft-liu-spring-sr-policy-flexible-path-selection and draft clarification

Yisong Liu <liuyisong@chinamobile.com> Wed, 19 November 2025 01:26 UTC

Return-Path: <liuyisong@chinamobile.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 4D9998C1FD4D; Tue, 18 Nov 2025 17:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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
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 HAFr5K9bkLQh; Tue, 18 Nov 2025 17:26:49 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta6.chinamobile.com [111.22.67.139]) by mail2.ietf.org (Postfix) with ESMTP id D28FD8C1FD46; Tue, 18 Nov 2025 17:26:42 -0800 (PST)
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-app01-12001 (RichMail) with SMTP id 2ee1691d1cc9ba2-e759e; Wed, 19 Nov 2025 09:26:34 +0800 (CST)
X-RM-TRANSID: 2ee1691d1cc9ba2-e759e
X-RM-SPAM-FLAG: 00000000
Received: from liuyisong@chinamobile.com ( [10.1.6.55] ) by ajax-webmail-syy-spmd05-11015 (Richmail) with HTTP; Wed, 19 Nov 2025 09:26:34 +0800 (CST)
Date: Wed, 19 Nov 2025 09:26:34 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: spring-chairs <spring-chairs@ietf.org>, spring <spring@ietf.org>
Message-ID: <2b07691d0db1434-00050.Richmail.00005082154910795526@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_974523_1044873578.1763515594114"
X-Priority: 3
X-RM-TRANSID: 2b07691d0db1434-00050
X-PARTNER-PROJECT-ID: 0
X-RM-OA-ENC-TYPE: 0
X-RM-FontColor: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.5.01)
Message-ID-Hash: JKKYKU3H3PHC3W764TWAO75ASLHMTRHM
X-Message-ID-Hash: JKKYKU3H3PHC3W764TWAO75ASLHMTRHM
X-MailFrom: liuyisong@chinamobile.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: draft-liu-spring-sr-policy-flexible-path-selection <draft-liu-spring-sr-policy-flexible-path-selection@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Follow-up on IETF 124 Presentation of draft-liu-spring-sr-policy-flexible-path-selection and draft clarification
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/uQDf-_R64MoR70NJ8A4CnPIBB58>
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>


Dear Chairs and WG,






Thank you for the valuable feedback following our presentation at IETF 124. We would like to offer some clarification to ensure our draft's purpose is properly understood.


In our latest revision, we have referenced draft-karboubi-spring-sr-policy-eligibility, though we wish to emphasize that the two drafts serve distinctly different purposes. The eligibility draft introduces new concepts for path qualification, while our draft focuses specifically on defining a mechanism for path selection and switching based on forwarding performance metrics such as latency, jitter, and bandwidth. Our approach predefines quality requirements for SR policies and enables rapid path selection or switching when real-time monitoring indicates these requirements are no longer met. The reference to eligibility is included to maintain compatibility with the SR Policy architecture defined in RFC 9256.


We believe there is no  significant overlap between our draft and eligibility draft and see value in advancing them independently. We would appreciate if the chairs can give the guidance on how to proceed with our draft. Additionally, we have formally requested an adoption call during our presentation and would be grateful if the chairs can help to schedule this.


Welcome all comments and suggestions regarding our draft and look forward to continued feedback from the working group.






Best regards,
Yisong on behalf of co-authors