[spring] RFC 9256 on Segment Routing Policy Architecture

rfc-editor@rfc-editor.org Sun, 24 July 2022 21:17 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 744A7C16ED0E; Sun, 24 Jul 2022 14:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xf2RkQcPP5wc; Sun, 24 Jul 2022 14:16:59 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org []) (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 C3E51C16ED0A; Sun, 24 Jul 2022 14:16:59 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7497410D68; Sun, 24 Jul 2022 14:16:59 -0700 (PDT)
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: <20220724211659.7497410D68@rfcpa.amsl.com>
Date: Sun, 24 Jul 2022 14:16:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/sKZbLFKDyQNe5Ch-FDITnedtJGA>
Subject: [spring] RFC 9256 on Segment Routing Policy Architecture
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: Sun, 24 Jul 2022 21:17:03 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9256

        Title:      Segment Routing Policy Architecture 
        Author:     C. Filsfils,
                    K. Talaulikar, Ed.,
                    D. Voyer,
                    A. Bogdanov,
                    P. Mattes
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2022
        Mailbox:    cfilsfil@cisco.com,
        Pages:      35
        Updates:    RFC 8402

        I-D Tag:    draft-ietf-spring-segment-routing-policy-22.txt

        URL:        https://www.rfc-editor.org/info/rfc9256

        DOI:        10.17487/RFC9256

Segment Routing (SR) allows a node to steer a packet flow along any
path. Intermediate per-path states are eliminated thanks to source
routing. SR Policy is an ordered list of segments (i.e.,
instructions) that represent a source-routed policy. Packet flows are
steered into an SR Policy on a node where it is instantiated called a
headend node. The packets steered into an SR Policy carry an ordered
list of segments associated with that SR Policy.

This document updates RFC 8402 as it details the concepts of SR
Policy and steering into an SR Policy.

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

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