From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: Michael Welzl <michawe@ifi.uio.no>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [iccrg] Musings on the future of Internet Congestion Control
Date: Tue, 12 Jul 2022 21:12:10 +0200 [thread overview]
Message-ID: <B7BDAA70-F902-4BAC-ACBB-02C75E565901@gmx.de> (raw)
In-Reply-To: <o1537rr9-r4o3-9r99-9135-6o35rq79n0r8@ynat.uz>
Hi David,
Thanks!
> On Jul 12, 2022, at 19:56, David Lang <david@lang.hm> wrote:
>
> On Tue, 12 Jul 2022, Sebastian Moeller via Bloat wrote:
>
>>>>> There are plenty of useful things that they can do and yes, I personally think they’re the way of the future - but **not** in their current form, where they must “lie” to TCP, cause ossification,
>>>>
>>>> [SM] Here I happily agree, if we can get the nagative side-effects removed that would be great, however is that actually feasible or just desirable?
>>>>> etc. PEPs have never been considered as part of the congestion control design - when they came on the scene, in the IETF, they were despised for breaking the architecture, and then all the trouble with how they need to play tricks was discovered (spoofing IP addresses, making assumptions about header fields, and whatnot). That doesn’t mean that a very different kind of PEP - one which is authenticated and speaks an agreed-upon protocol - couldn’t be a good solution.
>>>>
>>>> [SM] Again, I agree it could in theory especially if well-architected.
>>> That’s what I’m advocating.
>>
>> [SM] Well, can you give an example of an existing well-architected PEP as proof of principle?
>
> the windows protocols work very poorly over high latency links (i.e. long distance links) and the PEPs that short circuit those protocols make life much nicer for users as well as reducing network traffic.
[SM] Windows protocols, like in microsoft's server message block (smb) protocol or as in "protocols using data windows", like TCP's congestion and receive window?
> it's a nasty protocol to start with, but it's the reality on the ground and proxies do help a lot.
[SM] Are such proxies located in third party middle boxes/proxies or are these part of microsoft's software suite for enterprises (assuming the first as answer to my question)?
> David Lang
Regards
Sebastian
next prev parent reply other threads:[~2022-07-12 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6458C1E6-14CB-4A36-8BB3-740525755A95@ifi.uio.no>
2022-06-15 17:49 ` [Bloat] Fwd: " Dave Taht
2022-06-19 16:53 ` [Bloat] " Sebastian Moeller
2022-06-20 12:58 ` Michael Welzl
2022-07-10 17:27 ` Sebastian Moeller
2022-07-10 20:01 ` Michael Welzl
2022-07-10 21:29 ` Sebastian Moeller
2022-07-11 6:24 ` Michael Welzl
2022-07-11 7:33 ` Sebastian Moeller
2022-07-11 8:49 ` Michael Welzl
2022-07-12 9:47 ` Sebastian Moeller
2022-07-12 17:56 ` David Lang
2022-07-12 19:12 ` Sebastian Moeller [this message]
2022-07-12 19:22 ` David Lang
2022-07-13 6:54 ` Sebastian Moeller
2022-07-13 15:43 ` David Lang
2022-07-12 22:27 ` Michael Welzl
2022-07-13 6:16 ` Sebastian Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B7BDAA70-F902-4BAC-ACBB-02C75E565901@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=michawe@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox