Speaking of many problems yet to solve, another IETF group bufferbloat people may be interested in is RMCAT - RTP Media Congestion Avoidance Techniques<div>Charter - <a href="http://datatracker.ietf.org/wg/rmcat/charter/">http://datatracker.ietf.org/wg/rmcat/charter/</a></div>
<div>Join mailing list - <a href="https://www.ietf.org/mailman/listinfo/rmcat">https://www.ietf.org/mailman/listinfo/rmcat</a><br><div><br><div>Kevin Gross<br><div>+1-303-447-0517</div><div>Media Network Consultant<br><div>
AVA Networks - <a href="http://www.avanw.com/" target="_blank">www.AVAnw.com</a>, <a href="http://www.X192.org" target="_blank">www.X192.org</a></div></div></div>
<br><br><div class="gmail_quote">On Sun, Mar 17, 2013 at 12:32 PM, Jim Gettys <span dir="ltr"><<a href="mailto:jg@freedesktop.org" target="_blank">jg@freedesktop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>The ICCRG meeting at last week's IETF went very well, as did a variety of live demos of fq_codel.<br></div><div><br></div><div>You can find the ICCRG slide sets here:</div><div>
<a href="https://datatracker.ietf.org/meeting/86/materials.html" target="_blank">https://datatracker.ietf.org/meeting/86/materials.html</a><div style="width:16px;min-height:16px;display:inline-block"> </div> and, though the sessions were not video'ed by the IETF, Dave and I used our phones and may put some low quality video up later.<br>
</div><div><br></div><div>See: <a href="http://www.ietf.org/blog/" target="_blank">http://www.ietf.org/blog/</a><div style="width:16px;min-height:16px;display:inline-block"> </div> and</div><span style="font-family:arial,sans-serif;font-size:14px"><div>
<br></div></span><a href="https://plus.google.com/u/0/107942175615993706558/posts/A1seNKANmDg" style="font-family:arial,sans-serif;font-size:14px" target="_blank">https://plus.google.com/u/0/107942175615993706558/posts/A1seNKANmDg</a><div>
<br><div>My great thanks to Dave Taht and Comcast to pull off a live demo of bufferbloat helping drive bufferbloat's reality home to people. Such live demos are always a huge amount of work.<br></div><div><div><br></div>
<div>The tsvarea meeting resulted in consensus to work toward establishing a working group and updated set of best practices and RFCs regarding AQM recommendations. First up was establishing a new mailing list for "aqm", which can be joined here:</div>
<div><br><a href="https://www.ietf.org/mailman/listinfo/aqm" target="_blank">https://www.ietf.org/mailman/listinfo/aqm</a><div style="width:16px;min-height:16px;display:inline-block"> </div><br><div style="font-family:arial,sans-serif;font-size:14px;width:16px;min-height:16px;display:inline-block">
</div><br style="font-family:arial,sans-serif;font-size:14px">Now is the time to see how standards sausage is made!<br><br>Some advise was published in the ICCRG meeting about how to proceed further:<br style="font-family:arial,sans-serif;font-size:14px">
<br><a href="http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-4.pdf" target="_blank">http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-4.pdf</a><div style="width:16px;min-height:16px;display:inline-block">
</div></div><div><br>
</div><div>Those of you familiar with RFC 2309 may know that it was informally called the "RED manifesto", and aware that RED's shortcomings doomed it. But such a document (as a public statement of the IETF that this problem must be urgently solved).<br>
</div><div><br>Fred Baker (who was IETF chair recently) just issued an initial internet draft:</div><div><br></div><a href="http://datatracker.ietf.org/doc/draft-baker-aqm-recommendation/?include_text=1" target="_blank">http://datatracker.ietf.org/doc/draft-baker-aqm-recommendation/?include_text=1</a><div style="width:16px;min-height:16px;display:inline-block">
</div><div><div style="font-family:arial,sans-serif;font-size:14px;width:16px;min-height:16px;display:inline-block"></div><br style="font-family:arial,sans-serif;font-size:14px">This one is intended to obsolete RFC2309, and is mostly RFC2309 with the old stuff ripped out, and not a lot of new added. YET! Please join the AQM list to discuss what the new advice (AQM manifesto) should look like.<br>
</div></div><div><br></div><div>Since multiple AQM algorithms can co-exist (e.g. CoDel & PIE), and multiple flow queuing algorithms, we expect that "one size fits all" is unlikely, but documenting them (so that purchasing RFP's can reference them) and explaining their best areas of use; best guess is we'll see a number of informational RFC's and BCP's result, though standards track for the algorithms are not out of the question.</div>
<div><br></div><div>The research and development in this area is still very young. This is the beginning of a long road. As Matt Mathis put it in the ICCRG meeting, the results (which you can see repeated in all the slide sets in the ICCRG meeting) are compelling, and it is important to start the deployment process without years of optimization: seldom do you see orders of magnitude improvement shown as everyone did at the meeting.<br>
</div><div><br></div><div>I would like to thank all of you (and Dave Taht, Kathy Nichols and Van Jacobson in particular) for helping us to get to this point. I started as a lone voice in the wilderness and felt very alone. </div>
<div><br></div><div>With all your help and support there is now a growing chorus and we have billions of devices to deploy to, and many problems yet to solve.</div><div><br></div><div>Again, thanks to all.</div><span class="HOEnZb"><font color="#888888">
<div> Jim</div><div><br></div><div><br></div><div><br></div></font></span></div></div>
<br>_______________________________________________<br>
Bloat mailing list<br>
<a href="mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/bloat" target="_blank">https://lists.bufferbloat.net/listinfo/bloat</a><br>
<br></blockquote></div><br></div></div>