Skip to main content
  • Towards a net zero IETF

    Introducing a new project to measure and potentially offset IETF carbon emissions so that the IETF could potentially reach the level of a net zero emitter.

    • Jay DaleyIETF Executive Director
    6 May 2022
  • IETF 113 post-meeting survey

    The results from our IETF 113 post-meeting survey are now available on a web-based interactive dashboard. This commentary highlights where changes we have made based on feedback have been a success, and areas we still need to work on.

    • Jay DaleyIETF Executive Director
    2 May 2022
  • IETF 113 Hackathon – Back in person!

    The IETF 113 Hackathon held 19-20 March 2022 in Vienna and online marked the return to in-person collaboration on running code related to Internet standards.

    • Charles EckelIETF Hackathon Co-chair
    19 Apr 2022
  • IETF Datatracker updates and service outages planned

    Two updates in the coming weeks will significantly revise the look of the IETF Datatracker and, after a short outage on 25 April 2022, upgrade the hardware for most IETF services.

    • Robert SparksIETF Tools Project Manager
    13 Apr 2022
  • New Independent Submissions Editor looks for interoperability, continuous improvement

    Eliot Lear, a long-time Internet Engineering Task Force participant and engineer for Cisco Systems, was recently appointed independent submissions editor by the Internet Architecture Board (IAB).

    • Grant GrossIETF Blog Reporter
    31 Mar 2022

Filter by topic and date

Filter by topic and date

QUIC in the Internet industry

    3 Jun 2021

    QUIC, a new Internet transport technology that improves web application performance, security and privacy, was reviewed, redesigned and improved in the IETF, incorporating a broad range of input from across the industry.

    (Also read more about QUIC and how it fits into the range of Internet transport technology innovation underway.)

    Facebook

    "Over 75% of Facebook's traffic is now using QUIC. We're excited to be able to deploy this technology at scale, bringing the performance and reliability improvements of QUIC to the billions of people who use our products everyday. QUIC and the work done by the IETF enable us to move fast and continuously innovate at the network layer in ways which were never possible with TCP."

    Akamai

    "QUIC is already improving the user experience and the efficiency of the Internet, and improving it more for the most challenging connections. But the real value remains to be seen. An encrypted transport means that new technology can be tested and deployed rapidly, just by updating your browser. QUIC isn't just today's great idea -- it's what will make tomorrow's great idea possible."

    • Mike Bishop, Principal Architect, Akamai

    Microsoft

    "Microsoft is an active participant and driver of QUIC in the industry as well as the IETF and has open sourced its implementation. MsQuic brings performance and security improvements to many important networking scenarios particularly reduced tail latency and fast secure connection setup for our online services. Microsoft is committed to deploying HTTP/3 and QUIC at scale and fostering innovation in Internet protocols to deliver secure, reliable, and performant connectivity experiences for our users."

    • Krishna Ganugapati, VP Engineering, Microsoft

    Cloudflare

    "QUIC is a major advancement in transport protocols. Cloudflare believes strongly that its security and mobility features give it the potential to become the dominant transfer protocol on the Internet. For this reason, we deployed QUIC and HTTP/3 early and made it available for all. We have invested our learnings back into the IETF standards and our open source implementation — quiche — to help build a better Internet."

    • John Graham-Cumming, Chief Technology Officer of Cloudflare

    Ericsson

    “We are excited to see the QUIC specification published by the IETF. The development of QUIC has been a prominent example of rapid innovation and evolution in the area of Internet transport protocols. More importantly, QUIC sets the base that will enable and facilitate future innovation and evolution. When it comes to deployments QUIC already represents a large share of the traffic carried by mobile networks Ericsson has built, and we expect that share to still grow significantly in the future. At Ericsson, we believe in the network as a platform where applications and the network itself work together to provide the best performance for the end user. We are particularly happy that QUIC also provides features designed to assist in the performance analysis process in the network."

    F5

    “F5 is privileged to have had the opportunity to contribute to the significant work at the IETF to establish HTTP/3 as the new web standard. Our BIG-IP and NGINX customers will benefit from the performance and security improvements of this new protocol, and we are poised to offer additional support as future enhancements are rolled out.”

    Fastly

    "Fastly has been invested in helping make QUIC a success from its early days, and its ratification is a major milestone for the Internet ecosystem. QUIC and HTTP/3 are available on our network and improve the experience of our customers and their users around the globe, especially those with a less-than-reliable Internet connection. We believe the real potential of QUIC is in accelerating an entirely new generation of Internet innovation. Fastly is already extending and building on QUIC to solve novel infrastructure and technology problems, and we are excited to continue contributing to this space in our mission to build a faster, more resilient, more trusted Internet."

    Google

    “QUIC began as a small experiment at Google in 2013 and now carries the majority of Google’s traffic. The IETF process resulted in a dramatically different protocol with better functionality, performance, and security. The clean separation between QUIC transport and HTTP/3 sets the stage for decades of transport and application innovation.  Due to the improved latency, HTTP/3 was default enabled for all Google sites and in Chrome in November 2020. We look forward to the continued growth of HTTP/3 as others default enable it as well.”

    • Ian Swett, Web Performance Lead, Google

    Share this page