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: bloat-announce@lists.bufferbloat.net,
	codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] revised Codel RFC is up
Date: Sat, 2 Mar 2013 14:33:19 -0500 (EST)	[thread overview]
Message-ID: <1362252799.912230623@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4mggTK=WW98zs0=Hs_Rimyi19XUfF7D2r8ifdAgfA9eQ@mail.gmail.com>

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


This is an excellent RFC.  It should be issued immediately.  It should also be (along with fq_codel) cited as one alternative for managing queues properly in a new version of a "best practices" RFC.  There may be alternatives of similar quality, but those alternatives should have quantitative experimental evidence that shows similar benefits.
 
My own personal view of the effectiveness of IETF as an organization would be positively affected by how quickly a solution goes from this to widespread deployment (including upgrades of existing defective gear) - since I have occasionally asked to testify on the value of IETF in coordinating the Internet's evolution in policy circles, it should be noted that much of my opinion depends on such observations of organizational effectiveness in dealing with important problems, to the extent that matters.
 
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.
 
Organizations such as BITAG seem to have been invented because IETF fails.  I don't think BITAG is an appropriate forum, as it shows no competence whatever to discuss such things as congestion management with "clue" and experimental evidence.
 
We'll see.
 
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Saturday, March 2, 2013 1:27pm
To: "bloat" <bloat@lists.bufferbloat.net>, bloat-announce@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: [Cerowrt-devel] revised Codel RFC is up


[http://tools.ietf.org/html/draft-nichols-tsvwg-codel-01] http://tools.ietf.org/html/draft-nichols-tsvwg-codel-01

-- 
Dave Täht

Fixing bufferbloat with cerowrt: [http://www.teklibre.com/cerowrt/subscribe.html] http://www.teklibre.com/cerowrt/subscribe.html

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

  reply	other threads:[~2013-03-02 19:33 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 [this message]
2013-03-04 17:46   ` William Allen Simpson

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=1362252799.912230623@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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