From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] public safety and jitter and latency concerns
Date: Tue, 13 Mar 2018 13:19:13 -0700 [thread overview]
Message-ID: <CAA93jw4xWUxw0vaz5OUWsctY-ykNJ_xivc_JTFH-Zj8t8SmXVQ@mail.gmail.com> (raw)
are gradually trickling over to the IEEE
http://sci-hub.name/10.1109/ACCESS.2017.2762471
This concludes my monthly internet scan for bufferbloat related
issues. I'm terribly, terribly burned out on this subject, and yet
there seems to be infinite depth to the deployment problems that
remain.
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
reply other threads:[~2018-03-13 20:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4xWUxw0vaz5OUWsctY-ykNJ_xivc_JTFH-Zj8t8SmXVQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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