RFC 8185 on Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires Protection
rfc-editor@rfc-editor.org Mon, 26 June 2017 19:39 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 EA06D126C3D; Mon, 26 Jun 2017 12:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 iiAe8DrJ5wot; Mon, 26 Jun 2017 12:39:20 -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 3F9FF12EB5B; Mon, 26 Jun 2017 12:38:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 83BDCB806A3; Mon, 26 Jun 2017 12:38:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8185 on Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires Protection
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, pals@ietf.org
Message-Id: <20170626193823.83BDCB806A3@rfc-editor.org>
Date: Mon, 26 Jun 2017 12:38:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Fl2Sa0iOP0fraLJERa83iifMPNw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Jun 2017 19:39:24 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8185
Title: Dual-Homing Coordination for MPLS Transport
Profile (MPLS-TP) Pseudowires Protection
Author: W. Cheng,
L. Wang,
H. Li,
J. Dong,
A. D'Alessandro
Status: Standards Track
Stream: IETF
Date: June 2017
Mailbox: chengweiqiang@chinamobile.com,
wangleiyj@chinamobile.com,
lihan@chinamobile.com,
jie.dong@huawei.com,
alessandro.dalessandro@telecomitalia.it
Pages: 17
Characters: 40293
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pals-mpls-tp-dual-homing-coordination-06.txt
URL: https://www.rfc-editor.org/info/rfc8185
DOI: 10.17487/RFC8185
In some scenarios, MPLS Transport Profile (MPLS-TP) pseudowires (PWs)
(RFC 5921) may be statically configured when a dynamic control plane
is not available. A fast protection mechanism for MPLS-TP PWs is
needed to protect against the failure of an Attachment Circuit (AC),
the failure of a Provider Edge (PE), or a failure in the Packet
Switched Network (PSN). The framework and typical scenarios of dual-
homing PW local protection are described in RFC 8184. This document
proposes a dual-homing coordination mechanism for MPLS-TP PWs that is
used for state exchange and switchover coordination between the dual-
homing PEs for dual-homing PW local 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/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