Robin Marx
Robin Marx
### Describe the feature you'd like supported [qlog](https://github.com/quiclog/internet-drafts) is a structured endpoint logging format specifically for QUIC and HTTP/3. It is on track to be adopted by the IETF QUIC...
We currently extracted these to other events, assuming they wouldn't change or only change sparingly at specific times, handled by other events (e.g., when doing migration). However, this is not...
At the moment, the QPACK events very closely mimic the QPACK instructions as defined in the draft (Or at least, they should... the current definitions are somewhat outdated wrt the...
qlog should be specific about which fields are potentially privacy sensitive and the possible actions that can be taken to mitigate these issues (e.g., hashing, exclusion, mapping, ...). The current...
Currently, we define the TLS_ALERT error codes as 0x100 to 0x199, while apparently in RFC9000 it's [0x0100, 0x01ff] (see https://datatracker.ietf.org/doc/html/rfc9000#section-22.5). Should be tackled as part of #174.
The new CDDL approach uses a CDDL extension point to be more strict about which values are allowed in the `Event:data` field. Currently, it's defined as: ``` ; The ProtocolEventBody...
We currently have the `summary` (in QlogFile) and `configuration` (in Trace) fields. These fields made sense when qlog was viewed as a file format that would primarily be used to...
Once data for a stream is sent in a packet, it has to remain in some form of retransmission buffer (either a separate buffer or as ranges in the main...
Apparently, what was once (colloquially) known as key "retire" is now called key "discard" in [RFC 9001](https://www.rfc-editor.org/rfc/rfc9001.html#name-discarding-unused-keys). As such, we should update the event definition's name (and probably add some...
using transport.parameters_set there are two parameters to signal 0-RTT: - resumption_allowed - early_data_enabled As pointed out by @jlaine, these are a bit ambiguous, as 0-RTT can either be used for...