Re: [quicwg/base-drafts] http: Allow unquoted tokens in Alt-Svc quic parameter (#3063)

[Peter Wu <[e-mail]>]

I think that the problem here is independent from whether structured headers should be applied or not.

- `Alt-Svc: h3=":443"; quic=1; quic=1abadaba` - Structured header issue: duplicate keys.
- `Alt-Svc: h3=":443"; quic=1,1abadaba` - Invalid grammar according to RFC 7838 since "token" does not include commas.
- `Alt-Svc: h3=":443"; quic="1,1abadaba"` - valid grammar according to both RFC 7838 and the QUIC description.

However, if only a single version has to be advertised, then the quoting is not necessary:
- `Alt-Svc: h3=":443"; quic="1"` - valid grammar according to both RFC 7838 and the QUIC description.
- `Alt-Svc: h3=":443"; quic=1` - valid grammar according to both RFC 7838, but QUIC currently forbids it.

In #3059 I proposed to fix the grammar (editorial issue). However, at the same time I could also make the grammar match RFC 7838 (the last bullet point above).

@DavidSchinazi I would mind not making the semantics more restrictive (e.g. restricting the values of the QUIC parameter to hexadecimal only), but restricting the parser grammar would impose extra restrictions on those who have to generate the header. It is conceivable that implementations will continue accepting the RFC 7838 grammar, and end up accepting `quic=1` while others would reject it and accept `quic="1"` only. By making sure that the grammars align, I hope that this becomes a non-issue.

So far @mikkelfj, @tatsuhiro-t and @bagder seems to support this proposal and @DavidSchinazi is not sure. Can this be considered consensus? :smiley:

-- 
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/issues/3063#issuecomment-536314485