Re: [Pce] RE: Comment on draft-ietf-pce-pcecp-interarea-reqs-00.txt

JP Vasseur <jvasseur@cisco.com> Fri, 13 January 2006 13:11 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExOiU-00084k-Gr; Fri, 13 Jan 2006 08:11:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExOiS-000845-Qg for pce@megatron.ietf.org; Fri, 13 Jan 2006 08:11:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04340 for <pce@ietf.org>; Fri, 13 Jan 2006 08:10:19 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ExOpj-0002c8-32 for pce@ietf.org; Fri, 13 Jan 2006 08:19:14 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 13 Jan 2006 05:11:28 -0800
X-IronPort-AV: i="3.99,365,1131350400"; d="scan'208,217"; a="391416368:sNHT52795504"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k0DDBRWF020340; Fri, 13 Jan 2006 05:11:27 -0800 (PST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 13 Jan 2006 08:11:27 -0500
Received: from [192.168.1.101] ([10.86.240.196]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 13 Jan 2006 08:11:26 -0500
In-Reply-To: <D109C8C97C15294495117745780657AE03FCE27D@ftrdmel1.rd.francetelecom.fr>
References: <D109C8C97C15294495117745780657AE03FCE27D@ftrdmel1.rd.francetelecom.fr>
Mime-Version: 1.0 (Apple Message framework v746.2)
Message-Id: <B6B66917-0277-4DB5-A353-26138286B0A4@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] RE: Comment on draft-ietf-pce-pcecp-interarea-reqs-00.txt
Date: Fri, 13 Jan 2006 08:10:51 -0500
To: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@francetelecom.com>, Zhang Renhai <zhangrenhai@huawei.com>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 13 Jan 2006 13:11:26.0422 (UTC) FILETIME=[DBFB3760:01C61842]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Cc: pce@ietf.org
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0456990763=="
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

Hi,

On Jan 13, 2006, at 4:22 AM, LE ROUX Jean-Louis RD-CORE-LAN wrote:

> Hi Zhang
>
> sorry for replying so late...
>
> Please see inline,
>
> De : Zhang Renhai [mailto:zhangrenhai@huawei.com]
> Envoyé : mercredi 28 décembre 2005 08:04
> À : LE ROUX Jean-Louis RD-CORE-LAN
> Cc : pce@ietf.org
> Objet : Comment on draft-ietf-pce-pcecp-interarea-reqs-00.txt
>
> Hi, Jean-Louis
>
>  I have some comment on the draft draft-ietf-pce-pcecp-interarea- 
> reqs-00.txt
>
>  In section 7.11.1, In case of network failure, jittering will be  
> used to avoid
> simultaneous requests sent to one PCE. Could more consideration be  
> given here to
> the preemptment, becouse the jittering timeout is stochastic, some  
> lower request
> may be served before a higher request and the path may be  
> calculated differently.
> which may increase the probability of a preemptment.
>
> JLLR: You raised a good point.
> First of all note that this point is not a protocol requirement,  
> this is a local implementation issue, and the jittering was just  
> given as an example...
> The PCC could apply different jitter to low priority and high  
> priority requests, and could send
> high priority request before low priority one, this is a local PCC  
> decision.
> Also the request prioritization function could be used so that the  
> PCE serves high priority requests first. The way a PCE is going to  
> handle request prioritites is also a local implementation issue.
> Maybe we should remove this sentence to avoid any confusion.
> By the way note that this section is generic and has just been  
> moved to the generic requirement draft.
> So we will have to clarify in the generic draft.
Thanks indeed to remove this section since this is out of scope.

JP.
>
>
>  I have always been thinking a question: if a PCC will not perform  
> the CSPF
> computation, why does it still maintain the TEDB any longer? which  
> may consume
> a lot of memory and CPU of a LSR.This question dost not aid at this  
> draft.
>
> [JLLR] A LSR may be a PCC for some LSPs and a PCE for other LSPs.
> Anyway a LSR that runs ISIS or OSPF for IP routing has to maintain  
> a LSDB. I agree removing TE info would save some memory and CPU but  
> the gain sounds quite low compared to the impact: For any  
> computation, even a simple intra-area CSPF, you would have to ask a  
> PCE, and this may lead to a high PCE stress. You would have a small  
> CPU gain on LSRs at a cost of a huge CPU consumption on PCEs...
>
> In inter-area environment,sometimes, a PCC may wish to get as many  
> paths as possible,
> for all kinds of purpose,so could the PCC send the request to more  
> than one PCEs?
>
> [JLLR] Yes, and this is a procedure local to the PCC, that does not  
> imply specific PCECP procedure.
>
> Thanks for these valuable comments
>
> Regards,
>
> JL
>
>
> Regards,
> Zhang
> _______________________________________________
> Pce mailing list
> Pce@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/pce

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce