Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to rephrase the Reg_Info definition #113

Merged
merged 7 commits into from
Oct 18, 2023
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion draft-ietf-scitt-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -624,9 +624,14 @@ All Signed Statements MUST include the following protected headers:
- Issuer (label: `TBD`, temporary: `391`): DID (Decentralized Identifier {{DID-CORE}}) of the signer, as a string. `did:web:example.com` is an example of a DID.
- Feed (label: `TBD`, temporary: `392`): The Issuer's name for the Artifact, as a string.
- Content type (label: `3`): Media type of payload, as a string. For example, `application/spdx+json` is the media type of SDPX in JSON encoding.
- Registration Policy info (label: `TBD`, temporary: `393`): A map of additional attributes to help enforce Registration Policies.
- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs provided and controlled by the Issuer that are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each individual Issuer or are specific to the Issuer and Feed tupel. Examples include: sequence number of signed statement on feed, Issuer metadata, or reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for).
henkbirkholz marked this conversation as resolved.
Show resolved Hide resolved
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved
- Key ID (label: `4`): Key ID, as a bytestring.


Registration:

: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, producing a Receipt, and returning it to the submitting Issuer.
henkbirkholz marked this conversation as resolved.
Show resolved Hide resolved

SteveLasker marked this conversation as resolved.
Show resolved Hide resolved
In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows:

~~~ cddl
Expand Down