Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MsQuic – QUIC Implementation from Microsoft

github.com

Post reply on HN
Print view View original

21–30 of 87 posts

Re: MsQuic – QUIC Implementation from Microsoft

#25

Post by zvrba »

slowstart wrote: post #4

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-blog/msqui...

I know it's not your team, but now that it's going in Windows kernel, maybe you could ask around... Any plans to support QUIC for data transfers from/to Azure Blob Storage?

Re: MsQuic – QUIC Implementation from Microsoft

#26

Post by davidfowl »

gravypod wrote: post #6
slowstart wrote: post #4

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-blog/msqui...

Sorry, this might be a bit off topic but it's something I've been excited about for a while. From what I've heard Microsoft is sort of getting behind gRPC. Have you tested using QUIC as a transport layer for the gRPC client/server libraries that MS maintains? Are you seeing notable performance benefits with QUIC as the underlying channel?

I'm from the .NET Core team and we've looked at it a little from the HTTP/3 angle but not from a pure QUIC angle. This is because the gRPC RPC protocol is described in terms of HTTP/2 frames today.

Re: MsQuic – QUIC Implementation from Microsoft

#27

Post by sansnomme »

slowstart wrote: post #18
saagarjha wrote: post #14

Earlier quoted context omitted.

Since this is going in the kernel and is exposed to the network, what kinds of things are you doing to prevent security or reliability bugs due to undefined behavior? Love the username, by the way :)

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 networking stacks deployed widely today are completely immune to security vulnerabilities. Responsible disclosure also plays an important role.

Any plans to integrate or collaborate with Project Everest?

Re: MsQuic – QUIC Implementation from Microsoft

#29

Post by fulafel »

slowstart wrote: post #4

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-blog/msqui...

Does QUIC or your implementation of it support application control of keying or is it always based on x.509 certs and CAs?

edit: the spec (https://tools.ietf.org/html/draft-ietf-quic-tls-27) seems agnostic on this. Also simple APIs especially in security are important, so supporting certs only is no flaw in my book, just curious about the edges of how the OS QUIC could be used in the future.

Re: MsQuic – QUIC Implementation from Microsoft

#30

Post by cosmie »

battery_cowboy wrote: post #12
vorpalhex wrote: post #8

Earlier quoted context omitted.

Even during the evil days Microsoft occasionally produced great software like Microsoft Money. Like any large corporation, MS is not a single cohesive entity and I suspect the Win10 group pushing metrics and Cortana is not the same folks writing nifty quic implementations.

Exactly! I loved Microsoft money, BTW, I wish it was still a thing.

While not quite the same, they're releasing an Excel feature/template called "Money in Excel" soon[1], that uses a Plaid integration to pull live financial data into Excel to work with.

[1] https://support.office.com/en-us/article/what-is-money-in-ex...

Post reply on HN