RFC 8754 on IPv6 Segment Routing Header (SRH)

rfc-editor@rfc-editor.org Sat, 14 March 2020 05:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 777A83A0EA5; Fri, 13 Mar 2020 22:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H42NozGLZpqO; Fri, 13 Mar 2020 22:24:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9121A3A0E9F; Fri, 13 Mar 2020 22:24:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C64FF40717; Fri, 13 Mar 2020 22:24:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8754 on IPv6 Segment Routing Header (SRH)
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, ipv6@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200314052430.9C64FF40717@rfc-editor.org>
Date: Fri, 13 Mar 2020 22:24:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/k1zq5EJAZ2p9fT1L8FV7YOZ5gvc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Mar 2020 05:24:40 -0000

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

        
        RFC 8754

        Title:      IPv6 Segment Routing Header (SRH) 
        Author:     C. Filsfils, Ed.,
                    D. Dukes, Ed.,
                    S. Previdi,
                    J. Leddy,
                    S. Matsushima,
                    D. Voyer
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    cfilsfil@cisco.com, 
                    ddukes@cisco.com, 
                    stefano@previdi.net,
                    john@leddy.net, 
                    satoru.matsushima@g.softbank.co.jp,                      
                    daniel.voyer@bell.ca
        Pages:      27
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-segment-routing-header-26.txt

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

        DOI:        10.17487/RFC8754

Segment Routing can be applied to the IPv6 data plane using a new
type of Routing Extension Header called the Segment Routing Header
(SRH). This document describes the SRH and how it is used by nodes
that are Segment Routing (SR) capable.

This document is a product of the IPv6 Maintenance 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