Re: [tsvwg] Neal Cardwell's rationale for supporting ECT(1) as an input/L4S signal

Steven Blake <slblake@petri-meat.com> Tue, 12 May 2020 21:48 UTC

Return-Path: <slblake@petri-meat.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 C2DC63A0C10 for <tsvwg@ietfa.amsl.com>; Tue, 12 May 2020 14:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 w-BEznzajY4e for <tsvwg@ietfa.amsl.com>; Tue, 12 May 2020 14:48:22 -0700 (PDT)
Received: from bumble.birch.relay.mailchannels.net (bumble.birch.relay.mailchannels.net [23.83.209.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 319463A0D9F for <tsvwg@ietf.org>; Tue, 12 May 2020 14:48:01 -0700 (PDT)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3438A64125D; Tue, 12 May 2020 21:48:01 +0000 (UTC)
Received: from pawpaw.tchmachines.com (100-96-12-34.trex.outbound.svc.cluster.local [100.96.12.34]) (Authenticated sender: totalchoicehosting) by relay.mailchannels.net (Postfix) with ESMTPA id AB004641242; Tue, 12 May 2020 21:47:59 +0000 (UTC)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
Received: from pawpaw.tchmachines.com (pawpaw.tchmachines.com [208.76.80.100]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Tue, 12 May 2020 21:48:01 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
X-MailChannels-Auth-Id: totalchoicehosting
X-Rock-Little: 565aea056754acfc_1589320080961_3693010275
X-MC-Loop-Signature: 1589320080961:1683647032
X-MC-Ingress-Time: 1589320080961
Received: from [136.56.88.61] (port=35126 helo=axion.home.arpa) by pawpaw.tchmachines.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <slblake@petri-meat.com>) id 1jYckl-0002vg-1Z; Tue, 12 May 2020 17:47:55 -0400
Message-ID: <875e9d72813c00fa0810266b7820dd68db154f5c.camel@petri-meat.com>
From: Steven Blake <slblake@petri-meat.com>
To: Jonathan Morton <chromatix99@gmail.com>, Neal Cardwell <ncardwell@google.com>
Cc: tsvwg IETF list <tsvwg@ietf.org>
Date: Tue, 12 May 2020 17:47:56 -0400
In-Reply-To: <B11F5EAC-7172-480D-9C73-9823F775AB4E@gmail.com>
References: <CADVnQy=7f79Mj_GQBU-UsodTRORjB2U6rCPPQ+1Zck_gxr-rww@mail.gmail.com> <2fe941a4-6824-a6bf-5d4d-ac2402912414@wizmail.org> <2F3117CD-6939-4FC3-89B3-D45C481A1B02@gmail.com> <CADVnQykYxdHDPb3XJ6hGRk2Lbx_9gT22TUq=i5ZfP=L0KGx3jw@mail.gmail.com> <B11F5EAC-7172-480D-9C73-9823F775AB4E@gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-AuthUser: slblake+petri-meat.com@pawpaw.tchmachines.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ajVfsXW9h2NINnBXdx8U2XgigBo>
Subject: Re: [tsvwg] Neal Cardwell's rationale for supporting ECT(1) as an input/L4S signal
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: Tue, 12 May 2020 21:48:24 -0000

On Tue, 2020-05-12 at 23:38 +0300, Jonathan Morton wrote:
> > On 12 May, 2020, at 11:29 pm, Neal Cardwell <ncardwell@google.com>
> > wrote:
> > 
> > > The shallow queues referred to are intended for deployment in
> > > tightly
> > > controlled datacentre environments, where the typical path RTT is
> > > measured in
> > > microseconds rather than milliseconds. It would not be surprising
> > > if a
> > > transport passing through such a queue as part of a typical
> > > Internet path of
> > > many milliseconds experienced poor utilisation.
> > 
> > I think the issue is that such paths do not currently suffer from
> > throughput problems, but could if they attempt to participate in an
> > SCE conversation.
> 
> Except that they *do* already suffer from throughput problems if they
> attempt to participate in an RFC-3168 ECN conversation, to precisely
> the same extent, and for precisely the same reasons.

In (the vast majority of) datacenter switches, all queues are shallow
(10s of microseconds) relative to typical Internet RTTs (tens of
milliseconds). It is completely orthogonal to any AQM or ECN scheme.

If you want your Internet-facing servers buried within a datacenter
network, you are well advised to carve out a BW capacity slice for that
traffic sufficient to avoid congestion.


Regards,

// Steve