MaximumNumberOfKeys - Issue #778 clarification - #811
Conversation
MaximumNumberOfKeys - Since it is not able to test maximum capability with RSA and ECC Keys simultaneously, this parameter description is changed to minimum supported number of private keys that the device is able to store simultaneously.
| </entry> | ||
| <entry> | ||
| <para>Indicates the maximum number of private keys that the device is able to store | ||
| <para>Indicates the minimum supported number of private keys that the device is able to store |
There was a problem hiding this comment.
do we really want to turn an upper bound into a minimum?
There was a problem hiding this comment.
We had a discussion in VEWG on July 16th 2026 for this issue, currently it is not possible to test maximum number of keys capability from device test tool since device itself does not know what to return if the no of supported RSA and EC keys are different. For Example, the device supports 2 RSA Keys, 4 EC Keys, what should be returned in MaximumNumberOfKeys Capablity, Is it 4 or Is it 2? If 4 is provided in the response, device test tool try to create 4 RSA Keys and the test will fail. What device can safely return in this case is 2 which is minimum supported no of keys irrespective of RSA or EC keys. The decision in the WG on Jul16 th 2026, update the parameter description to minimum supported keys and do not change parameter name since changing parameter name can cause backward capability issues.
MaximumNumberOfKeys - Since it is not able to test maximum capability with RSA and ECC Keys simultaneously, this parameter description is changed to minimum supported number of private keys that the device is able to store simultaneously.