You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The meaning of is_coalesced should be clarified. I assume this is
set to true unless a packet is both the first and last packet in a
datagram. However that is not necessarily obvious when a packet is
being generated; another option is to define this as being true for
every packet but the first packet in a datagram.
quic:packet_received:
See comment on is_coalesced above
The text was updated successfully, but these errors were encountered:
However, in cases where implementations cannot track datagrams in this way, the is_coalesced field can be used to indicate that a packet was (intended to be)
coalesced. Implementations MAY use both methods concurrently.
is that is_coalesced is basically non-preferred and only for use if an implementation cannot use datagram_id. That seems like a good approach.
"intended to be" needs clarifying... this implies a packet could be intended to be coalesced but isn't actually. So to have that you actually have to introduce a concept of "coalescable" rather than "was coalesced", which feels like it opens a bit of a can of worms where either we have to define that, or an implementation basically gets to define some arbitrary set of conditions which is "coalescing desired". But that then kind of feels uselessly vague.
I almost feel like we should just drop is_coalesced unless we can identify a concrete use case for it. It seems hard to lock down a proper meaning for it and the utility (unless I am missing something) seems minimal given the minimal implementation costs of the preferred datagram_id approach.
As reported by @hlandau on the mailing list:
quic:packet_sent:
The meaning of
is_coalesced
should be clarified. I assume this isset to true unless a packet is both the first and last packet in a
datagram. However that is not necessarily obvious when a packet is
being generated; another option is to define this as being true for
every packet but the first packet in a datagram.
quic:packet_received:
See comment on is_coalesced above
The text was updated successfully, but these errors were encountered: