[mpls] RFC 8663 on MPLS Segment Routing over IP

rfc-editor@rfc-editor.org Fri, 06 December 2019 21:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9F01512012E; Fri, 6 Dec 2019 13:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 kcX1tddNfUJr; Fri, 6 Dec 2019 13:53:48 -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 85443120A65; Fri, 6 Dec 2019 13:53:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 697C4F4074B; Fri, 6 Dec 2019 13:53:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191206215338.697C4F4074B@rfc-editor.org>
Date: Fri, 06 Dec 2019 13:53:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/J-pwYQZRaCzvscz4DR3zMAnAtKY>
Subject: [mpls] RFC 8663 on MPLS Segment Routing over IP
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2019 21:53:52 -0000

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

        RFC 8663

        Title:      MPLS Segment Routing over IP 
        Author:     X. Xu,
                    S. Bryant,
                    A. Farrel,
                    S. Hassan,
                    W. Henderickx,
                    Z. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    xiaohu.xxh@alibaba-inc.com, 
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-sr-over-ip-07.txt

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

        DOI:        10.17487/RFC8663

MPLS Segment Routing (SR-MPLS) is a method of source routing a packet
through an MPLS data plane by imposing a stack of MPLS labels on the
packet to specify the path together with any packet-specific
instructions to be executed on it.  SR-MPLS can be leveraged to
realize a source-routing mechanism across MPLS, IPv4, and IPv6 data
planes by using an MPLS label stack as a source-routing instruction
set while making no changes to SR-MPLS specifications and
interworking with SR-MPLS implementations.

This document describes how SR-MPLS-capable routers and IP-only
routers can seamlessly coexist and interoperate through the use of
SR-MPLS label stacks and IP encapsulation/tunneling such as
MPLS-over-UDP as defined in RFC 7510.

This document is a product of the Multiprotocol Label Switching 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