qlog
qlog copied to clipboard
quicwg
The IETF I-D documents for the qlog format
Similarly to the ALPN string issue, we define the `CONNECTION_CLOSE` reason string here as text: https://github.com/quicwg/qlog/blob/57b679678b44d80234a0e10a08e53fe5ef9e7532/draft-ietf-quic-qlog-quic-events.md?plain=1#L313 The problem here is that RFC 9000 only says the reason string SHOULD be...
``` ConnectivityConnectionClosed = { ; which side closed the connection ? owner: Owner ? connection_code: TransportError / CryptoError / uint32 ? application_code: $ApplicationError / uint32 ? internal_code: uint32 ? reason:...
Fixes #370. This better explains the intent behind `is_coalesced` and also adds it to other events that *probably* should have it as well. I'm not sure anymore that this is...
As reported by @hlandau on the mailing list: quic:packet_sent: The meaning of `is_coalesced` should be clarified. I assume this is set to true unless a packet is both the first...
Spinoff/splitoff from #369. @hlandau originally reported for `quic:parameters_set`: I think this event needs more clarify in terms of the distinction between attempting to negotiate a feature and it being enabled....
Currently the `raw` field includes the wire representation of the frame. This doesn't seem useful, and would mean that a qlog consumer would need to implement a frame parser. Instead,...
In H3 [parameters_set](https://quicwg.org/qlog/draft-ietf-quic-qlog-h3-events.html#name-parameters_set) , we have a ``` ; additional settings for grease and extensions * text => uint64 ``` if I grok CDDL correctly, this allows us to have...
Today qlog has packet_sent events and datagrams_sent events, which can be used to log the event and the time it occurred. In some scenarios, the application generating packets or even...
Fixes #192. Currently, `$ProtocolEventData` accepts just about anything, which makes it extensible but very useless for any real validation. By not explicitly assigning the `* text => any` to the...