Re: RFC: DLT for "application TCP stream capture"

[David Laight <David.Laight () ACULAB COM>]

From: Denis Ovsienko
> > Eventually, we'll be using this format to debug multi-path TCP, in which case
> > the IP addresses (and maybe even the IP4/IP6-ness of it) might change.
>
> Also there exists SCTP, which implements the concept of variable (0..65535)
> number of "streams" for each direction of an "association" between a pair of
> sockets (in TCP these two things are the same), so a stream_id field in the
> encoding (0 for TCP and UDP) could be handy for SCTP payload representation.

SCTP 'streams' aren't entirely separate data flows.

There is only one transmit window and one set of acks.
Each data 'chunk' does have a stream-id (and in-stream sequence number) so
that data for a specific stream can be delivered to the application even
when data for a different stream has been lost (and retransmit requested).

SCTP also has a field that identifies the data encoding for each chunk.

If you are trying to add this into some kind of packet header then
you'll need some kind of free-format (but don't use XML).

        David

_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers