Re: [LOOPS] How important is congestion detection

Mirja Kuehlewind <ietf@kuehlewind.net> Tue, 30 July 2019 10:14 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: loops@ietfa.amsl.com
Delivered-To: loops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF2701203D5 for <loops@ietfa.amsl.com>; Tue, 30 Jul 2019 03:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0cBQU5wjeA0J for <loops@ietfa.amsl.com>; Tue, 30 Jul 2019 03:14:44 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 373411203DA for <loops@ietf.org>; Tue, 30 Jul 2019 03:14:44 -0700 (PDT)
Received: from 200116b82cf82f00096e5b7dce73fffb.dip.versatel-1u1.de ([2001:16b8:2cf8:2f00:96e:5b7d:ce73:fffb]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hsP9S-0005ql-Vg; Tue, 30 Jul 2019 12:14:39 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CAKKJt-fknF=ieOZDTBjsdNCJST7KnUZzXmL=CD55GoMDag74uw@mail.gmail.com>
Date: Tue, 30 Jul 2019 12:14:38 +0200
Cc: Carsten Bormann <cabo@tzi.org>, loops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2693E1C9-B778-48CD-9790-EEE70DAFDADF@kuehlewind.net>
References: <CEC56E4C-6C17-4812-A0C4-5B8306C76CE5@tzi.org> <7CF8FA24-C705-48EB-9D7D-F1520ED379AE@ifi.uio.no> <6CA35516-1E10-4638-9B87-0F6AE2FEE1F1@tzi.org> <5EEF6351-EC39-40A1-8A99-876B53094B08@ifi.uio.no> <CAKKJt-fknF=ieOZDTBjsdNCJST7KnUZzXmL=CD55GoMDag74uw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1564481684;bc3d3898;
X-HE-SMSGID: 1hsP9S-0005ql-Vg
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/sYN3euUggllib2pGbcPWytH73Gw>
Subject: Re: [LOOPS] How important is congestion detection
X-BeenThere: loops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Local Optimizations on Path Segments <loops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/loops>, <mailto:loops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/loops/>
List-Post: <mailto:loops@ietf.org>
List-Help: <mailto:loops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/loops>, <mailto:loops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2019 10:14:46 -0000

BRR is ignoring loss (up to some % of loss rate) while it will always react to CE.


> On 23. Jul 2019, at 16:45, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> FWIW, 
> 
> On Mon, Jul 22, 2019 at 6:51 PM Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> 
> > On Jul 22, 2019, at 6:17 PM, Carsten Bormann <cabo@tzi.org> wrote:
> > 
> > Sorry for typing a message from a heated BOF where I was representing a WG that needs a specific outcome…
> > 
> >>> Bob pointed out that some end host implementations today interpret CE as definite congestion events, while applying congestion detection to loss signals, so this conversion might be counterproductive.
> >> 
> >> The last sentence - I don't understand it (“interpret CE as definite… while applying detection to loss” - huh?). What does it mean? Or, maybe: what’s the issue here?
> > 
> > What I think Bob meant: An end-host noticing a loss might make its own determination (a.k.a. congestion detection) whether that is a reason to slow down or not.
> > An end-host getting a CE might simply assume this is indeed congestion, and always slow down.  So, CE > loss, and a simple replacement of loss by CE worsens throughput.
> 
> Ok, thanks!  now I understand that the statement is indeed what I thought, but it still makes zero sense to me. See below:
> 
> 
> >> I thought the whole point is to signal CE *as a replacement* for the loss that LOOPS repairs. So, then… ?
> > 
> > If CE > loss, replacing loss by CE is not enough, we need to vet the losses via a LOOPS-side congestion detection that is as good as the one as the end-host would do, or (preferably) better.
> 
> RFC 3168 says CE = loss. RFC 8311 finally allows us to diverge from this rule, which we used in RFC to state: “CE < loss”.
> L4S of course also does “CE < loss”, albeit in much more elaborate ways.
> 
> However: "CE > loss” is truly weird to me - perhaps this IS now allowed by RFC 8311  :-D    but if it’s spec’ed then it must be an April 1 RFC.
> 
> What am I missing, Bob?
> 
> I was hoping CE > loss was a typo, myself.
> 
> Spencer
>  
> 
> Cheers,
> Michael
> 
> -- 
> LOOPS mailing list
> LOOPS@ietf.org
> https://www.ietf.org/mailman/listinfo/loops
> -- 
> LOOPS mailing list
> LOOPS@ietf.org
> https://www.ietf.org/mailman/listinfo/loops