Re: [quicwg/base-drafts] encoding of CONNECTION_CLOSE reason phrases (#1990)

[Kazuho Oku <[e-mail]>]

> Is there any reason not to require this to be UTF-8 though? I think it would help debugging interoperability testing (and error logging) if you can rely on the charset.

If we say "MUST be UTF-8", then the natural outcome would be that people would expect QUIC stacks to validate if the reason phase contains a valid UTF-8 string. I do not think we should have such a requirement.

Current text saying "SHOULD be UTF-8" is fine in this respect because QUIC stacks can simply emit the binary octets that it has received to the application.

Note that most (if not all) of HTTP logging does not deal with charsets; for example a URL can contain any charset, and they are logged as bytes.

-- 
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/1990#issuecomment-437779182