Hi,

I was reviewing the proposal and had a few questions on usage of the new params.   

1) When using plaintext keys, is the “attributes” param unused and should/could it be set to NULL?

2) If using key store (i.e. opaque), is the key ID the only attribute field which needs to be set?   My assumption is attributes would be populated from the key store using the key ID?

3) If using key store, are the “key_buffer” and “key_buffer_size” params typically unused (i.e. can be set to null and zero respectively)?  I do the proposal says the buffer content is up to the driver.  Are there any usage cases in mind?

4) For drivers that support both opaque and transparent operation, which param would be used to determine the mode?  (I had assumed key ID = 0 would be transparent, and non-zero is opaque)

I’m unclear how persistent_state for opaque driver’s is used.  Could you elaborate on how it’s used by the driver and core and why it isn’t needed for transparent drivers?

Key management with opaque drivers

Transparent drivers may provide the following key management functions:

Should this be “Opaque”?

Regards,

Brian Quach

SimpleLink MCU

Texas Instruments Inc.

12500 TI Blvd, MS F-4000

Dallas, TX 75243

214-479-4076