[mpls] RFC 8227 on MPLS-TP Shared-Ring Protection (MSRP) Mechanism for Ring Topology
rfc-editor@rfc-editor.org Wed, 30 August 2017 00:26 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB0013218E; Tue, 29 Aug 2017 17:26:51 -0700 (PDT)
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 K6b2im_vE0vg; Tue, 29 Aug 2017 17:26:50 -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 42A2E132113; Tue, 29 Aug 2017 17:26:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F3A0EB813FF; Tue, 29 Aug 2017 17:26:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, mpls@ietf.org
Message-Id: <20170830002613.F3A0EB813FF@rfc-editor.org>
Date: Tue, 29 Aug 2017 17:26:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/mXqA-oqNO1b_iHeyyzIOTs85y48>
Subject: [mpls] RFC 8227 on MPLS-TP Shared-Ring Protection (MSRP) Mechanism for Ring Topology
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Aug 2017 00:26:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8227
Title: MPLS-TP Shared-Ring Protection (MSRP) Mechanism
for Ring Topology
Author: W. Cheng,
L. Wang,
H. Li,
H. van Helvoort,
J. Dong
Status: Standards Track
Stream: IETF
Date: August 2017
Mailbox: chengweiqiang@chinamobile.com,
wangleiyj@chinamobile.com,
lihan@chinamobile.com,
huubatwork@gmail.com,
jie.dong@huawei.com
Pages: 56
Characters: 128880
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-tp-shared-ring-protection-06.txt
URL: https://www.rfc-editor.org/info/rfc8227
DOI: 10.17487/RFC8227
This document describes requirements, architecture, and solutions for
MPLS-TP Shared-Ring Protection (MSRP) in a ring topology for point-
to-point (P2P) services. The MSRP mechanism is described to meet the
ring protection requirements as described in RFC 5654. This document
defines the Ring Protection Switching (RPS) protocol that is used to
coordinate the protection behavior of the nodes on an MPLS ring.
This document is a product of the Multiprotocol Label Switching 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