Re: [quicwg/base-drafts] Use quic= instead of v= (#235)

[Lucas Pardue <[e-mail]>]

LPardue commented on this pull request.



> -QUIC versions are four-octet sequences with no additional constraints on format.
-Versions containing octets not allowed in tokens (tchar, {{!RFC7230}}, Section
-3.2.6) MUST be encoded using the hexadecimal representation.  Versions
-containing only octets allowed in tokens MAY be encoded using either
-representation.
-
-On receipt of an Alt-Svc header indicating QUIC support, a client MAY attempt to
-establish a QUIC connection on the indicated port and, if successful, send HTTP
-requests using the mapping described in this document. Servers SHOULD list only
-versions which they support, but MAY omit supported versions for any reason.
-
-Connectivity problems (e.g. firewall blocking UDP) may result in QUIC connection
-establishment failure, in which case the client should gracefully fall back to
-HTTP/2.
+Origins SHOULD list only versions which they support, but MAY omit supported
+versions for any reason.

In the host-neutral case the origin is listing versions for the HTTP/QUIC endpoint. I don't think there is a requirement for the advertising host to support any version of QUIC, right?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/235#pullrequestreview-19428017