Microsoft reveals it’s rolled its own QUIC and is testing it on Microsoft 365 and in .NET Core 5.0
(2020/05/04)
- Reference: 1588568762
- News link: https://www.theregister.co.uk/2020/05/04/microsoft_reveals_msquic_quic_implementation/
- Source link:
Microsoft’s [1]revealed it’s a user of QUIC – the TCP successor that’s integral to HTTP3 but hasn’t quite excited too many folk beyond Google and Cloudflare.
QUIC – an acronym for Quick UDP Internet Connections – is a [2]Google emission from 2013 that aims to help the internet scale and speed up by offering an alternative to TCP’s chatty and OS-dependent ways. Google and Cloudflare, who both have an interest in faster and more elegant internetworking, eased QUIC into an IETF standards process and the protocol has become a part of HTTP/3.
While [3]QUIC has made it into Chrome observers like W 3 Techs [4]detect just three or four percent of web sites using the protocol.
Which is why Microsoft putting its hand up as a user, advocate and source of code with which to implement QUIC caught your vulture’s eye!
True to form, Microsoft has cooked up its own QUIC and changed the typography by calling it [5]MsQuic . The company’s post revealed its using MsQuic as follows:
Windows will ship with MsQuic in the kernel to support various inbox features. The Windows HTTP/3 stack is being built on top of MsQuic.
Microsoft 365 is testing a preview version of IIS using HTTP/3 to reduce tail loss latencies in the last mile. This is currently active in internal dogfood environments.
.NET Core has built HTTP/3 support into Kestrel and HttpClient on top of MsQuic. HTTP/3 support is in experimental preview for the 5.0 release of .NET Core.
SMB in Windows is also prototyping MsQuic usage. QUIC brings several benefits for SMB, such as better internet reachability, a secured connection based on industry standard TLS and server authentication with certificate validation. Best of all, this brings a completely different workload on top of MsQuic, strengthening the general-purpose nature of the transport.
The post also tells us a little about why Microsoft is playing with QUIC:
“MsQuic brings performance and security improvements to many important networking scenarios. Our online services benefit the most from performance improvements like reduced tail latency and faster connection setup. Our connections will be able to seamlessly switch networks because they can survive IP address/port changes. This equates to better user experience on our edge devices.”
QUIC is still on the [6]IETF’s standards track . Microsoft says MsQuic shares QUICs status as “ready for prototyping and testing” and has promised a deeper dive into its implementation of the protocol soon. ®
Sponsored: [7]Forrester Build a Digital Experience Portfolio
[1] https://techcommunity.microsoft.com/t5/networking-blog/msquic-is-open-source/ba-p/1345441
[2] https://www.theregister.co.uk/2013/07/10/http_20_ietf_draft_lands/
[3] https://www.theregister.co.uk/2019/09/26/quic_head_to_the_latest_chrome_version_and_try_out_http3/
[4] https://w3techs.com/technologies/details/ce-quic
[5] https://github.com/microsoft/msquic
[6] https://tools.ietf.org/html/draft-ietf-quic-transport-27
[7] https://go.theregister.co.uk/tl/1936/-8554/forrester-build-a-digital-experience-portfolio?td=wptl1936
QUIC – an acronym for Quick UDP Internet Connections – is a [2]Google emission from 2013 that aims to help the internet scale and speed up by offering an alternative to TCP’s chatty and OS-dependent ways. Google and Cloudflare, who both have an interest in faster and more elegant internetworking, eased QUIC into an IETF standards process and the protocol has become a part of HTTP/3.
While [3]QUIC has made it into Chrome observers like W 3 Techs [4]detect just three or four percent of web sites using the protocol.
Which is why Microsoft putting its hand up as a user, advocate and source of code with which to implement QUIC caught your vulture’s eye!
True to form, Microsoft has cooked up its own QUIC and changed the typography by calling it [5]MsQuic . The company’s post revealed its using MsQuic as follows:
Windows will ship with MsQuic in the kernel to support various inbox features. The Windows HTTP/3 stack is being built on top of MsQuic.
Microsoft 365 is testing a preview version of IIS using HTTP/3 to reduce tail loss latencies in the last mile. This is currently active in internal dogfood environments.
.NET Core has built HTTP/3 support into Kestrel and HttpClient on top of MsQuic. HTTP/3 support is in experimental preview for the 5.0 release of .NET Core.
SMB in Windows is also prototyping MsQuic usage. QUIC brings several benefits for SMB, such as better internet reachability, a secured connection based on industry standard TLS and server authentication with certificate validation. Best of all, this brings a completely different workload on top of MsQuic, strengthening the general-purpose nature of the transport.
The post also tells us a little about why Microsoft is playing with QUIC:
“MsQuic brings performance and security improvements to many important networking scenarios. Our online services benefit the most from performance improvements like reduced tail latency and faster connection setup. Our connections will be able to seamlessly switch networks because they can survive IP address/port changes. This equates to better user experience on our edge devices.”
QUIC is still on the [6]IETF’s standards track . Microsoft says MsQuic shares QUICs status as “ready for prototyping and testing” and has promised a deeper dive into its implementation of the protocol soon. ®
Sponsored: [7]Forrester Build a Digital Experience Portfolio
[1] https://techcommunity.microsoft.com/t5/networking-blog/msquic-is-open-source/ba-p/1345441
[2] https://www.theregister.co.uk/2013/07/10/http_20_ietf_draft_lands/
[3] https://www.theregister.co.uk/2019/09/26/quic_head_to_the_latest_chrome_version_and_try_out_http3/
[4] https://w3techs.com/technologies/details/ce-quic
[5] https://github.com/microsoft/msquic
[6] https://tools.ietf.org/html/draft-ietf-quic-transport-27
[7] https://go.theregister.co.uk/tl/1936/-8554/forrester-build-a-digital-experience-portfolio?td=wptl1936