| Connection ID exchange in Californium [message #1838140] |
Wed, 17 February 2021 06:10  |
Eclipse User |
|
|
|
Hi,
It appears that Scandium-core README.md supports the latest draft of Connection Identifiers for DTLS 1.2 (draft-ietf-tls-dtls-connection-id-09).
According to Connection Identifiers for DTLS 1.2, Section 7(Examples), the CID exchange happens between the Client & the server if the client and the server want to talk based on Connection Id.
I have attached the screenshot of the connection id exchange.
When I run the demo-apps of Scandium Server & Scandium Client, I am not able to see the exchange of CID happening between the client and the server. Though I can see the Connection Id generation on the Client as well on the Server side of DTLS. I have added the logger in the Record.java of eclipse scandium-core but the connection Id has been always null in the loggers.
My question is whether the CID exchange logic between the DTLS Server and DTLS client is implemented in scandium-core API? If yes, please help me to find out the classes used for this.
|
|
|
| Re: Connection ID exchange in Californium [message #1855008 is a reply to message #1838140] |
Fri, 23 September 2022 03:06  |
| Eclipse User |
|
|
|
Late answer:
In the current version 3.7.0, the ExampleDTLSClient supports DTLS 1.2 CID, and the ExampleDTLSServer is using it.
Therefore the client sends CID RFC9146 records, while the server sends plain RFC6347 records.
If the client should not only support CID and should used CID as well, then change the value of
DTLS.CONNECTION_ID_LENGTH=0
in the Californium3.properties to a larger value, e.g. 4.
|
|
|
Powered by
FUDForum. Page generated in 0.04196 seconds
Home