RFC 9800 on Compressed SRv6 Segment List Encoding
rfc-editor@rfc-editor.org Mon, 30 June 2025 20:37 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3AE5C3BD4FB0; Mon, 30 Jun 2025 13:37:47 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 16C7923B3EF; Mon, 30 Jun 2025 13:37:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9800 on Compressed SRv6 Segment List Encoding
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250630203747.16C7923B3EF@rfcpa.rfc-editor.org>
Date: Mon, 30 Jun 2025 13:37:47 -0700
Message-ID-Hash: A4FDXD4HQRAVIFH3F3LGVLUFNSIQX7YE
X-Message-ID-Hash: A4FDXD4HQRAVIFH3F3LGVLUFNSIQX7YE
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spring@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5vHiemxLn1nwepCKB7r0RXh6rl0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
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: chengweiqiang@chinamobile.com,
cf@cisco.com,
lizhenbin@huawei.com,
bruno.decraene@orange.com,
fclad.ietf@gmail.com
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team