QUIC implementation #2379

🚀 Feature Proposal

Implementation of QUIC https://tools.ietf.org/html/draft-ietf-quic-transport-27

RFC: https://datatracker.ietf.org/doc/rfc9000/

More related RFCs:

• https://datatracker.ietf.org/doc/rfc8999/
• https://datatracker.ietf.org/doc/rfc9001/
• https://datatracker.ietf.org/doc/rfc9002/

About QUIC:

• https://dl.acm.org/doi/abs/10.1145/3098822.3098842
• https://blog.cloudflare.com/the-road-to-quic/
• https://blog.cloudflare.com/http3-the-past-present-and-future/
• https://www.researchgate.net/publication/318801580_QUIC_Better_for_what_and_for_whom

This shall pave way for implementation of HTTP/3 since HTTP over QUIC is proposed to be called HTTP/3. QUIC will likely be used for transporting more than just HTTP.

Motivation

• The web is gaining a new protocol for communication (HTTP/3)
• Nodejs recently merged QUIC initial implementation with master branch. Landed in nodejs/node master nodejs/quic#390
  -- Implementation was removed: quic: remove experimental quic nodejs/node#37067
• QUIC shall be essential for implementation of HTTP/3 and node is working hard on this: QUIC support nodejs/node#23064
  One should read this discussion, it's really interesting

Misc

• New tracking issue: HTTP/3 support nodejs/node#38478

QUIC will likely be used for transporting more than just HTTP.

This turned out to be true. Checkout WebTransport: https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/

Example

N/A