# Get ready for HTTP/3 (well, TCP 3?)

**URL:** <https://forum.kirupa.com/t/get-ready-for-http-3-well-tcp-3/638993>\
**Category:** Uncategorized\
**Created:** [November 24, 2018, 8:08pm UTC](https://forum.kirupa.com/t/get-ready-for-http-3-well-tcp-3/638993 "2018-11-24T20:08:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirupa](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/kirupa/32/11616_2.png) [@kirupa](https://forum.kirupa.com/u/kirupa)\
**Post date:** [November 24, 2018, 8:08pm UTC](https://forum.kirupa.com/t/get-ready-for-http-3-well-tcp-3/638993/1 "2018-11-24T20:08:36Z")

</div>

Overview:

> **[QUIC](https://en.wikipedia.org/wiki/QUIC)**
>
> QUIC is an experimental transport layer network protocol initially designed, implemented, and deployed by Google in 2012, and announced publicly in 2013 as experimentation broadened.
> QUIC's main goal is to improve perceived performance of connection-oriented web applications that are currently using TCP. It does this by establishing a number of multiplexed connections between two endpoints over User Datagram Protocol (UDP). This works hand-in-hand with HTTP/2's multiplexed connections, allowing...

Additional details: [https://blog.erratasec.com/2018/11/some-notes-about-http3.html](https://blog.erratasec.com/2018/11/some-notes-about-http3.html)

Just when we were all getting used to HTTP/2, there is something better that we’ve all been using already as part of using Chrome. It’s about to get a whole lot more mainstream. Gotta love the smell of new protocols ☕

Cheers,  
Kirupa