[mpls-tp] LDI generation during slow CC

"Vijayanand C - ERS, HCL Tech" <vijayc@hcl.in> Fri, 18 June 2010 06:31 UTC

Return-Path: <vijayc@hcl.in>
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 376C63A69C7 for <mpls-tp@core3.amsl.com>; Thu, 17 Jun 2010 23:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.596
X-Spam-Level:
X-Spam-Status: No, score=0.596 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
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 JeAHJtXZIHP6 for <mpls-tp@core3.amsl.com>; Thu, 17 Jun 2010 23:31:10 -0700 (PDT)
Received: from gws07.hcl.in (gws07.hcl.in [203.105.186.27]) by core3.amsl.com (Postfix) with ESMTP id 9AAE83A67B7 for <mpls-tp@ietf.org>; Thu, 17 Jun 2010 23:31:06 -0700 (PDT)
Received: from gws07.hcl.in (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 1C7EF20F0E1 for <mpls-tp@ietf.org>; Fri, 18 Jun 2010 11:54:56 +0530 (IST)
Received: from chn-hclin-ht02.CORP.HCL.IN (unknown [10.249.64.36]) by gws07.hcl.in (Postfix) with ESMTP id D12DF20F11E for <mpls-tp@ietf.org>; Fri, 18 Jun 2010 11:54:55 +0530 (IST)
Received: from CHN-HCLT-CASHT2.HCLT.CORP.HCL.IN (10.108.45.28) by chn-hclin-ht02.CORP.HCL.IN (10.249.64.36) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 18 Jun 2010 12:01:02 +0530
Received: from CHN-HCLT-EVS07.HCLT.CORP.HCL.IN ([fe80::f46b:fdf2:3218:985d]) by CHN-HCLT-CASHT2.HCLT.CORP.HCL.IN ([::1]) with mapi; Fri, 18 Jun 2010 11:59:18 +0530
From: "Vijayanand C - ERS, HCL Tech" <vijayc@hcl.in>
To: MPLS TP <mpls-tp@ietf.org>
Date: Fri, 18 Jun 2010 11:59:17 +0530
Thread-Topic: LDI generation during slow CC
Thread-Index: AcsOr5R5fjMFwGrSSt2OOtULqP2Q/A==
Message-ID: <66E3DDEEA70F0D469D1FFE238526B6ED29980BEF68@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_66E3DDEEA70F0D469D1FFE238526B6ED29980BEF68CHNHCLTEVS07H_"
MIME-Version: 1.0
X-TM-AS-Product-Ver: IMSS-7.0.0.3220-6.0.0.1038-17452.005
X-TM-AS-Result: No--5.073-7.0-31-1
X-imss-scan-details: No--5.073-7.0-31-1
X-TM-AS-User-Approved-Sender: No
Subject: [mpls-tp] LDI generation during slow CC
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, 18 Jun 2010 06:31:15 -0000

Hello all,
In draft-ietf-mpls-tp-fault, section 2.3 says that when CC is slow LDI enables faster switchover

"In more general MPLS environments the CC function may
   be running at a much slower rate.  In this environment, LDI enables
   faster switch-over upon a failure occurring along the LSP."


It is not clear in the spec how LDI will be generated when CC is slow and has not detected failure.
Is it implicit that the LSPs own detection mechanism ( refresh timeout, path tear etc..) will trigger the LDI ?
Can anyone clarify this ?


Regards
Vijay



DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. 
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have 
received this email in error please delete it and notify the sender immediately. Before opening any mail and 
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------