From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave@taht.net>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Making AQM harder...
Date: Sat, 13 Aug 2016 07:52:03 +0200 [thread overview]
Message-ID: <DE6F4A47-EA8F-4684-BEC7-4C68C27FBC2E@gmx.de> (raw)
In-Reply-To: <5efaf086-bdd1-040e-8b03-3681ff51dbe7@taht.net>
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
Dear all,
It looks like I forgot the link to the ms announcement:
https://blogs.technet.microsoft.com/networking/2016/07/18/announcing-new-transport-advancements-in-the-anniversary-update-for-windows-10-and-windows-server-2016/
On August 13, 2016 12:27:14 AM GMT+02:00, "Dave Täht" <dave@taht.net> wrote:
>
>
>On 8/13/16 12:26 AM, dpreed@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
>consumers?
>>
>> 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@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,
>effectively
>>> monopolizing links with (competent) AQWM/QoS setups, it seems we
>need cake to
>>> fully bake soon ;)
>>>
>>>
>>> Best Regards
>>> Sebastian
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 3247 bytes --]
prev parent reply other threads:[~2016-08-13 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 13:21 moeller0
2016-08-12 22:26 ` dpreed
2016-08-12 22:27 ` Dave Täht
2016-08-13 5:52 ` Sebastian Moeller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DE6F4A47-EA8F-4684-BEC7-4C68C27FBC2E@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox