Any generic key-value map type can be assigned to $ProtocolEventData (the only common "data" subfield defined in this document is the optional trigger field, see Section 7.4).
I don't quite understand how this is a common field, since there is no CDDL for it. Should we be defining $ProtocolEventData with the actual optional ?trigger field? Or is is more like "common by convention" or some other magic.
Or is it actually the case that "trigger" is a design pattern that concrete event definitions can adopt but that they must explicitly declare the trigger field in their event definition?
In https://quicwg.org/qlog/draft-ietf-quic-qlog-main-schema.html#section-8.2-5 we say:
Any generic key-value map type can be assigned to $ProtocolEventData (the only common "data" subfield defined in this document is the optional trigger field, see Section 7.4).
I don't quite understand how this is a common field, since there is no CDDL for it. Should we be defining
$ProtocolEventData
with the actual optional?trigger
field? Or is is more like "common by convention" or some other magic.Or is it actually the case that "trigger" is a design pattern that concrete event definitions can adopt but that they must explicitly declare the trigger field in their event definition?