[spring] RFC 9545 on Path Segment Identifier in MPLS-Based Segment Routing Networks
rfc-editor@rfc-editor.org Thu, 22 February 2024 22:06 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 47FC3C180B52; Thu, 22 Feb 2024 14:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 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_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 nfuTo0Eio773; Thu, 22 Feb 2024 14:06:30 -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 065EFC14F6A6; Thu, 22 Feb 2024 14:06:30 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DF9DF1BA3F2C; Thu, 22 Feb 2024 14:06:29 -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: <20240222220629.DF9DF1BA3F2C@rfcpa.amsl.com>
Date: Thu, 22 Feb 2024 14:06:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/3IrRW-pg4rHkMXIuB7eQMvKG0EU>
Subject: [spring] RFC 9545 on Path Segment Identifier in MPLS-Based Segment Routing Networks
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 22:06:34 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9545 Title: Path Segment Identifier in MPLS-Based Segment Routing Networks Author: W. Cheng, Ed., H. Li, C. Li, Ed., R. Gandhi, R. Zigler Status: Standards Track Stream: IETF Date: February 2024 Mailbox: chengweiqiang@chinamobile.com, lihan@chinamobile.com, c.l@huawei.com, rgandhi@cisco.com, royi.zigler@broadcom.com Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-spring-mpls-path-segment-22.txt URL: https://www.rfc-editor.org/info/rfc9545 DOI: 10.17487/RFC9545 A Segment Routing (SR) path is identified by an SR segment list. A subset of segments from the segment list cannot be leveraged to distinguish one SR path from another as they may be partially congruent. SR path identification is a prerequisite for various use cases such as performance measurement and end-to-end 1+1 path protection. In an SR over MPLS (SR-MPLS) data plane, an egress node cannot determine on which SR path a packet traversed the network from the label stack because the segment identifiers are removed from the label stack as the packet transits the network. This document defines a Path Segment Identifier (PSID) to identify an SR path on the egress node of the path. 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