Topic: ConnectionID supported only on DTLSv1.3?

Is ConnectionID in WolfSSL only supported for DTLSv1.3 and not for DTLS1.2?

Share

Re: ConnectionID supported only on DTLSv1.3?

Hi SunnySunday,

It's been added in PR https://github.com/wolfSSL/wolfssl/pull/7995 and should be merged shortly. It will be in the next release planned in a few weeks.

Can you tell us more about your project and use-case involving connection ID with DTLS v1.2? Feel free to email support at wolfssl dot com if you'd like to keep it confidential.

Thanks,
David Garske, wolfSSL

Share

3 (edited by Sunnysunday 2024-09-30 07:57:03)

Re: ConnectionID supported only on DTLSv1.3?

Hi,

Thanks for answer. That's good news!

I am a student of computer science writing a Bachelor Thesis on the performance of DTLS (both v1.2 and v1.3) with and without ConnectionID over Narrowband-IoT networks. I will be using the Nordic Thingy:91 and wolfSSL to test that with CoAP data.

Share

Re: ConnectionID supported only on DTLSv1.3?

Does the WolfSSL port for Zephyr support the DTLS Connection ID feature?
Iā€™m aware that the mainline WolfSSL library supports Connection ID in its latest releases, but I want to confirm if this functionality is available and stable in the Zephyr environment.

Share

Re: ConnectionID supported only on DTLSv1.3?

Yes, the Zephyr port just builds against the main wolfSSL project, so it will be supported.