Skip to content
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

modified match boxing rules - DTLS with connection ID #42

Open
boaks opened this issue Oct 8, 2024 · 0 comments
Open

modified match boxing rules - DTLS with connection ID #42

boaks opened this issue Oct 8, 2024 · 0 comments

Comments

@boaks
Copy link

boaks commented Oct 8, 2024

DTLS with Connection ID

I'm not sure, what will be required.

In my view, CoAP defines a "distributed state machine" on (mainly) two peers. That uses for plain UDP transport the "ip-address:port" tuple to identify the related parts of that "distributed state machine" (client-state and server-state).

If the transport is changed, the data used for that identification is changing.
In some cases that "other identity" is the imply mapped into a IPv:port address and so it's possible to use different transport layers also with common coap implementations. And some implementations are just flexible enough to work with other identities as well, e.g. Eclipse/Californium with DTLS CID.

With that it may require to specify, where in the RFCs the ip-address:port is used for that identification and may be replaced by something else (I guess that applies for the most places), or where it is really used for the ip-transport (I guess only in rare cases).

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

No branches or pull requests

1 participant