-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add client dtls connection ID (2.). #149
base: main
Are you sure you want to change the base?
Conversation
fa939b1
to
0af8db6
Compare
4becf0b
to
0272b27
Compare
d8e717b
to
fb7a4aa
Compare
3dabb24
to
4b60a6b
Compare
Simple client side implementation indicates support and uses the cid of the server, when negotiated by that. Signed-off-by: Achim Kraus <[email protected]>
Signed-off-by: Achim Kraus <[email protected]>
It would be good if a server side API could be added where the calling application can define the CID to use so that it can be tracked by the application to change the tuple to send back any response on. |
As for now, tinydtls CID only supports the client side. To be more precise, the client only indicates to support CID, but doesn't use a CID on it's own side. For the next time I will not able to spend the required time to implement a server side. If that changes, the proposed API will make a lot of sense. |
Simple client side implementation indicates support and uses the cid of
the server, when negotiated by that.
Signed-off-by: Achim Kraus [email protected]