[mpls] A new draft for the (re-)initialization of PSC in APS mode

류정동 <ryoo@etri.re.kr> Mon, 27 July 2015 07:33 UTC

Return-Path: <ryoo@etri.re.kr>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id BA3A51ACE81 for <mpls@ietfa.amsl.com>; Mon, 27 Jul 2015 00:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.629
X-Spam-Status: No, score=-100.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1hQZTmygsbRH for <mpls@ietfa.amsl.com>; Mon, 27 Jul 2015 00:33:24 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1B181ACE49 for <mpls@ietf.org>; Mon, 27 Jul 2015 00:33:23 -0700 (PDT)
Received: from SMTP4.etri.info ( by SMTPEG1.etri.info ( with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 27 Jul 2015 16:33:23 +0900
Received: from SMTP2.etri.info ([]) by SMTP4.etri.info ([]) with mapi id 14.01.0355.002; Mon, 27 Jul 2015 16:33:19 +0900
From: =?utf-8?B?66WY7KCV64+Z?= <ryoo@etri.re.kr>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: A new draft for the (re-)initialization of PSC in APS mode
Thread-Index: AdDIPoG1ujFRZnTMTxG1LT6Br9QNFw==
Date: Mon, 27 Jul 2015 07:33:18 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A2915C889@SMTP2.etri.info>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_5B4A6CBE3924BB41A3BEE462A8E0B75A2915C889SMTP2etriinfo_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/qIff3gm9o9PKeZkrBhjEd7aEVSw>
Subject: [mpls] A new draft for the (re-)initialization of PSC in APS mode
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Jul 2015 07:33:26 -0000

Hi All,

A new version of ID, draft-ryoo-mpls-tp-aps-updates-00.txt is available at

This draft is to update RFC 7271 (MPLS-TP linear protection in APS mode), and the updates are related to the (re-)initialization of the PSC Control Logic, in which the state machine resides. when operating in APS mode.

Since the publication of RFC 7271 in June 2014, there have been some questions on what the correct and desirable behavior is when the node or the linear protection switching process should be rebooted or re-initialized due to the power outage or the operator’s act of re-booting, etc. Although it is a common perception that the state machine starts at the Normal state (but, not explicitly specified in any of MPLS-TP linear protection solution documents, RFC 7271 and RFC 6378), various questions have been raised concerning the detailed actions that the PSC Control Logic should take.

The authors of this new draft has been analyzing various initialization scenarios, such as warm and cold reboots while the related OAM functions are in operation or not, and came up with a set of the initialization rules that can cover all the possible cases related to (re-)initialization while traffic disruptions are minimized.

Your questions, comments and feedbacks are welcome.

Best regards,

Jeong-dong and Authors