You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: