From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: Michael Richardson <mcr@sandelman.ca>,
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 21:08:16 -0300 [thread overview]
Message-ID: <20180405000816.GD8555@localhost.localdomain> (raw)
In-Reply-To: <7DC0ADE6-3D20-417F-8940-96E4A68197B5@ifi.uio.no>
On Wed, Apr 04, 2018 at 09:38:02PM +0200, Michael Welzl wrote:
>
>
> Sent from my iPhone
>
> > On 4 Apr 2018, at 21:23, Michael Richardson <mcr@sandelman.ca> wrote:
> >
> >
> > Dave Taht <dave.taht@gmail.com> wrote:
> >> How dead is posix these days? Ietf does not generally do apis well.
> >
> > I disagree.
> >
> > IETF has lore says that it doesn't do APIs well, and so it's a
> > self-fullfiling prophecy. Everyone knows it's true without any actual
> > evidence, so nobody tries.
> >
> > Who does do APIs well today? Microsoft's API story is a disaster,
> > so despite decades of market dominance, their networking APIs are not
> > defacto standard. While it looks like Linux does APIs well, actually,
> > it just does a really good job at getting the public APIs implemented.
> >
> > The IPv6 BSD sockets API is a roaring success.
> > It's just not enough given MIF, DNSSD, IPsec, LISP, etc. The problem
> > space has expanded.
> >
> > The problem is getting API work funded across Google, Apple, MS, *BSD,
> > and Linux.
>
> fwiw, apple is on board of taps and actively involved, and the neat
> project ( www.neat-project.org ) made an open source library that
> runs on linux and bsd systems
Neat has a very interesting concept. If they can pull that out, it
will be very nice.
prev parent reply other threads:[~2018-04-05 0:08 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
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 [this message]
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=20180405000816.GD8555@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=mcr@sandelman.ca \
--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