Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05

Qin Wu <bill.wu@huawei.com> Thu, 20 June 2013 00:37 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 D413621F9E37 for <xrblock@ietfa.amsl.com>; Wed, 19 Jun 2013 17:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.208
X-Spam-Level:
X-Spam-Status: No, score=-6.208 tagged_above=-999 required=5 tests=[AWL=0.391, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBx0RC+8N-MX for <xrblock@ietfa.amsl.com>; Wed, 19 Jun 2013 17:37:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EA7E621F9E31 for <xrblock@ietf.org>; Wed, 19 Jun 2013 17:36:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUB86931; Thu, 20 Jun 2013 00:36:57 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 20 Jun 2013 01:35:35 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 20 Jun 2013 01:35:59 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Thu, 20 Jun 2013 08:35:55 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05
Thread-Index: AQHOXI02E/6EsXw3xEis/tO+Qhjv9JkwOqgAgAL6qUCABtpggIAA2oNQgAH4+wCAAP/wkA==
Date: Thu, 20 Jun 2013 00:35:54 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43B4272E@nkgeml501-mbs.china.huawei.com>
References: <4FFE5264-C78F-4B45-BE8B-4EB649FD91EE@ntt-at.com> <578DC4BF-7282-4BBB-BA92-CCC7B29F0D7C@csperkins.org> <B8F9A780D330094D99AF023C5877DABA43B40E5F@nkgeml501-mbs.china.huawei.com> <962CF375-9496-45BA-8FD1-CAF3CEB20065@csperkins.org> <B8F9A780D330094D99AF023C5877DABA43B41FB9@nkgeml501-mbs.china.huawei.com> <D6CF4887-EF35-4C6F-8C76-5BAEBFFD35D1@csperkins.org>
In-Reply-To: <D6CF4887-EF35-4C6F-8C76-5BAEBFFD35D1@csperkins.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: xrblock-chairs <xrblock-chairs@tools.ietf.org>, xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05
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: Thu, 20 Jun 2013 00:37:34 -0000

Thanks!

-----Original Message-----
From: Colin Perkins [mailto:csp@csperkins.org] 
Sent: Thursday, June 20, 2013 1:20 AM
To: Qin Wu
Cc: Shida Schubert; xrblock-chairs; xrblock
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05

Qin,

Makes sense, thanks. 

Colin



On 18 Jun 2013, at 04:20, Qin Wu wrote:
> Good points. I fully agree.
> However changing measurement unit from RTP timestamp unit to ms may cause measurement unit inconsistency.
> 
> Taking loss concealment metrics block as an example, both 32 bit On-time Playout Duration field and 16 bit Mean Playout Interrupt Size uses the same measurement unit (ms), if we only change measurement unit for all 32 bit fields that carry loss concealment metrics to RTP timestamp unit, this cause
> Some fields in the block use "ms" as unit, some field uses RTP timestamp unit.
> 
> Taking concealment seconds metrics as another example, "SCS Threshold" field also uses milliseconds as unit.
> 
> Let me know what you think of this?
> 
> Regards!
> -Qin
> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org] 
> Sent: Tuesday, June 18, 2013 6:10 AM
> To: Qin Wu
> Cc: Shida Schubert; xrblock-chairs; xrblock
> Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05
> 
> Qin,
> 
> The length of time represented by an audio payload tends to be an integer number of milliseconds for frame-based codecs, but can have an arbitrary length for sample-based codecs. Using RTP timestamp units might allow you to precisely match up the timings, if that matters. Plus, don't you have RTP timestamp units, but would need to convert to milliseconds?
> 
> Colin
> 
> 
> 
> On 13 Jun 2013, at 06:34, Qin Wu wrote:
>> Colin,
>> Yes, you are right.
>> The length of time represented by audio playload in the RTP packet is usually measured using ms.
>> Another rationale is concealment metrics are just terminal related end system metrics and its calculation does not need to rely on RTP timestamp in the RTP packet.
>> 
>> Regards!
>> -Qin
>> -----Original Message-----
>> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Colin Perkins
>> Sent: Wednesday, June 12, 2013 12:02 AM
>> To: Shida Schubert
>> Cc: xrblock-chairs; xrblock
>> Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-loss-conceal-05
>> 
>> Shida,
>> 
>> I've read the draft, and believe it's in reasonable shape to progress. I would be interested in hearing the authors' rationale for choosing ms as the measurement unit rather than RTP timestamp units, however. It would seem that there might be an argument for using RTP timestamp units, so the reports can exactly line-up with the audio data in the RTP packets.
>> 
>> Colin
>> 
>> 
>> 
>> On 29 May 2013, at 17:53, Shida Schubert wrote:
>>> This is an announcement of a 2 weeks XRBLOCK WG last call on 
>>> "Report Block for Concealment metrics Reporting on Audio Applications" 
>>> prior to requesting publication of the document as a proposed standard. 
>>> 
>>> As per discussion at the last meeting, we are running a second 
>>> WGLC on this draft.
>>> 
>>> Please send your comments, including nits, to the list by the
>>> 
>>> 12th of June
>>> 
>>> If you read the draft and you see no issues, concerns, or nits, please
>>> express the fact that you have no issue progressing the draft on the
>>> list as well. 
>>> 
>>> The latest version can be found here:
>>> 
>>> http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-loss-conceal-05
>>> 
>>> Regards
>>> 
>>> Shida as co-chair
>>> _______________________________________________
>>> xrblock mailing list
>>> xrblock@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xrblock
>> 
>> 
>> 
>> -- 
>> Colin Perkins
>> http://csperkins.org/