Re: [tsvwg] DTLS for SCTP: DTLS Chunk kernel part testing

[Michael Tuexen <[e-mail]>]

> On 18. Mar 2024, at 00:04, Magnus Westerlund <magnus.westerlund=[e-mail]> wrote:
> 
> Hi,
>  In the design team we have discussion around barriers to implement DTLS Chunk (https://datatracker.ietf.org/doc/draft-westerlund-tsvwg-sctp-dtls-chunk/) as part of SCTP stacks that are in open source OS kernels. The discussion in the design team indicated that they could implement and release the functionality described in the above draft. What was raised as an issue was the testing of this code using the API that would exist to the upper layer implementation that would implement the DTLS handshakes and rekeying per: https://datatracker.ietf.org/doc/draft-westerlund-tsvwg-sctp-dtls-handshake/.
>  Is there any reason why one cannot actually write code to test this API without implementing almost any of draft-westerlund-tsvwg-sctp-dtls-handshake? I would think the goal of the kernel parts is to show that the lower layer and its API works and can 
Hi Magnus,

this is my personal opinion with respect to implementing this in FreeBSD.
Of course, one can do what you suggest. When I would implement it, most
likely I would add support for it in packetdrill to do some functional
testing. I guess some fuzz testing with tools like syzkaller would also
be done.
But when I'm implementing something (functionality in the kernel and
an API for it) which has mainly one use case, I would really prefer to
be able to test this in this use case. This is my personal preference
and nothing requires me to do this testing. But not testing it seem
sub-optimal to me.

Best regards
Michael
> be used by a higher layer application on top of the SCTP stack. In a test application one could use hard coded keys and have multiple sets  to test rekeying and not run DTLS handshakes at all between the endpoints.
>  Cheers
>  Magnus