Hi Wes, Just to let you know that we are still working on AQMs that support scalable (L4S) TCPs. We could present some of our latest results (if there will be a meeting in Buenos Aires, otherwise in Berlin?)
* Performance of HTTP Adaptive Video Streaming (HAS) with different TCP's and AQMs o HAS is currently ~30% of Internet traffic, but no AQM testing so far has included it o the results are very poor with a particular popular AQM Presenter: Inton Tsang Duration: 10mins Draft: Comparative testing of draft-ietf-aqm-pie-01, draft-ietf-aqm-fq-codel-04, draft-briscoe-aqm-dualq-coupled For experiment write-up, see Section 3 of https://riteproject.files.wordpress.com/2015/12/rite-deliverable-3-3-public1.pdf * PI^2: PI simplified with a square o PIE embeds some auto-tuning and heuristics, which can be removed by simple transformation of a variable o Allows PIE to control also scalable congestion controls (DCTCP, ...) Presenter: Koen De Schepper Duration: 15mins Draft: (probably impacted) draft-ietf-aqm-pie * DualQ update o extensive additional tests, including different RTTs and mixed RTTs, better visualization o using other AQMs than Curvy-RED for 'Classic' traffic, e.g. PI^2 Presenter: Koen De Schepper Duration: 20min Draft: draft-briscoe-aqm-dualq-coupled-01 Regards, Koen. > -----Original Message----- > From: aqm [mailto:aqm-boun...@ietf.org] On Behalf Of Wesley Eddy > Sent: woensdag 10 februari 2016 20:27 > To: aqm@ietf.org > Subject: [aqm] AQM plans > > Hello AQMers, this is just a quick note to be clear on working group > status and forward planning. > > Currently, all of the active drafts are either in WGLC, or in the > process of shepherd writeups to go the the AD. > > Once we get the current set of drafts out for publication, there are a > few things the WG can do: > - close down > - remain open to continue coordinating and advance algorithms (e.g. > within the standards track) > - remain open as a venue for potential new work (e.g. the DualQ Coupled > AQM) > > I think we should discuss this and plan to make a decision after the > IETF 96 meeting in Berlin (July 17-22). We can have a "closing or > re-chartering" meeting in Berlin if it will benefit from face-to-face > discussion. > > > _______________________________________________ > aqm mailing list > aqm@ietf.org > https://www.ietf.org/mailman/listinfo/aqm _______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm