Repository navigation
Classify RFC 10024 PQ/T hybrid groups and add policy pack 0.3 - #63
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
X25519MLKEM768,SecP256r1MLKEM768andSecP384r1MLKEM1024areclassified as
pq_t_hybrid_kem,quantum_resistant,standardized_pq_t_hybrid. Matching is exact after normalization. Otherhybrid spellings, and
X25519Kyber768Draft00/SecP256r1Kyber768Draft00(obsoleted by RFC 10024 Section 7.4), receive no positive classification.
componentsare spelled as in RFC 10024, in the shared-secret order ofSection 4.3;
certification_componentfollows Section 5 and must be a component;excerpt, verbatim text from the cited section.retain_monitor; human review is required under every policypack; reason code
classification:standardized_pq_t_hybrid.nist-pqc-basic0.3 addsstandardized_pq_t_hybrid_requires_certification_evidence_reviewand thereference
RFC-10024.policy_pack_hashchanges.Section 5 and states which component implementation must be shown to be
certified. Reports list components and the certification component.
validation_componentis namedcertification_component,the term used by RFC 10024 Section 5. PDR 0.3 has not been released.
design/r0-architecture.mdhas 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
unknownand are listed as intended changes; the other 213 pinned classifications
are unchanged.
examples/sample_inventory.yamlare unchanged; only policypack identity fields differ.
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.
registry_hash,were recomputed with the independent
rfc87850.1.4 package and matched.Python 3.11, 1440 passed, 4 skipped. A generated PDR for an
X25519MLKEM768asset passes 8 of 8 verification checks.