-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update DTLS CID implementation to comply with the "final" draft. #4860
Comments
Hi @boaks and thanks for letting us know about the final draft. Unfortunately we don't have the capacity to implement this at the moment. We've added this to our backlog and hopefully schedule this in the next couple of months. |
Thanks! |
Yes, it's good to have public record about that, and it's good for us to have an issue in our backlog as a reminder. Thanks for the reminder about 4427, I thought we had merged it already. We're currently in an effort to finish off pending things, to hopefully we should be able to close it in the coming days! |
Just as some hints, if someone want to spend time in: If only the new IANA code-point (54) and the new MAC must be supported (maybe by a compile-time switch), then for v2.27 the following changes are required: In "include/mbedtls/ssl.h": In "library/ssl_msg.c": |
See PR #5061 |
Hello -- I've been following this CID saga, and noticed that above you mentioned the need to adapt the length of |
My saga was about adapting mbedtls version 2.27. |
Just to mention: |
The draft-ietf-tls-dtls-connection-id has reached version 13 is is short before being released.
The current implementation in mbedTLS (2.28) reflects version 05 and is using a proprietary code point for the extension (see my issue #3892).
In order to comply with the upcoming definitions in that draft, it is required to
Implementations will only be interoperable with other implementations, if the comply to the definitions of RFCs. For Eclipse/Californium I updated the implementation to support the new definitions along with the possibility to use the deprecated definitions (before 09). It will be contained in the upcoming Californium release 3.0.
The text was updated successfully, but these errors were encountered: