Re: [xrblock] Burst Discard Count

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 28 February 2015 03:21 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 369C01A013B for <xrblock@ietfa.amsl.com>; Fri, 27 Feb 2015 19:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXDtDsiGUeOp for <xrblock@ietfa.amsl.com>; Fri, 27 Feb 2015 19:21:52 -0800 (PST)
Received: from BLU004-OMC3S14.hotmail.com (blu004-omc3s14.hotmail.com [65.55.116.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F65F1A00A7 for <xrblock@ietf.org>; Fri, 27 Feb 2015 19:21:51 -0800 (PST)
Received: from BLU406-EAS284 ([65.55.116.74]) by BLU004-OMC3S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Fri, 27 Feb 2015 19:21:50 -0800
X-TMN: [qnzGcXXpRp4iYJcELj7aTUSQ4LwIAkseCJlHlUeBmTs=]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU406-EAS28476AC94C59797ACEC6CC893120@phx.gbl>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
References: <CAEbPqrxHJSNMins8ROMALvAPii7aKphYbWgSOKh61L8Mx_uGOw@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA846DA5C2@nkgeml501-mbs.china.huawei.com> <CAEbPqrzi+LPg3La-pBGpjo4rpwKXyj8JZuY+-1yfnHieDy8yfQ@mail.gmail.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <CAEbPqrzi+LPg3La-pBGpjo4rpwKXyj8JZuY+-1yfnHieDy8yfQ@mail.gmail.com>
Date: Fri, 27 Feb 2015 19:21:47 -0800
To: Varun Singh <vsingh.ietf@gmail.com>
X-OriginalArrivalTime: 28 Feb 2015 03:21:50.0808 (UTC) FILETIME=[B149A580:01D05305]
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/eoatstfdlRt2aBDV-NpkMzMepC4>
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [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: Sat, 28 Feb 2015 03:21:54 -0000

Also consider a FEC scheme that is dynamic and can adjust for burst loss as well as supporting retransmission of packets and FEC.  In that situation, losses most certainly do not equal discards. 



> On Feb 27, 2015, at 3:36 AM, Varun Singh <vsingh.ietf@gmail.com> wrote:
> 
> I think the implicit assumption is that losses and discards are
> correlated, and that discards may occur before losses. However,
> consider a congestion control algorithm that is sensitive to discards
> may correct before any losses occur. Then the burstCount measuring
> only losses would not increase  and hence burst discards count will
> not correspond to burst loss count.
> 
> 
>> Also burst gap discard is intended to be sent together with burst gap loss.
>> See the section 1 of RFC7003:
>> "
>> This block is intended to be used in conjunction with [RFC7002], which provides the
>> total packets discarded and on which this block therefore depends.
>> However, the metric in [RFC7002] may be used independently of the
>> metrics in this block.
>> "
>> 
>> -Qin
>> -----邮件原件-----
>> 发件人: xrblock [mailto:xrblock-bounces@ietf.org] 代表 Varun Singh
>> 发送时间: 2015年2月26日 19:34
>> 收件人: xrblock@ietf.org
>> 主题: [xrblock] Burst Discard Count
>> 
>> 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,
>> Varun
>> 
>> 
>> --
>> http://www.callstats.io
>> 
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
> 
> 
> 
> -- 
> http://www.callstats.io
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock