IETF Logo Mail Archive

Re: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-02.txt

Qin Wu <bill.wu@huawei.com> Mon, 14 January 2013 00:46 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 B762521F8648 for <xrblock@ietfa.amsl.com>; Sun, 13 Jan 2013 16:46:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level:
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=-1.372, BAYES_20=-0.74, 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 wQqZ8HsPfaZR for <xrblock@ietfa.amsl.com>; Sun, 13 Jan 2013 16:46:53 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D61AA21F85FE for <xrblock@ietf.org>; Sun, 13 Jan 2013 16:46:52 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOS86397; Mon, 14 Jan 2013 00:46:50 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 Jan 2013 00:46:44 +0000
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 Jan 2013 00:46:48 +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; Mon, 14 Jan 2013 08:46:43 +0800
Message-ID: <0326892069B04DA88E01A3365C022667@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Kevin Gross <kevin.gross@avanw.com>
References: <FAB2D6A6BD794F67B5EF665FB7966291@china.huawei.com><9904FB1B0159DA42B0B887B7FA8119CA021171@AZ-FFEXMB04.global.avaya.com><-5577438416726931362@unknownmsgid><9904FB1B0159DA42B0B887B7FA8119CA02129A@AZ-FFEXMB04.global.avaya.com><56FF1AB29F4046F0BDCDF6F7B21FC0EC@china.huawei.com><CALw1_Q1UfwNR+7jNx=r+P3rMR35NRdby_S+Xh1GADivvx3_r6w@mail.gmail.com><686F7A581585402D82BDCA8F213EB5E7@china.huawei.com><CALw1_Q1FqHh0SVBKudc-cJoJxw9hPUeBUwdgrf54xLwSFDfO6g@mail.gmail.com><6C47A394F32143709E3B1E7CB411A08E@china.huawei.com> <CALw1_Q0E867g+Rae84dwisaPWQh=vQ-cN5iMPexqSW6n+Gn+gQ@mail.gmail.com>
Date: Mon, 14 Jan 2013 08:46:42 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01CDF233.AD1DAEF0"
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] Fw: I-D Action: 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, 14 Jan 2013 00:46:55 -0000

Kevin:
As I clarified to you in the previous email, "implemention specific time window" described in Burst Gap drafts will be used to identify a "packet that arrives exactly on time".
That is to say, if the receiving packet falls within  implemention specific time window and can be sucessfully playout, such packet will be regarded as packet that arrives exactly on time.
Hope this clarifies.

Regards!
-Qin
  ----- Original Message ----- 
  From: Kevin Gross 
  To: Qin Wu 
  Cc: xrblock 
  Sent: Sunday, January 13, 2013 6:04 AM
  Subject: Re: offlist//Re: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-02.txt


  Qin,


  Of the jitter buffer delay metric, the draft currently says "It is calculated based on the difference between the receipt time and the playout time for the packet that arrives exactly on time."


  My issue is that I don't know how to identify a "packet that arrives exactly on time".


  Kevin Gross

  +1-303-447-0517
  Media Network Consultant

  AVA Networks - www.AVAnw.com, www.X192.org

v2.23.0 | Report a Bug | By Email