IETF Logo Mail Archive

[Pce] Few comments/queries on draft-ietf-pce-pce-initiated-lsp-04

Venugopal Reddy K <venugopalreddyk@huawei.com> Wed, 10 June 2015 07:33 UTC

Return-Path: <venugopalreddyk@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FD41AC43A for <pce@ietfa.amsl.com>; Wed, 10 Jun 2015 00:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 O6lzUhkgOQLh for <pce@ietfa.amsl.com>; Wed, 10 Jun 2015 00:33:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24FE1AC434 for <pce@ietf.org>; Wed, 10 Jun 2015 00:33:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BXF00018; Wed, 10 Jun 2015 07:33:52 +0000 (GMT)
Received: from SZXEML428-HUB.china.huawei.com (10.82.67.183) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 10 Jun 2015 08:32:51 +0100
Received: from szxeml561-mbx.china.huawei.com ([169.254.5.64]) by szxeml428-hub.china.huawei.com ([10.82.67.183]) with mapi id 14.03.0158.001; Wed, 10 Jun 2015 15:32:07 +0800
From: Venugopal Reddy K <venugopalreddyk@huawei.com>
To: pce <pce@ietf.org>, "inaminei@google.com" <inaminei@google.com>
Thread-Topic: Few comments/queries on draft-ietf-pce-pce-initiated-lsp-04
Thread-Index: AdCjT4xvj1BlUKqBR8qnFF/EsjI9dg==
Date: Wed, 10 Jun 2015 07:32:06 +0000
Message-ID: <10376B02BC561F4185654159EF7900204593E90C@szxeml561-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.146.97]
Content-Type: multipart/alternative; boundary="_000_10376B02BC561F4185654159EF7900204593E90Cszxeml561mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/pce/c9QP8j_nscNm_3YYiWkIOIyB8M4>
Subject: [Pce] Few comments/queries on draft-ietf-pce-pce-initiated-lsp-04
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2015 07:33:59 -0000

Hi, Everyone!

Have few comments/queries on draft-ietf-pce-pce-initiated-lsp-04. Could you please clarify on below points:


  Section 6

  In case of PCEP session failure, control over PCE-initiated LSPs
   reverts to the PCC at the expiration of the redelegation timeout.  At
   this point, the LSP is an "orphan" until the expiration of the State
   Timeout timer.  To obtain control of a PCE-initiated LSP, a PCE
   (either the original or one of its backups) sends a PCInitiate
   message, including just the SRP and LSP objects, and carrying the
   PLSP-ID of the LSP it wants to take control of

1.       In case of Backup PCE, what is the trigger point to send PCInitiate message to take control of orphan PCE-initiated LSP? I am wondering how does a backup PCE come to know that some LSPs are orphaned?



2.       Another option would be, if PCC takes charge and delegate the orphaned PCE initiated LSPs to backup PCE based on the local policy?


Response will be appreciated.

Thanks a lot.

Regards,
Venu

v2.23.0 | Report a Bug | By Email