Re: [xrblock] XRBlock Template...follow PMOL?
"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 14 February 2011 10:13 UTC
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: xrblock@core3.amsl.com
Delivered-To: xrblock@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E77AF3A6A91 for <xrblock@core3.amsl.com>; Mon, 14 Feb 2011 02:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.989
X-Spam-Level:
X-Spam-Status: No, score=-104.989 tagged_above=-999 required=5 tests=[AWL=1.260, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-FvNTh3FOYA for <xrblock@core3.amsl.com>; Mon, 14 Feb 2011 02:13:34 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 9E5DB3A6CA1 for <xrblock@ietf.org>; Mon, 14 Feb 2011 02:13:32 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p1EADgBx030260 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 14 Feb 2011 11:13:45 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 14 Feb 2011 11:13:45 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Qin Wu <sunseawq@huawei.com>, Peter Musgrave <peter.musgrave@magorcorp.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Date: Mon, 14 Feb 2011 11:13:44 +0100
Thread-Topic: [xrblock] XRBlock Template...follow PMOL?
Thread-Index: AcvL8un4906zGKFmQYSRvkksNFhB3wAPMY1w
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E828191@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <7C4F525D-BFF5-40E6-A373-23D64312416F@magorcorp.com> <016601cbcbf2$b3893930$30298a0a@china.huawei.com>
In-Reply-To: <016601cbcbf2$b3893930$30298a0a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: Roni Even <Even.roni@huawei.com>
Subject: Re: [xrblock] XRBlock Template...follow PMOL?
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Feb 2011 10:13:35 -0000
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
- [xrblock] XRBlock Template...follow PMOL? Peter Musgrave
- Re: [xrblock] XRBlock Template...follow PMOL? DRAGE, Keith (Keith)
- Re: [xrblock] XRBlock Template...follow PMOL? Peter Musgrave
- Re: [xrblock] XRBlock Template...follow PMOL? Qin Wu
- Re: [xrblock] XRBlock Template...follow PMOL? DRAGE, Keith (Keith)
- Re: [xrblock] XRBlock Template...follow PMOL? Peter Musgrave
- Re: [xrblock] XRBlock Template...follow PMOL? Qin Wu
- Re: [xrblock] XRBlock Template...follow PMOL? Qin Wu