Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: Vint Cerf <vint@google.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Congratulations
Date: Wed, 20 Aug 2014 15:09:08 -0400 (EDT)	[thread overview]
Message-ID: <1408561748.07039917@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4mT4N1RWkcTernE_8UADR_8hsC2UoMPYga5=oT3aO8dA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]


I just read Vint Cerf's latest column in IEEE Internet Computing (October 2014), paper edition that arrived in the mail.  Entitled "Bufferbloat and other Internet challenges", it highlights Jim Gettys, Dave Taht, Eric Dumazet, Codel/FQ_code, the CeroWRT/OpenWRT team, etc. pointing out that
 
"The use of open source software to promote broad adoption and use of new technology is now well demonstrated ... The CeroWRT/OpenWRT effort could have a similar effect, especially if the resulting software can be ported to a variety of hardware platforms."
 
This is a quote and a column you can "take to the bank", especially the "if ... can be ported to other hardware platforms", which it should be.
 
Congratulations, all.  I have said before that this project's technical contribution impresses me as much as Bram Cohen's creation of the original BitTorrent, and that's no small comment.  I nominated him for a number of awards at the time, and he got at least one (he would have gotten "best paper of the year" if he had published his paper in an ACM journal, in my opinion.)  Now Vint's opinion is supporting your work as well (and that has real weight).

[-- Attachment #2: Type: text/html, Size: 1904 bytes --]

      reply	other threads:[~2014-08-20 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53F2A0F4.9020705@opentechinstitute.org>
2014-08-19  1:00 ` [Cerowrt-devel] Fwd: [Commotion-dev] Wireless talks from DEFCON Dave Taht
2014-08-20 19:09   ` dpreed [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/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=1408561748.07039917@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=vint@google.com \
    /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