Re: [xrblock] XRBlock Template...follow PMOL?

No, I am not expecting draft-ietf-sipping-rtcp-summary to reference small and resuable new metrics report that will be developed in XRBlock.
We may let it be. Actually draft-ietf-sipping-rtcp-summary make a good use of a larger application specific metric, i.e., VOIP metric report 
defined in RFC3611.

Regards!
-Qin
----- Original Message ----- 
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Qin Wu" <sunseawq@huawei.com>; "Peter Musgrave" <peter.musgrave@magorcorp.com>; <xrblock@ietf.org>
Cc: "Roni Even" <Even.roni@huawei.com>
Sent: Monday, February 14, 2011 6:13 PM
Subject: RE: [xrblock] XRBlock Template...follow PMOL?

Draft-ietf-sipping-rtcp-summary has already been published as RFC 6035. Are you proposing that XRBLOCK should do a revision?

Regards

Keith

________________________________

From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Qin Wu
Sent: 14 February 2011 02:56
To: Peter Musgrave; xrblock@ietf.org
Cc: Roni Even
Subject: Re: [xrblock] XRBlock Template...follow PMOL?

Hi,
I agree that all the XRBlock work should observe the guideline of draft-ietf-pmol-metrics-framework-06
and it is good to have such XRBlcok Template as checklist to check any inconsistency in the new XRBlock
work.
As you know, [I-D.ietf-pmol-metrics-framework] provides the guideline to develop new performance metrics 
that is applicable to the IETF environment and Permance metric  may take different data formats. Therefore 
It seems to me all the existing XRBlock work including RFC3611 has already been in accordance with the
guideline in the PMOLFRAME, am I right? 

What's more I think SIP event package defined in [I-D.ietf-sipping-rtcp-summary], 
RAQMON Protocol Data Unit define in  [RFC4710] should also followed the guideline
for developing performance metrics in PMOLFRAME whether or not they make 
reference to PMOLFRAME.

As for the concern to XRBlock Template elements, I am wondering if all the elements
listed in PMOLFRAME is in the scope of current XRBlock Charter, e.g.,
Measurement method? Does it indicate the the scope of XRBlock WG needs to be
enlarged if such XRBlock Template with all elements is adopted?

Regards!
-Qin
----- Original Message ----- 

From: Peter Musgrave <mailto:peter.musgrave@magorcorp.com>  
To: xrblock@ietf.org 
Cc: Roni Even <mailto:Even.roni@huawei.com>  
Sent: Sunday, February 13, 2011 8:55 PM
Subject: [xrblock] XRBlock Template...follow PMOL?

Hi all, 

In our charter it states: "The group will consider the guidelines for performance metric 
development currently being discussed in the PMOL working group." 

So let's consider them. 

I'd suggest we develop a standard template (as is used e.g. for SIP event packages) for XR block definitions. PMOL already defines elements it wants in the template. 

I have provided a typical XR draft and the PMOL guidelines below. 

I would suggest we agree on a standard template for XR blocks which meet our needs and fit in with PMOL. I am willing to create a first cut of this template but first:

Q: Is such a template a good idea?
Q: Does anyone have any concerns about the PMOL template elements?
Q: Is there anything else people want to see in a template?

Regards, 

Peter Musgrave
(as co-chair)

PMOL Template (from http://tools.ietf.org/html/draft-ietf-pmol-metrics-framework-07)
Normative
   o  Metric Name
   o  Metric Description
   o  Method of Measurement or Calculation
   o  Units of Measurement
   o  Measurement Point(s) with potential Measurement Domain
   o  Measurement Timing

Informative
   o  Implementation
   o  Verification
   o  Use and Applications
   o  Reporting Model

A typical XR draft has a structure such as (e.g. http://tools.ietf.org/id/draft-ietf-avt-rtcp-xr-burst-gap-discard-02.txt). While this draft makes reference to PMOLFRAME
there are elements which are not as per the latest PMOL draft. 
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Burst and Gap Discard Report Block . . . . . . . . . . . .  3
     1.2.  RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . .  3
     1.3.  Performance Metrics Framework  . . . . . . . . . . . . . .  3
     1.4.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Burst/Gap Discard Block  . . . . . . . . . . . . . . . . . . .  6
     3.1.  Report Block Structure . . . . . . . . . . . . . . . . . .  6
     3.2.  Definition of Fields in Burst/Gap Discard Report Block . .  6
     3.3.  Derived metrics based on reported metrics  . . . . . . . .  8
   4.  Considerations for Voice-over-IP applications  . . . . . . . . 10
   5.  SDP Signaling  . . . . . . . . . . . . . . . . . . . . . . . . 11
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
     6.1.  New RTCP XR Block Type value . . . . . . . . . . . . . . . 12
     6.2.  New RTCP XR SDP Parameter  . . . . . . . . . . . . . . . . 12
     6.3.  Contact information for registrations  . . . . . . . . . . 12
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13

________________________________

_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock