Re: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt - review

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Wed, 17 October 2012 07:04 UTC

Return-Path: <rachel.huang@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 22C5A21F8658 for <xrblock@ietfa.amsl.com>; Wed, 17 Oct 2012 00:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.407
X-Spam-Level:
X-Spam-Status: No, score=-6.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, 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 uLC8azkS6z5V for <xrblock@ietfa.amsl.com>; Wed, 17 Oct 2012 00:04:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 628EA21F86C3 for <xrblock@ietf.org>; Wed, 17 Oct 2012 00:04:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKR30864; Wed, 17 Oct 2012 07:04:08 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 17 Oct 2012 08:02:07 +0100
Received: from SZXEML442-HUB.china.huawei.com (10.82.67.180) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 17 Oct 2012 08:02:55 +0100
Received: from SZXEML539-MBX.china.huawei.com ([169.254.6.74]) by szxeml442-hub.china.huawei.com ([10.82.67.180]) with mapi id 14.01.0323.003; Wed, 17 Oct 2012 15:02:50 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt - review
Thread-Index: Ac2ruZQ/bbW4+gpOSkG2a9MAWtTFsgAeqzKw
Date: Wed, 17 Oct 2012 07:02:50 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB4438ED69@szxeml539-mbx.china.huawei.com>
References: <00a501cdabbc$8d00e5a0$a702b0e0$@gmail.com>
In-Reply-To: <00a501cdabbc$8d00e5a0$a702b0e0$@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.163]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt - review
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: Wed, 17 Oct 2012 07:04:14 -0000

Hi Roni,

Thanks for your review. Please see my reply inline.

Best Regards!
Rachel


-----Original Message-----
From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: Wednesday, October 17, 2012 12:38 AM
To: Huangyihong (Rachel); xrblock@ietf.org
Subject: RE: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt - review

Hi,
I read the draft and have some comments.

1. Is these blocks used for any media type or just video. The text hints at
video but it will be good to discuss it in the introduction.

[Rachel]: The first two blocks (Burst/Gap Loss Summary Statistics Block and Burst/Gap Discard Summary Statistics Block) are applicable to any media type and not limited to video, while the last metrics block (i.e., Frame Impairment Statistics Summary Block) is only used for video. We would add some texts to clarify this.

2. In the introduction the following sentence "These two blocks are intended
   to be used in conjunction with information from the Burst Gap Loss
   metric block or Burst Gap Discard metric block, and on which these
   two block therefore depends." Maybe add reference to the two metric
blocks since they are mentioned as normative.

[Rachel]: Okay.

3. The draft talk about frames and packet. Current codecs like H.264 use the
term access units and IDR, look at section 4.1 of RFC6184 maybe use some of
the terminology from there in the terminology section.

[Rachel]: Good point, for terminology consistency, we'd like to propose the following change to terminology section:
OLD TEXT:
" Picture Type
      Picture types used in the different video algorithms compose of
      the key-frame and the Derived frame.  Key-frame is also called a
      reference frame and used as a reference for predicting other
      pictures.  It is coded without prediction from other pictures.
      The Derived frame is derived from Key-frame using prediction from
      the reference frame.
"

NEW TEXT:

"
  Picture Type
      Picture types used in the different video algorithms compose of
      the key frame and the Derived frame.  Key frame is also called a
      intra-coded frame [H.222.0] or IDR picture [H.264]and used as a reference frame for predicting other
      pictures.  It is coded without prediction from other pictures.
      The Derived frame is derived from Key-frame using prediction.
"

4. in section 3.2.2 the reserved field has the definition of the I field.

[Rachel]: Good catch and will fix this.


Thanks
Roni even
-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf
Of Huangyihong (Rachel)
Sent: 15 October, 2012 6:04 AM
To: xrblock@ietf.org
Subject: [xrblock] FW: I-D Action:
draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt

Dear all,

Here is the update of draft-ietf-xrblock-rtcp-xr-summary-stat, which mainly
addressed the issues discussed in the list and raised in last meeting. If
you have any different opinions, please let us know. 

Best Regards!
Rachel


-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf
Of internet-drafts@ietf.org
Sent: Monday, October 15, 2012 10:43 AM
To: i-d-announce@ietf.org
Cc: xrblock@ietf.org
Subject: [xrblock] I-D Action:
draft-ietf-xrblock-rtcp-xr-summary-stat-01.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)
Block for Summary Statistics Metrics Reporting
	Author(s)       : Glen Zorn
                          Roland Schott
                          Qin Wu
                          Rachel Huang
	Filename        : draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt
	Pages           : 15
	Date            : 2012-10-14

Abstract:
   This document defines three RTP Control Protcol (RTCP) Extended
   Report (XR) Blocks and associated SDP parameters that allows the
   reporting of loss, duplication and discard summary statistics 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-summary-stat

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-summary-stat-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcp-xr-summary-stat-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock
_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock