PCE monitoring doc (was Re: [Pce] IPR PCE Monitoring)

dimitri papadimitriou <dpapadimitriou@psg.com> Thu, 16 August 2007 08:21 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ILabG-0000lt-RL; Thu, 16 Aug 2007 04:21:02 -0400
Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1ILabF-0000lo-T3 for pce-confirm+ok@megatron.ietf.org; Thu, 16 Aug 2007 04:21:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ILabF-0000lg-F2 for pce@ietf.org; Thu, 16 Aug 2007 04:21:01 -0400
Received: from psg.com ([147.28.0.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILabF-0006UH-08 for pce@ietf.org; Thu, 16 Aug 2007 04:21:01 -0400
Received: from localhost ([127.0.0.1]) by psg.com with esmtp (Exim 4.67 (FreeBSD)) (envelope-from <dpapadimitriou@psg.com>) id 1ILabC-000GOv-NS; Thu, 16 Aug 2007 08:21:00 +0000
Message-ID: <46C408C7.1080409@psg.com>
Date: Thu, 16 Aug 2007 10:20:23 +0200
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: JP Vasseur <jvasseur@cisco.com>
Subject: PCE monitoring doc (was Re: [Pce] IPR PCE Monitoring)
References: <AC162EA1-BFFA-41A5-B643-597D9C9630A9@cisco.com>
In-Reply-To: <AC162EA1-BFFA-41A5-B643-597D9C9630A9@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -104.2 (---------------------------------------------------)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: pce@ietf.org
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com
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>
Errors-To: pce-bounces@lists.ietf.org

hi j-p

as far as i remember, this doc. is still open for discussion from San 
Diego and Prague mtg discussion.

here below for the record

<http://www3.ietf.org/proceedings/06nov/minutes/pce.txt>

v03 has been reworked but does not provide answer to the concerns 
expressed so far - quoting the doc.

 > In PCE-based environments, it is critical to monitor the state of the

critical for what ? if computation time is an issue why delegate it 
(isn't that the safest assumption ?)

 > path computation chain for troubeshooting and performance monitoring
 > purposes:

troubleshooting of what ? if there is congestion/troubles how would you 
ensure the information received back is accurate ?

 > liveness of each element (PCE) involved in the PCE chain,

if i well remember the PCE is a client-server model (fundamental 
assumption about the PCE approach) hence, why the client needs to know 
the "chain" of PCE servers ?

 > detection of potential resource contention states

a t[0] contention, at t[1] message for perf.mon -> are running 
conditions identical ? since probabilisticaly, not what is the 
expectation behind this mechanism ?

would it be possible to have a "curve" of the deterioration of the 
performance as with an increasing number of computed path the number of 
"monitoring messages" will also increase ?

 > statistics in term of path computation times are examples of such
 > metrics of interest.

interest to who and for which purpose (detection is fine but what is the 
issue to be solved) ? like any system, PCE requires suitable planning 
and dimensioning wrt to perf.objectives i have impression that these 
fundamental design steps are skipped.

let's start discussion with this.

side note: the document states "In this document we call a "state 
metric" a metric that characterizes a PCE state" -> need to define the 
latter.

thanks,
-d.


JP Vasseur wrote:
> Hi,
> 
> Just let you know about an IPR disclosure that has been filed with the 
> IETF in relation to 
> http://tools.ietf.org/id/draft-vasseur-pce-monitoring-03.txt. You can 
> see the disclosure at https://datatracker.ietf.org/ipr/872/ and see the 
> terms offered by the IPR claimant.
> 
> Thanks,
> 
> JP.
> 
> 
> _______________________________________________
> 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