From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>,
Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Seen in passing: mention of Valve's networking scheme and RFC 5348
Date: Wed, 4 Apr 2018 09:01:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1804040857200.18650@uplift.swm.pp.se> (raw)
In-Reply-To: <0ED5B59A-5C31-4F70-A2C9-04D9EA779A7B@ifi.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On Tue, 3 Apr 2018, Michael Welzl wrote:
> Sure, when you’re in control of both ends of a connection, you can build
> whatever you want on top of UDP - but there’s a lot of wheel
> re-inventing there. Really, the transport layer can’t change as long as
> applications (or their libraries) are exposed to only the services of
> TCP and UDP, and thereby statically bound to these transport protocols.
I'm aware of TAPS and I have been trying to gather support for this kind
of effort for years now, and I'm happy to see there is movement. I have
also heard encouraging talk from several entities interested in actually
doing serious work in this area, including some opensourcing part of their
now non-FOSS code-base as part of that work.
So we need applications to be able to get more access to what's going on
the wire, including access to non-TCP/UDP, but also to be able to create
"pluggable TCP-stacks" so that a host can have several different ones, and
the user can install new ones even on older operating systems.
With more and more IPv6 around, I hope we'll be able to deploy new
protocols that are not TCP/UDP (A+P), and that this will bring back some
innovation in that area.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-04-04 7:01 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
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 [this message]
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.1804040857200.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 \
--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