[mpls] RFC 8234 on Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode

rfc-editor@rfc-editor.org Wed, 23 August 2017 18:01 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 843311329C1; Wed, 23 Aug 2017 11:01:10 -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 s-Sdjt6ycQEA; Wed, 23 Aug 2017 11:01:08 -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 A1CDE13248E; Wed, 23 Aug 2017 11:01:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8BF88B80DC2; Wed, 23 Aug 2017 11:00:39 -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: <20170823180039.8BF88B80DC2@rfc-editor.org>
Date: Wed, 23 Aug 2017 11:00:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/W4POaO_bAnTU1e5ZmHtqAVKjJCU>
Subject: [mpls] RFC 8234 on Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode
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, 23 Aug 2017 18:01:10 -0000

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

        
        RFC 8234

        Title:      Updates to MPLS Transport Profile (MPLS-TP) 
                    Linear Protection in Automatic Protection 
                    Switching (APS) Mode 
        Author:     J. Ryoo,
                    T. Cheung,
                    H. van Helvoort,
                    I. Busi,
                    G. Wen
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2017
        Mailbox:    ryoo@etri.re.kr, 
                    cts@etri.re.kr, 
                    huubatwork@gmail.com,
                    Italo.Busi@huawei.com, 
                    wenguangjuan@huawei.com
        Pages:      9
        Characters: 16898
        Updates:    RFC 7271

        I-D Tag:    draft-ietf-mpls-tp-aps-updates-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8234

        DOI:        10.17487/RFC8234

This document contains updates to MPLS Transport Profile (MPLS-TP)
linear protection in Automatic Protection Switching (APS) mode
defined in RFC 7271.  The updates provide rules related to the
initialization of the Protection State Coordination (PSC) Control
Logic (in which the state machine resides) when operating in APS mode
and clarify the operation related to state transition table lookup.

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