The not-so-nice part about the newer HTTP versions is that they are not really layered in the classical sense. This means HTTP/1, HTTP/2 and HTTP over QUIC all carry the same semantics (you got methods, addresses, headers, and body streams), but implementation of HTTP itself is different and it's not only a substitution of the underlying transport layer: E.g. in HTTP/2 there's no classical HTTP data transferred over a multiplexed stream (like what HTTP over SCTP could have brought us). Instead it carries HTTP aspects (headers), multiplexing and flow control all in a single layer which makes layering and generic reuse hard.
Have not looked into that QUIC mapping yet, but I have read that generic use is a goal for it, which is good. If HTTP over QUIC succeeds (it probably will if pushed by google) I'm wondering how of how much use HTTP/2 still will be. Classical HTTP will most likely always exist as it's easy to implement and is covered by lots of systems (even embedded) and libraries.
Have not looked into that QUIC mapping yet, but I have read that generic use is a goal for it, which is good. If HTTP over QUIC succeeds (it probably will if pushed by google) I'm wondering how of how much use HTTP/2 still will be. Classical HTTP will most likely always exist as it's easy to implement and is covered by lots of systems (even embedded) and libraries.