[xrblock] Comments on burst loss/discard drafts
Alan Clark <alan.d.clark@telchemy.com> Tue, 15 November 2011 03:07 UTC
Return-Path: <alan.d.clark@telchemy.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 E02BF1F0CA6 for <xrblock@ietfa.amsl.com>; Mon, 14 Nov 2011 19:07:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.674
X-Spam-Level:
X-Spam-Status: No, score=0.674 tagged_above=-999 required=5 tests=[AWL=1.876, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 T7ZBIrJH0jTY for <xrblock@ietfa.amsl.com>; Mon, 14 Nov 2011 19:07:24 -0800 (PST)
Received: from smtp01.myhostedservice.com (smtp01.myhostedservice.com [216.134.213.70]) by ietfa.amsl.com (Postfix) with ESMTP id 518831F0C92 for <xrblock@ietf.org>; Mon, 14 Nov 2011 19:07:24 -0800 (PST)
Received: from mail01.netplexity.net (172.29.251.14) by SMTP01.netplexity.local (172.29.211.9) with Microsoft SMTP Server id 14.0.722.0; Mon, 14 Nov 2011 22:07:17 -0500
Received: from [192.168.1.88] (c-24-99-98-209.hsd1.ga.comcast.net [24.99.98.209]) by mail01.netplexity.net with SMTP; Mon, 14 Nov 2011 22:07:15 -0500
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Mon, 14 Nov 2011 22:07:12 -0500
From: Alan Clark <alan.d.clark@telchemy.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Shida Schubert <shida@ntt-at.com>
Message-ID: <CAE74190.3D9A4%alan.d.clark@telchemy.com>
Thread-Topic: Comments on burst loss/discard drafts
Thread-Index: AcyjQ6tcll6lrFVfIkab80pKhUpcfg==
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="B_3404153236_3671548"
Cc: xrblock@ietf.org
Subject: [xrblock] Comments on burst loss/discard drafts
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: Tue, 15 Nov 2011 03:07:25 -0000
I will not be at the XRBLOCK meeting however would appreciate the following comment being considered as part of the discussion on burst loss/discard. Packet loss and PDV/jitter (and hence discards) are often caused by congestion - i.e. the same cause - and can therefore occur at the same time. >From the perspective of the impact of loss and discard on user perceived quality - they have a combined effect and need to be considered together. If there are separate metrics for packet loss bursts/gaps and packet discard burst/gaps then any timing relationship between these is lost. - It is therefore desirable to have a burst/gap loss/discard metric block. - Having a burst/gap loss block has some utility as loss can be caused by layer 1/2 problems. - Having a burst/gap discard block has limited usefulness So have one of: - Burst/Gap Loss/Discard or - Burst/Gap Loss/Discard, Burst/Gap Loss or - Burst/Gap Loss/Discard, Burst/Gap Loss, Burst/Gap Discard Alan