RFC 9800: Compressed SRv6 Segment List Encoding
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9800
- Published
- June 2025
- Authors
- W. Cheng; C. Filsfils; Z. Li; B. Decraene; F. Clad
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 59
- Also known as
- —
- Updates:
- RFC 8754
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8986Segment Routing over IPv6 (SRv6) Network ProgrammingCurrent
February 2021
- RFC 9831Segment Type Extensions for BGP Segment Routing (SR) PolicyCurrent
September 2025
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9514Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9513OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9488Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP)Current
October 2023
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?