Re: [iccrg] Will Fair Queuing change Congestion Control?

Vidhi Goel <vidhi_goel@apple.com> Tue, 03 January 2023 19:46 UTC

Return-Path: <vidhi_goel@apple.com>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC5DC14CE24 for <iccrg@ietfa.amsl.com>; Tue, 3 Jan 2023 11:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMTPvyLoJSms for <iccrg@ietfa.amsl.com>; Tue, 3 Jan 2023 11:46:05 -0800 (PST)
Received: from rn-mailsvcp-ppex-lapp44.apple.com (rn-mailsvcp-ppex-lapp44.apple.com [17.179.253.48]) (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 9BFE0C1522C6 for <iccrg@irtf.org>; Tue, 3 Jan 2023 11:45:56 -0800 (PST)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp44.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp44.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 303JgIQW028020; Tue, 3 Jan 2023 11:45:55 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=biXYpOhgKaTCMY+xlQfjp/zPxxiznN2HlOoVVpwPJE8=; b=XLbH2xQpHFeVgS5ydVfYtaOixPeo9x5yUFvUu2QGg+xXC7HVWm80fprTecCOV+IryKwo geNuIHLRx5SYPmfUchYzMn6UpBszFdBdAFmyvip+UktzzDy0z1hojHgEg9a7vqXRIMLR xRlJhTsTDBwx/jBIfy03SiFWY16bLsW4hOq0qd5z/KiMuGJV+xpkbLUzhiU4ii+zw9iM IbiNNSW/VFClH0MUHqip/CcANerd8bB7HG/MbDdJ6J9pOo91lBwbIZqiAf19ENmAt0KZ MI8CpD8UEz3U3/+79AZhzN+uJAJtx6Hz1TeP9uQRSmdxR29eLSsuquz38hl3qIjzHj5c uQ==
Received: from rn-mailsvcp-mta-lapp04.rno.apple.com (rn-mailsvcp-mta-lapp04.rno.apple.com [10.225.203.152]) by rn-mailsvcp-ppex-lapp44.rno.apple.com with ESMTP id 3mthfbmnwk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 03 Jan 2023 11:45:55 -0800
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.20.20220923 64bit (built Sep 23 2022)) with ESMTPS id <0RNX00C7YDKIIBM0@rn-mailsvcp-mta-lapp04.rno.apple.com>; Tue, 03 Jan 2023 11:45:55 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.20.20220923 64bit (built Sep 23 2022)) id <0RNX00300DKEOK00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 03 Jan 2023 11:45:55 -0800 (PST)
X-Va-A:
X-Va-T-CD: cd8e0fbb4526d43066b44f97ac1b6301
X-Va-E-CD: 6cfd992a87ee215416ee3d355bad10ed
X-Va-R-CD: 11a8e9dc2d494839c6a0d248fede85a4
X-Va-ID: 986a6d63-e528-4580-93c2-c369aae3c7d4
X-Va-CD: 0
X-V-A:
X-V-T-CD: cd8e0fbb4526d43066b44f97ac1b6301
X-V-E-CD: 6cfd992a87ee215416ee3d355bad10ed
X-V-R-CD: 11a8e9dc2d494839c6a0d248fede85a4
X-V-ID: 5d7dbbc8-194a-48db-bf07-4387605644e6
X-V-CD: 0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545, 18.0.923 definitions=2023-01-03_07:2023-01-03, 2023-01-03 signatures=0
Received: from smtpclient.apple (vimac.scv.apple.com [17.192.154.53]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.20.20220923 64bit (built Sep 23 2022)) with ESMTPSA id <0RNX00K84DKIZE00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 03 Jan 2023 11:45:54 -0800 (PST)
From: Vidhi Goel <vidhi_goel@apple.com>
Message-id: <E8CE0E38-BC35-416D-8D56-FEA1416968D6@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_F0903581-E96E-4BFD-97FE-2F579536FF1D"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3726.0.9.1.22\))
Date: Tue, 03 Jan 2023 11:45:44 -0800
In-reply-to: <CAEXAmbs1WwvJ7761eSkSeT_w1GfwnbPL9Tcja8K7fxZHxAiMWA@mail.gmail.com>
Cc: iccrg@irtf.org
To: Maximilian Bachl <maximilian.bachl@gmail.com>
References: <CAEXAmbs1WwvJ7761eSkSeT_w1GfwnbPL9Tcja8K7fxZHxAiMWA@mail.gmail.com>
X-Mailer: Apple Mail (2.3726.0.9.1.22)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.545, 18.0.923 definitions=2023-01-03_07:2023-01-03, 2023-01-03 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/GIrTEbXBtR4iU3EXCe_wNvVn8gQ>
Subject: Re: [iccrg] Will Fair Queuing change Congestion Control?
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2023 19:46:09 -0000

Hello Max,


Few things to note, FQ expands to Flow Queue (not fair queueing) which means every flow (4 tuple) has a different queue. Priorities are implemented based on service classes, for example. Also, Apple devices are not the most common bottleneck on an end to end path.

Even if we assume there is enough deployment of flow queueing in the network, flows can hurt themselves by not responding to growing latency. This problem has been addressed in L4S drafts and I highly recommend reading them. ECN combined with an immediate AQM combined with Prague congestion control is basically the idea of L4S.

Vidhi

> On Jan 3, 2023, at 9:20 AM, Maximilian Bachl <maximilian.bachl@gmail.com> wrote:
> 
> Apple introduced fair queuing (FQ) on more than a billion of devices in the last years (https://blog.cerowrt.org/post/state_of_fq_codel/). I wonder if this could have an impact on congestion control. When there’s fair queuing at the bottleneck link of a path, the endpoints can use delay-minimizing congestion control and don’t have to worry about more aggressive senders. 
> 
> However, currently, there’s no established mechanism for endpoints to know of the existence of fair queuing on a path. There are some possibilities, though, how endpoints can be made aware of the existence of fair queuing: 
> A dedicated bit in some packet header. For example, some ECN or DSCP bits could be repurposed to indicate the existence of fair queuing at the bottleneck. Drawback: It’s hard to convince people to repurpose/introduce new bits and switches/routers have to support it. 
> An end-host-based mechanism to detect fair queuing without the involvement of switches/routers. I created a proof-of-concept implementation of such a mechanism, which can detect the presence/absence of fair queuing with an accuracy of > 95% (https://arxiv.org/abs/2206.10561).
> Closed ecosystems in which all components are aware that there is fair queuing: As a hypothetical example, let’s assume a user plays a game on nvidia’s cloud-gaming platform on an iPhone. The phone is connected to T-Mobile’s 5G network. Both the client on the iPhone as well as the server in nvidia’s network know that there’s fair queuing on the path between the client and the server, since they have an agreement with T-Mobile, which controls the entire path. No extra bits in packet headers are needed, just mutual agreement between the user’s device, the cellular network provider as well as the server on the internet. 
> 
> If you have some opinions on whether fair queuing is going to change how we do congestion control, I’d be curious. 
> 
> Regards,
> Max
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg