commonkeySize and specifiedkeySize properties definition: improvements

[toscalix]

Background

• Comment done by @zvr to the Crypto Algorithms List Properties Description #15
• Discussion about the above comment during the meeting held on 2025-08-13
• The list is not planned to become a model but the Crypto Algorithms List Group expect some profiles to pick up or use some elements

Description

• Applying this agreement to commonkeySize property will require some adaptation of the current version of the list
• There is consensus on the group on describing this property so several commonkeySize are allowed, avoiding the usage of the operator "AND", as suggested by @zvr
• A discussion is required on extending this approach to specifiedkeySize when several values should be specified in the list.
• A discussion is required on how to adapt this policy to the case of ranges. In the current version of the list the operator "TO" is used

Actions

• Prioritize this discussion during September 2025 to improve the current version of the list in the line of the current agreement (commonkeySize).
• Open a PR with the changes required in the List properties file and the affected elements of the list due to the improvements of the commonkeySize property description
• Reach a consensus on how to apply an analogous approach to specifiedkeySize
• Open a PR with the changes required in the List properties file and the affected elements of the list due to the improvements of the specifiedkeySize property description

DoD

• Link to the PR corresponding to the commonkeySize property description
  • PR merged
• Link to the PR corresponding to the list adaptations on commonkeySize property entries for the algorithms affected
  • PR merged
• Link to the PR corresponding to the specifiedkeySize property description
  • PR merged
• Link to the PR corresponding to the list adaptations on specifiedkeySize property entries for the algorithms affected
  • PR merged