qlog
qlog copied to clipboard
quicwg
The IETF I-D documents for the qlog format
I am wondering if the new H3PriorityUpdated event (see #312) needs some specified `trigger` field values. Conceptually, you can get the necessary context from other events surrounding this event (e.g.,...
This would be interesting for Version Negotiation, Retry, CONNECTION_CLOSE etc. sent by a server.
Fixes #375. Per the discussion, it can be useful to know when an application triggers a stream close, or when it receives one, without having to do offset/length maths. I...
`ECNState` currently has 4 different options. During IETF 118, it was mentioned by @mirjak that the `capable` option is potentially not fine-grained enough. I don't know enough about ECN/L4S to...
https://quicwg.org/qlog/draft-ietf-quic-qlog-h3-events.html#section-5.3.4 ``` H3Setting = { name: text value: uint64 } ``` 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...
As reported by @hlandau on the mailing list: quic:stream_data_moved: A brief explanation of each from/to value here and the intended meaning would be a big improvement. Also clarify that raw...
As reported by @hlandau on the mailing list: quic:stream_state_updated: I think this needs to be clarified a little that an event logged here with both a `stream_id` field and a...
This first sentence is not precise about whether it refers to the logging use case or the use case of the logged exchange. _Originally posted by @martinthomson in https://github.com/quicwg/qlog/pull/353#discussion_r1410158849_