From ee44e15c3737be0ab4debb53a87f18a6c7b16926 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Tue, 15 Oct 2024 15:07:48 +0000
Subject: [PATCH] Script updating gh-pages from d788e9f. [ci skip]

---
 steve/268/draft-ietf-scitt-architecture.html | 60 ++++++++++----------
 steve/268/draft-ietf-scitt-architecture.txt  | 43 +++++++-------
 2 files changed, 50 insertions(+), 53 deletions(-)

diff --git a/steve/268/draft-ietf-scitt-architecture.html b/steve/268/draft-ietf-scitt-architecture.html
index 4606b78..c0af9b6 100644
--- a/steve/268/draft-ietf-scitt-architecture.html
+++ b/steve/268/draft-ietf-scitt-architecture.html
@@ -22,7 +22,7 @@
 <meta content="draft-ietf-scitt-architecture-latest" name="ietf.draft">
 <!-- Generator version information:
   xml2rfc 3.23.2
-    Python 3.12.6
+    Python 3.12.7
     ConfigArgParse 1.7
     google-i18n-address 3.1.1
     intervaltree 3.1.0
@@ -1036,7 +1036,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Birkholz, et al.</td>
-<td class="center">Expires 11 April 2025</td>
+<td class="center">Expires 18 April 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1049,12 +1049,12 @@
 <dd class="internet-draft">draft-ietf-scitt-architecture-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-10-08" class="published">8 October 2024</time>
+<time datetime="2024-10-15" class="published">15 October 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-04-11">11 April 2025</time></dd>
+<dd class="expires"><time datetime="2025-04-18">18 April 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1123,7 +1123,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 11 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 18 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1558,39 +1558,37 @@ <h2 id="name-architecture-overview">
 <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 the three main roles and associated processes that comprise a Transparency Service, independent of any one use case.<a href="#section-4-3" class="pilcrow">¶</a></p>
-<ol start="1" type="1" class="normal type-1" id="section-4-4">
-<li id="section-4-4.1">
-          <p id="section-4-4.1.1">Issuers that use their credentials to create Signed Statements about Artifacts.
-Issuer Credentials are also used to verify the Signed Statements within the Transparency Service registration process, and Transparent Statements.<a href="#section-4-4.1.1" 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 id="section-4-4.2">
-          <p id="section-4-4.2.1">Transparency Services that evaluate Signed Statements against Registration Policies, using credentials to sign Receipts upon successful Registration.<a href="#section-4-4.2.1" class="pilcrow">¶</a></p>
+        <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 id="section-4-4.3">
-          <p id="section-4-4.3.1">Relying Parties that:<a href="#section-4-4.3.1" class="pilcrow">¶</a></p>
+        <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-4.3.2.1">
-              <p id="section-4-4.3.2.1.1">collect Receipts, combining them with the Signed Statements to create a Transparent Statement;<a href="#section-4-4.3.2.1.1" class="pilcrow">¶</a></p>
-</li>
-            <li class="normal" id="section-4-4.3.2.2">
-              <p id="section-4-4.3.2.2.1">retrieve Transparent Statements for analysis of Statements about Artifacts;<a href="#section-4-4.3.2.2.1" class="pilcrow">¶</a></p>
+<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-4.3.2.3">
-              <p id="section-4-4.3.2.3.1">uses credentials to authenticate the Signed Statement and the Receipts of the Transparent Statement (e.g. verification);<a href="#section-4-4.3.2.3.1" class="pilcrow">¶</a></p>
+            <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-4.3.2.4">
-              <p id="section-4-4.3.2.4.1">replay a series of Transparent Statements checking for the consistency of the Transparency Service's Append-only Log (e.g. auditing)<a href="#section-4-4.3.2.4.1" class="pilcrow">¶</a></p>
+            <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>
-      </ol>
-<p id="section-4-5">In addition, <a href="#fig-concept-relationship" class="auto internal xref">Figure 1</a> illustrates multiple Transparency Services and multiple Receipts as a single Signed Statement <span class="bcp14">MAY</span> be registered with one or more Transparency Service.
-Each Transparency Service produces a Receipt, which may be aggregated in a single Transparent Statement, demonstrating the Signed Statement was registered by multiple Transparency Services.<a href="#section-4-5" class="pilcrow">¶</a></p>
-<p id="section-4-6">The arrows indicate the flow of information.<a href="#section-4-6" class="pilcrow">¶</a></p>
+      </ul>
+<p id="section-4-6">In addition, <a href="#fig-concept-relationship" class="auto internal xref">Figure 1</a> illustrates multiple Transparency Services and multiple Receipts as a single Signed Statement <span class="bcp14">MAY</span> be registered with one or more Transparency Service.
+Each Transparency Service produces a Receipt, which may be aggregated in a single Transparent Statement, demonstrating the Signed Statement was registered by multiple Transparency Services.<a href="#section-4-6" class="pilcrow">¶</a></p>
+<p id="section-4-7">The arrows indicate the flow of information.<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-7.1">
-          <div class="alignLeft art-svg artwork" id="section-4-7.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>
@@ -1739,14 +1737,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-7.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-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">
@@ -2408,7 +2406,7 @@ <h3 id="name-normative-references">
 <dd class="break"></dd>
 <dt id="I-D.draft-ietf-cose-merkle-tree-proofs">[I-D.draft-ietf-cose-merkle-tree-proofs]</dt>
         <dd>
-<span class="refAuthor">Steele, O.</span>, <span class="refAuthor">Birkholz, H.</span>, <span class="refAuthor">Delignat-Lavaud, A.</span>, and <span class="refAuthor">C. Fournet</span>, <span class="refTitle">"COSE Receipts"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-cose-merkle-tree-proofs-05</span>, <time datetime="2024-06-18" class="refDate">18 June 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-cose-merkle-tree-proofs-05">https://datatracker.ietf.org/doc/html/draft-ietf-cose-merkle-tree-proofs-05</a>&gt;</span>. </dd>
+<span class="refAuthor">Steele, O.</span>, <span class="refAuthor">Birkholz, H.</span>, <span class="refAuthor">Delignat-Lavaud, A.</span>, and <span class="refAuthor">C. Fournet</span>, <span class="refTitle">"COSE Receipts"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-cose-merkle-tree-proofs-06</span>, <time datetime="2024-10-09" class="refDate">9 October 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-cose-merkle-tree-proofs-06">https://datatracker.ietf.org/doc/html/draft-ietf-cose-merkle-tree-proofs-06</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="IANA.cwt">[IANA.cwt]</dt>
         <dd>
diff --git a/steve/268/draft-ietf-scitt-architecture.txt b/steve/268/draft-ietf-scitt-architecture.txt
index 42be078..c7e9586 100644
--- a/steve/268/draft-ietf-scitt-architecture.txt
+++ b/steve/268/draft-ietf-scitt-architecture.txt
@@ -5,13 +5,13 @@
 SCITT                                                        H. Birkholz
 Internet-Draft                                            Fraunhofer SIT
 Intended status: Standards Track                      A. Delignat-Lavaud
-Expires: 11 April 2025                                        C. Fournet
+Expires: 18 April 2025                                        C. Fournet
                                                       Microsoft Research
                                                             Y. Deshpande
                                                                      ARM
                                                                S. Lasker
                                                               DataTrails
-                                                          8 October 2024
+                                                         15 October 2024
 
 
  An Architecture for Trustworthy and Transparent Digital Supply Chains
@@ -66,7 +66,7 @@ Status of This Memo
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on 11 April 2025.
+   This Internet-Draft will expire on 18 April 2025.
 
 Copyright Notice
 
@@ -406,29 +406,28 @@ Table of Contents
    that comprise a Transparency Service, independent of any one use
    case.
 
-   1.  Issuers that use their credentials to create Signed Statements
-       about Artifacts.  Issuer Credentials are also used to verify the
-       Signed Statements within the Transparency Service registration
-       process, and Transparent Statements.
+   This section describes the three main roles and associated processes
+   in SCITT:
 
-   2.  Transparency Services that evaluate Signed Statements against
-       Registration Policies, using credentials to sign Receipts upon
-       successful Registration.
+   *  Issuers that use their credentials to create Signed Statements
+      about Artifacts
 
-   3.  Relying Parties that:
+   *  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.
 
-       *  collect Receipts, combining them with the Signed Statements to
-          create a Transparent Statement;
+   *  Relying Parties that:
 
-       *  retrieve Transparent Statements for analysis of Statements
-          about Artifacts;
+      -  collect Receipts of Signed Statements for subsequent
+         registration of Transparent Statements;
 
-       *  uses credentials to authenticate the Signed Statement and the
-          Receipts of the Transparent Statement (e.g. verification);
+      -  retrieve Transparent Statements for analysis of Statements
+         about Artifacts themselves (e.g. verification);
 
-       *  replay a series of Transparent Statements checking for the
-          consistency of the Transparency Service's Append-only Log
-          (e.g. auditing)
+      -  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 multiple Transparency Services and
    multiple Receipts as a single Signed Statement MAY be registered with
@@ -1299,9 +1298,9 @@ Table of Contents
    [I-D.draft-ietf-cose-merkle-tree-proofs]
               Steele, O., Birkholz, H., Delignat-Lavaud, A., and C.
               Fournet, "COSE Receipts", Work in Progress, Internet-
-              Draft, draft-ietf-cose-merkle-tree-proofs-05, 18 June
+              Draft, draft-ietf-cose-merkle-tree-proofs-06, 9 October
               2024, <https://datatracker.ietf.org/doc/html/draft-ietf-
-              cose-merkle-tree-proofs-05>.
+              cose-merkle-tree-proofs-06>.
 
    [IANA.cwt] IANA, "CBOR Web Token (CWT) Claims",
               <https://www.iana.org/assignments/cwt>.