Hi Mach,

On Oct 31, 2006, at 4:36 AM, Mach Chen wrote:

Hi JP,
 
Your I-D is great.

Thanks.

 
I have some comments and questions.
 
1.Section 4.1
 
"C (Check) - 1 bit: when set, this indicates that the performance
   metric of interest is the PCE's availability."
 
When this "C bit" present in a PCMonRep messages, whether it indicates the PCE is available? Is it enough to indicate a PCE's availability? Some more detail info may be desirable.
 

Yes, the aim of this bit is just to check the PCE's liveness. As pointed in the ID, other metrics may be collected that will be carried in new objects / flags (to be defined). 

 
2.Section 4.1
"The monitoring-id-number MUST be incremented each time a new monitoring is sent to a PCE."
 
Although 32-bit monitoring-id-number is a huge number, it will overflow one day.So, when this happen, how to deal with it? Restart another round or by other means?

Yes the counter will simply roll-over and considering the set of values, the probability of overlap is extremely low ... to say the least. I'll clarify this.

 
When a PCMonReq message is sent along with a PCE chain, the monitoring-id-number is always the same or each PCE will regenerate a new one?
 

Yes,

3.Section 4.3
 
What's the meaning of "Variance-processing-time"?
 

This is the mean squared deviation.

4.Section 7
"Reception of a PCMonRep message: upon receiving a PCMonRep message,
   the PCE processes the request, adds the relevant objects to the
   PCMonRep message and forwards the PCMonRep message to the upstream
   requesting PCE or PCC."
For a specific PCMonReq message, whether all the PCE along with the PCE chain will do the some collection or some of them will do some special collection?

It is requested to gather performance metrics from all PCE along the path computation chain. That said, if some of them do not provide the requested data, then the I bit of the MONITORING object is set.

Thanks for your comments.

JP.

 
 
Thanks,
 
Mach
----- Original Message -----
Sent: Friday, October 20, 2006 8:30 PM
Subject: [Pce] Feed-back on Monitoring ?

Hi,

See below a new ID related to the monitoring of PCE-based path computation architecture so as to required various performance metrics such as liveness verification of the various elements of a path computation chain, processing time spent on path computation at each hop (for performance monitoring or troubleshooting, ...). 

Comments and opinions are most welcome.

Thanks.

JP. 


Begin forwarded message:

Date: October 20, 2006 2:50:01 AM EDT
Subject: I-D ACTION:draft-vasseur-pce-monitoring-01.txt 

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


Title : A set of monitoring tools for Path Computation Element based Architecture
Author(s) : J. Vasseur
Filename : draft-vasseur-pce-monitoring-01.txt
Pages : 16
Date : 2006-10-19

A Path Computation Element (PCE) based architecture has been
   specified for the computation of Traffic Engineering (TE) Label
   Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) networks in the context of single or
   multiple domains (where a domain is referred to as a collection of
   network elements within a common sphere of address management or path
   computational responsibility such as IGP areas and Autonomous
   Systems).  In such PCE-based environment it is thus critical to
   monitor the state of the path computation chain and potentially
   gather various performance metrics with regards to the set of
   involved PCE(s) that can be used for performance monitoring and
   troubleshooting purposes.  This document specifies procedures and
   extensions to the Path Computation Element Protocol (PCEP) in order
   to gather such information.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to 
[EMAIL PROTECTED] with the word unsubscribe in the body of 
the message. 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-vasseur-pce-monitoring-01.txt".

A list of Internet-Drafts directories can be found in

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
"FILE /internet-drafts/draft-vasseur-pce-monitoring-01.txt".

NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility.  To use this
feature, insert the command "ENCODING mime" before the "FILE"
command.  To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader.  Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Content-Type: text/plain
Content-ID: <[EMAIL PROTECTED]>

_______________________________________________
I-D-Announce mailing list




_______________________________________________
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