Topic: ConnectionID supported only on DTLSv1.3?
Is ConnectionID in WolfSSL only supported for DTLSv1.3 and not for DTLS1.2?
You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → wolfSSL → ConnectionID supported only on DTLSv1.3?
Is ConnectionID in WolfSSL only supported for DTLSv1.3 and not for DTLS1.2?
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
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.
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.
Yes, the Zephyr port just builds against the main wolfSSL project, so it will be supported.
wolfSSL - Embedded SSL Library → wolfSSL → ConnectionID supported only on DTLSv1.3?
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.027 seconds (89% PHP - 11% DB) with 11 queries