3 ms·
Seems to me there is a difference between "we're gonna propose that naming" and "will most likely be"? That said, it doesn't seem like a good idea to me, since
by detaro 8y ago
Seems to me there is a difference between "we're gonna propose that naming" and "will most likely be"?
That said, it doesn't seem like a good idea to me, since it's less of a clear protocol evolution. A variation of the http/2 name would IMHO make more sense, e.g. http/2q or something, since it's not changing the HTTP semantics.
- bpicolo 8y agoTo be fair, helps that this is coming from the chair of the IETF HTTP working group
- gsnedders 8y ago> A variation of the http/2 name would IMHO make more sense, e.g. http/2q or something, since it's not changing the HTTP semantics. HTTP/2 didn't change semantics, either. We literally only have one version of HTTP semantics, and a variety of transports for it.
- h1d 8y agoPlease keep it with simple numbers, we don't want to go the wifi route of a/b/g/n/ac where you can't tell what is more modern which they fixed.
- Matthias247 8y ago> A variation of the http/2 name would IMHO make more sense Why? The core of HTTP/2 is defining how individual HTTP streams get multiplexed across a single TCP connection. That part is not applicable to QUIC over HTTP. There HTTP streams get mapped on top of QUIC streams. Some things might be similar between HTTP/2 and HTTP/QUIC mappings, but in the end they are separate definitions. The both define how HTTP semantics are carried over a different lower layer mechanism. So HTTP/3 or HTTP/QUIC seem reasonable.