Skip to content

Commit

Permalink
Script updating gh-pages from bbd7102. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Oct 1, 2024
1 parent 634f373 commit 52fd5b5
Show file tree
Hide file tree
Showing 2 changed files with 64 additions and 35 deletions.
53 changes: 33 additions & 20 deletions steve/268/draft-ietf-scitt-architecture.html
Original file line number Diff line number Diff line change
Expand Up @@ -1557,18 +1557,43 @@ <h2 id="name-architecture-overview">
<p id="section-4-1">The SCITT architecture consists of a very loose federation of Transparency Services, and a set of common formats and protocols for issuing and registering Signed Statements, and auditing Transparent Statements.<a href="#section-4-1" class="pilcrow"></a></p>
<p id="section-4-2">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 <span>[<a href="#I-D.draft-ietf-cose-merkle-tree-proofs" class="cite xref">I-D.draft-ietf-cose-merkle-tree-proofs</a>]</span>.<a href="#section-4-2" class="pilcrow"></a></p>
<p id="section-4-3"><a href="#fig-concept-relationship" class="auto internal xref">Figure 1</a> illustrates two Transparency Services and two Receipts as a single Signed Statement <span class="bcp14">MAY</span> be registered on more than one Transparency Service.
<p id="section-4-3"><a href="#fig-concept-relationship" class="auto internal xref">Figure 1</a> illustrates entities and processes that comprise a Transparency Service independent of any one use case.<a href="#section-4-3" class="pilcrow"></a></p>
<p id="section-4-4">This section describes the three main roles and associated processes in SCITT:<a href="#section-4-4" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-4-5.1">
<p id="section-4-5.1.1">Issuers that use their credentials to create Signed Statements about Artifacts<a href="#section-4-5.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-5.2">
<p id="section-4-5.2.1">Transparency Services that evaluate Signed Statements against Registration Policies, producing Receipts upon successful Registration.
The returned Receipt may be combined with the Signed Statement to create a Transparent Statement.<a href="#section-4-5.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-5.3">
<p id="section-4-5.3.1">Relying Parties that:<a href="#section-4-5.3.1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-4-5.3.2.1">
<p id="section-4-5.3.2.1.1">collect Receipts of Signed Statements for subsequent registration of Transparent Statements;<a href="#section-4-5.3.2.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-5.3.2.2">
<p id="section-4-5.3.2.2.1">retrieve Transparent Statements for analysis of Statements about Artifacts themselves (e.g. verification);<a href="#section-4-5.3.2.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-5.3.2.3">
<p id="section-4-5.3.2.3.1">or replay all the Transparent Statements to check for the consistency of the Transparency Service's Append-only Log (e.g. auditing)<a href="#section-4-5.3.2.3.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
</ul>
<p id="section-4-6">In addition, <a href="#fig-concept-relationship" class="auto internal xref">Figure 1</a> illustrates two Transparency Services and two Receipts as a single Signed Statement <span class="bcp14">MAY</span> be registered on more than one Transparency Service.
Each Transparency Service produces a Receipt.
A Transparent Statement <span class="bcp14">MAY</span> contain multiple Receipts, for each Transparency Service it was successfully Registered.<a href="#section-4-3" class="pilcrow"></a></p>
<p id="section-4-4">The arrows indicate the flow of information.
A Transparent Statement <span class="bcp14">MAY</span> contain multiple Receipts, for each Transparency Service it was successfully Registered.<a href="#section-4-6" class="pilcrow"></a></p>
<p id="section-4-7">The arrows indicate the flow of information.
For example, Credentials are used to produce Signed Statements and the Transparency Service verifies the Signed Statements.
The Transparency Service produces a Receipt.
A Receipt combined with a Signed Statement creates a Transparent Statement.
To verify a Transparent Statement, credentials are required to authenticate the Signed Statement and the Receipts of the Transparent Statement.<a href="#section-4-4" class="pilcrow"></a></p>
To verify a Transparent Statement, credentials are required to authenticate the Signed Statement and the Receipts of the Transparent Statement.<a href="#section-4-7" class="pilcrow"></a></p>
<span id="name-relationship-of-concepts-in"></span><div id="fig-concept-relationship">
<figure id="figure-1">
<div id="section-4-5.1">
<div class="alignLeft art-svg artwork" id="section-4-5.1.1">
<div id="section-4-8.1">
<div class="alignLeft art-svg artwork" id="section-4-8.1.1">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="704" width="400" viewBox="0 0 400 704" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
<path d="M 16,208 L 16,240" fill="none" stroke="black"></path>
<path d="M 40,304 L 40,384" fill="none" stroke="black"></path>
Expand Down Expand Up @@ -1717,26 +1742,14 @@ <h2 id="name-architecture-overview">
<text x="300" y="676">Replay</text>
<text x="344" y="676">Log</text>
</g>
</svg><a href="#section-4-5.1.1" class="pilcrow"></a>
</svg><a href="#section-4-8.1.1" class="pilcrow"></a>
</div>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
<a href="#name-relationship-of-concepts-in" class="selfRef">Relationship of Concepts in SCITT</a>
</figcaption></figure>
</div>
<p id="section-4-6">This section describes at a high level, the three main roles and associated processes in SCITT:<a href="#section-4-6" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-4-7.1">
<p id="section-4-7.1.1">Issuers and Signed Statements<a href="#section-4-7.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-7.2">
<p id="section-4-7.2.1">Transparency Service and the registration process<a href="#section-4-7.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4-7.3">
<p id="section-4-7.3.1">Relying Parties of the Transparent Statements and the Receipt validation process<a href="#section-4-7.3.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-4-8">The subsequent sections describe the main concepts, namely Transparency Service, Signed Statements, Registration, and Transparent Statements in more detail.<a href="#section-4-8" class="pilcrow"></a></p>
<p id="section-4-9">The subsequent sections describe the main concepts, namely Transparency Service, Signed Statements, Registration, and Transparent Statements in more detail.<a href="#section-4-9" class="pilcrow"></a></p>
<div id="sec-transparency-service">
<section id="section-4.1">
<h3 id="name-transparency-service">
Expand Down
46 changes: 31 additions & 15 deletions steve/268/draft-ietf-scitt-architecture.txt
Original file line number Diff line number Diff line change
Expand Up @@ -402,11 +402,37 @@ Table of Contents
COSE Signed Merkle Tree Proof document
[I-D.draft-ietf-cose-merkle-tree-proofs].

Figure 1 illustrates two Transparency Services and two Receipts as a
single Signed Statement MAY be registered on more than one
Transparency Service. Each Transparency Service produces a Receipt.
A Transparent Statement MAY contain multiple Receipts, for each
Transparency Service it was successfully Registered.
Figure 1 illustrates entities and processes that comprise a
Transparency Service independent of any one use case.

This section describes the three main roles and associated processes
in SCITT:

* Issuers that use their credentials to create Signed Statements
about Artifacts

* Transparency Services that evaluate Signed Statements against
Registration Policies, producing Receipts upon successful
Registration. The returned Receipt may be combined with the
Signed Statement to create a Transparent Statement.

* Relying Parties that:

- 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)

In addition, Figure 1 illustrates two Transparency Services and two
Receipts as a single Signed Statement MAY be registered on more than
one Transparency Service. Each Transparency Service produces a
Receipt. A Transparent Statement MAY contain multiple Receipts, for
each Transparency Service it was successfully Registered.

The arrows indicate the flow of information. For example,
Credentials are used to produce Signed Statements and the
Expand Down Expand Up @@ -461,16 +487,6 @@ Table of Contents

Figure 1: 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.
Expand Down

0 comments on commit 52fd5b5

Please sign in to comment.