[Cerowrt-devel] revised Codel RFC is up
dpreed at reed.com
dpreed at reed.com
Sat Mar 2 14:33:19 EST 2013
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 at gmail.com>
Sent: Saturday, March 2, 2013 1:27pm
To: "bloat" <bloat at lists.bufferbloat.net>, bloat-announce at lists.bufferbloat.net, cerowrt-devel at lists.bufferbloat.net, codel at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat-announce/attachments/20130302/3c6af803/attachment-0002.html>
More information about the Bloat-announce
mailing list