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

Kevin Gross <kevin.gross@avanw.com> Fri, 21 December 2012 03:36 UTC

Return-Path: <kevin.gross@avanw.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 C020721E8039 for <xrblock@ietfa.amsl.com>; Thu, 20 Dec 2012 19:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.576
X-Spam-Level:
X-Spam-Status: No, score=-1.576 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 ciQlUUnNmWeA for <xrblock@ietfa.amsl.com>; Thu, 20 Dec 2012 19:36:00 -0800 (PST)
Received: from oproxy8-pub.bluehost.com (oproxy8-pub.bluehost.com [69.89.22.20]) by ietfa.amsl.com (Postfix) with SMTP id 5199721E802E for <xrblock@ietf.org>; Thu, 20 Dec 2012 19:36:00 -0800 (PST)
Received: (qmail 15002 invoked by uid 0); 21 Dec 2012 03:35:39 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy8.bluehost.com with SMTP; 21 Dec 2012 03:35:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=SkUi0wIBoWWJdm6X3I9rtQ664wliqLlOhU90LHrrpT4=; b=Z8SMnkJxJpcpkqq5nzmMgZM2hDQdrRss7PMECZAhbmh7rIbkXCxfl3/1OzW6Omws/Oorxty63vNbp4o5AoUxPPdQw+l1AyS5AvYmYkzmv0VZB80226DGgCh74sC77lCI;
Received: from [209.85.223.177] (port=34515 helo=mail-ie0-f177.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TltOc-0007nc-Vk for xrblock@ietf.org; Thu, 20 Dec 2012 20:35:39 -0700
Received: by mail-ie0-f177.google.com with SMTP id k13so5615378iea.22 for <xrblock@ietf.org>; Thu, 20 Dec 2012 19:35:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.50.53.161 with SMTP id c1mr7292552igp.95.1356060938080; Thu, 20 Dec 2012 19:35:38 -0800 (PST)
Received: by 10.50.151.135 with HTTP; Thu, 20 Dec 2012 19:35:37 -0800 (PST)
In-Reply-To: <50CC10DF.4030403@gmail.com>
References: <50CAF991.8050508@gmail.com> <A58F079A8D804929AA28B535FAB72BAC@china.huawei.com> <50CC10DF.4030403@gmail.com>
Date: Thu, 20 Dec 2012 20:35:37 -0700
Message-ID: <CALw1_Q1Gy8SLh1VryxOdMsLanJQYkd_WeapqLG5b=FgrAjxHEg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04339d188212ed04d1548a16
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.223.177 authed with kevin.gross@avanw.com}
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 03:36:00 -0000

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