In the context of Asymmetric Key Algorithms, should Public-Key-Encryption and Public-Key-Cipher be merge as the same cryptoSubClass?

Background

With the restructuring of the list, by adapting the cryptoClass (#68 ) and cryptoSubClass (#69 )properties description, the question of Public-Key-Encryption and Public-Key-Cipher, both subCryptoClass values, being synonyms arised

Rationale

It seems that these two terms are used interchangeably in papers and other references, in the context of Asymmetric Key Algorithms. Should we merge them as a single value for subCryptoClass property?

Description

Discuss within the Cryptography Group this case, reach a consensus and, if the decision is to merge them, adapt:

• The properties description document
• The affected algorithms of the list

accordingly, referring it as public-key-encryption

Action

• Discuss the case within the Cryptography Group
  • Reach a consensus
• Create a proposal, including the changes in
  • property description file
  • affected algorithm description
• Validate it within the Cryptography Group
• Create a PR
• Review and merge the PR

DoD

• Will the two values be merged:
• Link to the proposal:
• Link to the PR
• Link to the adapted properties description file
• Link to the affected algorithms description

Start by reviewing the properties description document and the affected algorithm descriptions, then bring the synonym question to the Cryptography Group. Done means a consensus is recorded, a proposal is created and validated, and the relevant descriptions and list entries are updated if the values are merged.