You may have seen the announcements over the past two weeks -- the IETF QUIC RFCs  have been published ! That leads to a lot of questions, depending on how closely you've followed this space. You might be wondering what this means to you, or you might think QUIC has been an established thing for years now. And how does HTTP/3 fit into this? Is HTTP/3 another name for QUIC? \r\n QUIC is a new transport for the internet. The use of QUIC enables deployment of years of research developments at once, improves privacy, and offers substantially better performance in challenging network conditions.  HTTP/3 is the mapping of HTTP which uses IETF QUIC as a transport. \r\n I'm the editor of HTTP/3 and an active contributor to the IETF QUIC specs. In this post, I'm going to take a look at where IETF QUIC came from, how far it has progressed, and what's left to do. \r\n Origins of QUIC \r\n The IETF  published  TCP four decades ago.…