Congratulations to the authors and contributors! Such a challenge and excellent work.
RFC9800 will help the industry to deploy SRv6 for sure, way too many customers are asking and waiting for this standard 😊 Respect, Cheng -----Original Message----- From: [email protected] <[email protected]> Sent: Monday, June 30, 2025 10:38 PM To: [email protected]; [email protected] Cc: [email protected]; [email protected]; [email protected] Subject: RFC 9800 on Compressed SRv6 Segment List Encoding A new Request for Comments is now available in online RFC libraries. RFC 9800 Title: Compressed SRv6 Segment List Encoding Author: W. Cheng, Ed., C. Filsfils, Z. Li, B. Decraene, F. Clad, Ed. Status: Standards Track Stream: IETF Date: June 2025 Mailbox: [email protected], [email protected], [email protected], [email protected], [email protected] Pages: 59 Updates: RFC 8754 I-D Tag: draft-ietf-spring-srv6-srh-compression-23.txt URL: https://www.rfc-editor.org/info/rfc9800 DOI: 10.17487/RFC9800 Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation needed to steer packets over long segment lists. This document updates RFC 8754 by allowing a Segment List entry in the Segment Routing Header (SRH) to be either an IPv6 address, as specified in RFC 8754, or a REPLACE-CSID container in packed format, as specified in this document. This document is a product of the Source Packet Routing in Networking Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to [email protected]. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
