RFC 8986 on Segment Routing over IPv6 (SRv6) Network Programming

rfc-editor@rfc-editor.org Mon, 22 February 2021 18:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9B6E13A1F41; Mon, 22 Feb 2021 10:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9sFb_sZuV99S; Mon, 22 Feb 2021 10:26:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA643A1F9A; Mon, 22 Feb 2021 10:26:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 21623F407A4; Mon, 22 Feb 2021 10:26:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg5ODYgb24gU2VnbWVudCBSb3V0aW5nIG92ZXIgSVB2NiAoU1J2NikgTmV0d29yayBQcm9ncmFtbWluZw==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210222182601.21623F407A4@rfc-editor.org>
Date: Mon, 22 Feb 2021 10:26:01 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2agaZ6BAV7AI-wrJU098_LS2ePo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 18:26:29 -0000

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

        RFC 8986

        Title:      Segment Routing over IPv6 (SRv6) 
                    Network Programming 
        Author:     C. Filsfils, Ed.,
                    P. Camarillo, Ed.,
                    J. Leddy,
                    D. Voyer,
                    S. Matsushima,
                    Z. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2021
        Mailbox:    cf@cisco.com,
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-srv6-network-programming-28.txt

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

        DOI:        10.17487/RFC8986

The Segment Routing over IPv6 (SRv6) Network Programming framework
enables a network operator or an application to specify a packet
processing program by encoding a sequence of instructions in the IPv6
packet header.

Each instruction is implemented on one or several nodes in the
network and identified by an SRv6 Segment Identifier in the packet.

This document defines the SRv6 Network Programming concept and
specifies the base set of SRv6 behaviors that enables the creation of
interoperable overlays with underlay optimization.

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