RFC 7412 on Requirements for MPLS Transport Profile (MPLS-TP) Shared Mesh Protection
rfc-editor@rfc-editor.org Sat, 13 December 2014 00:54 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 F30751A884D for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 16:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 VV6CTQzSzWcV for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 16:54:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 566131A8847 for <ietf-announce@ietf.org>; Fri, 12 Dec 2014 16:54:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7BFA1181CD3; Fri, 12 Dec 2014 16:54:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7412 on Requirements for MPLS Transport Profile (MPLS-TP) Shared Mesh Protection
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141213005416.7BFA1181CD3@rfc-editor.org>
Date: Fri, 12 Dec 2014 16:54:16 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/xZPDzp0ByiBlBtM_TgVShuciDLo
Cc: 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: <http://www.ietf.org/mail-archive/web/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: Sat, 13 Dec 2014 00:54:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7412
Title: Requirements for MPLS Transport Profile
(MPLS-TP) Shared Mesh Protection
Author: Y. Weingarten, S. Aldrin,
P. Pan, J. Ryoo,
G. Mirsky
Status: Informational
Stream: IETF
Date: December 2014
Mailbox: wyaacov@gmail.com,
aldrin.ietf@gmail.com,
ppan@infinera.com,
ryoo@etri.re.kr,
gregory.mirsky@ericsson.com
Pages: 16
Characters: 34117
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-smp-requirements-09.txt
URL: https://www.rfc-editor.org/rfc/rfc7412.txt
This document presents the basic network objectives for the behavior
of Shared Mesh Protection (SMP) that are not based on control-plane
support. This document provides an expansion of the basic
requirements presented in RFC 5654 ("Requirements of an MPLS Transport
Profile") and RFC 6372 ("MPLS Transport Profile (MPLS-TP)
Survivability Framework"). This document provides requirements for
any mechanism that would be used to implement SMP for MPLS-TP data
paths, in networks that delegate protection switch coordination to
the data plane.
This document is a product of the Multiprotocol Label Switching 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/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