Fred, all, Below is the recommneded text as requested.
-Shahid. ______________________________________________ Manual Tuning Current text section 4: "The algorithms that the IETF recommends SHOULD NOT require operational (especially manual) configuration or tuning." section 4.3: "Algorithms recommended for general Internet deployment by the IETF need to be designed so that they do not require operational (especially manual)configuration or tuning." Recommended text section 4.3: "Algorithms recommended for general Internet deployment by the IETF need to be designed so that they minimize operational (especially manual) configuration or tuning. An AQM considered by IETF SHOULD provide rules which determine its parameters based on a set of well-known initial conditions." section 4: "The algorithms that the IETF recommends SHOULD minimize operational (especially manual) configuration or tuning." Recommend the following text in section 4.7 Research should focus on improving end user QoE from AQMs rather than network related metrics only. Often a significant change in a network metric may only make a minimal change in end-user QoE and thus the value of such change may be minimal. Research should make suggestions on how to make good decisions on buffer sizes with each type of AQM (e.g. 2xBDP) - explaining why or how such buffer sizes improve end-user QoE and network health. Research should be done on methods or good configurations that leverage deployed AQMs such as RED/WRED that reduce delays and prevent lockout with typical traffic and network conditions. ________________________________ From: Fred Baker (fred) [mailto:f...@cisco.com] Sent: Friday, November 08, 2013 10:27 AM To: Akhtar, Shahid (Shahid) Cc: Richard Scheffenegger; aqm@ietf.org; Naeem Khademi (nae...@ifi.uio.no); Gorry Fairhurst; Wesley Eddy Subject: Re: IETF88 Fri 08Nov13 - 12:30 Regency B On Nov 8, 2013, at 5:56 AM, "Akhtar, Shahid (Shahid)" <shahid.akh...@alcatel-lucent.com<mailto:shahid.akh...@alcatel-lucent.com>> wrote: One of the the objectives of newer AQMs being defined here should be to minimize tuning, but we should recognize that likely tuning or some configuration cannot be eliminated altogether. FB: That's an opinion. One of the objectives of Van and Kathy's work, and separately of Rong Pan et al's work, is to design an algorithm that may have different initial conditions drawn from a table given the interface it finds itself on, but requires no manual tuning. The great failure of RED, recommended in RFC 2309, is not that it doesn't work when properly configured; it's that real humans don't have the time to properly tune it differently for each of the thousands of link endpoints in their networks. There is no point in changing away from RED if that is also true of the replacement. SA: You argue that "initial conditions" determine some of the parameters of newer AQMs (like Codel and PIE), then those same initial conditions would also determine some of the key parameters for RED/WRED. I'm simply going to point out that Van and Kathy spent quite a bit of time and effort trying to do exactly that, and it didn't pan out. Codel is their suggestion of a replacement that is largely auto-tuning within a specified range of situations. On your other points, please suggest text, and the WG can discuss whether they buy it.
_______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm
