-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
H3Settings is a bit underspecified #382
Comments
Also we might want to state that the name should be the name IANA use, possiblyeven define a explicit names in addition to free form string. |
Discussed during meeting. |
Another thing I'm wondering is if we should clarify what the i.e., I've previously logged this myself as You could argue this should be obvious, but e.g., in RFC9204, they use the unprefixed version (see https://www.rfc-editor.org/rfc/rfc9204.html#section-8.1) with a note |
Agree 100%, I'll add some text |
https://quicwg.org/qlog/draft-ietf-quic-qlog-h3-events.html#section-5.3.4
Looking at IANA https://www.iana.org/assignments/http3-parameters/http3-parameters.xhtml, I think qlog nudges implementations to log the setting name. When an implementation receives an unknown setting (not a greased one) it won't know the name. It could log the setting type value code in the name field, but that is not specified. This makes things annoying for parsers since they need to do some thinking.
One suggestion is to add another field like
type
that could contain the numerical type value. It would be duplicative to have both, so that might require makingtype
andname
optional.The text was updated successfully, but these errors were encountered: