RFC 8184 on Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) Pseudowires
rfc-editor@rfc-editor.org Mon, 26 June 2017 19:38 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 EF77C12EB51; Mon, 26 Jun 2017 12:38:38 -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 3XphU-QUJPo4; Mon, 26 Jun 2017 12:38: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 4611C12EB07; Mon, 26 Jun 2017 12:38:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9E573B8037D; Mon, 26 Jun 2017 12:38:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8184 on Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) Pseudowires
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: <20170626193810.9E573B8037D@rfc-editor.org>
Date: Mon, 26 Jun 2017 12:38:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Du7KJqBrD4WQIZ8s-OvI7JJqwYg>
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:38:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8184
Title: Dual-Homing Protection for MPLS and
the MPLS Transport Profile (MPLS-TP) Pseudowires
Author: W. Cheng,
L. Wang,
H. Li,
S. Davari,
J. Dong
Status: Informational
Stream: IETF
Date: June 2017
Mailbox: chengweiqiang@chinamobile.com,
wangleiyj@chinamobile.com,
lihan@chinamobile.com,
davari@broadcom.com,
jie.dong@huawei.com
Pages: 11
Characters: 24298
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pals-mpls-tp-dual-homing-protection-06.txt
URL: https://www.rfc-editor.org/info/rfc8184
DOI: 10.17487/RFC8184
This document describes a framework and several scenarios for a
pseudowire (PW) dual-homing local protection mechanism that avoids
unnecessary switchovers and does not depend on whether a control
plane is used. A Dual-Node Interconnection (DNI) PW is used to carry
traffic between the dual-homing Provider Edge (PE) nodes when a
failure occurs in one of the Attachment Circuits (AC) or PWs. This
PW dual-homing local protection mechanism is complementary to
existing PW protection mechanisms.
This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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