Lucas Pardue

Meeting notes: not much has changed since last discussed. Another approach could be remove streaming format altogether. Proposal to present idea of defining our own newline streaming JSON in qlog...

FWIW: Of this 40 events we define for QUIC and H3, only 10 of them currently define a trigger field.

Thanks for the explanation, that makes more sense. I think we can probably wordsmith the text on triggers a bit. I just reread section 8.2 and 8.2.1 and its seems...

Thanks for doing the work on the associated PR but it seems like a rather huge breaking change and I'm not sure that balances well against the concrete value it...

> Cleanly separating the QUIC transport layer from the HTTP/3 application mapping could make the codebase easier to work with. The code is already structured that way, the QUIC module...

Coming back to this, its not something we want to do for the reasons explained previously. It would cause a lot of churn in real projects and deployments for little...

I've pushed two commits that address feedback by: talking about security providers and an explicity TLS default, moving the new text as a fourth work area bullet

@gorryfair this charter text has now reached the point several WG members and proponents are happy with

Good question, its not entirely clear but quiche does support HTTP/3 datagrams as defined in RFC 9297. When the QUIC transport is configured to support RFC 9221 Datagrams via https://docs.quic.tech/quiche/struct.Config.html#method.enable_dgram,...

h3i takes a hostname and optional port as documented on https://github.com/cloudflare/quiche/tree/master/h3i#command-line-tool and the tool itself. There is no need for a scheme.