spdx / spdx/cryptographic-algorithm-list

Post-Quantum-Cryptography as property

Open
#73 3 comments 0 reactions 0 assignees View on GitHub

@toscalix is already working on this.

Since Sep 9, 2026.

  • #91 by @toscalix — open
enhancement question
Dominant language
No language data
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Background

As a result of restructuring the list (cryptoClass and CryptoSubClass values), effort tracked in #68 the Cryptography Group took the decision on 2026-04-22 to consider Post-Quantum-Cryptography (PQC) a new property, instead of a cryptoSubClass

Rationale

PQC follows a logic that does not fit in the cryptoClass structure. It would require us to challenge the current values of cardinality we follow in cryptoClass and cryptoSubClass, among other considerations. Pre and Post Quantum Cryptography tits better as a different dimension in the algorithms categorizations

Description

Discuss and reach a consensus on the description of this new property, related with PQC. Evaluate which algorithms are currently affected and use the existing candidates to the list #43 to check if the proposed property make sense.

Actions

  • Define a proposal for the new property. Include
    • The changes in the list properties description
    • Algorithms affected and the new description for each one of them
    • how would potential candidates be described based on this proposal
  • Reach consensus about this proposal wirthin the Cryptography Group
  • Create and submit a PR
  • Review and merge the PR

DoD

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the proposal in the linked issue comment, the Cryptography Group consensus in HackMD, and the existing candidates from #43, while checking the restructuring context in #68. The work is already represented by open PR #91; completion requires the PR and the new property description and affected-algorithm descriptions to be linked in the issue DoD.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.