Skip to content

Classify RFC 10024 PQ/T hybrid groups and add policy pack 0.3 - #63

Merged
ILIASTEKEOGLOU merged 1 commit into
mainfrom
registry/hybrids
Oct 10, 2026
Merged

ILIASTEKEOGLOU merged 1 commit into
mainfrom
registry/hybrids

Conversation

@ILIASTEKEOGLOU

Copy link
Copy Markdown
Owner

Summary

  • X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 are
    classified as pq_t_hybrid_kem, quantum_resistant,
    standardized_pq_t_hybrid. Matching is exact after normalization. Other
    hybrid spellings, and X25519Kyber768Draft00 / SecP256r1Kyber768Draft00
    (obsoleted by RFC 10024 Section 7.4), receive no positive classification.
  • Registry schema 2, content version 2:
    • components are spelled as in RFC 10024, in the shared-secret order of
      Section 4.3;
    • certification_component follows Section 5 and must be a component;
    • sources may carry excerpt, verbatim text from the cited section.
  • Decision: retain_monitor; human review is required under every policy
    pack; reason code classification:standardized_pq_t_hybrid.
  • Policy pack nist-pqc-basic 0.3 adds
    standardized_pq_t_hybrid_requires_certification_evidence_review and the
    reference RFC-10024. policy_pack_hash changes.
  • PDR target-state rationale names the components, quotes RFC 10024
    Section 5 and states which component implementation must be shown to be
    certified. Reports list components and the certification component.
  • The PDR field validation_component is named certification_component,
    the term used by RFC 10024 Section 5. PDR 0.3 has not been released.
  • design/r0-architecture.md has a dated amendment (A1 to A4).

Source text

Registry excerpts were compared with the published text of RFC 10024 and
NIST SP 800-227 and appear there verbatim. One notation change: a subscript
is written as S_j. Tests pin every excerpt and every generated message.
No generated text states that a hybrid is approved; a test enforces this.

Verification

  • Classification snapshot: the three group names were pinned as unknown
    and are listed as intended changes; the other 213 pinned classifications
    are unchanged.
  • Decisions for examples/sample_inventory.yaml are unchanged; only policy
    pack identity fields differ.
  • Property tests over deterministic corpora: normalization is idempotent;
    every registry identifier resolves to its entry; more than 500 generated
    spellings with a PQ marker and not in the registry get no positive
    classification.
  • All hashes of a PDR containing hybrid assets, including registry_hash,
    were recomputed with the independent rfc8785 0.1.4 package and matched.
  • Local runs: Linux Python 3.11 and 3.13, 1441 passed, 3 skipped; Windows
    Python 3.11, 1440 passed, 4 skipped. A generated PDR for an
    X25519MLKEM768 asset passes 8 of 8 verification checks.

X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 are
classified as pq_t_hybrid_kem, quantum_resistant,
standardized_pq_t_hybrid. Matching is exact after normalization;
every other hybrid spelling and the pre-standard names obsoleted by
RFC 10024 Section 7.4 receive no positive classification.

Registry schema version 2 and content version 2:
- components are spelled as in RFC 10024, in the shared-secret
  order of Section 4.3; certification_component follows Section 5
  and must be one of the components;
- sources may carry an excerpt, verbatim text from the cited
  section; the hybrid entries quote RFC 10024 Sections 3, 4.3, 5
  and 7 and NIST SP 800-227 Section 4.6.2;
- identifiers are unique after normalization.

The canonical action for these groups is retain_monitor, and human
review is required under every policy pack. Policy pack
nist-pqc-basic 0.3 adds the rule
standardized_pq_t_hybrid_requires_certification_evidence_review and
the reference RFC-10024. The PDR target-state rationale names the
components, quotes RFC 10024 Section 5 and states which component
implementation must be shown to be certified. Reports list the
components and the certification component.

The PDR field validation_component is named certification_component,
matching the wording of RFC 10024 Section 5. The design record has a
dated amendment.

The three group names were pinned as unknown in the classification
snapshot; they are listed as intended changes, and the other 213
pinned classifications are unchanged.
@ILIASTEKEOGLOU
ILIASTEKEOGLOU merged commit f5ee727 into main Oct 10, 2026
19 checks passed
@ILIASTEKEOGLOU
ILIASTEKEOGLOU deleted the registry/hybrids branch October 10, 2026 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant