qlog
qlog copied to clipboard
quicwg
The IETF I-D documents for the qlog format
This will be RFC soon, I'd like for the HTTP/3 schema to include this event formally. Spec: https://httpwg.org/http-extensions/draft-ietf-httpbis-priority.html#section-7.2
It's possible that a peer would open stream types of unknown type, and not in the reserved range. So let's fix that up.
What is this type supposed to represent? If it's a request stream, lets just call it that.
In https://quicwg.org/qlog/draft-ietf-quic-qlog-h3-events.html#appendix-A.3.9 you say > HTTP/3 qlog re-uses QUIC's UnknownFrame definition, since their values and usage overlaps This is ambiguous to me. Are you saying the defined object - QUIC...
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.
We had a question about quiche's logging on https://github.com/cloudflare/quiche/issues/1197 this got me thinking some more about representations of time in qlog. In quiche, we use a monotonic non-decreasing clock. When...
In https://www.ietf.org/archive/id/draft-ietf-quic-qlog-main-schema-02.html#section-1.1.1 you define `uint8`, `uint16`, `uint32`, `uint64` and `hexstring`types. Have you considered if these types should be defined in their own document? This seems like something where direction from...
Editorial work on draft-ietf-quic-qlog-main-schema has been a lower priority than the design work. That's fine. But as we look ahead, we should think a bit about what the scope or...
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...