From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] the "ietf" accord bof
Date: Thu, 7 Apr 2016 19:51:48 -0700 [thread overview]
Message-ID: <CAA93jw7xUO+eooRQpx5H2wBz6vy_zY6bS1chNXFV2VzkN8tAQg@mail.gmail.com> (raw)
I rather enjoyed the "accord" bof, which was trying to find diffserv
models to fit 3gpp (5g) behavior.
The analogy jari made about fq_codel being the "zero bit" alternative
to diffserv was quite good, but I missed his actual presentation. The
session had a really good, basic, introduction to 3ggp's design,
also... Then the ecn-ish debate started... The session was closed by
ted hardie's refresher of how rfc791's original use case, but the
slides don't do it justice.
You can find the slides at:
https://datatracker.ietf.org/meeting/95/materials.html/
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
next reply other threads:[~2016-04-08 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 2:51 Dave Taht [this message]
2016-04-08 18:53 ` Jonathan Morton
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=CAA93jw7xUO+eooRQpx5H2wBz6vy_zY6bS1chNXFV2VzkN8tAQg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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