Re: [Bloat] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi, Dave, strangely it looks like nobody has been copying TSVWG on this thread, even though that is where the L4S work is happening in the IETF!  :) I just wanted to respond to one part of your message since I am currently acting as document shepherd for the L4S drafts in TSVWG, and it seems

Re: [Bloat] Fixing bufferbloat in 2017

On 11/28/2016 10:12 AM, Dave Taht wrote: On Mon, Nov 28, 2016 at 4:48 AM, David Collier-Brown wrote: A short RFC with a clear summary would change the ground on which we stand. Include me in if you're planning one. Call me grumpy. Call me disaffected. But it's been 4 years

Re: [Bloat] some good bloat related stuff on the ICCRG agenda, IETF #86 Tuesday, March 12 2013, 13:00-15:00, room Caribbean 6

On 2/28/2013 10:53 AM, Dave Taht wrote: For those that don't attend ietf meetings in person, there is usually live audio and jabber chat hooked up into the presentations. See y'all there, next month, in one form or another. In the TSVAREA meeting, we've also set aside some time to talk

Re: [Bloat] [Codel] RFC: Realtime Response Under Load (rrul) test specification

On 11/6/2012 8:56 AM, Dave Taht wrote: On Tue, Nov 6, 2012 at 2:42 PM, Henrique de Moraes Holschuh h...@hmh.eng.br wrote: On Tue, 06 Nov 2012, Dave Taht wrote: I have been working on developing a specification for testing networks more effectively for various side effects of bufferbloat,

Re: [Bloat] Random idea in reaction to all the discussion of TCPflavours - timestamps?

On 3/20/2011 9:28 PM, da...@lang.hm wrote: On Mon, 21 Mar 2011, Jonathan Morton wrote: On 21 Mar, 2011, at 12:18 am, da...@lang.hm wrote: 0) Buffering more than 1 second of data is always unacceptable. what about satellite links? my understanding is that the four round trips to geosync