[xrblock] Burst Discard Count

Varun Singh <vsingh.ietf@gmail.com> Thu, 26 February 2015 11:34 UTC

Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 131721A7021 for <xrblock@ietfa.amsl.com>; Thu, 26 Feb 2015 03:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id gFexAsx4AEIb for <xrblock@ietfa.amsl.com>; Thu, 26 Feb 2015 03:34:27 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C9B1A702B for <xrblock@ietf.org>; Thu, 26 Feb 2015 03:34:27 -0800 (PST)
Received: by lbjb6 with SMTP id b6so10194265lbj.2 for <xrblock@ietf.org>; Thu, 26 Feb 2015 03:34:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=lJFea8gwlUqk9cpq9TTbihZpWTZRLoGb3z8NFtaJ5vE=; b=J2he4/oB685SpcWKlqeJiNcpktz67TNyKyD9ZyytOAs6ybmvSUIJJon85HHVuepJcX V+rQO/CyECbEf3MWlt5brkjjt5FoLsf0+WJq6a3Trq4Vae7Dnk8f2yXOKt1/jQTPFHfB yBnrcij5CaiLfylE/ukwNNLKTZtrL9mCCAndPW+pcKv1GuQ6cDzM5wSBjiZMKxShcXky vD3HfD1tAgfOUf8OHFKJT9ZhttZOb08s+8LgSSi+ql0MHWba4cWPbrVnY/N7usqtD4+k TdYv1+O14HORuF56R+sFLc/ERiwpWXwDOBZtdPKBkxo3IvDaST4D2XGDgO1vX+qnMus2 9Pxg==
X-Received: by with SMTP id v20mr6966195laz.81.1424950465944; Thu, 26 Feb 2015 03:34:25 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Thu, 26 Feb 2015 03:34:04 -0800 (PST)
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Thu, 26 Feb 2015 13:34:04 +0200
Message-ID: <CAEbPqrxHJSNMins8ROMALvAPii7aKphYbWgSOKh61L8Mx_uGOw@mail.gmail.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/7SZYdFAhQjChJuierke-N8UU7Yg>
Subject: [xrblock] Burst Discard Count
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Feb 2015 11:34:29 -0000

Hi all,

While preparing the -01 version of the
draft-ietf-xrblock-rtcweb-rtcp-xr-metrics, I noticed that the
RFC6958 - Burst/Gap Loss reports a "burst count" metric, which
indicates the number of bursts  in an reporting interval (cumulative
or arbitrary time interval). However, RFC7003 does not report a
corresponding burst count metric for discarded packets.

I forget if this was discussed before, but it appears to be an
oversight, as arguments for including burst count for loss also apply
to burst discards -- unless I am missing something or it is defined
elsewhere. How do we fix this?

This may be non-blocking for the rtcweb metrics as we could instead
use the burstLossRate and burstDiscardRate which are defined in the
summary statistics in RFC7004.

Thanks and Regards,