The two registries defined by the Compliance Receipts profile
(draft-marques-asqav-compliance-receipts), administered here rather than at IANA because the
document is an Independent Submission and RFC 8726 bars that stream from creating IANA
registries.
| File | Registry |
|---|---|
registry/extension-fields.json |
Compliance Receipt Extension Fields |
registry/type-namespaces.json |
Compliance Receipt Type Namespaces |
Each has a JSON Schema alongside it. Both carry a version that verifiers report in their output.
To register an entry, read REGISTRATION.md. Third parties may register only
under their own top-level namespace; protectmcp and its sub-namespaces are reserved to the
defining document. Nothing is pre-registered on anyone's behalf.
Verifiers vendor both files at build time. The rules they enforce, and the reasoning behind each,
are in REGISTRATION.md. In short: an
unregistered protectmcp:* type is a non-conformance, an unregistered third-party namespace is
reported but not failed, and a wrong scope tag is a non-conformance.
Apache License 2.0 — see LICENSE. Deliberately permissive: every conformant verifier
has to vendor these files, so a registry nobody can lawfully embed would make the format one that
only Asqav can implement. Same reasoning, and the same licence, as the conformance vectors in
asqav-sdk. The SDK implementation itself stays under the Elastic License 2.0 — that is a product;
this is a reference, and contains no implementation.
This URL is intended not to move. The registries are versioned; entries are added, and existing entries are not renamed or removed, so a verifier pinned to an older copy stays correct about everything it already knew.