Re: [tsvwg] L4S dual-queue re-ordering and VPNs

Sebastian Moeller <moeller0@gmx.de> Tue, 18 May 2021 09:40 UTC

Return-Path: <moeller0@gmx.de>
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 47D953A1520 for <tsvwg@ietfa.amsl.com>; Tue, 18 May 2021 02:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 (1024-bit key) header.d=gmx.net
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 MhEp-u7Xf6vm for <tsvwg@ietfa.amsl.com>; Tue, 18 May 2021 02:40:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 391FE3A1543 for <tsvwg@ietf.org>; Tue, 18 May 2021 02:40:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1621330762; bh=wQKWET9B8+B8kxCgbIV+U99t9XUu3aiDMgoPjrRpJfg=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=kUXnkWPSbOX9q0T2RQmzjgLL+LFZu0Uz5FWgCRKPnFj+tbQPqt5H0Is3+yatsEhnB frI5+i7aECb4DMkkwjQhyfwp74IaC3/BvDNAD0M2odzTA/dI+kCJrHfdx6FeST5CVs XZgEOQAm3E9VW25RsPuwo1rP7vdgSzKnnOk0mtS8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.250.105] ([134.76.241.253]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N5G9n-1lJKk32EBJ-01178T; Tue, 18 May 2021 11:39:22 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.20\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <d76d9f2b-e801-0084-2e22-fd74ae8bd83a@bobbriscoe.net>
Date: Tue, 18 May 2021 11:39:20 +0200
Cc: TSVWG <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <700B3AA8-FA52-4DE5-A805-22C063400099@gmx.de>
References: <68F275F9-8512-4CD9-9E81-FE9BEECD59B3@cablelabs.com> <1DB719E5-55B5-4CE2-A790-C110DB4A1626@gmx.de> <MN2PR19MB40452C9DD1164609A005139583569@MN2PR19MB4045.namprd19.prod.outlook.com> <e15d732f64bf983975dbe507092b39f0744f7f74.camel@heistp.net> <1efe0dfb-afb6-0aa4-dcff-fb4ddeb46b8f@bobbriscoe.net> <689EAC46-9873-40BC-A8EE-12060336FB19@gmx.de> <a6ae94e9-4bdb-222b-d206-7f35fc807948@bobbriscoe.net> <42ECC889-440C-4DE1-BD8C-C983387E460C@gmx.de> <2a3d13ef-043d-aaa9-d036-c7945676f6f7@bobbriscoe.net> <595F0D20-CE6C-4A85-85BD-536DDFDF4D82@gmx.de> <d76d9f2b-e801-0084-2e22-fd74ae8bd83a@bobbriscoe.net>
To: Bob Briscoe <ietf@bobbriscoe.net>
X-Mailer: Apple Mail (2.3445.104.20)
X-Provags-ID: V03:K1:ek1eLKLnS6UiwuybX4wpGQbzRPslbLasIP/T2i0EZAPagv4/GMb ZNjjNwhGKNCdt3TyhRClxt20N9PJFT+7wNFJGKIuTZMkz3LdEEUD2/J9mmEFBbi4z//3DxL D6oriP6sJoCUXlribcCPm4WsdWwKg/qr+pkRFVNeYZC/sYGRWec4NrFJXatpZ46eMiCFs7k QeMJWhqWKTLkXX4B1/6KQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:i60KeS9R2ZI=:oJkFLsOgTuqU1dFI+bBspM mq8NjyfDDVa6ixrAPdY2IJf8pPuafIyWLozqDsxGC2vxVhGP7d/1t6Y3gZ/8pRZafSheBhryI IUqV8Gj8j1KbW5NGPfn+1890+jSsIktx7HLkV5UsqtI/CT4rM8GxvKolPVBRLfLUpy2wF3wEV OU0wPJ3lDjgAN64veUTodXJupmHf1RScherwV57FPltKLBuirrs61ZPhYLHwNi2i9uaa7Pm0h kV29NJ2Kf3C1LQ96hApGAzh9MkMDoUHjxXddGllfza7Yuu604S6XSM3Cc9SyY0JGvmsNpRkqJ +3dQ/19FICMQU/NrYGdUrtR+OBGGBjHmuUHO1x3G1Sw0far0cnoONRuwmdyaBRzywaMrvp7be ZKl3uyHzjb+Z13pzEi3/Dsu3ouSe6NGDmMTyLVuHU+wtnJXXY7/aG7wpjR88vGiRFeLtJ1TTO jRrJYSHf5gWKS24s2ceB3lzU/E+CtWrLxaS2wQcs70Khe2CclrgWCpmDe2ILqTnU+px5w2HD2 3AZ03gXydwYedbv2KPVSzfvK/sfy2fzcAw7FYiQ4Pj5hMn9yi1+vARgimYxAu5YVk/CGzMAlE xIzS/IE3FOW2cSJFJVRANhShlgCvdD5fANgI+9hoyRymliqIidECczkGcFwl5DsFb43iza7QW +jzmzTdwAgFPuvABZb5mXDA7DRDOhC8Vlm3KNZb9n3FxXMRKkbNhRcFOAUMM1UMPg67Y7Lx89 5Te4ubfl/a6D0KvoAC/O2rTOcqjhBckXLamhC/FXODTD70VoVna5SqR8z+s7wwZrcXYnMQ8Ys VrinDY2gTMRyQ/+HnJTFlftqLoOxVYnQfu1jUx5u7ICX2iZzEJSUkSI6y/5RL9Qvkn5O5U1HQ bD21gWCia6j08vdPcFKird9bcyDwi6STrEQiVkxoQ4mVcBXaL43a8VcdLRog0jyeDEgrAm7sw JXKTg8ymU62KTQqNuoC6j8TSvvq+m41W8N52Y8YZeW3Cd7DZmfFlch5SKINRvD2L1sSreJge0 PhPoQFWmc26X7/24/Q0dE7ybSS4dhNj/0fl0PvYaIR4aMoB992EI/9XcvXd2g7vlqWlieqarS rQ+oNaZZP+IjgZVpbtGq9ENSM85o0Cps86w7KrCNvEit5uGtOVcXKSQDh0m4NQa4blz/UKpJ9 4Wi3SIKjMpe2DFO02AavrdHevzfZTs84GqxwaQJ1dOO1Qj4D2ZLd20lZsvvI6lNk+IqAk=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/kf7W7Ir1RtNCr_5hpxAgZIDimbg>
Subject: Re: [tsvwg] L4S dual-queue re-ordering and VPNs
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, 18 May 2021 09:40:27 -0000

Hi Bob,

> On May 18, 2021, at 10:06, Bob Briscoe <ietf@bobbriscoe.net> wrote:
> 
> Sebastian,
> 
> I think this thread has converged on agreement on every point - so no need to reply.
> See [BB2] for a couple of clarifications.

	[SM] I just want to emphasize one point below, see [SM3], I took the liberty to reduce the cited text.


> 
> On 09/05/2021 22:07, Sebastian Moeller wrote:
>> Hi Bob,
>> more below, prefixed [SM2].
>> 
>>> On May 9, 2021, at 18:50, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>>> [...]
>>> [BB] I thought you agreed it would likely be worse with Diffserv (which is status quo)
>> 	[SM2] Not what I intended to convey. In my setting of end-users using an encryppted VPN from their home link, and either OpenVPN or nowadays more often wireguard, DSCP propagation is not happening by default and hence can not be a significant cause of concern, I hope that clarifies my position.
> 
> [BB2] This is a view of a world populated by techies who choose their own VPN software. I accept that the VPN products that you select from don't propagate the DSCP. But we also need to think of all the commercial VPN products that IT departments choose and install on behalf of their end-users so they can access the work intranet from home or while on the road. That's all I'm trying to explain here.

	[SM3] I think that getting change into commercial VPN products to change is a much easier task than to get in into all end-user run VPNs. For one there is only a limited number of relevant VPN vendors/developers that would need to "bake" changes into their product and/or their documentation and that might even be able to send all of their customers information about expected changes (via update notes or maintenance contacts). Also if an IT department exists that is in charge of operating a VPN, IMHO they can be reasonably expected to understand/research how to implement such a change or find different work-arounds. 
	Normal end-users will have to do all of this themselves... without professional help, this is why I want to focus on that perspective of the issue (and I do not want to imply that getting change into commercial VPNs is going to be easy, just a lot easier than without).

Best Regards
	Sebastian