Closed LPardue closed 4 months ago
While I like the general prose editorial work, I'm personally not too convinced that we need the trigger_frame_type
on the connectivity
event. As stated elsewhere, you rarely get all combined information from a single qlog event, and you often need to look at surrounding events for more low-level info (in this case: a field specifically on the CONNECTION_CLOSE frame).
While I'm not terribly opposed to it, I'd still like to not add to the connectivity
event, but do keep the editorial work with the CONNECTION_CLOSE frame (and maybe just reference that for the connectivity
event?)
While I'm not terribly opposed to it, I'd still like to not add to the
connectivity
event, but do keep the editorial work with the CONNECTION_CLOSE frame (and maybe just reference that for theconnectivity
event?)
Makes sense, I spun it off to its own PR https://github.com/quicwg/qlog/pull/386.
If we want to do a cross reference from connection_closed, then lets do that separate
As explained above, I think we should close this without action (i.e., don't add trigger_frame_type
to connection_closed
)
Tweaks the language related to the ConnectionCloseFrame trigger_frame_type and adds it to connection_closed event.
Closes #366