RFC 7771 on Switching Provider Edge (S-PE) Protection for MPLS and MPLS Transport Profile (MPLS-TP) Static Multi-Segment Pseudowires
rfc-editor@rfc-editor.org Fri, 29 January 2016 22:36 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA3D1A8F45; Fri, 29 Jan 2016 14:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 02yxT7iBb7nD; Fri, 29 Jan 2016 14:36:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C9751A8BB3; Fri, 29 Jan 2016 14:36:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C280C180094; Fri, 29 Jan 2016 14:35:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7771 on Switching Provider Edge (S-PE) Protection for MPLS and MPLS Transport Profile (MPLS-TP) Static Multi-Segment Pseudowires
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160129223517.C280C180094@rfc-editor.org>
Date: Fri, 29 Jan 2016 14:35:17 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/nkplp9BfeGIVhL0K8JsKQh9DOh0>
Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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, 29 Jan 2016 22:37:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7771
Title: Switching Provider Edge (S-PE) Protection
for MPLS and MPLS Transport Profile
(MPLS-TP) Static Multi-Segment Pseudowires
Author: A. Malis, Ed., L. Andersson,
H. van Helvoort, J. Shin,
L. Wang, A. D'Alessandro
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: agmalis@gmail.com,
loa@mail01.huawei.com,
huubatwork@gmail.com,
jongyoon.shin@sk.com,
wangleiyj@chinamobile.com,
alessandro.dalessandro@telecomitalia.it
Pages: 9
Characters: 19235
Updates: RFC 6870
I-D Tag: draft-ietf-pals-ms-pw-protection-04.txt
URL: https://www.rfc-editor.org/info/rfc7771
DOI: http://dx.doi.org/10.17487/RFC7771
In MPLS and MPLS Transport Profile (MPLS-TP) environments, statically
provisioned Single-Segment Pseudowires (SS-PWs) are protected against
tunnel failure via MPLS-level and MPLS-TP-level tunnel protection.
With statically provisioned Multi-Segment Pseudowires (MS-PWs), each
segment of the MS-PW is likewise protected from tunnel failures via
MPLS-level and MPLS-TP-level tunnel protection. However, static
MS-PWs are not protected end-to-end against failure of one of the
Switching Provider Edge Routers (S-PEs) along the path of the
MS-PW. This document describes how to achieve this protection via
redundant MS-PWs by updating the existing procedures in RFC 6870.
It also contains an optional approach based on MPLS-TP Linear
Protection.
This document is a product of the Pseudowire And LDP-enabled Services 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/rfc.html
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