Re: [tsvwg] Disable ECN on VPNs, really?

Jonathan Morton <chromatix99@gmail.com> Wed, 18 November 2020 11:10 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 40FF33A17B5 for <tsvwg@ietfa.amsl.com>; Wed, 18 Nov 2020 03:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Qom8YyBF0KHG for <tsvwg@ietfa.amsl.com>; Wed, 18 Nov 2020 03:10:33 -0800 (PST)
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 E2B2E3A17B3 for <tsvwg@ietf.org>; Wed, 18 Nov 2020 03:10:32 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id b17so1848271ljf.12 for <tsvwg@ietf.org>; Wed, 18 Nov 2020 03:10:32 -0800 (PST)
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=MwyjUvW5lyu1HdXrVaelxbHNIY41W3dYBvzX4DM4Tqg=; b=L8EWFgJ3jGJgWmfYYte0nSxV4vydtzvbP8PCPNQuEQipjgtheDPISgMtpTfAyBQkQb tIcIMe5KLzNwo4iBGCYoDcosdm/uLuChJiXVElPXZPIh5OH9hzyrMdTK13+u3aA7+GYH lmJFnHX18Sx4sCUz4iKeHo3Gj8w2qh6ddmqNvgKZxQOluVub5onZuQV7X+JOVJ3wpmOY MKlK0qJi1/XMQZNfc7Jea+NtjJHhxOlgwCEairFojmxyz7jrFZtYJ2PmG+Y1GbKJzdLS K61/bkhtJUywaD/2mKj+neixvhCv4kUEMmXEtBEw5qVEqlBWvT2jQF9SSCXGKIC0RNU0 StBg==
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=MwyjUvW5lyu1HdXrVaelxbHNIY41W3dYBvzX4DM4Tqg=; b=I0ahS+nxbNWXpolIsvtFn6K0ADl1O5bwnzgRtxwQ0SN5VUIs47H97iBWTphVdG+kbh CsGOO2eUEwviFyUqtV+2Q8H4m2kBygk+qs8fJvGiqCbeKZKQcJ0LJw5I3iNyMPUGQkW6 VQpkCmv5cGKiRtmS0vQ/od175a9B3OSfc/ULncxuDISBBvBF+P660tZHFFMwYZsgyJU+ ArgqIauIL19lpC8/9l3G5XPlTeGvvifl5TfSQ8tPRQOCWjCeDt84ZE6mlOzSqfYTJ+59 ZVoMKxdpvQwGNnwAwICz/jBu1YzIHDyGDC1RStYZbTWod1sjJZ2f5t4HpSzwA9go9lMF n+1g==
X-Gm-Message-State: AOAM530vGrODABZ/azo0ATcyr6Om+NffyTeKQnfLggf4vOCWlwkF8JAp sZoeQropA7uk8j7WYzDOL0E=
X-Google-Smtp-Source: ABdhPJwCBvm+QbywM/FAXmXoPgsWZSktKKu2D1UhuH5xTesjtYZLGqqua/UYsqk+CCbOKeB5c1d86g==
X-Received: by 2002:a2e:80d1:: with SMTP id r17mr3430443ljg.176.1605697830914; Wed, 18 Nov 2020 03:10:30 -0800 (PST)
Received: from jonathartonsmbp.lan (178-55-159-67.bb.dnainternet.fi. [178.55.159.67]) by smtp.gmail.com with ESMTPSA id f25sm3520803lfc.234.2020.11.18.03.10.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Nov 2020 03:10:30 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <AM8PR07MB7476D5789213C029A27C2228B9E10@AM8PR07MB7476.eurprd07.prod.outlook.com>
Date: Wed, 18 Nov 2020 13:10:28 +0200
Cc: Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F95F39DE-3809-404D-B863-92EBEC874DFA@gmail.com>
References: <B5C557FF-4631-4C2D-9A86-C498B357ED8D@gmx.de> <AM8PR07MB7476D5789213C029A27C2228B9E10@AM8PR07MB7476.eurprd07.prod.outlook.com>
To: "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/c1IGeLIDs-KBQT5igS7kgvHxGg0>
Subject: Re: [tsvwg] Disable ECN on VPNs, really?
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: Wed, 18 Nov 2020 11:10:34 -0000

> On 18 Nov, 2020, at 12:39 pm, De Schepper, Koen (Nokia - BE/Antwerp) <koen.de_schepper@nokia-bell-labs.com> wrote:
> 
> Indeed, a better solution would be to support L4S in those deployments. Are there any constraints in doing so? It seems to be installable/upgradable packages, not?

Have you ever tried to walk an end-user through upgrading their modem firmware?  Remember, L4S requires replacing *every* potential bottleneck's AQM before it is safe to deploy.  That's a lot of end-users.

It would be better to adopt an architecture which accommodated existing AQM deployments instead of displacing them.

 - Jonathan Morton