[mpls] Re: Ketan Talaulikar's No Objection on draft-ietf-mpls-spring-lsp-ping-path-sid-10: (with COMMENT)
xiao.min2@zte.com.cn Thu, 29 May 2025 07:02 UTC
Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: mpls@mail2.ietf.org
Delivered-To: mpls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 67C6E2E3B14E; Thu, 29 May 2025 00:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 KkLaMrvUQb95; Thu, 29 May 2025 00:02:00 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3948E2E3B144; Thu, 29 May 2025 00:02:00 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4b7HNg2d09z8RTZL; Thu, 29 May 2025 15:01:55 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl1.zte.com.cn with SMTP id 54T71jmP032016; Thu, 29 May 2025 15:01:45 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Thu, 29 May 2025 15:01:48 +0800 (CST)
Date: Thu, 29 May 2025 15:01:48 +0800
X-Zmail-TransId: 2afe6838065cffffffffa62-0bd72
X-Mailer: Zmail v1.0
Message-ID: <202505291501483861IVNdcD1ky8vlwagtiXJL@zte.com.cn>
In-Reply-To: <CAH6gdPxT7NoUVBfihqgr81ApJT6j19E3P14urq0aTu45D2q=YA@mail.gmail.com>
References: CAH6gdPwAk4c-qZrgWm=xGqe59XNDqaTyqj5Meu0C-LBtkb61Qw@mail.gmail.com,20250529142908286WdE0kb-iSvI9R3Cfet9wF@zte.com.cn,CAH6gdPxT7NoUVBfihqgr81ApJT6j19E3P14urq0aTu45D2q=YA@mail.gmail.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: ketant.ietf@gmail.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 54T71jmP032016
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 68380663.001/4b7HNg2d09z8RTZL
Message-ID-Hash: DQ73KS6D4IGWWVOWPTEXFWCTVIDOQWA3
X-Message-ID-Hash: DQ73KS6D4IGWWVOWPTEXFWCTVIDOQWA3
X-MailFrom: xiao.min2@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: iesg@ietf.org, draft-ietf-mpls-spring-lsp-ping-path-sid@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org, tsaad@cisco.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mpls] Re: Ketan Talaulikar's No Objection on draft-ietf-mpls-spring-lsp-ping-path-sid-10: (with COMMENT)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/in7TiI78kFPWtjhzNbGtdvyB8ZY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>
Hi Ketan, Thank you for the prompt response. Please see inline. Original From: KetanTalaulikar <ketant.ietf@gmail.com> To: 肖敏10093570; Cc: iesg@ietf.org <iesg@ietf.org>;draft-ietf-mpls-spring-lsp-ping-path-sid@ietf.org <draft-ietf-mpls-spring-lsp-ping-path-sid@ietf.org>;mpls-chairs@ietf.org <mpls-chairs@ietf.org>;mpls@ietf.org <mpls@ietf.org>;tsaad@cisco.com <tsaad@cisco.com>; Date: 2025年05月29日 14:39 Subject: Re: Ketan Talaulikar's No Objection on draft-ietf-mpls-spring-lsp-ping-path-sid-10: (with COMMENT) Hi Xiao Min, This is about the only remaining point. The other one is left to the WG. As clarified by you, there is a data plane and control plane aspect. My concern is that the current text is half baked as it references only the (data plane) verification of PSID reaching the tailend but not the rest about validating the context associated with that PSID (i.e., the control plane part). Do you see a problem in updating the text to clarify what you stated in your response below? [XM]>>> This part of text was first added by me and then improved by Med to address his another DISCUSS point. NEW text that was added by me: Among them,checking correct operation of the PSID means that the initiator can useLSP Ping to check whether the PSID reached the responder and got processedby the responder correctly; verifying the PSID against the control planemeans that the initiator can use LSP Ping to verify whether the responderhas the same understanding with the initiator on how the PSID was constructedby the control plane.NEW text that was proposed by Med: Checking correct operation means that an initiator can use LSP Ping to check whether a PSID reached the intended node and got processed by that node correctly. Moreover, verifying a PSID against the control plane means that the initiator can use LSP Ping to verify whether a given node has the same understanding with the initiator on how the PSID was constructed by the control plane.Overall, this part of text contains two sentences, one is to clarify the check of the data plane, another is to clarify the verification of the data plane against the control plane. Cheers, Xiao Min Thanks, Ketan On Thu, May 29, 2025 at 11:59 AM <xiao.min2@zte.com.cn> wrote: > Hi Ketan, > > > Thank you for the prompt reply. > > Please see inline with [XM-2]>>>. > Original > *From: *KetanTalaulikar <ketant.ietf@gmail.com> > *To: *肖敏10093570; > *Cc: *iesg@ietf.org <iesg@ietf.org>; > draft-ietf-mpls-spring-lsp-ping-path-sid@ietf.org < > draft-ietf-mpls-spring-lsp-ping-path-sid@ietf.org>;mpls-chairs@ietf.org < > mpls-chairs@ietf.org>;mpls@ietf.org <mpls@ietf.org>;tsaad@cisco.com < > tsaad@cisco.com>; > *Date: *2025年05月29日 12:59 > *Subject: **Re: Ketan Talaulikar's No Objection on > draft-ietf-mpls-spring-lsp-ping-path-sid-10: (with COMMENT)* > Hi Xiao Min, > > Thanks for your quick response. Please check inline below for my > follow-up/clarification. I've trimmed out the parts where we have converged > > [XM-2]>>> The following text was truncated by my mailbox, so pasted from > MPLS archive. > > On Thu, May 29, 2025 at 7:52 AM <xiao.min2@zte.com.cn> wrote: > > > Hi Ketan, > > > > > > Thanks for clearing your DISCUSS and carefully reviewing the -10 version. > > > > I've posted a new -11 version attempting to address your comments. Link as > > below. > > > > > > <https://datatracker.ietf.org/doc/html/draft-ietf-mpls-spring-lsp-ping-path-sid-11> > > https://datatracker.ietf.org/doc/html/draft-ietf-mpls-spring-lsp-ping-path-sid-11> > > > > < trimmed > > > 100 verify the PSID against the control plane. Checking correct > > > > 101 operation means that an initiator can use LSP Ping to check whether a > > 102 PSID reached the intended node and got processed by that node > > 103 correctly. Moreover, verifying a PSID against the control plane > > > > > > <major> PSID is not about getting to the correct endpoint/tailend node. That > > > > is the property of the Node SID of that node. The PSID is about identification > > of the correct context of the SR Path on that endpoint/tailend node - is it > > matching the correct SL, CP, or SR Policy. > > > > [XM]>>> I would argue that comparing to a data packet carrying PSID, an > > LSP Ping packet carrying PSID can be used differently, because for LSP Ping > > there is a query/response mechanism. I suggest to remain the text as is
- [mpls] Re: Ketan Talaulikar's No Objection on dra… mohamed.boucadair
- [mpls] Ketan Talaulikar's No Objection on draft-i… Ketan Talaulikar via Datatracker
- [mpls] Re: Ketan Talaulikar's No Objection on dra… Ketan Talaulikar
- [mpls] Re: Ketan Talaulikar's No Objection on dra… xiao.min2
- [mpls] Re: Ketan Talaulikar's No Objection on dra… Ketan Talaulikar
- [mpls] Re: Ketan Talaulikar's No Objection on dra… xiao.min2
- [mpls] Re: Ketan Talaulikar's No Objection on dra… Ketan Talaulikar
- [mpls] Re: Ketan Talaulikar's No Objection on dra… xiao.min2
- [mpls] Re: Ketan Talaulikar's No Objection on dra… Ketan Talaulikar
- [mpls] Re: Ketan Talaulikar's No Objection on dra… xiao.min2
- [mpls] Re: Ketan Talaulikar's No Objection on dra… Ketan Talaulikar