Skip to content

Conversation

@boaks
Copy link
Contributor

@boaks boaks commented Nov 19, 2021

Start support DTLS Connection ID / RFC 9146.

Client implementation using an empty CID to indicate support.
If the server negotiates a CID, that is used to send records.
Setup matches the very common use-case, where the server has a fixed ip-address, but the client ip-address's may be temporary. Requires a server with cid support, which is not contained in this PR.

Signed-off-by: Achim Kraus achim.kraus@bosch.io

@boaks
Copy link
Contributor Author

boaks commented Dec 9, 2021

@obgm

Would it be possible to include that into a special development branch, e.g. "develop_cid"?
It would make it little easier for some to use it. Sure, it's also not that complicated either to fetch the PR or to fetch from the bosch-io fork. So it will also be OK, to leave it "as it is".

@obgm
Copy link
Contributor

obgm commented Dec 9, 2021

Sure. There now is a new branch feature/connection_id for this. (I picked the name to be rather explicit, whereas it is clear from the nature of this branch that it is for development.)

@boaks
Copy link
Contributor Author

boaks commented Feb 25, 2022

@obgm

Please "reset" the feature/connection_id branch to this Pr in order to include the recent bugfixes.

@obgm
Copy link
Contributor

obgm commented Feb 28, 2022

Done, the branch head now points to 8ff2595.

Simple client side implementation indicates support and uses the cid of
the server, when negotiated by that.

Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
@boaks
Copy link
Contributor Author

boaks commented Jun 25, 2022

I prepared PR #149 to merge it into main.

@boaks boaks closed this Jun 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants