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

Jonathan Morton <chromatix99@gmail.com> Fri, 08 May 2020 17:53 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 168243A0E6C for <tsvwg@ietfa.amsl.com>; Fri, 8 May 2020 10:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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] autolearn=ham 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 8zgRcC-M32sR for <tsvwg@ietfa.amsl.com>; Fri, 8 May 2020 10:53:16 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 F07973A0F07 for <tsvwg@ietf.org>; Fri, 8 May 2020 10:53:07 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id a21so2570824ljb.9 for <tsvwg@ietf.org>; Fri, 08 May 2020 10:53:07 -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=KWiyjEq7xWdwoujEpcoc/xwbOqNy2e9YQoBDDTm1E30=; b=D8wF1g4aS9OmlyFWDP++nmVdzrwhnCa+g7t/X+AFeblKnfwrYoUnre525MXMYDhQXb SigjF2wRTIyUy7DdpM4FQsVGXUgyUrKcweMcS6hGXTawBQATfFlOyVDc3rDU+xeWnsVf DM2aJPY1pbB/lTtVUp3UEeI8p/PNjWlo3NpjvA2Mke/ZDi3dKp/oD40Obd+FPDf6wHmG U2uYPiK7OpGP1fhF0ETyXMHaV2OSr/yVmebhqkOfdzWtBSqae6GIbTwie/mqjzEyGr9s hgm2nh+kLAm55pBlKcjsuxXPfWpIgzIbdabmvZaQfda1UAeAPXOsyuWZzpeoPITsWGCL J2yQ==
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=KWiyjEq7xWdwoujEpcoc/xwbOqNy2e9YQoBDDTm1E30=; b=dlWON49/GWCr5b76UBXl4k6wSJzGyuezJO5/Xgm7Qr6MQQ3gz7KjfHruOR4j78wC+f Akxm477WQ0O0bPwOzV2S3WW607XWxhD6rSzAZzw1Kv86Xwr0699Qpd/KN10wS7s3HG79 I+FrrbS3HkH5dqhekkoQ2h/SJpVjsr3+LbUZzpZnV0UMaTbn8iYMtfVMCQony2pWawOc 8gmRwAvfj0GqP91VuH058JIiGAISaBi63//gyVkLEuOnNt77uSAT/kSgTTKCujkuhSj6 DEeEEqQtljCCPyJscpluX1zHWzj6+gUZbacliWXW0NHUa504nbpr3FNyMeEYAvaCYTYi buag==
X-Gm-Message-State: AOAM533OM2uYIHiZX2pfW9xsr8IjLYU7z+EjTAaxPPL9+2R7cTx1unYN VMI98tgYothNg0LQSl6kHeU2hD/H
X-Google-Smtp-Source: ABdhPJzsaGtAcAHmMa8Gbm/JBDuRDSItZfwkR4VBp41vU4EKaCo5YDs58MNfBeXHYjItaU0EL7lkcA==
X-Received: by 2002:a2e:8199:: with SMTP id e25mr2505024ljg.87.1588960386109; Fri, 08 May 2020 10:53:06 -0700 (PDT)
Received: from jonathartonsmbp.lan (83-245-235-192-nat-p.elisa-mobile.fi. [83.245.235.192]) by smtp.gmail.com with ESMTPSA id h84sm1757364lfd.88.2020.05.08.10.53.05 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 May 2020 10:53:05 -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>
In-Reply-To: <2fe941a4-6824-a6bf-5d4d-ac2402912414@wizmail.org>
Date: Fri, 08 May 2020 20:53:03 +0300
Cc: tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F3117CD-6939-4FC3-89B3-D45C481A1B02@gmail.com>
References: <CADVnQy=7f79Mj_GQBU-UsodTRORjB2U6rCPPQ+1Zck_gxr-rww@mail.gmail.com> <2fe941a4-6824-a6bf-5d4d-ac2402912414@wizmail.org>
To: Jeremy Harris <jgh@wizmail.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Y9L9m5s3MuyPFGEaGnmTE3HsLiE>
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: Fri, 08 May 2020 17:53:29 -0000

>> - SCE is basically an extension of RFC3168 ECN: senders mark their packets
>> ECT(0), and respond to CE like RFC 3168 says they should, by halving cwnd.
>> This would not work well for large sites with a substantial installed base
>> of shallow-threshold (DCTCP-style) ECN: if these sites marked their traffic
>> with ECT(0) to try to use SCE, their local switches configured for
>> shallow-threshold ECN would make CE marks at low queue occupancies, which
>> would cause large RFC3681-style reductions in cwnd, which would cause
>> underutilization. To the best of my knowledge this applies to several large
>> Internet services.
> 
> Wait, that doesn't match my understanding.  In such an example site
> using SCE I would expect ECT(0) marking only at "large" queue
> occupancies (and resulting in cwnd halving when seen), but more
> prevalently ECT(1) marking at "small" queue occupancies - resulting
> in some smaller percentage (than 50) decrease in cwnd when seen.
> 
> What did I miss?

I think there are two points to clear up here.

1: SCE proposes keeping the existing meanings of ECT(0) (ie. ECN Capable Transport) and CE (ie. Congestion Experienced).  At an SCE AQM, CE marks would be expected at relatively deep queuing, and SCE marks - ECT(1) - would be applied at the shallower depth.  The AQM would not "introduce" ECT(0) marks; that codepoint is set at the packet's origin.

2: Neal is referring to an existing installation which signals congestion only with CE.  SCE would react to that in the same way as existing ECN transports.  In particular, SCE does not introduce any special problems with such deployments that do not already exist with RFC-3168.

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.  But that, I think, should be taken as a misconfiguration of the network - one which SCE deals with identically to existing ECN transports.

 - Jonathan Morton