Skip to content

Commit

Permalink
Script updating gh-pages from 7824536. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jan 2, 2025
1 parent 06a7ffd commit 7851643
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 17 deletions.
14 changes: 7 additions & 7 deletions jag-uk/23-async-operations-locators/draft-ietf-scitt-scrapi.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1046,11 +1046,11 @@
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">SCRAPI</td>
<td class="right">December 2024</td>
<td class="right">January 2025</td>
</tr></thead>
<tfoot><tr>
<td class="left">Birkholz &amp; Geater</td>
<td class="center">Expires 4 July 2025</td>
<td class="center">Expires 6 July 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1063,12 +1063,12 @@
<dd class="internet-draft">draft-ietf-scitt-scrapi-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-12-31" class="published">31 December 2024</time>
<time datetime="2025-01-02" class="published">2 January 2025</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-07-04">4 July 2025</time></dd>
<dd class="expires"><time datetime="2025-07-06">6 July 2025</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1122,7 +1122,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 4 July 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 6 July 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand All @@ -1131,7 +1131,7 @@ <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
</h2>
<p id="section-boilerplate.2-1">
Copyright (c) 2024 IETF Trust and the persons identified as the
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow"></a></p>
<p id="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Expand Down Expand Up @@ -1519,7 +1519,7 @@ <h5 id="name-status-202-registration-is-">
</ul>
<p id="section-2.1.2.2-5"><code>OperationID</code> is Transparency Service-specific and <span class="bcp14">MUST</span> not be used for querying status in any Transparency Service other than the one that returned it.<a href="#section-2.1.2.2-5" class="pilcrow"></a></p>
<p id="section-2.1.2.2-6">If the <code>OperationID</code> is a valid URL, it <span class="bcp14">MAY</span> be included as a <code>Location</code> header in the HTTP response.<a href="#section-2.1.2.2-6" class="pilcrow"></a></p>
<p id="section-2.1.2.2-7">Transparency Services <span class="bcp14">MAY</span> clean up old operation records to manage practical implementation concerns.
<p id="section-2.1.2.2-7">Transparency Services do not guarantee retention of operation IDs for a period of time or the entirety of its lifecycle. A Transparency <span class="bcp14">MAY</span> delete operation records and some operation IDs lookups <span class="bcp14">MAY</span> return error XYZ at one time even though they were valid in the past.
The length of validity of the <code>OperationID</code> is Transparency Service specific, but at a minimum, the Transparency Service <span class="bcp14">MUST</span> maintain a record of every running or successful operation until at least one client has fetched the completed Receipt.<a href="#section-2.1.2.2-7" class="pilcrow"></a></p>
<p id="section-2.1.2.2-8">The Transparency Service <span class="bcp14">MAY</span> include a <code>Retry-After</code> header in the HTTP response to help with polling.<a href="#section-2.1.2.2-8" class="pilcrow"></a></p>
<div class="lang-http-message sourcecode" id="section-2.1.2.2-9">
Expand Down
22 changes: 12 additions & 10 deletions jag-uk/23-async-operations-locators/draft-ietf-scitt-scrapi.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@
SCITT H. Birkholz
Internet-Draft Fraunhofer SIT
Intended status: Standards Track J. Geater
Expires: 4 July 2025 DataTrails Inc.
31 December 2024
Expires: 6 July 2025 DataTrails Inc.
2 January 2025


SCITT Reference APIs
Expand Down Expand Up @@ -50,11 +50,11 @@ 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 4 July 2025.
This Internet-Draft will expire on 6 July 2025.

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Expand Down Expand Up @@ -364,12 +364,14 @@ Table of Contents
If the OperationID is a valid URL, it MAY be included as a Location
header in the HTTP response.

Transparency Services MAY clean up old operation records to manage
practical implementation concerns. The length of validity of the
OperationID is Transparency Service specific, but at a minimum, the
Transparency Service MUST maintain a record of every running or
successful operation until at least one client has fetched the
completed Receipt.
Transparency Services do not guarantee retention of operation IDs for
a period of time or the entirety of its lifecycle. A Transparency
MAY delete operation records and some operation IDs lookups MAY
return error XYZ at one time even though they were valid in the past.
The length of validity of the OperationID is Transparency Service
specific, but at a minimum, the Transparency Service MUST maintain a
record of every running or successful operation until at least one
client has fetched the completed Receipt.

The Transparency Service MAY include a Retry-After header in the HTTP
response to help with polling.
Expand Down

0 comments on commit 7851643

Please sign in to comment.