Re: [xrblock] [rtcweb] FW: I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt

Qin Wu <bill.wu@huawei.com> Sat, 29 September 2012 03:40 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29ADE21F8496; Fri, 28 Sep 2012 20:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.81
X-Spam-Level:
X-Spam-Status: No, score=-4.81 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nD7ZXO2atBAR; Fri, 28 Sep 2012 20:40:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4156B21F85C4; Fri, 28 Sep 2012 20:40:54 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKD04659; Sat, 29 Sep 2012 03:40:52 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 29 Sep 2012 04:39:46 +0100
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 29 Sep 2012 04:40:33 +0100
Received: from w53375 (10.138.41.149) by szxeml417-hub.china.huawei.com (10.82.67.156) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 29 Sep 2012 11:40:28 +0800
Message-ID: <CC9C3260223F4A52879A330E37711A24@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Harald Alvestrand <harald@alvestrand.no>, rtcweb@ietf.org
References: <EDC652A26FB23C4EB6384A4584434A04081AB2D9@307622ANEX5.global.avaya.com><3C8D9E30D9654AD0A3E1F21668D1CBFB@china.huawei.com><EDC652A26FB23C4EB6384A4584434A04081AB4AD@307622ANEX5.global.avaya.com><20E112E82D30472AA48E653041BC0A78@china.huawei.com>, <EDC652A26FB23C4EB6384A4584434A04081AB5BE@307622ANEX5.global.avaya.com><5F7BCCF5541B7444830A2288ABBEBC96218CFC7599@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <50658AA6.5090200@alvestrand.no>
Date: Sat, 29 Sep 2012 11:40:26 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Cc: xrblock@ietf.org
Subject: Re: [xrblock] [rtcweb] FW: I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 29 Sep 2012 03:40:57 -0000

Hi,Harald:
----- Original Message ----- 
From: "Harald Alvestrand" <harald@alvestrand.no>
To: <rtcweb@ietf.org>
Sent: Friday, September 28, 2012 7:31 PM
Subject: Re: [rtcweb] [xrblock]FW: I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt


> On 09/27/2012 01:20 AM, Schwarz, Albrecht (Albrecht) wrote:
>>> I am happy to see my comments being forwarded to rtcweb@ietf.org if
>> they
>>> are interested and want to more input from XRBLOCK WG. However I am
>> not
>>> sure how much of their work is related to XRBLOCK work? Do they only
>>> look for some basic metrics obtained from SR/RR. But I agree with you
>>> consistency between the metrics used by RTCP XR and RTCWEB is a good
>>> thing.
>> The work on "rtcweb-stats" is related to XRBLOCK in my opinon.
>> At least the "basic metrics from SR/RR" with respect to packet loss are controversial and could be misleading, and should be replaced by correspondent XR performance metric types.
>> The deficiency of some of these basic metrics was one reason to start work on extension reports (XR, and former HR).
> Indeed. The reason I started the document with packet counts and packet 
> loss from SR/RR was that I thought these would be uncontroversial and 
> unambiguous; I'm seeking guidance from XR people on what other metrics 
> are well known enough - and implemented widely enough - that it makes 
> sense to include them.
> 
> (For reference, the WebRTC codebase seems to decode block type 7 and no 
> other block type....)

[Qin]: For jitter, you may refer to both RFC3550 section 6.4.1 for inter-arrival jitter and
draft-ietf-xrblock-rtcp-xr-pdv for "2-point PDV" and "Absolute Packet Delay Variation 2 (MAPDV2) ".
Since jitter is also known as Packet Delay Variation.

For other metrics, I think you may also include round trip delay metric by referring to draft-ietf-rtcp-xr-delay
include discard metric by referring to draft-ietf-rtcp-xr-discard.

For measurement timing for these XR blocks, you should refer to draft-ietf-xrblock-meas-identity.

If you look into end device related metrics, you may look at jitter buffer metric,
concealment seconds metrics, loss concealment metrics developed in XRBLOCK WG, 
these metrics also affect real time appliation quality.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb