CBOR encoding profile for access devices
Scope
Deterministic encoding per RFC 8949 Section 4.2. Bounded element sizes, so a parser can allocate once and refuse anything larger. A restricted tag set limited to what the envelope needs. A security-validated parser subset covering the hazards specific to CBOR in firmware. Profiled for two device classes, reader and wallet, with the reference performance target assuming hardware acceleration for ECDSA P-256 and SHA-256 and a software fallback where it is absent. Designed for a PoE power budget and a sub-second target from presentation to door action.
Operational properties
Each ratified specification carries commitments on privacy (the deployment holds no stable, deployment-specific identifier for the holder, because it issued nothing; schema-level disclosure constraints; decline-for-insufficient-disclosure as a defined outcome), revocation (issuer-side and access-side paths kept separate, the access-side path under a defined propagation contract), audit (federated chain, tenant data stays with the tenant), and offline operation (deterministic policy on cached trust data with bounded freshness; reconciliation on reconnect; egress and life-safety paths never depend on audit-buffer state). Sections 6.1 through 6.4 of the paper state them in full.
Public review
No review period is open.
Want to be notified when this specification opens for public review? Register on the Participate page.
Disposition log
No review periods recorded yet.
Text
Not yet published.
Related
Paper reference: Section 5.4 of Beyond Credentials (Beyond Credentials)
Adjacent standards: