RFC 8661 on Segment Routing MPLS Interworking with LDP
rfc-editor@rfc-editor.org Fri, 06 December 2019 21:53 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54859120132; Fri, 6 Dec 2019 13:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwY-6617E5U6; Fri, 6 Dec 2019 13:53:27 -0800 (PST)
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 A558D1209B2; Fri, 6 Dec 2019 13:53:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F7A4F4073C; Fri, 6 Dec 2019 13:53:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8661 on Segment Routing MPLS Interworking with LDP
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: <20191206215322.8F7A4F4073C@rfc-editor.org>
Date: Fri, 06 Dec 2019 13:53:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HsWVRyRceb2PDJN5ZqcCwQRfqyk>
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: Fri, 06 Dec 2019 21:53:32 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8661
Title: Segment Routing MPLS Interworking with
LDP
Author: A. Bashandy, Ed.,
C. Filsfils, Ed.,
S. Previdi,
B. Decraene,
S. Litkowski
Status: Standards Track
Stream: IETF
Date: December 2019
Mailbox: abashandy.ietf@gmail.com,
cfilsfil@cisco.com,
stefano@previdi.net,
bruno.decraene@orange.com,
slitkows.ietf@gmail.com
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-spring-segment-routing-ldp-interop-15.txt
URL: https://www.rfc-editor.org/info/rfc8661
DOI: 10.17487/RFC8661
A Segment Routing (SR) node steers a packet through a controlled set
of instructions, called segments, by prepending the packet with an SR
header. A segment can represent any instruction, topological or
service based. SR allows enforcing a flow through any topological
path while maintaining per-flow state only at the ingress node to the
SR domain.
The Segment Routing architecture can be directly applied to the MPLS
data plane with no change in the forwarding plane. This document
describes how Segment Routing MPLS operates in a network where LDP is
deployed and in the case where SR-capable and non-SR-capable nodes
coexist.
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