Skip to main content
  • Suggested IETF 114 Sessions for Getting Familiar with New Topics

    This list of sessions at the IETF 114 meeting are likely to include discussions and new proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

      19 Jul 2022
    • The value of in-person collaboration

      As the world slowly recovers from COVID-19, in-person meetings at IETF and other organizations are coming back.

      • Grant GrossIETF Blog Reporter
      15 Jul 2022
    • A New Model for the RFC Editor Function

      The new RFC Editor Model is intended to provide greater transparency, improved responsiveness to the needs of the community, and increased clarity regarding the roles and responsibilities of the groups and individuals involved.

      • Peter Saint-Andre
      30 Jun 2022
    • IETF updates HTTP specifications, publishes HTTP/3

      The IETF has been busy working on updates to the specifications that make up HTTP, one of the most widely used protocols on the Internet, and documenting them in several RFCs published this month.

      • Grant GrossIETF Blog Reporter
      24 Jun 2022
    • Finalizing the IETF tools transition

      The final stage of transitioning services from tools.ietf.org will take place over the next few weeks. New services are in place, and some older services will disappear. Several measures are planned to ensure these final steps proceed smoothly.

      • Robert SparksIETF Tools Project Manager
      17 Jun 2022

    Filter by topic and date

    Filter by topic and date

    Innovative New Technology for Sending Data Over the Internet Published as Open Standard

      3 Jun 2021

      Already broadly deployed and used, QUIC provides lower delay, improved security, and more robust delivery of data.

      QUIC badge

      June 3, 2021 — A new Internet transport technology that improves web application performance, security, and privacy has been published as a standard by the Internet Engineering Task Force (IETF).

      Already used by a range of Internet services, an initial version of QUIC was designed and tested by Google and then proposed to IETF for standardization. Over the past 5 years it was reviewed, redesigned and improved in the IETF, incorporating a broad range of input from across the industry. QUIC is an important example of a range of innovation in core Internet technologies underway in the IETF. While QUIC is a general transport protocol, the IETF will also soon release HTTP/3, the first application protocol designed for use over QUIC.

      “While widely-known IETF standards such as TCP have served the Internet’s growth and evolution for decades, technologies like QUIC are more extensible to enable future innovation,” said IETF Transport Area Director Martin Duke. “Beyond QUIC, IETF participants have been exploring a broad range of ideas in Internet technologies, such as the next version of Web Transport, HTTP/3, the Low Latency, Low Loss, Scalable Throughput (L4S) service architecture, and Delay Tolerant Networking (DTN).”

      QUIC provides a new building block that can improve application performance by reducing latency and enabling the multiple data streams needed by many modern Web services and other applications. QUIC applies encryption at the transport layer, instead of above it, substantially improving its privacy and security properties.

      An important part of ensuring the rapid deployment of QUIC has been parallel development and testing of running code as it was developed. IETF Hackathons have helped implementers find problems and improve the standard before its final publication. While “running code” has long been a core principle of the IETF, it has been increasingly important in recent IETF standards development efforts like QUIC.

      “I think the hackathons were great,” said Nick Banks, a QUIC developer from Microsoft. “They encouraged implementations to make measured progress towards a common goal. This, in turn, led to a number of spec bugs being found and fixed early on in the process. I have no doubt that the whole standardization process would have taken longer without those interops.”

      The QUIC Working Group continues its work by improving the protocol’s manageability and deployability. Other working groups are expanding QUIC to new use cases and building APIs to make it easier for applications to use.

      More information about a broad range of work on new Internet transport protocols is available in a recent post by the IETF Transport Area Directors on the IETF Blog.


      Share this page