From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Seen in passing: mention of Valve's networking scheme and RFC 5348
Date: Tue, 3 Apr 2018 14:35:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1804031432531.18650@uplift.swm.pp.se> (raw)
In-Reply-To: <8DE589C3-9537-416D-AC7C-9250464869F9@gmail.com>
On Tue, 3 Apr 2018, Jonathan Morton wrote:
> notwithstanding). In the end, people have kept reinventing "reliable
> datagram" protocols on top of UDP, whenever they ran up against
> requirements that TCP didn't fulfil.
Yes, for multiple reasons. TCP is ossified and typically lives in the OS,
because of NAT the only options for protocols that work are TCP and UDP,
so if you want to move your "transmission stack" to userspace, your only
choice is UDP. So enter things like QUIC and others that are mux:ed stream
protocols over UDP, which can then live in userland on all major operating
systems.
This is not ideal, but it's not strange that this is happening. The only
way to innovate as an application/protocol developer is to use UDP.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-04-03 12:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tag:www.oreilly.com, 2018-04-02:/ideas/four-short-links-2-april-2018@localhost.localdomain>
2018-04-02 12:46 ` David Collier-Brown
2018-04-03 11:54 ` Jesper Louis Andersen
2018-04-03 12:14 ` Jonathan Morton
2018-04-03 12:35 ` Mikael Abrahamsson [this message]
2018-04-03 14:27 ` Michael Welzl
2018-04-03 14:48 ` Jesper Louis Andersen
2018-04-03 15:04 ` Jim Gettys
2018-04-04 12:45 ` Jesper Louis Andersen
2018-04-04 13:39 ` David Collier-Brown
2018-04-03 16:14 ` Michael Welzl
2018-04-04 7:01 ` Mikael Abrahamsson
2018-04-04 7:42 ` Dave Taht
2018-04-04 7:55 ` Michael Welzl
2018-04-04 8:53 ` Mikael Abrahamsson
2018-04-04 8:52 ` Mikael Abrahamsson
2018-04-04 9:56 ` Luca Muscariello
2018-04-04 10:52 ` Mikael Abrahamsson
2018-04-04 11:06 ` Luca Muscariello
2018-04-05 0:04 ` Marcelo Ricardo Leitner
2018-04-04 19:23 ` Michael Richardson
2018-04-04 19:38 ` Michael Welzl
2018-04-05 0:08 ` Marcelo Ricardo Leitner
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=alpine.DEB.2.20.1804031432531.18650@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=jesper.louis.andersen@gmail.com \
/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