RFC 7271 on MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators

rfc-editor@rfc-editor.org Thu, 12 June 2014 21:03 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 D19481A02C4; Thu, 12 Jun 2014 14:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 MITb_HF6rH4Q; Thu, 12 Jun 2014 14:03:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 74E901A028B; Thu, 12 Jun 2014 14:03:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 146ED180095; Thu, 12 Jun 2014 14:02:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7271 on MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140612210237.146ED180095@rfc-editor.org>
Date: Thu, 12 Jun 2014 14:02:37 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/2R2RKUouBZTquegegeFXyRuqy78
Cc: drafts-update-ref@iana.org, mpls@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: <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: Thu, 12 Jun 2014 21:03:36 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7271

        Title:      MPLS Transport Profile (MPLS-TP) Linear 
                    Protection to Match the Operational Expectations 
                    of Synchronous Digital Hierarchy, Optical Transport 
                    Network, and Ethernet Transport Network Operators 
        Author:     J. Ryoo, Ed., E. Gray, Ed.,
                    H. van Helvoort, A. D'Alessandro,
                    T. Cheung, E. Osborne
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    ryoo@etri.re.kr, 
                    eric.gray@ericsson.com, 
                    huub.van.helvoort@huawei.com,   
                    alessandro.dalessandro@telecomitalia.it, 
                    cts@etri.re.kr,
                    eric.osborne@notcom.com
        Pages:      40
        Characters: 87586
        Updates:    RFC 6378

        I-D Tag:    draft-ietf-mpls-tp-psc-itu-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7271.txt

This document describes alternate mechanisms to perform some of the
functions of MPLS Transport Profile (MPLS-TP) linear protection
defined in RFC 6378, and also defines additional mechanisms.  The
purpose of these alternate and additional mechanisms is to provide
operator control and experience that more closely models the behavior
of linear protection seen in other transport networks.

This document also introduces capabilities and modes for linear
protection.  A capability is an individual behavior, and a mode is a
particular combination of capabilities.  Two modes are defined in
this document: Protection State Coordination (PSC) mode and Automatic
Protection Switching (APS) mode.

This document describes the behavior of the PSC protocol including
priority logic and state machine when all the capabilities associated
with the APS mode are enabled.

This document updates RFC 6378 in that the capability advertisement
method defined here is an addition to that document.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://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