As responsible AD confirmed. Jim
From: [email protected] <[email protected]> Date: Monday, October 20, 2025 at 8:16 PM To: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, James Guichard <[email protected]>, [email protected] <[email protected]> Subject: Re: [AD] AUTH48: RFC-to-be 9884 <draft-ietf-mpls-spring-lsp-ping-path-sid-13> for your review Authors and *AD, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the source file. 1) <!--[rfced] Please note that we have updated the title as follows (to include articles). Original Document Title: Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane Current: A Label Switched Path Ping for the Segment Routing Path Segment Identifier with an MPLS Data Plane --> 2) <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fsearch&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811035563%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=q%2FjWqsWp2wDEaCXHDjfauU1ZgkGrgcO77jAGLepyv6g%3D&reserved=0<https://www.rfc-editor.org/search>. --> 3) <!--[rfced] Please review the use of the two citations in the sentence below. RFC 8029 is "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" while RFC 8287 is "Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes". Original: Procedure for LSP Ping [RFC8029] as defined in Section 7.4 of [RFC8287] is also applicable to PSID, and this document appends existing step 4a with a new step 4b specific to PSID. --> 4) <!--[rfced] *ADs - Please confirm that no "Updates" relationship to RFC 8287 should be indicated in the header/Abstract/metadata of the document with the following text (and all of Section 4.1) in mind: Original: Procedure for LSP Ping [RFC8029] as defined in Section 7.4 of [RFC8287] is also applicable to PSID, and this document appends existing step 4a with a new step 4b specific to PSID. --> 5) <!--[rfced] Please review our following update and let us know any objections. Original: As specified in Section 2 of [RFC9545], a PSID is used to identify a segment list, some or all segment lists in a Candidate path or an SR policy, so six different Target FEC Stack sub-TLVs need to be defined for PSID. Current: As specified in Section 2 of [RFC9545], a PSID is used to identify a segment list and/or some or all segment lists in a Candidate path or an SR policy, so six different Target FEC Stack sub-TLVs need to be defined for PSID. --> 6) <!--[rfced] Please review the following uses of "PSID FEC Stack sub-TLV" and "malformed FEC Stack sub-TLV". Other uses of "FEC Stack sub-TLV" begin with "Target". Original: ...validity checks on the content of the PSID FEC Stack sub-TLV. and If a malformed FEC Stack sub-TLV is received... Perhaps: ...validity checks on the content of the PSID Target FEC Stack sub-TLV. and If a malformed Target FEC Stack sub-TLV is received... --> 7) <!--[rfced] Please confirm that the following are the general concepts and not field names (note that these are examples, more instances occur): Original: * Validate that the signaled or provisioned headend, color, and endpoint, for the PSID, matches with the corresponding fields in the received SR Policy Associated PSID - IPv4 sub- TLV. Perhaps: * Validate that the signaled or provisioned Headend, Color, and Endpoint fields for the PSID match with the corresponding fields in the received SR Policy Associated PSID - IPv4 sub-TLV. Original: * Validate that the signaled or provisioned headend, color, endpoint, originator, and discriminator, for the PSID, matches with the corresponding fields in the received SR Candidate Path Associated PSID - IPv4 sub-TLV. Perhaps: * Validate that the signaled or provisioned Headend, Color, Endpoint, Originator, and Discriminator fields for the PSID match with the corresponding fields in the received SR Candidate Path Associated PSID - IPv4 sub-TLV. --> 8) <!--[rfced] Please note that we have updated the reference to draft-ietf-idr-bgp-ls-sr-policy-17 to point to the RFC-to-be: as this I-D is currently in AUTH48 (with nearly all approvals complete), we assume it will move to publication prior to the publication of this document. Please let us know how you would like to proceed if RFC-to-be 9857 is not published before this document (i.e., return to the I-D form of the reference or wait for the publication of 9857). --> 9) <!--[rfced] We had the following questions/comments related to abbreviation use throughout the document: a) Please note that abbreviations have been expanded upon first use. Please review and confirm all expansions inserted appear as desired. b) Please note that we will update to use the following abbreviations, instead of their expanded forms, after the first use in accordance with https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fstyleguide%2Fpart2%2F%23exp_abbrev&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811077325%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wuS4oc9ti5HcEM6I0Fe3bQwLls%2FJ1PJtJGm6%2BLNxclk%3D&reserved=0:<https://www.rfc-editor.org/styleguide/part2/#exp_abbrev> SR PSID --> 10) <!--[rfced] We had the following questions related to terminology used throughout the document: a) We see mixed use of the following forms. Please let us know if/how these should be made consistent. SR path vs. SR Path segment-list vs. Segment List vs. segment list candidate path vs. Candidate Path vs. Candidate path b) Is Return Subcode <RSC> the same as "return code"? Please review and advise if these should be made uniform. --> 11) <!-- [rfced] Please review the "Inclusive Language" portion of the online Style Guide <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811097740%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=M7CdGE9PdglHegcJfQ%2BPCGOkpJbIHE0oWHgcEOdStFA%3D&reserved=0<https://www.rfc-editor.org/styleguide/part2/#inclusive_language>> and let us know if any changes are needed. Updates of this nature typically result in more precise language, which is helpful for readers. Note that our script did not flag any words in particular, but this should still be reviewed as a best practice. --> Thank you. Megan Ferguson RFC Production Center *****IMPORTANT***** Updated 2025/10/20 RFC Author(s): -------------- Instructions for Completing AUTH48 Your document has now entered AUTH48. Once it has been reviewed and approved by you and all coauthors, it will be published as an RFC. If an author is no longer available, there are several remedies available as listed in the FAQ (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ffaq%2F&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811117565%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=D0SGwF0ly4U8QWVcYg9qnDAOdeq%2FoTbXPWYZgYmQYT4%3D&reserved=0<https://www.rfc-editor.org/faq/>). You and you coauthors are responsible for engaging other parties (e.g., Contributors or Working Group) as necessary before providing your approval. Planning your review --------------------- Please review the following aspects of your document: * RFC Editor questions Please review and resolve any questions raised by the RFC Editor that have been included in the XML file as comments marked as follows: <!-- [rfced] ... --> These questions will also be sent in a subsequent email. * Changes submitted by coauthors Please ensure that you review any changes submitted by your coauthors. We assume that if you do not speak up that you agree to changes submitted by your coauthors. * Content Please review the full content of the document, as this cannot change once the RFC is published. Please pay particular attention to: - IANA considerations updates (if applicable) - contact information - references * Copyright notices and legends Please review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP – https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrustee.ietf.org%2Flicense-info&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811138038%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=u0t9uHA0hBYZrB6CyMTi%2BtJ5SHeW1bn7gsvWscMelxE%3D&reserved=0)<https://trustee.ietf.org/license-info>. * Semantic markup Please review the markup in the XML file to ensure that elements of content are correctly tagged. For example, ensure that <sourcecode> and <artwork> are set correctly. See details at <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Frfcxml-vocabulary&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811157848%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=H%2FV4O%2FnIaZ638pvlykQsbgG6B2NtlUHwB1KkU1UBx3U%3D&reserved=0<https://authors.ietf.org/rfcxml-vocabulary>>. * Formatted output Please review the PDF, HTML, and TXT files to ensure that the formatted output, as generated from the markup in the XML file, is reasonable. Please note that the TXT will have formatting limitations compared to the PDF and HTML. Submitting changes ------------------ To submit changes, please reply to this email using ‘REPLY ALL’ as all the parties CCed on this message need to see your changes. The parties include: * your coauthors * [email protected] (the RPC team) * other document participants, depending on the stream (e.g., IETF Stream participants are your working group chairs, the responsible ADs, and the document shepherd). * [email protected], which is a new archival mailing list to preserve AUTH48 conversations; it is not an active discussion list: * More info: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811178536%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Bz4Prtc4rt7r%2BZVBx4cgNiyE6SFoZhbzPXN23OxBjvg%3D&reserved=0<https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc> * The archive itself: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811199327%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ThrjJ6JtAIv91jkeB75GONe3yvu9n5uhlHJmyLuSou4%3D&reserved=0<https://mailarchive.ietf.org/arch/browse/auth48archive/> * Note: If only absolutely necessary, you may temporarily opt out of the archiving of messages (e.g., to discuss a sensitive matter). If needed, please add a note at the top of the message that you have dropped the address. When the discussion is concluded, [email protected] will be re-added to the CC list and its addition will be noted at the top of the message. You may submit your changes in one of two ways: An update to the provided XML file — OR — An explicit list of changes in this format Section # (or indicate Global) OLD: old text NEW: new text You do not need to reply with both an updated XML file and an explicit list of changes, as either form is sufficient. We will ask a stream manager to review and approve any changes that seem beyond editorial in nature, e.g., addition of new text, deletion of text, and technical changes. Information about stream managers can be found in the FAQ. Editorial changes do not require approval from a stream manager. Approving for publication -------------------------- To approve your RFC for publication, please reply to this email stating that you approve this RFC for publication. Please use ‘REPLY ALL’, as all the parties CCed on this message need to see your approval. Files ----- The files are available here: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884.xml&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811218733%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=HNmKrJiDUH0KCcVmlrW08lG6Ffd2gupaYMNND9WJb7o%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884.xml> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884.html&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811237644%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=AHwCV%2BWvbeATTh8WBQSb0HwYLAB9M4MddQwSyivtTro%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884.html> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884.pdf&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811256925%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=w2XmLNs0S%2BuGLMhscHOk5sAj6Zk4jZ9fqtFH3ExIFyI%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884.pdf> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884.txt&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811276201%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ysSSRT3wLrHXiznfNPF8pFYsmnCy5zIFDvlXcme3T20%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884.txt> Diff file of the text: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884-diff.html&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811294999%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rHZ9p1KVJZbAQeyf7B2JVZ29wjnXWUFL3tBvsh%2BbXKk%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884-diff.html> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884-rfcdiff.html&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811315132%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fX9Qp%2FzyAjMV22iDOnJgd8%2FWwLICw%2BG3diRWjlkmf1k%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884-rfcdiff.html> (side by side) Diff of the XML: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9884-xmldiff1.html&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811333158%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dFE%2Fgo8bljuvQmF9chIpSnHV59FZgDw2aMDmEqnvtvM%3D&reserved=0<https://www.rfc-editor.org/authors/rfc9884-xmldiff1.html> Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9884&data=05%7C02%7Cjames.n.guichard%40futurewei.com%7C843e36a9dc1d4db89dee08de10370d36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638966025811352331%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=lTK7JEXUCe40BRjVbXPWJsleCh5mAMH77TWGjkBdO5I%3D&reserved=0<https://www.rfc-editor.org/auth48/rfc9884> Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9884 (draft-ietf-mpls-spring-lsp-ping-path-sid-13) Title : Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane Author(s) : X. Min, S. Peng, L. Gong, R. Gandhi, C. Pignataro WG Chair(s) : Tarek Saad, Tony Li, Adrian Farrel Area Director(s) : Jim Guichard, Ketan Talaulikar, Gunter Van de Velde
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
