[spring] RFC 9524 on Segment Routing Replication for Multipoint Service Delivery
rfc-editor@rfc-editor.org Thu, 22 February 2024 21:25 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13FEAC15154A; Thu, 22 Feb 2024 13:25:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wBf4sEtkd2An; Thu, 22 Feb 2024 13:25:08 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FEF7C14F5F4; Thu, 22 Feb 2024 13:25:08 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4E9FA191A48B; Thu, 22 Feb 2024 13:25:08 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spring@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240222212508.4E9FA191A48B@rfcpa.amsl.com>
Date: Thu, 22 Feb 2024 13:25:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ZxQy_0npSzGHmKCgCsdtmjtzjYo>
Subject: [spring] RFC 9524 on Segment Routing Replication for Multipoint Service Delivery
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 21:25:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9524
Title: Segment Routing Replication for Multipoint
Service Delivery
Author: D. Voyer, Ed.,
C. Filsfils,
R. Parekh,
H. Bidgoli,
Z. Zhang
Status: Standards Track
Stream: IETF
Date: February 2024
Mailbox: daniel.voyer@bell.ca,
cfilsfil@cisco.com,
riparekh@cisco.com,
hooman.bidgoli@nokia.com,
zzhang@juniper.net
Pages: 22
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-spring-sr-replication-segment-19.txt
URL: https://www.rfc-editor.org/info/rfc9524
DOI: 10.17487/RFC9524
This document describes the Segment Routing Replication segment for
multipoint service delivery. A Replication segment allows a packet to
be replicated from a replication node to downstream nodes.
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
Association Management Solutions, LLC