Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: William Allen Simpson <william.allen.simpson@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] revised Codel RFC is up
Date: Mon, 04 Mar 2013 12:46:49 -0500	[thread overview]
Message-ID: <5134DE09.1000502@gmail.com> (raw)
In-Reply-To: <1362252799.912230623@apps.rackspace.com>

On 3/2/13 2:33 PM, dpreed@reed.com wrote:
> In general, my observation of the IETF has been that it is largely dysfunctional as a vehicle for achieving important consensus that leads to problem solutions.  I'm not expecting better than that, but I could be surprised.
>
There was a period between throwing off the yoke of (often well
intentioned) DEC and the dominance of (less well intentioned)
Cisco and Microsoft where IETF got a lot done -- before 1996.

Still, there was a long-standing TCP Implementors list that was
helpful.  The current TCPM WG is not.


      reply	other threads:[~2013-03-04 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 18:27 Dave Taht
2013-03-02 19:33 ` dpreed
2013-03-04 17:46   ` William Allen Simpson [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=5134DE09.1000502@gmail.com \
    --to=william.allen.simpson@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