Re: [LOOPS] How important is congestion detection

Carsten Bormann <cabo@tzi.org> Mon, 22 July 2019 22:17 UTC

Return-Path: <cabo@tzi.org>
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 3ABAF1200B1 for <loops@ietfa.amsl.com>; Mon, 22 Jul 2019 15:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 kJN2YOP9hep9 for <loops@ietfa.amsl.com>; Mon, 22 Jul 2019 15:17:09 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A13A812006B for <loops@ietf.org>; Mon, 22 Jul 2019 15:17:09 -0700 (PDT)
Received: from client-0195.vpn.uni-bremen.de (client-0195.vpn.uni-bremen.de [134.102.107.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 45swvR66Z4zyXT; Tue, 23 Jul 2019 00:17:07 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7CF8FA24-C705-48EB-9D7D-F1520ED379AE@ifi.uio.no>
Date: Mon, 22 Jul 2019 18:17:06 -0400
Cc: loops@ietf.org
X-Mao-Original-Outgoing-Id: 585526624.6265661-936b29a38df59ab5a6f0b933801204aa
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CA35516-1E10-4638-9B87-0F6AE2FEE1F1@tzi.org>
References: <CEC56E4C-6C17-4812-A0C4-5B8306C76CE5@tzi.org> <7CF8FA24-C705-48EB-9D7D-F1520ED379AE@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/pjZ1nTvIhCOC_qRVREVnZwJZB9I>
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: Mon, 22 Jul 2019 22:17:11 -0000

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.

>  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.

Grüße, Carsten