From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: Michael Welzl <michawe@ifi.uio.no>,
bloat <bloat@lists.bufferbloat.net>,
Jonathan Morton <chromatix99@gmail.com>
Subject: Re: [Bloat] Seen in passing: mention of Valve's networking scheme and RFC 5348
Date: Wed, 04 Apr 2018 15:23:46 -0400 [thread overview]
Message-ID: <12848.1522869826@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw5Z=cAOfNtuJyYrjJviucWRZK628mVearkPH3rzifrEDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
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.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-04-04 19:23 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 [this message]
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=12848.1522869826@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@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