From: Luca Muscariello <luca.muscariello@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Dave Taht <dave.taht@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 11:56:29 +0200 [thread overview]
Message-ID: <CAHx=1M6jSVdwgb0q4W7wMtSkzOVQ8NbEwO=RE-D0iB-yC=Ri8A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1804041051360.18650@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
I'm looking at TAPS too as I'm looking for a general transport API other
than TCP/UDP.
The kind of transport services we have developed in here
https://git.fd.io/cicn/ do not fit in the current API.
Full user land implementation, which seems to be accepted nowadays, but not
at all a few years back.
The API however is a hack of the INET API, which is rather obsolete, but
this is what current apps can use.
So, hope TAPS gets traction.
And yes, IPv6, absolutely. Going through IPv4 middle boxes is a nightmare.
No hope there.
And yes, flow queueing, absolutely. Flow isolation, becomes fundamental is
such a zoo, or jungle.
On Wed, Apr 4, 2018 at 10:52 AM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:
> On Wed, 4 Apr 2018, Dave Taht wrote:
>
> How dead is posix these days? Ietf does not generally do apis well.
>>
>
> POSIX nowadays is
>
> http://pubs.opengroup.org/onlinepubs/9699919799/
>
> My take on it is that the IETF should not be scared to do APIs, even
> though there is a lot of resistance still.
>
> However, the IETF should not do POSIX APIs, but instead something of their
> own.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2489 bytes --]
next prev parent reply other threads:[~2018-04-04 9:56 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
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 [this message]
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='CAHx=1M6jSVdwgb0q4W7wMtSkzOVQ8NbEwO=RE-D0iB-yC=Ri8A@mail.gmail.com' \
--to=luca.muscariello@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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