IETF Logo Mail Archive

Re: [xrblock] Comment on draft-ietf-xrblock-rtcp-xr-jb

Qin Wu <bill.wu@huawei.com> Thu, 11 October 2012 00:43 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 E56F711E80EF for <xrblock@ietfa.amsl.com>; Wed, 10 Oct 2012 17:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.674
X-Spam-Level:
X-Spam-Status: No, score=-5.674 tagged_above=-999 required=5 tests=[AWL=0.924, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 i5cnj+OHYqd8 for <xrblock@ietfa.amsl.com>; Wed, 10 Oct 2012 17:43:08 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 26DC111E80E5 for <xrblock@ietf.org>; Wed, 10 Oct 2012 17:43:07 -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 AKM44377; Thu, 11 Oct 2012 00:43:06 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 11 Oct 2012 01:42:34 +0100
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 11 Oct 2012 01:42:50 +0100
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; Thu, 11 Oct 2012 08:42:42 +0800
Message-ID: <FA2B5ECDD3D84792A07DCC8661D01B32@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Claire Bi(jiayu)" <bijy@sttri.com.cn>, xrblock <xrblock@ietf.org>
References: <399210426.2451349879280803.JavaMail.hermes@ent-web6>
Date: Thu, 11 Oct 2012 08:42:42 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DC_01CDA78C.609DB260"
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
Subject: Re: [xrblock] Comment on draft-ietf-xrblock-rtcp-xr-jb
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 Oct 2012 00:43:09 -0000

Hi,Clarie:
Thank for your review to this draft. Regarding your comment to section 1.4,
I like to propose the following change to section 1.4:

OLD TEXT:
"
1.4.  Applicability

   These metrics are applicable to a range of RTP applications.
"
NEW TEXT:
"
1.4.  Applicability

   These metrics are applicable to a range of RTP applications. 
   Real-time applications employ a buffer to smooth out delay 
   variation encountered on the path from source to destination. 
   Network managers   can use these metrics to adapt to changes 
   in the network's delay by changing the size of the jitter buffer, 
   which help ensure the quality of real-time application performance.
   Also these metrics takes terminal related factor that affects 
   real-time application quality into account and are useful to provide
   more precise application quality estimation.
"
Hope this addresses your comment.

Regards!
-Qin
  ----- Original Message ----- 
  From: Claire Bi(jiayu) 
  To: xrblock 
  Sent: Wednesday, October 10, 2012 10:28 PM
  Subject: [xrblock] Comment on draft-ietf-xrblock-rtcp-xr-jb


  Hi,

  I've read draft-ietf-xrblock-rtcp-xr-jb and think it is pretty much in a good shape. 

  However，I have one comment to the section 1.4. It seems section 1.4 is still incomplete. It is proposed to add some use cases and further explanation in this section.

  Besides this, I think this draft is ready for going for Last Call in the WG.



  Regards!

  Claire Bi



------------------------------------------------------------------------------


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

v2.23.0 | Report a Bug | By Email