[xrblock] 答复: (2nd) WGLC for draft-ietf-xrblock-rtcp-xr-jb

Qin Wu <bill.wu@huawei.com> Thu, 11 April 2013 07:14 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 1CE9D21F8EB1 for <xrblock@ietfa.amsl.com>; Thu, 11 Apr 2013 00:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.178
X-Spam-Level: *
X-Spam-Status: No, score=1.178 tagged_above=-999 required=5 tests=[AWL=-1.610, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 zIpb-Y7qCdoR for <xrblock@ietfa.amsl.com>; Thu, 11 Apr 2013 00:14:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F011021F8E8F for <xrblock@ietf.org>; Thu, 11 Apr 2013 00:14:44 -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 AQG64101; Thu, 11 Apr 2013 07:14:43 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Apr 2013 08:14:08 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Apr 2013 15:14:43 +0800
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.126]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Thu, 11 Apr 2013 15:14:35 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, "'xrblock'" <xrblock@ietf.org>
Thread-Topic: [xrblock] (2nd) WGLC for draft-ietf-xrblock-rtcp-xr-jb
Thread-Index: Ac40Yjq4Xn7GWM4iS5GYjSTAh3YdmgBHWUsAAED5OQA=
Date: Thu, 11 Apr 2013 07:14:34 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43A3C24A@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA0C42A3@AZ-FFEXMB04.global.avaya.com> <038d01ce35c2$b05ac7b0$11105710$@gmail.com>
In-Reply-To: <038d01ce35c2$b05ac7b0$11105710$@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.149]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [xrblock] =?gb2312?b?tPC4tDogICgybmQpIFdHTEMgZm9yIGRyYWZ0LWlldGYt?= =?gb2312?b?eHJibG9jay1ydGNwLXhyLWpi?=
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, 11 Apr 2013 07:14:46 -0000

Hi, Roni:
Thank for your valuable comments, see my reply below.

Regards!
-Qin

-----邮件原件-----
发件人: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] 代表 Roni Even
发送时间: 2013年4月10日 16:09
收件人: 'Romascanu, Dan (Dan)'; 'xrblock'
主题: Re: [xrblock] (2nd) WGLC for draft-ietf-xrblock-rtcp-xr-jb

Hi,
I reviewed the document and it is ready for publication.

Just some nits

1. Section 3 5th paragraph "then then"

[Qin]: Okay, thank for your good catch.

2. In section 3.1 "In practice jitter buffer implementations vary
considerably however should behave" suggest " In practice jitter buffer
implementations vary considerably however they should behave".

[Qin]: Okay.

3. in section 4 change the two "should" to "SHOULD"

[Qin]: In IESG review to burst gap loss draft, similar comment was raised,
It was suggested to use "MUST" in two places. So I think we should use 
"MUST" here. But thanks for raising this issue.

4. in section 4.2  in the " jitter buffer maximum delay" description "
earliest arriving packet In simple queue" to "earliest arriving packet. In
simple queue"

[Qin]: Good catch, thanks.

5. in section 5.2 " When SDP is used in offer-answer" suggest adding a
reference to RFC3264.

[Qin]: Okay, make sense.

Roni Even


-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf
Of Romascanu, Dan (Dan)
Sent: 08 April, 2013 5:06 PM
To: xrblock
Subject: [xrblock] (2nd) WGLC for draft-ietf-xrblock-rtcp-xr-jb


This is the second WGLC for the Internet-Draft 'RTP Control Protocol (RTCP)
Extended Report (XR) Block for Jitter Buffer Metric Reporting'. Please send
your comments, questions, and concerns to the WG list before Monday 4/22
COB. 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-jb-10.txt.

Thanks and Regards,

Dan



_______________________________________________
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