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

Qin Wu <bill.wu@huawei.com> Fri, 21 December 2012 09:12 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 4444321F8A8C for <xrblock@ietfa.amsl.com>; Fri, 21 Dec 2012 01:12:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.282
X-Spam-Level:
X-Spam-Status: No, score=-4.282 tagged_above=-999 required=5 tests=[AWL=-0.321, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 Bii0boUVRB5K for <xrblock@ietfa.amsl.com>; Fri, 21 Dec 2012 01:12:09 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3D05821F8A82 for <xrblock@ietf.org>; Fri, 21 Dec 2012 01:12:08 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOA87311; Fri, 21 Dec 2012 09:12:07 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 09:11:56 +0000
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 09:12:04 +0000
Received: from w53375 (10.138.41.149) by szxeml405-hub.china.huawei.com (10.82.67.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 17:09:48 +0800
Message-ID: <825E4E83E41B4F81A44BFD4D0B51320D@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Kevin Gross <kevin.gross@avanw.com>, Glen Zorn <glenzorn@gmail.com>
References: <50CAF991.8050508@gmail.com><A58F079A8D804929AA28B535FAB72BAC@china.huawei.com><50CC10DF.4030403@gmail.com> <CALw1_Q1Gy8SLh1VryxOdMsLanJQYkd_WeapqLG5b=FgrAjxHEg@mail.gmail.com>
Date: Fri, 21 Dec 2012 17:09:47 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CF_01CDDF9D.FAE7D7D0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
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: Fri, 21 Dec 2012 09:12:10 -0000

Your suggested change looks good to me.

Regards!
-Qin
  ----- Original Message ----- 
  From: Kevin Gross 
  To: Glen Zorn 
  Cc: Qin Wu ; xrblock 
  Sent: Friday, December 21, 2012 11:35 AM
  Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt


  Good words from Glen. I suggest replacing "smooth out" with "absorb" below.


  Kevin


  On Fri, Dec 14, 2012 at 10:55 PM, Glen Zorn <glenzorn@gmail.com> wrote:



    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).