HTTP-over-QUIC will officially become HTTP/3
The vendor history of network and transport protocols can be 
seen as invisible to end user market warfare. Those who are able to push their network based ideas to better address the way they want to do things (and shape the market) win.<p>Way back this was IPX/SPX vs IP/(TCP|UDP). We know who won that and what happened to the loser.<p>There is another aspect to this: agnostic network and 'good enough' conceptions have been historically adopted by engineering organizations to remove vendor disposition from the end user landscape and protect the end user. On this forum a lot of these historical protections are seen as passe or unimportant for reasons best not scrutinized too closely.<p>IMO, the idea embodied in encapsulation of application protocol traffic in stateless transport to avoid a vendors technical issues with existing application stream orientation|transport in the non-vendor real world is one of the ugliest ideas I've yet encountered.<p>There are a lot of good ideas floating around in the comments here that avoid vendor lock in for applications
stream based transport that already exist.