qlog
qlog copied to clipboard
quicwg
The IETF I-D documents for the qlog format
As requested by Damien Neil on the QUIC wg mailing list on November 9, this adds an option to log the raw ack_delay value seen in the AckFrame, as opposed...
The DATA frame section includes some commentary on H3, frames and streams. In reviewing a PR, I made the following observations: > This seems like it can be genericised and...
We've had the following todo's for `loss_timer_updated` in the quic schema for a while, pulling them out into this issue 1. TODO: how about CC algo's that use multiple timers?...
Most of what was in here is good but we can tighten it up a bit. After tightening up, it makes it easier to introduce another TimeFormat - monotonic -...
We presently have 3 documents: main schema, quic schema, HTTP/3 and QPACK schema. We presently have 1 version field `qlog_version` to express changes in any of these documents. We make...
It is expected that the initial 3 qlog documents will be extended in the future with new events and frames (e.g., for QUIC and H3 extensions like DATAGRAM or Multipath,...
e.g. max_datagram_frame_size and grease_quic_bit
In https://quicwg.org/qlog/draft-ietf-quic-qlog-main-schema.html#section-8.2-5 we say: Any generic key-value map type can be assigned to $ProtocolEventData (the only common "data" subfield defined in this document is the optional trigger field, see [Section...
I'm still a bit confused by triggers, hence opening https://github.com/quicwg/qlog/issues/429. However, all this PR does is moves text as proposed in https://github.com/quicwg/qlog/issues/423. Closes https://github.com/quicwg/qlog/issues/423
It's not clear to me why we would want to use an incommon string like "HTTP3" instead of "HTTP/3", there's no issues with slashes I can think of and saving...