On Tue, Nov 14, 2023 at 12:01 PM Lucas Pardue <[email protected]> wrote:
> Why not? > I think what I wanted to say is that you don't want to require every qlog consumer to have both a QUIC wire protocol frame parser and a qlog event Frame parser. Frames in qlog should be either structured objects (in practice, JSON objects) or QUIC wire bytes, but not a mix of both. > It would help to better understand the use case. How can debugging use the > value? Do we expect all tools to offer this and hence standardizing > something has value. If not, logging endpoints can always insert custom > fields into any element. And custom tooling can consume it. > >From my perspective as an event producer, it's odd to have a frame which I can't log without inserting custom fields. Perhaps that's okay, but if so, I think qlog should define the expected behavior for producers logging uninterpretable ACK Delay fields. - Damien >
