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

Jump to bottom

Improve description for Figure 1 #300

Merged
merged 8 commits into from
Oct 1, 2024
Merged

Improve description for Figure 1 #300

Changes from 4 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
f55cf7a
Relocate section summary as-is to before Figure 1
aj-stein-nist Aug 7, 2024
5a1d988
Expand description, relate it back to figure for #268
aj-stein-nist Aug 7, 2024
eb58640
Update draft-ietf-scitt-architecture.md
SteveLasker Aug 13, 2024
b5a2c0f
Update draft-ietf-scitt-architecture.md
SteveLasker Sep 30, 2024
dad88f9
Update draft-ietf-scitt-architecture.md
SteveLasker Sep 30, 2024
8d9a6b6
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 1, 2024
ef07db7
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 1, 2024
71a1ed2
Update draft-ietf-scitt-architecture.md
SteveLasker Oct 1, 2024
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
17 changes: 11 additions & 6 deletions draft-ietf-scitt-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -326,6 +326,17 @@ The SCITT architecture consists of a very loose federation of Transparency Servi
In order to accommodate as many Transparency Service implementations as possible, this document only specifies the format of Signed Statements (which must be used by all Issuers) and a very thin wrapper format for Receipts, which specifies the Transparency Service identity and the agility parameters for the Signed Inclusion Proofs.
Most of the details of the Receipt's contents are specified in the COSE Signed Merkle Tree Proof document {{-COMETRE}}.

{{fig-concept-relationship}} illustrates entities and processes that comprise a Transparency Service independent of any one use case.
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved

There are three main entities and their associated processes in SCITT:
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved

* Issuers that use Statements about Artifacts and their credentials to create Signed Statements
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved
* Transparency Services that register Signed Statements and Transparent Statements and in doing produce Receipts
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved
* Relying Parties that
SteveLasker marked this conversation as resolved.
Show resolved Hide resolved
* collect Receipts of Signed Statements for subsequent registration of Transparent Statements;
* retrieve Transparent Statements for analysis of Statements about Artifacts themselves (e.g. verification);
* or replay all the Transparent Statements to check for the consistency of the Transparency Service's Append-only Log (e.g. auditing)

~~~aasvg
.----------.
| Artifact |
Expand Down Expand Up @@ -372,12 +383,6 @@ Most of the details of the Receipt's contents are specified in the COSE Signed M
~~~
{: #fig-concept-relationship title="Relationship of Concepts in SCITT"}

This section describes at a high level, the three main roles and associated processes in SCITT:

* Issuers and Signed Statements
* Transparency Service and the registration process
* Relying Parties of the Transparent Statements and the Receipt validation process

The subsequent sections describe the main concepts, namely Transparency Service, Signed Statements, Registration, and Transparent Statements in more detail.

## Transparency Service
Expand Down
Loading