From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] diffserv in cake
Date: Fri, 30 Oct 2015 08:13:47 -0400 [thread overview]
Message-ID: <CAA93jw7LEsR96bm60-61onGEQZkxu-m8zC_7QY49Qv=7SC6xsg@mail.gmail.com> (raw)
I am still way behind on email, only reading things peripherally, and
trying to keep to one subject per mail.
I have never thought the schemes we currently have in cake for
diffserv will survive exposure to what ISPs and other users consider
the "real world".
It was my hope, instead, that with ease we could add new models for
how to handle diffserv handling along existing htb based schemes.
I have long pursued every isp that I have contact with to talk about
their stuff, and none have responded.
We have not even tried to address vlans, for example... and probably should.
However the API lets us add new models easily, and I am thus, certain,
no matter what we deliver, that some big user will diss us as to what
we got wrong, fix it internally, and end up with a conflicting api for
whatever they deploy, and diss us for not intuiting their needs well
enough. I'm prepared to live with that.
Dave Täht
I just invested five years of my life to making wifi better. And,
now... the FCC wants to make my work, illegal for people to install.
https://www.gofundme.com/savewifi
next reply other threads:[~2015-10-30 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 12:13 Dave Taht [this message]
2015-10-30 12:32 ` Toke Høiland-Jørgensen
[not found] ` <5A86B264-B957-41D2-9E4C-D1F9C525A99F@gmx.de>
[not found] ` <CAA93jw4xv-PLtAnw96xQmJoRFZmd24fJq04BJnc4_NPTPH2LqA@mail.gmail.com>
2015-10-30 12:40 ` Sebastian Moeller
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7LEsR96bm60-61onGEQZkxu-m8zC_7QY49Qv=7SC6xsg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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