Re: [xrblock] (2nd) WGLC for draft-ietf-xrblock-rtcp-xr-jb

Colin Perkins <csp@csperkins.org> Mon, 22 April 2013 14:57 UTC

Return-Path: <csp@csperkins.org>
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 A63AC21F8F44 for <xrblock@ietfa.amsl.com>; Mon, 22 Apr 2013 07:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtQpRGTUa0xI for <xrblock@ietfa.amsl.com>; Mon, 22 Apr 2013 07:57:57 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0D90221F8E2C for <xrblock@ietf.org>; Mon, 22 Apr 2013 07:57:57 -0700 (PDT)
Received: from [81.187.2.149] (port=35077 helo=[192.168.0.11]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1UUIBK-0005JQ-Nq; Mon, 22 Apr 2013 15:57:52 +0100
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA0C42A3@AZ-FFEXMB04.global.avaya.com>
Date: Mon, 22 Apr 2013 15:57:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <01F8E350-5922-4E68-A9C5-9E1BB0545217@csperkins.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA0C42A3@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1283)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] (2nd) WGLC for 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: Mon, 22 Apr 2013 14:57:57 -0000

On 8 Apr 2013, at 15:06, Romascanu, Dan (Dan) wrote:
> This is the second WGLC for the Internet-Draft 'RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer Metric Reporting'. Please send your comments, questions, and concerns to the WG list before Monday 4/22 COB. If you have no comments or questions and you believe that this document is ready for submission to the IESG for consideration as a Proposed Standard, please send a message stating this. 
> 
> The latest version of the document can be retrieved from http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-jb-10.txt.


I think this is essentially ready, but I did have a quick comments on re-reading the draft:

How is the jitter buffer nominal delay calculated for an interval metric or for a cumulative metric? The draft talks about "the current nominal jitter buffer delay", which makes sense for a sampled metric, but it's not clear how it applies for an interval or as a cumulative metric?

It might also be necessary to clarify the other jitter buffer metrics for the cumulate case.

-- 
Colin Perkins
http://csperkins.org/