Comment ledger
A public ledger of comments received on the v0.2 draft and their Council review status.
The standard is a v0.2 draft. Every comment received is logged in the ledger and reviewed by the working group. This page shows the aggregate status — no personal data and no comment bodies: only the requirement or section the comment targets, the date, the status, and the Council's short disposition.
Draft v0.2 -> v1.0. Subject to change before 2027-01-01.
What each status means
Status is conveyed by weight and glyph, not color. Every disposition carries a published rationale.
Logged and awaiting initial triage by the working group.
The working group is assessing the comment on its merits and preparing a disposition.
Will be reflected in a future version of the standard.
Considered valid but parked for a later version.
Considered and not adopted; rationale published.
Merged into another ledger entry.
Comment ledger
Ledger of received comments and their review status.
Registry rows are examples and do not reflect real certifications.
2
2
2
1
1
1
Filter
| ID | Date | Requirement / section | Who | Status | Summary | Council disposition |
|---|---|---|---|---|---|---|
| CMT-0009 | 2026-06-07 | B.3.1 | Vendor | Received | Clarify the list of permitted storage form factors for Critical Cryptographic Material. | Disposition not yet published |
| CMT-0008 | 2026-06-05 | B.6 | Community | Received | Proposal to detail key-recovery requirements in the wallet architecture. | Disposition not yet published |
| CMT-0007 | 2026-06-03 | B.2.1 | Academia | Under review | Comment on the wording of verifiable entropy in key generation. | Referred to the cryptography working group; opinion pending. |
| CMT-0006 | 2026-05-29 | Annex 2 | Auditor | Under review | Request to extend the list of approved algorithms in the annex. | Being aligned with the post-quantum migration roadmap. |
| CMT-0005 | 2026-05-26 | B.5.2 | Auditor | Accepted | Proposal to align key-rotation timelines with industry practice. | Accepted: wording to be clarified in v1.0. Target: v1.0 |
| CMT-0004 | 2026-05-22 | Section A | Regulator | Accepted | Comment on the carry-over description from baseline standards in Section A. | Accepted: the mapping table will be expanded in v1.0. Target: v1.0 |
| CMT-0003 | 2026-05-19 | B.4.1 | Vendor | Deferred | Proposal for an additional level of detail in operation access control. | Deferred: valid, but moved to v1.1. Target: v1.1 |
| CMT-0002 | 2026-05-15 | B.7.3 | Community | Declined | Proposal to relax the compromise-response timing requirement. | Declined: the requirement stays critical; rationale published. |
| CMT-0001 | 2026-05-12 | B.3.1 | Academia | Duplicate | Clarification on the storage requirement for Critical Cryptographic Material. | Duplicate: merged into CMT-0009. |
How the consultation loop works
The standard evolves through an open feedback loop — from comment to version. Every step is public and traceable.
Related