Closed nashif closed 8 years ago
by Mark Linkmeyer:
Gajinder Vij , per the ww24.2 backlog grooming meeting this issue needs more details/clarification. It's too vague as written.
by Anas Nashif:
The algorithms and ciphers are all provided by mbedTLS, we need to support both DTLS and TLS so a good candidate that is modular and provides all the functionality needed for Thread and generic DTLS/TLS application would be mbedTLS.
by Mark Linkmeyer:
Sergio Rodriguez , please verify this functions correctly since it's labeled with "TestbyDev". Thx.
by Kuo-Lang Tseng:
by Mark Linkmeyer:
Thanks for the update Kuo-Lang Tseng . My follow-up questions:
by Jithu Joseph:
Mark Linkmeyer I am covering for Sergio (on Vacation) , I will look into #5 and #6 above
by Jithu Joseph:
by Kuo-Lang Tseng:
Thanks, Jithu for the update.
For #6 (#6 - AES-CMAC-PRF-128 [RFC 4615]), we need to watch out for the upstream and when it is added, we can integrate into our tree.
by Kuo-Lang Tseng:
Moved out AES-CMAC-PRF-128 [RFC 4615] from the list to a new story (GH-650) to track it separately, based on comments which indictaed it is currently not supported in mbedTLS. Closing this Jira story.
Reported by Gajinder Vij:
Provide a set of encryption libraries needed to support DTLS and Thread using 3rd party, well established and license compatible library.
The above are implemented in iotivity version of TinyDTLS and in mbedTLS.
AES-CMAC-PRF-128 [RFC 4615] is not available in current mbedTLS, so it is tracked in separate Jira.
(Imported from Jira ZEP-327)