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
[email protected]
https://www1.ietf.org/mailman/listinfo/pce

.



_______________________________________________
Pce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pce

Reply via email to