Re: [aqm] draft-khademi-alternativebackoff - lightly loaded, high BDP paths

Naeem Khademi <naeem.khademi@gmail.com> Wed, 14 October 2015 01:42 UTC

Return-Path: <naeem.khademi@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A231ACD96 for <aqm@ietfa.amsl.com>; Tue, 13 Oct 2015 18:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 NjaY60SQPX2A for <aqm@ietfa.amsl.com>; Tue, 13 Oct 2015 18:42:53 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (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 234C51ACD98 for <aqm@ietf.org>; Tue, 13 Oct 2015 18:42:53 -0700 (PDT)
Received: by lbcao8 with SMTP id ao8so36089311lbc.3 for <aqm@ietf.org>; Tue, 13 Oct 2015 18:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D9Dx1JwWvtSNi+g7JYvJEr5hY2x2O8eofro22+dU0DM=; b=IEWP3c4GN51uysuvwHwgaX4pdpxhmN4Dvt4Z/p9//50D99DlrcbuziKSLoNEE7Xn81 gl4a425rLGWSmQGil62FNA3CXlYi1wEQoG/NlFzQv7RmaOXzIoXPJb6nIJedDt7y3Izr zoyBj6q4Tdq06N3VoqIC8M6VBnKm27TKKdbrDacO/H/Maya87lODbGA/gEY0032lewq5 ZSOUBWyjzo3BUF3z+uUVIQ24K4KjuG3z8zADBmmzuPgQ3OrtV3ZrOY1DAqhHy022Y8MQ l7ND/3kMIC2iOKXwiodMqLnalDYFBhgFpjQRtwNXgZ1fOet6GSJWW2Nd3SSaxXgV5LNQ Pzbw==
MIME-Version: 1.0
X-Received: by 10.112.64.228 with SMTP id r4mr210678lbs.80.1444786971149; Tue, 13 Oct 2015 18:42:51 -0700 (PDT)
Received: by 10.114.80.106 with HTTP; Tue, 13 Oct 2015 18:42:51 -0700 (PDT)
In-Reply-To: <561C75D3.4050102@superduper.net>
References: <561C75D3.4050102@superduper.net>
Date: Wed, 14 Oct 2015 03:42:51 +0200
Message-ID: <CAEjQQ5U-jqmhfFxhpC9JoORoNke2EBKMD3J7TvvrBdxBtSb+Dg@mail.gmail.com>
From: Naeem Khademi <naeem.khademi@gmail.com>
To: Simon Barber <simon@superduper.net>
Content-Type: multipart/alternative; boundary="001a11343278310c59052206ae73"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/xi4KBCsmBYezFHwUua4_IFvZ-7w>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] draft-khademi-alternativebackoff - lightly loaded, high BDP paths
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 01:42:55 -0000

Hi Simon

Very good point -- I also think this falls into the scope
of draft-ietf-aqm-eval-guidelines aligned with my interpretation of your
words. I believe Section 8.2.2 of
https://tools.ietf.org/html/draft-ietf-aqm-eval-guidelines-08 somewhat
implicitly covers that.

Cheers,
Naeem

On Tue, Oct 13, 2015 at 5:09 AM, Simon Barber <simon@superduper.net> wrote:

> I was very interested to see this draft discusses a problem with AQMs
>
> AQM schemes like CoDel and PIE use congestion notifications to
>    constrain the queuing delays experienced by packets, rather than in
>    response to impending or actual bottleneck buffer exhaustion.  With
>    current default delay targets, CoDel and PIE both effectively emulate
>    a shallow buffered bottleneck (section II, [ABE2015 <https://tools.ietf.org/html/draft-khademi-alternativebackoff-ecn-01#ref-ABE2015>]).  This
>    interacts acceptably for TCP connections over low BDP paths, or
>    highly multiplexed scenarios (lmany concurrent TCP connections).
>    However, it interacts badly with lightly-multiplexed cases (few
>    concurrent connections) over high BDP paths.  Conventional TCP
>    backoff in such cases leads to gaps in packet transmission and
>    underutilisation of the path.
>
>
> I think it wold be good to add some discussion of this effect to the draft
> on evaluating AQM algorithms. In many access network scenarios the paths
> will be lightly loaded, and sometimes higher BDPs will be experienced. In
> these cases it's good to know that the AQM is not hurting your experience.
>
> Simon
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>
>