Lucas Pardue

Logging for paced packet sending

2

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...

Add fin and reset_stream fields

2

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...

State clearly what lengths mean for stream and datagram data moved

2

Addresses part of #375

Convert H3 setting param types to a real type

1

Closes #382

H3Settings is a bit underspecified

4

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...

Security use cases

2

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_

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?...

Rework the Timestamps section, add monotonic

2

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 -...

Versioning for additional schema

9

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...