[spring] Re: Re: Ask SPRING WG for review draft-liu-spring-sr-policy-flexible-path-selection
Yisong Liu <liuyisong@chinamobile.com> Wed, 11 December 2024 06:23 UTC
Return-Path: <liuyisong@chinamobile.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0857FC1516F3; Tue, 10 Dec 2024 22:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.752
X-Spam-Level:
X-Spam-Status: No, score=-0.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.001, HDRS_MISSP=1.85, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRTs3CfSt-tQ; Tue, 10 Dec 2024 22:23:23 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta6.chinamobile.com [111.22.67.139]) by ietfa.amsl.com (Postfix) with ESMTP id 30F2BC1519B6; Tue, 10 Dec 2024 22:23:16 -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-app05-12005 (RichMail) with SMTP id 2ee567592fc9fa8-04fcc; Wed, 11 Dec 2024 14:23:05 +0800 (CST)
X-RM-TRANSID: 2ee567592fc9fa8-04fcc
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-PC (unknown[10.2.51.63]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee467592fc787d-2091d; Wed, 11 Dec 2024 14:23:05 +0800 (CST)
X-RM-TRANSID: 2ee467592fc787d-2091d
MIME-Version: 1.0
x-PcFlag: 3d5ee0f7-97da-434f-a9dc-3d3e80983e51_5_189396
X-Mailer: PC_RICHMAIL 2.9.57
Date: Wed, 11 Dec 2024 14:23:03 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: Joel Halpern <jmh@joelhalpern.com>, spring <spring@ietf.org>
Message-ID: <202412111423032663948659@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart-1631018637_=----"
Message-ID-Hash: QC64BTRT63FN4EL6CQBPT6MWLSPMWR2U
X-Message-ID-Hash: QC64BTRT63FN4EL6CQBPT6MWLSPMWR2U
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] Re: Re: Ask SPRING WG for review draft-liu-spring-sr-policy-flexible-path-selection
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/EwUrXnjVZg3r6SDw8jjB83rUUHM>
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 Joel, Thank you for your comments. I want to provide some clarity regarding the purpose and scope of this draft . This draft tackles the scenario where multiple paths are available, and the need arises to switch paths based on their quality metrics. It is not intended to replace the controller's role in global optimization but rather to complement it by allowing for local, quality-driven responses to link degradation. The draft specifically addresses the ability to switch to alternative paths within a strategy when the current path fails to meet specified link quality criteria such as bandwidth, delay, or packet loss. In cases where a controller issues an SR Policy that encompasses multiple paths, if a path's link quality does not meet the set requirements, it will switch to a backup path for forwarding. Essentially, this draft resolves the forwarding status of SR Policy paths, facilitating a switch based on link quality. It is important to note that the overall path optimization remains under the purview of the controller, which continues to make global decisions. This draft addresses the selection issue of multiple paths under an SR Policy, ensuring that the network can adapt to local conditions without overriding the controller's broader strategies. I'm not sure if I've explained everything clearly. If you have any further questions, please feel free to continue the discussion. Best Regards Yisong 发件人: Joel Halpern 时间: 2024/12/09(星期一)11:45 收件人: Yisong Liu;spring; 抄送人: draft-liu-spring-sr-policy-flexible-path-selection; 主题: Re: [spring] Ask SPRING WG for review draft-liu-spring-sr-policy-flexible-path-selection Looking at this draft, there seem to be two related aspects, one of which makes sense, and one of which needs work. As a participant, I can understand the general goal. And adjusting the path selection when component link issues reduce the overall available bandwidth, increase the end-to-end delay, or increase the expected jitter is understandable. I leave whether this is the right approach to that problem to those who have worked more closely with SR policies. However, if I read section 4.1 properly, it wants to change the path selection in response to observed parameters such as observed packet loss (frequently in practice caused by congestion.) On fortunately, distributed dynamic path selection based on parameters that are sensitive to traffic load has well-known problems with various responders adjusting resulting in simply moving the problem. If you have recognized this problem and I missed it, please cite RFC 2386 early in the document, and point to the resolution. If you have not addressed this problem, please either do so or restrict the applicability of this proposal. Delaying response is not sufficient. Yours, Joel On 12/8/2024 9:37 PM, Yisong Liu wrote: Dear WG members, With the rise of AI models, new intelligent computing services require enhanced network reliability, especially in quality-sensitive scenarios like storage-compute separation and real-time inference. The draft-liu-spring-sr-policy-flexible-path-selection offers flexible path switching for quality degradation, crucial for maintaining network performance. This draft proposed a new mechanism to specify multiple candidate paths for SR policies, allowing for more sophisticated traffic engineering. It supports dynamic path adjustments based on real-time network conditions, optimizing resource utilization and ensuring high service quality. This draft aims to provide network operators with greater flexibility and control over traffic routing in SR networks. We have just posted a new version. Please see the draft in the following link: https://datatracker.ietf.org/doc/draft-liu-spring-sr-policy-flexible-path-selection/ I hope you can review this draft and share your feedback. Welcome any questions and comments. Best Regards Yisong on behalf of co-authors _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-leave@ietf.org