IETF Logo Mail Archive

Re: [tsvwg] [Ecn-sane] per-flow scheduling

Jonathan Morton <chromatix99@gmail.com> Thu, 18 July 2019 04:31 UTC

Return-Path: <chromatix99@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA66120088 for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 21:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 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_HELO_NONE=0.001, 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 iAwCfL0t7WSJ for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 21:31:10 -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 B8B41120025 for <tsvwg@ietf.org>; Wed, 17 Jul 2019 21:31:09 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id p17so25876485ljg.1 for <tsvwg@ietf.org>; Wed, 17 Jul 2019 21:31:09 -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=wqXYrpXRimZKY4/HFvEA0ewHK4uNe24cYBGzFi9KW98=; b=NQ1lWdvrrYoOVO/IKWUMhkDDdin/DZ6qK4Q6/RCiLoHOyifkLWRVzd2m5B55DIgORW lBLB7fNEt0JqesxtVCPKsM8shvn8jSf2TeDmSM3OpLvHbBIjGLYtNZ1lDXPes8Dy4G0K ty1vz07Xu1LnexgJS0V3sthJ9Mb6gQd2H8vNDNNsbJ9x3ha3UzqYoYg7m3+71lZQ6noB puvsVP1toV3fofi75uAvr1tbwZRmE8wXvI0Ax6aJPO9qvKQbpSqsvbeBlPKqMkzVkpfz TtMwCHFxsA29us/5yPiI0PwNzN+pp+x87uXrDrQlDcSmC0OunjC+LH9fi8lu5XERuy3n RZQQ==
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=wqXYrpXRimZKY4/HFvEA0ewHK4uNe24cYBGzFi9KW98=; b=BDbonA9rcwN41CwIitqAzvWkEP3YGVmGnF8sMjdyOVGCLESkk3Ub/z2BCJCMwxtOZO MWQYMuEJho/bCW9iOjEqkITu+7m3CFBibUwVu5EVskz/jU1u1sNgS2w/XCQ0vMaffql7 ElRG1ooEGU6Bgu53OhqvvZk9yxkl55uXhe1HROLVQsgTvLlCVZVuRNN6KnVoKAX1b5dA fqH7e4soLIzYqW6bAOOv4k/q3gjnBH+Lwm05MByLLBz53MOr1agxY68daDX/ZN5GWFTX FVYYdUbc4Hl8FKfEzz8k5+oFSTfsN/iEmJJ27A5CSpxFvcEUR+IFrLMpWX1/UJQ78XQo Yjsg==
X-Gm-Message-State: APjAAAXUlfoNfY4yObrPOT5LpQ4RqqUD3aFo3LXazSanvRSQu3sp/lP1 A8DDgT/yNX/S/9fROfDQiHE=
X-Google-Smtp-Source: APXvYqwLR1TsBtbctxyn65wOP0ldXiGJGlzBFA4XfucUuURiDPx+mTsll9QB1Ti8N4/vNeMUhjlJzw==
X-Received: by 2002:a2e:5b5b:: with SMTP id p88mr21928894ljb.192.1563424267886; Wed, 17 Jul 2019 21:31:07 -0700 (PDT)
Received: from [192.168.44.148] (37-219-185-236.nat.bb.dnainternet.fi. [37.219.185.236]) by smtp.gmail.com with ESMTPSA id v12sm4844859ljk.22.2019.07.17.21.31.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Jul 2019 21:31:06 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
X-Priority: 3 (Normal)
In-Reply-To: <1563401917.00951412@apps.rackspace.com>
Date: Thu, 18 Jul 2019 07:31:02 +0300
Cc: Sebastian Moeller <moeller0@gmx.de>, "ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>, Bob Briscoe <ietf@bobbriscoe.net>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <368B308A-C17C-42C6-AA37-F48DF6BC06AA@gmail.com>
References: <350f8dd5-65d4-d2f3-4d65-784c0379f58c@bobbriscoe.net> <40605F1F-A6F5-4402-9944-238F92926EA6@gmx.de> <1563401917.00951412@apps.rackspace.com>
To: "David P. Reed" <dpreed@deepplum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/OL890f5H9v0nWnGmUZ6sOxT1M54>
Subject: Re: [tsvwg] [Ecn-sane] per-flow scheduling
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 04:31:11 -0000

> On 18 Jul, 2019, at 1:18 am, David P. Reed <dpreed@deepplum.com> wrote:
> 
> So what are we talking about here (ignoring the fine points of SCE, some of which I think are debatable - especially the focus on TCP alone, since much traffic will likely move away from TCP in the near future.

As a point of order, SCE is not specific to TCP.  TCP is merely the most convenient congestion-aware protocol to experiment with, and therefore the one we have adapted first.  Other protocols which already are (or aspire to be) TCP friendly, especially QUIC, should also be straightforward to adapt to SCE.

I should also note that TCP is the de-facto gold standard, by which all other congestion control is measured, for better or worse.  SCE is included in this, insofar as competing reasonably with standard TCP flows under all reasonable network conditions is necessary to introduce a new congestion control paradigm.  This, I think, is also part of the end-to-end principle.

 - Jonathan Morton

v2.23.0 | Report a Bug | By Email