[ad_1]
Microsoft revealed that it is a user of QUIC, the successor to TCP that is an integral part of HTTP3 but has not excited many people beyond Google and Cloudflare.
QUIC, an acronym for Quick UDP Internet Connections, is a 2013 Google broadcast that aims to help the Internet scale and accelerate by offering an alternative to the talking and dependent forms of the TCP operating system. Google and Cloudflare, both interested in faster and more elegant network interconnection, facilitated QUIC in an IETF standards process and the protocol has become part of HTTP / 3.
While QUIC has turned it into Chrome watchers like W3Technicians detect only three to four percent of the websites that use the protocol.
That is why Microsoft put its hand as a user, defender and source of code with which to implement QUIC caught the attention of its vulture!
True to form, Microsoft has prepared its own QUIC and has changed the font by calling it MsQuic. The company’s post revealed that it uses 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 preliminary version of IIS using HTTP / 3 to reduce queue loss latencies in the last mile. He is currently active in internal dog food environments.
- .NET Core has incorporated HTTP / 3 support in Kestrel and HttpClient in addition to MsQuic. HTTP / 3 support is in experimental preview for .NET Core version 5.0.
- SMB on Windows is also prototyping using MsQuic. QUIC offers several benefits for SMBs, such as better Internet accessibility, an industry standard TLS-based secure connection, and server authentication with certificate validation. Best of all, this brings a completely different workload to MsQuic, strengthening the general-purpose nature of transportation.
The post also tells us a bit about why Microsoft is messing with QUIC:
QUIC is still on the IETF standards track. Microsoft says MsQuic shares QUIC status as “ready for prototyping and testing” and has promised a deeper dive into its protocol implementation soon. ®
Sponsored:
How to accelerate brilliant low-code digital experiences
