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.

Sign up for GitHub

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

Proposal to rephrase the Reg_Info definition #113

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ec0464e
proposal to rephrase the Reg_Info definition
henkbirkholz Oct 17, 2023
f7fa9f3
Apply suggestions from code review
SteveLasker Oct 18, 2023
32181ed
Update draft-ietf-scitt-architecture.md
henkbirkholz Oct 18, 2023
b24df6a
Update draft-ietf-scitt-architecture.md
henkbirkholz Oct 18, 2023
f98e886
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 18, 2023
fce9528
Move dupe of Registration definiton, merging content
SteveLasker Oct 16, 2023
3694890
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 18, 2023
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
4 changes: 2 additions & 2 deletions draft-ietf-scitt-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ Receipt:

Registration:

: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing it in the Registry, producing a Receipt, and returning it to the submitting Issuer.
: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, and producing a Receipt.

Registration Policy:

Expand Down Expand Up @@ -624,7 +624,7 @@ 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 set by the Issuer which are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each Issuer or are specific to the Issuer and Feed tuple. Examples include: the sequence number of signed statements on a feed, Issuer metadata, or a reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for).
- Key ID (label: `4`): Key ID, as a bytestring.

In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows:
Expand Down