A user might want to analyze data from TCP reassembly — things like retransmissions, duplicate data, missing segments, and out-of-order segments. It would be great to expose this to users as a subscribable data type.
There are two ways to do this, I think:
- Iris already tracks some TCP reassembly data (last sequence number, current ACK number, current OOO packets, consumed flags). Since Iris data types are read-only, this is a reasonable candidate for a built-in data type to directly expose to users.
- This could also be implemented independently in the datatypes crate. This will replicate work (if subscribed to), but it's easier to implement and can express additional semantics that Iris doesn't already track.
A user might want to analyze data from TCP reassembly — things like retransmissions, duplicate data, missing segments, and out-of-order segments. It would be great to expose this to users as a subscribable data type.
There are two ways to do this, I think: