Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt

"Claire Bi(jiayu)" <bijy@sttri.com.cn> Mon, 17 December 2012 08:24 UTC

Return-Path: <bijy@sttri.com.cn>
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 4521E21F897D for <xrblock@ietfa.amsl.com>; Mon, 17 Dec 2012 00:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.167
X-Spam-Level: *
X-Spam-Status: No, score=1.167 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
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 3gj+Ruz7SKET for <xrblock@ietfa.amsl.com>; Mon, 17 Dec 2012 00:24:38 -0800 (PST)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.39]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3AB21F8C09 for <xrblock@ietf.org>; Mon, 17 Dec 2012 00:24:37 -0800 (PST)
Received: from ip?218.92.227.107? (entas3.inner-hermes.com [10.27.101.3]) by corp.21cn.com (HERMES) with ESMTP id 4916A194075; Mon, 17 Dec 2012 16:24:27 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.3.1200099844
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.92.227.107> ([218.92.227.107]) by 21CN-entas3(MEDUSA 10.27.101.3) with ESMTP id 1355732667.16316 for glenzorn@gmail.com ; Mon Dec 17 16:24:35 2012
0/X-Total-Score: 0:
2/X-Total-Score: 3:
X-FILTER-SCORE: to=<888d868f9b90938f61888e828a8d4f84908e838a8d8d4f98966189968298868a4f84908e9993838d90848c618a8695874f909388>, score=<1355732675YHHSHHwH2OxYSwebKHHxHHDDcDDsDLOHgcsW4zDDHDDg>
X-REAL-FROM: bijy@sttri.com.cn
Date: Mon, 17 Dec 2012 16:24:27 +0800
From: "Claire Bi(jiayu)" <bijy@sttri.com.cn>
To: Glen Zorn <glenzorn@gmail.com>, Qin Wu <bill.wu@huawei.com>
Message-ID: <908227462.2121355732667678.JavaMail.hermes@ent-web1>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_224_1795837277.1355732667362"
HMM_WEBCLN_IP: 10.27.10.87
X-HERMES-SENDMODE: normal
X-HERMES-SET: KoH0oguRsun5ALVzckz3EqaqqOumqw==
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.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, 17 Dec 2012 08:24:40 -0000

>I have a different suggestion, now that I understand what you're trying
>to say :-).  How about this:
>
>Real-time applications employ a jitter buffer to smooth out jitter
>introduced on the path from source to destination.  These metrics are
>used to report how the jitter buffer at the receiving end of RTP stream
>behaves as a result of jitter in the network and are applicable to a
>range of RTP applications.
>
>These metrics reflect how terminal-related factors effect real-time
>application quality and are useful to provide better end-user quality of
>experience (QoE).
>

This suggestion looks okay to me. Now the section can be better understood. I have just one minor comment:

In the last sentence, would it be better to use *affect* instead of *effect*?

Regards,

Claire