Re: [iccrg] [tsvwg] IETF104 ICCRG TCP Prague presentation

Jonathan Morton <chromatix99@gmail.com> Thu, 04 April 2019 11:02 UTC

Return-Path: <chromatix99@gmail.com>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A19971204AA for <iccrg@ietfa.amsl.com>; Thu, 4 Apr 2019 04:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 doYTi_kb9Jwx for <iccrg@ietfa.amsl.com>; Thu, 4 Apr 2019 04:02:08 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 0C5C21200B2 for <iccrg@irtf.org>; Thu, 4 Apr 2019 04:00:18 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id h21so1637142ljk.13 for <iccrg@irtf.org>; Thu, 04 Apr 2019 04:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yLUsri1lMCJQLYQZe3aC1zLMmpTkfroqUkIv1PhMlZ4=; b=iafGRhFiHis874eDxG56oq3MJMMKUi4gqzQ84TdDFSOjZhO40bJwVx0KeysFC2L32S n6gjcakhgGpRQz+EWtRmrY7mxQJ8QDAYF6yfb+x/hAtzLKETrOIhIh5c5F5G4E1RkZQM 99VqcMxCCmQm4RvjHnfp81StgztAbY2GBLPxvcPq9nsY3p2Jm76ob2+gErRQCyXPbYxM 8nKgNj1sOQ6JRxGsyTf6G2cO0WWl/PMKTxN7K2+jqQ4r6LfXsV6mKr3szP/OASVNjWYS DQsd1rAKmGEkfQHw/V6dAfx8fWDma3kE2DCSDZfyXt72VyNhuTznQA/kUlJM+d2dpiDA mkZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yLUsri1lMCJQLYQZe3aC1zLMmpTkfroqUkIv1PhMlZ4=; b=rm64IFLnOURJ+HHgclt3fpSyJTQkZi+G9GJIxm0hteSxde5b7aJT275+f1RY4I+tMZ ywu0xUgA7jTAxYVa0D6mK3NQyyRY+cKQbkEovH3uD6LU6xMvbfHGO/Dh7mkhowuDPcB3 Gr+aOEjMr3L/vyLQq3dWpzJ+01kvzh88K730ywIeFbvfGfp4Rbr6pFRx7Qf0UCHm6fRS aUwesR2GO6y73LQ5Mn6573fKmsRwHR8EpjhljO6iwePL8odAgMNNodorTvZmeMHI5Ng6 06YY1UfwSnPiDS1BhPv2V7vP0b4nyyyj3lOuyfVFMzRwPowl8WrlGpV7GHuUKM/aI0mO mgzA==
X-Gm-Message-State: APjAAAU1cBCLHUYa46NEETNxSkw4LjqDxydQluilrpuCLDfLap+p2wMI xnqMMVvAUmzEFJnhiymAKMM=
X-Google-Smtp-Source: APXvYqzUStgNgi3TzoFS4gUNOcg3lBpdnSW6uiGpbruVPmM5nkoZnrAD99IxagSR51q5lf7sf39ouw==
X-Received: by 2002:a2e:9843:: with SMTP id e3mr2980897ljj.28.1554375616282; Thu, 04 Apr 2019 04:00:16 -0700 (PDT)
Received: from jonathartonsmbp.lan (85-76-23-211-nat.elisa-mobile.fi. [85.76.23.211]) by smtp.gmail.com with ESMTPSA id d3sm3851109ljc.15.2019.04.04.04.00.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 04:00:15 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
Date: Thu, 04 Apr 2019 14:00:14 +0300
Cc: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/SMta9Hj2pVeHQaN8I8RkNTOQ3zQ>
Subject: Re: [iccrg] [tsvwg] IETF104 ICCRG TCP Prague presentation
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 11:02:13 -0000

> On 4 Apr, 2019, at 12:40 pm, Greg White <g.white@CableLabs.com> wrote:
> 
> I don't doubt that the SCE signaling method could be used in a variant of DCTCP, but the *huge* downside is that it can only work on bottleneck links that are able (or willing) to support FQ, which will be precious few.

Let me stop you right there.  You are remembering a discussion we had at least two weeks ago, based on an early concept of SCE which has since been superseded.

We have running code which converges rapidly to fairly sharing the link between two SCE flows, with only a single-queue SCE-aware AQM.  That is, we used the "besteffort" and "flowblind" modes of Cake, which disable its Diffserv and flow-isolation capabilities, specifically to test that aspect of our work.  Since our prototype SCE response is DCTCP-like, that result should not be a surprise to you.

We *also* believe we have a solution for fairly sharing a single queue between SCE and non-SCE flows.  We haven't implemented and tested it yet, however.  Work continues.

> (unless you think blocking implementers from supporting dual-queue is some kind of perverse benefit)

Dual-queue AQM can still be supported through Diffserv, as I have repeatedly pointed out.  The associated PHB can specify the "short queue" and "no reordering" behaviours you're so keen on.

Now, reading back up your post:

> Has any progress been made on a variant of Cake that utilizes the L4S ECT(1) semantic?  It would be useful for comparison purposes.

We have not done so.  The code is freely available if you wish to try it yourself; it should not be difficult.  Cake also offers an excellent platform for exploring the behaviour of single-queue ECN-aware AQMs, which I think you would find valuable.

> I don't believe that the RFCs are on your side here.  RFC 3168 contemplates, and rejects, that definition of ECT(1)…

It also contemplates, rejects, and suggests a better alternative for L4S' use of ECT(1), right there in the quote.  And on the subject of RFC-8311, that document contains a section entitled "Effective Congestion Control Is Required", and it specifically leaves alone the several suggested uses of ECT(1) in its edits to RFC-3168.

I note in passing that SCE has the support of the TSVWG Chairs.  That is sufficient motivation to continue work to establish its true merits and limitations.

 - Jonathan Morton