Dear all, The document does not merely describe existing practices; it defines normative procedures and protocol behavior that are intended for interoperable implementation. As such, it creates protocol requirements that network operators like Colt and vendors can rely on consistently across multi-vendor environments, which is a primary purpose of the Standards Track process. I'm in favor to make this draft a standards track document.
Sincerely, Bart Janssens ________________________________ From: Alvaro Retana Sent: Friday, October 02, 2026 08:40 To: [email protected] Cc: [email protected]; spring-chairs; IETF MPLS List; Haoyu Song Subject: Re: Intended Status of draft-ietf-spring-stamp-srpm-mpls Dear WG: Haoyu Song is the Shepherd for this document. During his review, he proposed changing the Intended Status of this work from Informational to Standards Track. Here is his justification: Here’s the reason to support the standard type: the document describes standard procedures and protocol extensions for using STAMP over SR-MPLS networks. It specifies control and data plane interactions, encapsulation methods, and interoperability mechanisms that require standardization to ensure consistent implementations across different vendor hardware. Protocol extensions designed for widespread implementation and interoperability belong on the standards track. https://mailarchive.ietf.org/arch/msg/spring/EzMtFTSXO572dfHiiNi07hC9v0M/ Although he sent the message to the list, we haven't heard any other opinions (besides Rakesh's, as a co-author). We would like to hear opinions on Haoyu's proposed change. Please explain why you might be in favor of, or against, a change in the Status. We will take opinions until Oct/15, 2026. Thanks! Alvaro. [Colt Disclaimer] This email is from an entity of the Colt group of companies. Colt Group Holdings Limited, Colt House, 20 Great Eastern Street, London, EC2A 3EH, United Kingdom, registered in England and Wales, under company number 11530966. Corporate and contact information for our entities can be found at https://www.colt.net/legal/colt-group-of-companies/. Internet communications are not secure and Colt does not accept responsibility for the accurate transmission of this message. Content of this email or its attachments is not legally or contractually binding unless expressly previously agreed in writing by Colt
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
