Re: [iccrg] Musings on the future of Internet Congestion Control

Bob Briscoe <research@bobbriscoe.net> Thu, 16 June 2022 11:04 UTC

Return-Path: <research@bobbriscoe.net>
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 72AD3C14CF0A for <iccrg@ietfa.amsl.com>; Thu, 16 Jun 2022 04:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.981
X-Spam-Level:
X-Spam-Status: No, score=-8.981 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=bobbriscoe.net
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 u0oaAnMvF4Kz for <iccrg@ietfa.amsl.com>; Thu, 16 Jun 2022 04:04:12 -0700 (PDT)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (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 A063FC14CF09 for <iccrg@irtf.org>; Thu, 16 Jun 2022 04:04:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=qU6ZxBhtO06WO7DkjdOzskToyqTcNvkKQQSdNBT6DLs=; b=BfYvUSGBfnTr868w/UKWDCvkBS WnR0QLNP9BtX+GlNWWsCGLwAPCYkqjt1b/JmUQYFsDCJLZlsph0UWHCYssFShYRMWzBwNtBo6mokd rg6dUOE14Q7wo9VYs0Dxgy0x199HxIHNu9grv7rOXQzWwECqZldmNeB+wGutNKaiZ/zvJv4TECguk L2kbw+PN5rXTz1hvQyF5CG3uZH9EbYuPPMvPH9+4Dj1d35u00hvSanrOBD6cI2qCc+7lCOMOwUEsB J4ErjWYmtZ4tcyiQtkjZSbfYasRtzqR2OhPPvcoEyfCjmxrzrVbrTSUu09PEP3V1SF+yMYl2gzdmu wod7w6jw==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:56910 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from <research@bobbriscoe.net>) id 1o1nIL-0000Ql-6z; Thu, 16 Jun 2022 12:04:08 +0100
Content-Type: multipart/alternative; boundary="------------qRuQfeluxTt66EuEGSDKUS1X"
Message-ID: <cda373f5-0175-513f-4dbb-5b983d8faed8@bobbriscoe.net>
Date: Thu, 16 Jun 2022 12:04:05 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-GB
To: Michael Welzl <michawe@ifi.uio.no>, iccrg@irtf.org
Cc: Peyman Teymoori <peymant@ifi.uio.no>, Md Safiqul Islam <safiquli@ifi.uio.no>, "Hutchison, David" <d.hutchison@lancaster.ac.uk>, Stein Gjessing <steing@ifi.uio.no>
References: <6458C1E6-14CB-4A36-8BB3-740525755A95@ifi.uio.no>
From: Bob Briscoe <research@bobbriscoe.net>
In-Reply-To: <6458C1E6-14CB-4A36-8BB3-740525755A95@ifi.uio.no>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/iccrg/0ZNiEG0rxADzc2WUCdVU9Cy-UQg>
Subject: Re: [iccrg] Musings on the future of Internet 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: Thu, 16 Jun 2022 11:04:17 -0000

Michael,

This seems to be a case where a group of researchers has written a paper 
about wanting to shift its focus to congestion control over path 
segments (PEPs, proxies, etc), but it's written as if it's an argument 
for /everyone/ to shift away from the e2e problem (without actually 
providing strong enough arguments to justify that). I've tried to boil 
this down to 3 generic points (the last of which is a superset of 
Christian's point):


1) Segmented paths inherently involve a potential rate-mismatch between 
one segment (seg1) and the next (seg2). If flow over seg1 is /faster/ 
i.e. ahead of seg2, then yes, a middlebox can be worthwhile, 'cos the 
middlebox M between them can buffer the difference. But if seg1 is 
/slower/ i.e. behind seg2, M cannot invent data that hasn't arrived yet.

The mmWave case in your paper is an example of the latter (impossible) 
case: the typical mmWave case would be a v fast but intermittent link 
close to B (the 'client'). It would be no use getting up to speed fast 
over the short mmWave segment, unless A (the 'origin server') had 
premonition so that it had started getting up to speed earlier over the 
long RTT part of the path, before the client even knew it needed the 
data. {Note 1}

Obviously, a cache at M is a form of premonition. But my point is that 
for true communication of /new/ information between A & B, one cannot 
get round the fact that B cannot receive /new/ information faster than A 
sends it, no matter how much magic there is in box M between them. In 
such cases, information flow has to be e2e. So, if some researchers 
choose to focus on the simpler cases where paths can be segmented at 
middleboxes, someone is still going to have to solve the e2e problem, 
for all the cases when /new/ information generated at A needs to get to 
B fast. {Note 2}


2) This paper seemed to confuse what the comms industry has done (the 
low hanging fruit) with what needs to be researched (so industry can eat 
the high hanging fruit as well). Yes, CDNs have deployed solutions in 
cases where middleboxes /can/ improve performance (e.g. because some 
data or some programme logic is cachable), or where the last mile is the 
slow segment (e.g. satellite). And yes, there is research to be done to 
ensure middleboxes can help in the presence of e2e crypto provided by 
QUIC, etc. ...

...However, if a paper is going to argue for a move away from /research/ 
on the e2e problem, it needs to prove that middleboxes would be able to 
solve the /whole/ e2e problem (which requires premonition - see point 
#1). It is not enough to show that /some/ cases (the low hanging fruit) 
can be solved using middleboxes.

I would have expected to see such arguments in Pt IV-B on 
"Network-assisted congestion control", but these were the only sentences 
I could find that supported this argument:

  * "explicit feedback schemes may work well on shorter path segments"
  * "This could be achieved by putting the control close to the
    bottleneck." [having put it there, how does one communicate between
    A and B, when A or B is not close to the bottleneck?]

If you want to shift your research focus to segmented paths and 
middleboxes, please go ahead. But if you're going to tell everyone else 
to shift their focus as well, you're going to have to come up with a lot 
more convincing arguments than these. Pt IV-B was far too vague to 
support the following conclusion:
     "we argue
     for improved congestion feedback with a shift away from the
     current end-to-end approach; this will improve performance"


3) There are still promising directions to address the e2e diminishing 
feedback problem of getting up to speed. E.g.
* Using cached path knowledge, as Christian pointed out;
* Diminished feedback can be addressed e2e by sending some packets 
faster than others (eg. by sending chirps) to find the available 
capacity without increasing the overall average rate {Note 3}. That 
research direction is extremely relevant to a paper on diminished feedback.
* Ensuring control signal feedback scales with rate

Whether or not you had enough space to cite promising research 
directions that address the e2e problem, their very existence ought to 
have diluted the message that everyone should shift away from the e2e 
problem.


Bob


PS. Nits re. the assessment of the Neubot results around Fig 5:
1/ The appropriate metric for growth of the range of rates should be the 
ratio between P75 & P25, not the difference. If the average grows, it 
would be unusual for the /difference/ between P25 and P75 not to grow.
2/ All the Neubot measurements before 2019 seem highly questionable, 
given when it started to use CUBIC in 2019 the high end jumped about an 
order of magnitude.


{Note 1} With mmWave, it makes sense for M to be able to store up 
incoming data if the mmWave blocks for a while, but that's a not the 
problem of getting up to speed or diminishing feedback, that's the 
problem of intermittency, and Delay Tolerant Networking as a solution.

{Note 2} It is easy to fool oneself into thinking that A can just be 
moved nearer to M, which is placed near to B. But, ultimately, A and B 
map to physical points in the real world where information is generated 
and consumed, and they expect telecommunications to do the job of 
transmitting information between them. Even if they are virtualized 
processes that can migrate, the physical location of A is constrained by 
where (physically) prerequisite info flows are coming from and B is 
constrained by where (physically) onward information flows are going to.

{Note 3} Paced Chirping works well for continuous link types like 
Ethernet. But, since Joakim & I presented the work on Paced Chirping to 
the ICCRG, we've found it's really tough to probe many types of 
bottleneck link for their instantaneous rate, because lots of link types 
are highly discontinuous on short timescales (e.g. WiFi, DOCSIS, LTE). 
However, that doesn't mean that this whole direction is a non-starter - 
it needs more research attention, not less.


Bob

On 15/06/2022 09:02, Michael Welzl wrote:
> Dear ICCRGers,
>
> We just got a paper accepted that I wanted to share:
> Michael Welzl, Peyman Teymoori, Safiqul Islam, David Hutchison, Stein 
> Gjessing: "Future Internet Congestion Control: The Diminishing 
> Feedback Problem", accepted for publication in IEEE Communications 
> Magazine, 2022.
>
> The preprint is available at:
> https://arxiv.org/abs/2206.06642
> I thought that it could provoke an interesting discussion in this group.
>
> Figures 4 and 5 in this paper show that, across the world, network 
> links do not just become "faster”: the range between the low end and 
> the high end grows too.
> This, I think, is problematic for a global end-to-end standard - e.g., 
> it means that we cannot simply keep scaling IW along forever (or, if 
> we do, utilization will decline more and more).
>
> So, we ask: what is the way ahead?  Should congestion control really 
> stay end-to-end?
>
> Cheers,
> Michael
>
>
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/