News for hackers. Stuff that matters.

A comment on Some notes about HTTP/3. Parent comment

Re:Some notes about HTTP/3 by dharmab on Friday November 23, 2018 @01:15PM (#18518026)
>However, in those discussions, a related concern was identified; confusion between QUIC-the-transport-protocol, and QUIC-the-HTTP-binding. I and others have seen a number of folks not closely involved in this work conflating the two, even though they're now separate things.

>

>To address this, I'd like to suggest that -- after coordination with the HTTP WG -- we rename our the HTTP document to "HTTP/3", and using the final ALPN token "h3". Doing so clearly identifies it as another binding of HTTP semantics to the wire protocol -- just as HTTP/2 did -- so people understand its separation from QUIC.

https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0...

TL;DR the rename is to resolve the confusion.

[ Parent | on HN ]
Re:Some notes about HTTP/3 by yy77 on Saturday November 24, 2018 @11:33PM (#18525485)
why not just http/quic? using 3 seems strongly suggest that it is the next generation of http. They knew that but pretend it is not relavent.
[ Parent | on HN ]
Re:Some notes about HTTP/3 by dharmab on Monday November 26, 2018 @01:03PM (#18535394)
Because there's a decent chance that it will be the next generation of HTTP.

If it doesn't pan out they'll just move on. Remember IPv5?

[ Parent | on HN ]
Re:Some notes about HTTP/3 by popee on Friday November 23, 2018 @01:46PM (#18518176)
Aha, thanks for clearing that up
[ Parent | on HN ]