[Cerowrt-devel] Making AQM harder...
moeller0 at gmx.de
Sat Aug 13 01:52:03 EDT 2016
It looks like I forgot the link to the ms announcement:
On August 13, 2016 12:27:14 AM GMT+02:00, "Dave Täht" <dave at taht.net> wrote:
>On 8/13/16 12:26 AM, dpreed at reed.com wrote:
>> Maybe we all need to buy some Sandvine devices for our homes that
>detect IW10 and forge TCP RSTs? Or maybe Ellacoya will develop one for
>> That's what Comcast did when bufferbloat was killing their gear on
>upload, as I'm sure we all remember. Except the FCC is not going to
>ask me to testify on network management practices, nor is the CRTC or
>Ofcom, and a lame duck commission or a Brexiting UK is not going to
>stop folks from deploying DPI and packet forging technology.
>> So maybe the point of cake is past time. Let chaos reign.
>It is always darkest before the dawn.
>> On Friday, August 12, 2016 9:21am, "moeller0" <moeller0 at gmx.de> said:
>>> Hi List,
>>> according to (which most of you probably know already) MS is jumping
>on the IW10
>>> train, so brace for impact ;) Also windows “exposes” LEDBAT, if
>>> “LEDBAT is only exposed through an undocumented socket option at the
>>> moment” can actually be called exposure…
>>> Also I noticed some discussions of windows 10 update traffic,
>>> monopolizing links with (competent) AQWM/QoS setups, it seems we
>need cake to
>>> fully bake soon ;)
>>> Best Regards
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel at lists.bufferbloat.net
>> Cerowrt-devel mailing list
>> Cerowrt-devel at lists.bufferbloat.net
>Cerowrt-devel mailing list
>Cerowrt-devel at lists.bufferbloat.net
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cerowrt-devel