Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-07.txt

Colin Perkins <csp@csperkins.org> Mon, 20 May 2013 11:07 UTC

Return-Path: <csp@csperkins.org>
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 D994521F912C for <xrblock@ietfa.amsl.com>; Mon, 20 May 2013 04:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.357
X-Spam-Level:
X-Spam-Status: No, score=-106.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lopAgV-+UpJJ for <xrblock@ietfa.amsl.com>; Mon, 20 May 2013 04:07:21 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) by ietfa.amsl.com (Postfix) with ESMTP id A10FA21F8A14 for <xrblock@ietf.org>; Mon, 20 May 2013 04:07:14 -0700 (PDT)
Received: from [130.209.247.112] (port=61208 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1UeNvp-00087y-TU; Mon, 20 May 2013 12:07:10 +0100
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43B32A4A@nkgeml501-mbs.china.huawei.com>
Date: Mon, 20 May 2013 12:07:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5056F417-CC33-4ED2-8F15-DF44FEB4AEEE@csperkins.org>
References: <B8F9A780D330094D99AF023C5877DABA43B1DC6F@nkgeml501-mbs.china.huawei.com> <913AF110-B60A-4DF6-8B91-C525D65E8917@csperkins.org> <B8F9A780D330094D99AF023C5877DABA43B30055@nkgeml501-mbs.china.huawei.com> <3606100D-E90F-4C6F-B400-EE0F8AE7F1C0@csperkins.org> <B8F9A780D330094D99AF023C5877DABA43B32A4A@nkgeml501-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1283)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: 'xrblock-chairs' <xrblock-chairs@tools.ietf.org>, 'xrblock' <xrblock@ietf.org>
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-07.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: Mon, 20 May 2013 11:07:26 -0000

On 20 May 2013, at 12:03, Qin Wu wrote:
> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org] 
> Sent: Monday, May 20, 2013 6:46 PM
> To: Qin Wu
> Cc: 'xrblock'; 'xrblock-chairs'
> Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-07.txt
> 
> On 20 May 2013, at 03:26, Qin Wu wrote:
>> Hi, Colin:
>> Thank for your valuable review, please see my reply inline below.
>> 
>> Regards!
>> -Qin
>> 
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org] 
>> Sent: Thursday, May 16, 2013 8:58 PM
>> To: Qin Wu
>> Cc: 'xrblock'; 'xrblock-chairs'
>> Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-07.txt
>> 
>> Qin,
>> 
>> While I think this is in good shape, I do still have some comments on this version:
>> 
>> The ABNF in Section 4.1 defines mediatype and mosreference rules. It's not clear that these are needed: can't the media types and resolution be inferred from the payload type? If they are needed, I think their purpose needs to be clearer, and the draft needs to better explain how they interact with SDP O/A, especially in terms of failure modes. 
>> 
>> [Qin]: I agree mediatype can be inferred from payload type. Ad for mosrefereence, for audio application, I agree  whether it is narrowband or wideband, this can also be inferred from payload type since payload type will indicate whether it is narrowband or wideband.
>> For video, it seems payload type doesn't distinguish standard definition video codec and high definition video codec.
> 
> If you can't tell what video QoE metric to use from the payload format and it's parameters, then you might need to keep the parameter. I was assuming that the information needed was available.
> 
> [Qin]: Yes, I see.
> 
>> Anyway I am okay to remove mediatype and mosreference.
>> The question is shall we need to remove media type in the registry when we decide remove media type from SDP format?
> 
> I don't understand your question. Can you clarify?
> 
> [Qin]: Sorry for bringing you confusion. What I am saying is 
> In the registration template we defined in the section 5.4,"type" field is defined to indicate which media type the calculation algorithm is applied to.
> I am wondering if you we agree to remove syntax element "mediatype" in the SDP, shall we remove "type" in the registration template as well?

I wouldn't think so, since that defines what media types it applies to.

Colin



>> The ABNF defines video and multimedia mediatypes, but this draft only defines audio metric report blocks. 
>> 
>> [Qin]:That's not true. The single stream per segment will be used for video and multimedia media types. Multimedia media type means it can be either audio media type or video media type or audiovisual media type, e.g., P.1201.
>> 
>> The ABNF and the table of registrations in the IANA considerations include P1201_01, P1201_02, P1202_01, and P1202_02 algorithms, which only work for multimedia or video, but this draft only defines audio metric report blocks.
>> 
>> [Qin]: See above.
>> 
>> The policies for the new registry of calculation algorithms in Section 5.4 state that the information require should include "how values of the metric are reported in the one 16-bit fields or 13-bit fields", but the registration template and initial assignments do not do so. 
>> 
>> [Qin]:I am not sure how this sentence " how values of the metric are reported in the one 16-bit fields or 13-bit fields " affects registration template and initial assignment since this sentence really means how we format "MOS value" in 16 bits or 13 bits. The details of definition of "MOS value" field
>> Has been specified in the section 3.2.1 for 16-bit "MOS value" and in the section 3.2.2 for 13-bit "MoS value". What am I missing?
> 
> If you need to specify something different about how the metric values are reported for each metric then the IANA registration template needs to specify what information is needed. If not, then you should remove that sentence from Section 5.4, since it implies that additional information is needed. 
> 
> [Qin]: Agree, thank for your clarification.
> 
> Colin
> 
> 
> 
>> Regards,
>> Colin
>> 
>> 
>> 
>> On 14 May 2013, at 03:20, Qin Wu wrote:
>>> We have a minor update to QoE draft which incorporates the similar changes that are applied to burst gap related drafts.
>>> Also we add a new appendix to apply RFC6390 template.
>>> One comment was raised in the Last IETF meeting is about suggestion on soliciting review from SDP Directorate review for SDP part.
>>> We think the current version is ready to go for such review and WGLC.
>>> 
>>> Regards!
>>> -Qin
>>> -----Original Message-----
>>> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
>>> Sent: Tuesday, May 14, 2013 10:11 AM
>>> To: i-d-announce@ietf.org
>>> Cc: xrblock@ietf.org
>>> Subject: I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-07.txt
>>> 
>>> 
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>> This draft is a work item of the Metric Blocks for use with RTCP's Extended Report Framework Working Group of the IETF.
>>> 
>>> 	Title           : RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric Reporting
>>> 	Author(s)       : Alan Clark
>>>                        Qin Wu
>>>                        Roland Schott
>>>                        Glen Zorn
>>> 	Filename        : draft-ietf-xrblock-rtcp-xr-qoe-07.txt
>>> 	Pages           : 22
>>> 	Date            : 2013-05-13
>>> 
>>> Abstract:
>>> This document defines an RTP Control Protocol (RTCP) Extended Report
>>> (XR) Block including two new segment types and associated SDP
>>> parameters that allow the reporting of QoE metrics for use in a range
>>> of RTP applications.
>>> 
>>> 
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-qoe
>>> 
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-qoe-07
>>> 
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcp-xr-qoe-07
>>> 
>>> 
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>> 
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>> _______________________________________________
>>> xrblock mailing list
>>> xrblock@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xrblock
>> 
>> 
>> 
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>> 
>> 
>> 
> 
> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 



-- 
Colin Perkins
http://csperkins.org/