slowstart

8 ms·

1.
by slowstart 5mo ago
Hi Peter, are you seeing longer wait times for N-400 and citizenship processing? Can one travel out of the country for a few weeks while the application is pending or will this impact the residency requirements?
2.
by slowstart 5y ago
You may be interested in this: https://techcommunity.microsoft.com/t5/networking-blog/makin... . The gist is that yes QUIC has higher CPU usage but all OS platforms are investing in UDP hardware offloads and optimi
3.
by slowstart 5y ago
Our QUIC implementation MsQuic can run in both kernel and user mode on Windows. A PAL allows the core protocol logic to be agnostic.
4.
by slowstart 5y ago
Thanks for the heads up. We will investigate to see what fraction of connections end up losing these options. Pacing TCP is certainly on our roadmap. Our QUIC implementation MsQuic paces by default already.
5.
by slowstart 5y ago
Windows historically defaulted to accepting timestamps when negotiated by the peer but didn't initiate the negotiation. There are benefits to timestamps and one downside (12 bytes overhead per packet). Re. syncookies, that's an in
6.
by slowstart 5y ago
That's not expected. Are you using loopback sockets or are these sockets on different endpoints? Is this unidirectional or bidirectional traffic, i.e. are you doing both transfers from A to B and B to A simultaneously?
7.
by slowstart 5y ago
I cannot comment on queuing disciplines and limits in future products. Re. TCP_NOTSENT_LOWAT, you may want to look at the Ideal Send Backlog API that allows an application to have just more than BDP queued to keep the performance at the max
8.
by slowstart 5y ago
It's called R(ecent) Acknowledgement and yes the work came out of Google. This is the single biggest change to TCP loss recovery in a decade. It is now a Standards Track RFC: https://datatracker.ietf.org/doc/html&#
9.
by slowstart 5y ago
You should look into the RSS configuration. https://docs.microsoft.com/en-us/windows-hardware/drivers/ne... and https://docs.microsoft.com/en-us/windows-server/networking/t...
10.
by slowstart 5y ago
You are spot on. PktMon is the next generation tool in newer Windows 10 versions and brings many of the same benefits referred to in this blog - particularly being able to view packet captures and traces together in the same text file. And
11.
by slowstart 5y ago
PktMon is the next generation tool in newer Windows 10 versions and brings many of the same benefits referred to in this blog - particularly being able to view packet captures and traces together in the same text file.
12.
by slowstart 5y ago
I lead the Windows TCP team. We blogged about recent TCP advancements which is very relevant: https://techcommunity.microsoft.com/t5/networking-blog/algor...
13.
Alpha Support for Envoy on Windows (Envoyproxy.io)(blog.envoyproxy.io)
2 points by slowstart 6y ago|0 comments
14.
by slowstart 6y ago
We are currently testing HTTP/3 support in IIS/http.sys internally. Cannot comment on any external product release timelines.
15.
by slowstart 6y ago
Connection migration is part of the current Internet-Drafts. The generalized support for multi-path (i.e. usage of more than one path at the same time) is postponed to a future version of the protocol. You can follow the standards work here
16.
by slowstart 6y ago
We do extensive testing including stress testing and make use of tooling that can catch bugs early. We also partner with internal security teams to do fuzz testing and security reviews for all networking code. That said, none of the network
17.
by slowstart 6y ago
There is currently no standardization for QUIC APIs. You can check out the MsQuic API here: https://github.com/microsoft/msquic/blob/master/docs/API.md
18.
by slowstart 6y ago
Since this had to run in kernel mode on Windows to power our HTTP stack, C was the language of choice. There exist other open source implementations of QUIC in C++ and Rust etc.
19.
by slowstart 6y ago
RPC/gRPC are certainly possible use cases for the QUIC transport protocol. But no, we have not yet explored the use of QUIC in this context. For now we are focused on workloads that will benefit the most from the tail latency performan
20.
by slowstart 6y ago
Please fire away any questions you may have! I lead the team that built this library. This blog has details on current development status and adoption within Microsoft: https://techcommunity.microsoft.com/t5/networking-