IETF Logo Mail Archive

Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe

"Roni Even" <ron.even.tlv@gmail.com> Thu, 22 August 2013 10:40 UTC

Return-Path: <ron.even.tlv@gmail.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 46C5F11E8147 for <xrblock@ietfa.amsl.com>; Thu, 22 Aug 2013 03:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 lQUfnkRI6ksB for <xrblock@ietfa.amsl.com>; Thu, 22 Aug 2013 03:40:26 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 77E4611E80ED for <xrblock@ietf.org>; Thu, 22 Aug 2013 03:40:26 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id u54so1499706wes.9 for <xrblock@ietf.org>; Thu, 22 Aug 2013 03:40:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=NL6grNvuhl21jpSOcMGAh6yIO4D67PkNZfyjwXR1hWc=; b=J42r0J81rAwrPcmABvJbkfon9niMdc7O3Ulsf21FWzE2BhrWiXFN3EQajZpJtmHQaA yPlxKu7+D0xVKf70zLap6N8ta/zel+Bf+UnJahhaxyG88ZVrFHl2QjmKQvw+Rc0L3Vog +qdTfssAFegTaZ9XQkrySniTWBJ0aQNN3owS/z5h8vbiLiFalW9HdRlyCv2O0XIyth1X yOMMPQQy562qtC6LUvfG9jvBzAjqEV09R/tV4Ew2TZRfkCjzy7mz1KKdl1CN8RYfezct 5uCd+JS21zks4aaC96XEigomi03F/037cottNPJUg3KHc53o847o5ZjZl8XtbC3r6RaJ 5eMg==
X-Received: by 10.194.60.73 with SMTP id f9mr782145wjr.65.1377168025445; Thu, 22 Aug 2013 03:40:25 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id dt17sm37061071wic.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 22 Aug 2013 03:40:24 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, xrblock@ietf.org
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4B0F@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128B4B0F@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 22 Aug 2013 13:38:02 +0300
Message-ID: <035d01ce9f23$af873ab0$0e95b010$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGOGeCHL8tC4P27bQHTvwJAGeBJsZoiEPkQ
Content-Language: en-us
Subject: Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe
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, 22 Aug 2013 10:40:27 -0000

Hi,
I reviewed the document looks OK. Two editorial comments

1. In section 4.1, mosref has three values l, m, h yet the text 
" the syntax element "mosref" is referred to the media resolution  relative
reference (e.g., Narrowband (3.4kHz) Speech and Standard  Definition (SD)
Resolution Video with lower resolution, Wideband
   (7kHz) Speech and High Definition (HD) Resolution Video with higher
resolution).  MOS scores reported in the mos metrics block might vary with
the MoS reference; For example, MOS values for narrowband,
   wideband codecs occupy the same range but SHOULD be reported in different
value.  For video application, MoS scores for SD resolution, HD resolution
video also occupy the same ranges and
   SHOULD be reported in different value."
I think a better example and division should be for audio l = narrow band
3.5 Khz, m should be wideband 7 Khz and h should be super wideband or higher
>14kHz. For video l should be CIF or lower and h should  be 1080HD or higher
and m should be betwee CIF and 1080HD.

2.  section 4.1 defines mapentry =  "calg:" 1*5 DIGIT ["/" direction].  From
section 4.2 I got the impression that the range [4096-4351] is not to be
used as valid value. I think it should be clarified in section 4.1 what are
the valid range.

Thanks
Roni



> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Romascanu, Dan (Dan)
> Sent: 21 August, 2013 4:36 PM
> To: xrblock@ietf.org
> Subject: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe
> 
> Hi,
> 
> This is the second WGLC for the Internet-Draft 'RTP Control Protocol
(RTCP)
> Extended Report (XR) Blocks for MoS Metric Reporting' previously known as
> 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for QoE Metric
> Reporting'. Please send your comments, questions, and concerns to the WG
> list before Wednesday 9/4. If you have no comments or questions and you
> believe that this document is ready for submission to the IESG for
> consideration as a Proposed Standard, please send a message stating this.
> 
> The latest version of the document can be retrieved from
> http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-qoe-10.txt.
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

v2.23.0 | Report a Bug | By Email