They overlap significantly, and some of it is by accident and some is by design. Most of this resulted from convergent evolution by some of the same authors; HT

They overlap significantly, and some of it is by accident and some is by design. Most of this resulted from convergent evolution by some of the same authors; HTTP/2's transport innovations over HTTP/1.1 were largely lifted from SPDY by Google. QUIC is a more holistic view of the transport techniques to achieve some of the same design goals of SPDY, so the ultimate vision is HTTP/2-over-QUIC, and this is being reconciled [1]. In earlier versions of QUIC, it even included a homebrew transport encryption protocol [2], but this has since been downplayed in favor of TLS 1.3. [1] https://datatracker.ietf.org/doc/draft-ietf-quic-http/ https://datatracker.ietf.org/doc/draft-ietf-quic-http/ [2] https://www.ietf.org/proceedings/92/slides/slides-92-saag-5.pdf https://www.ietf.org/proceedings/92/slides/slides-92-saag-5....