[mpls-tp] Comments on draft-weingarten-mpls-tp-linear-protection-05.txt

Jishnu A <jishnu@india.tejasnetworks.com> Fri, 29 January 2010 02:51 UTC

Return-Path: <jishnu@india.tejasnetworks.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 849F43A69BE for <mpls-tp@core3.amsl.com>; Thu, 28 Jan 2010 18:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level:
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwAT56pzssb6 for <mpls-tp@core3.amsl.com>; Thu, 28 Jan 2010 18:51:26 -0800 (PST)
Received: from HUBMAIL.india.tejasnetworks.com (unknown [164.164.94.83]) by core3.amsl.com (Postfix) with ESMTP id 28EAD3A692A for <mpls-tp@ietf.org>; Thu, 28 Jan 2010 18:51:24 -0800 (PST)
Received: from HUBMAIL.india.tejasnetworks.com ([192.168.0.190]) by hubmail ([192.168.0.190]) with mapi; Fri, 29 Jan 2010 08:21:02 +0530
From: Jishnu A <jishnu@india.tejasnetworks.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "yaacov.weingarten@nsn.com" <yaacov.weingarten@nsn.com>
Date: Fri, 29 Jan 2010 08:21:30 +0530
Thread-Topic: Comments on draft-weingarten-mpls-tp-linear-protection-05.txt
Thread-Index: AcqgjfWaI4dvGoCvQeWpX1c2emFaUA==
Message-ID: <20674C50F7E3794CA35FDCAD2B0E494006B7C5EB7C@hubmail>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-IN
Content-Type: multipart/alternative; boundary="_000_20674C50F7E3794CA35FDCAD2B0E494006B7C5EB7Chubmail_"
MIME-Version: 1.0
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls-tp] Comments on draft-weingarten-mpls-tp-linear-protection-05.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2010 02:51:29 -0000

Dear Stewart/Yaacov,
I have few comments on the above draft:


1.       There is an inconsistency between signal fault and signal degrade "Signal fault (0101) or Signal degrade (0100)" mentioned in 4.2.3 and PSC request codes in 4.2.1 where "Signal fault (0110), Signal degrade (0101)".

2.       In 4.3.5 "either Manual switch of Forced switch" should be "either Manual switch or Forced switch"

3.       In 4.3.5, Fpath = 1 at LSR A and Z, in case of MS/FS

4.       In FS or MS case, as per 4.3.5, we are supposed to set Fpath as "1" (if comment 3 above is correct), how do we handle two of the following scenarios:

a)      There is a FS in work path but the working path otherwise is fine

b)      There is a FS in work path and there is a SD along the work path.

5.       Comment above also is valid for LoP in section 4.3.3

Regards,
Jishnu