Skip to content

Commit

Permalink
Script updating gh-pages from 61acdaf. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jul 5, 2024
1 parent a1ff0bf commit 64800e9
Show file tree
Hide file tree
Showing 2 changed files with 51 additions and 52 deletions.
51 changes: 25 additions & 26 deletions c2bo/batch-fetching/draft-ietf-oauth-status-list.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,10 @@
This specification defines status list data structures and processing rules for representing the status of tokens secured by JSON Object Signing and Encryption (JOSE) or CBOR Object Signing and Encryption(COSE), such as JSON Web Tokens (JWTs), CBOR Web Tokens (CWTs) and ISO mdoc.
The status list token data structures themselves are also represented as JWTs or CWTs.
" name="description">
<meta content="xml2rfc 3.21.0" name="generator">
<meta content="xml2rfc 3.22.0" name="generator">
<meta content="draft-ietf-oauth-status-list-latest" name="ietf.draft">
<!-- Generator version information:
xml2rfc 3.21.0
xml2rfc 3.22.0
Python 3.12.3
ConfigArgParse 1.7
google-i18n-address 3.1.0
Expand All @@ -25,9 +25,8 @@
platformdirs 4.2.2
pycountry 22.3.5
PyYAML 6.0.1
requests 2.31.0
requests 2.32.3
setuptools 69.5.1
six 1.16.0
wcwidth 0.2.13
-->
<link href="draft-ietf-oauth-status-list.xml" rel="alternate" type="application/rfc+xml">
Expand Down Expand Up @@ -1027,11 +1026,11 @@
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">Token Status List</td>
<td class="right">June 2024</td>
<td class="right">July 2024</td>
</tr></thead>
<tfoot><tr>
<td class="left">Looker, et al.</td>
<td class="center">Expires 13 December 2024</td>
<td class="center">Expires 6 January 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1044,12 +1043,12 @@
<dd class="internet-draft">draft-ietf-oauth-status-list-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-06-11" class="published">11 June 2024</time>
<time datetime="2024-07-05" class="published">5 July 2024</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Informational</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2024-12-13">13 December 2024</time></dd>
<dd class="expires"><time datetime="2025-01-06">6 January 2025</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1101,7 +1100,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 13 December 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 6 January 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1209,7 +1208,7 @@ <h2 id="name-copyright-notice">
</ul>
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
<p id="section-toc.1-1.9.1"><a href="#section-9" class="auto internal xref">9</a>.  <a href="#name-batch-fetching" class="internal xref">Batch Fetching</a></p>
<p id="section-toc.1-1.9.1"><a href="#section-9" class="auto internal xref">9</a>.  <a href="#name-status-list-aggregation" class="internal xref">Status List Aggregation</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="auto internal xref">9.1</a>.  <a href="#name-issuer-metadata" class="internal xref">Issuer Metadata</a></p>
Expand Down Expand Up @@ -1535,7 +1534,7 @@ <h3 id="name-status-list-in-json-format">
<p id="section-4.1-2.1.2.2.1"><code>lst</code>: <span class="bcp14">REQUIRED</span>. JSON String that contains the status values for all the Referenced Tokens it conveys statuses for. The value <span class="bcp14">MUST</span> be the base64url-encoded (as defined in Section 2 of <span>[<a href="#RFC7515" class="cite xref">RFC7515</a>]</span>) Status List as specified in <a href="#status-list" class="auto internal xref">Section 4</a>.<a href="#section-4.1-2.1.2.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4.1-2.1.2.3">
<p id="section-4.1-2.1.2.3.1"><code>aggregation_uri</code>: <span class="bcp14">OPTIONAL</span>. JSON String that contains an URI to retrieve a the Status List Aggregation for this credential type. See section <a href="#batch-fetching" class="auto internal xref">Section 9</a> for further detail.<a href="#section-4.1-2.1.2.3.1" class="pilcrow"></a></p>
<p id="section-4.1-2.1.2.3.1"><code>aggregation_uri</code>: <span class="bcp14">OPTIONAL</span>. JSON String that contains an URI to retrieve the Status List Aggregation for this type of Referenced Token. See section <a href="#batch-fetching" class="auto internal xref">Section 9</a> for further detail.<a href="#section-4.1-2.1.2.3.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
Expand Down Expand Up @@ -1570,7 +1569,7 @@ <h3 id="name-status-list-in-cbor-format">
<p id="section-4.2-2.1.2.2.1"><code>lst</code>: <span class="bcp14">REQUIRED</span>. Byte string (Major Type 2) that contains the Status List as specified in <a href="#status-list-json" class="auto internal xref">Section 4.1</a>.<a href="#section-4.2-2.1.2.2.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="section-4.2-2.1.2.3">
<p id="section-4.2-2.1.2.3.1"><code>aggregation_uri</code>: <span class="bcp14">OPTIONAL</span>. Text string (Major Type 3) that contains an URI to retrieve the Status List Aggregation for this credential type. See section <a href="#batch-fetching" class="auto internal xref">Section 9</a> for further detail.<a href="#section-4.2-2.1.2.3.1" class="pilcrow"></a></p>
<p id="section-4.2-2.1.2.3.1"><code>aggregation_uri</code>: <span class="bcp14">OPTIONAL</span>. Text string (Major Type 3) that contains an URI to retrieve the Status List Aggregation for this type of Referenced Token. See section <a href="#batch-fetching" class="auto internal xref">Section 9</a> for further detail.<a href="#section-4.2-2.1.2.3.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
Expand Down Expand Up @@ -1733,9 +1732,9 @@ <h3 id="name-status-list-token-in-cwt-fo">
d28453a20126106e7374617475736c6973742b637774a1044231325866a602782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f310173
68747470733a2f2f6578616d706c652e636f6d061a648c5bea041a8898dfea19fffe
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840acef50
5dbbbcb0ecb2c63526d6fdbac99e9575e82be5970b99d36464cd1677efc4e92ab987
c01371f1d0a1ccc62a4b2186a14a589a1ce22e0b111abe5c0b3eaf
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840ef2f61
5f6dcf9990d68e14839b93307ef35a4e566477cef3a1c076eb2259e279774d0bbe31
16ee68912deb47992cbbd02ca22c902de16bfdd320d009bd5c22fc
</pre><a href="#section-5.2-9" class="pilcrow"></a>
</div>
<p id="section-5.2-10">The following is the CBOR diagnostic output of the example above:<a href="#section-5.2-10" class="pilcrow"></a></p>
Expand All @@ -1761,12 +1760,12 @@ <h3 id="name-status-list-token-in-cwt-fo">
747301636c73744a78dadbb9 # "ts\x01clstJxÚÛ¹"
18000217015d # "\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
acef505dbbbcb0ecb2c63526 # "¬ïP]»¼°ì²Æ5&amp;"
d6fdbac99e9575e82be5970b # "ÖýºÉ\x9e\x95uè+å\x97\x0b"
99d36464cd1677efc4e92ab9 # "\x99ÓddÍ\x16wïÄé*¹"
87c01371f1d0a1ccc62a4b21 # "\x87À\x13qñСÌÆ*K!"
86a14a589a1ce22e0b111abe # "\x86¡JX\x9a\x1câ.\x0b\x11\x1a¾"
5c0b3eaf # "\\x0b&gt;¯"
ef2f615f6dcf9990d68e1483 # "ï/a_mÏ\x99\x90Ö\x8e\x14\x83"
9b93307ef35a4e566477cef3 # "\x9b\x930~óZNVdwÎó"
a1c076eb2259e279774d0bbe # "¡Àvë"YâywM\x0b¾"
3116ee68912deb47992cbbd0 # "1\x16îh\x91-ëG\x99,»Ð"
2ca22c902de16bfdd320d009 # ",¢,\x90-ákýÓ Ð\x09"
bd5c22fc # "½\"ü"
</pre><a href="#section-5.2-11" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -2008,10 +2007,10 @@ <h3 id="name-validation-rules">
</div>
<div id="batch-fetching">
<section id="section-9">
<h2 id="name-batch-fetching">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-batch-fetching" class="section-name selfRef">Batch Fetching</a>
<h2 id="name-status-list-aggregation">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-status-list-aggregation" class="section-name selfRef">Status List Aggregation</a>
</h2>
<p id="section-9-1">To allow a Relying Party to fetch all Status Lists for a specific Referenced Token or issuer, an optional mechanism is provided to retrieve a list of URIs to all Status List Tokens called Status List Aggregation. This mechanism is intended to support fetching and caching mechanisms and allow offline validation of the status.<a href="#section-9-1" class="pilcrow"></a></p>
<p id="section-9-1">Status List Aggregation is an optional mechanism to retrieve a list of URIs to all Status List Tokens, allowing a Relying Party to fetch all relevant Status Lists for a specific type of Referenced Token or issuer. This mechanism is intended to support fetching and caching mechanisms and allow offline validation of the status.<a href="#section-9-1" class="pilcrow"></a></p>
<p id="section-9-2">There are two options for a Relying Party to retrieve the Status List Aggregation.
An issuer <span class="bcp14">MAY</span> support any of these mechanisms:<a href="#section-9-2" class="pilcrow"></a></p>
<ul class="normal">
Expand All @@ -2036,7 +2035,7 @@ <h3 id="name-issuer-metadata">
<h3 id="name-status-list-parameter">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-status-list-parameter" class="section-name selfRef">Status List Parameter</a>
</h3>
<p id="section-9.2-1">The URI to the Status List Aggregation <span class="bcp14">MAY</span> be provided as the optional parameter <code>aggregation_uri</code> in the Status List itself as explained in<a href="#status-list-cbor" class="auto internal xref">Section 4.2</a> and <a href="#status-list-json" class="auto internal xref">Section 4.1</a> respectively. A Relying Party may use this link to retrieve an up-to-date list of relevant Status Lists.<a href="#section-9.2-1" class="pilcrow"></a></p>
<p id="section-9.2-1">The URI to the Status List Aggregation <span class="bcp14">MAY</span> be provided as the optional parameter <code>aggregation_uri</code> in the Status List itself as explained in<a href="#status-list-cbor" class="auto internal xref">Section 4.2</a> and <a href="#status-list-json" class="auto internal xref">Section 4.1</a> respectively. A Relying Party may use this URI to retrieve an up-to-date list of relevant Status Lists.<a href="#section-9.2-1" class="pilcrow"></a></p>
</section>
</div>
<div id="status-list-aggregation-in-json-format">
Expand All @@ -2047,7 +2046,7 @@ <h3 id="name-status-list-aggregation-in-">
<p id="section-9.3-1">This section defines the structure for a JSON-encoded Status List Aggregation:<a href="#section-9.3-1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-9.3-2.1">
<p id="section-9.3-2.1.1"><code>status_lists</code>: <span class="bcp14">REQUIRED</span>. The <code>status_lists</code> claim <span class="bcp14">MUST</span> be an array of strings, each containing an URI to a Status List (Token).<a href="#section-9.3-2.1.1" class="pilcrow"></a></p>
<p id="section-9.3-2.1.1"><code>status_lists</code>: <span class="bcp14">REQUIRED</span>. JSON array of strings that contains URIs linking to Status List (Tokens).<a href="#section-9.3-2.1.1" class="pilcrow"></a></p>
</li>
</ul>
<p id="section-9.3-3">The Status List Aggregation URI provides a list of Status List URIs. This aggregation in JSON and the media type return <span class="bcp14">SHOULD</span> be <code>application/json</code>. A Relying Party can iterate through this list and fetch all Status List Tokens before encountering the specific URI in a Referenced Token.<a href="#section-9.3-3" class="pilcrow"></a></p>
Expand Down
52 changes: 26 additions & 26 deletions c2bo/batch-fetching/draft-ietf-oauth-status-list.txt
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@
Network Working Group T. Looker
Internet-Draft MATTR
Intended status: Informational P. Bastian
Expires: 13 December 2024
Expires: 6 January 2025
C. Bormann
11 June 2024
5 July 2024


Token Status List
Expand Down Expand Up @@ -49,7 +49,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 13 December 2024.
This Internet-Draft will expire on 6 January 2025.

Copyright Notice

Expand Down Expand Up @@ -89,7 +89,7 @@ Table of Contents
8.1. Status List Request
8.2. Status List Response
8.3. Validation Rules
9. Batch Fetching
9. Status List Aggregation
9.1. Issuer Metadata
9.2. Status List Parameter
9.3. Status List Aggregation in JSON Format
Expand Down Expand Up @@ -346,8 +346,8 @@ Table of Contents
[RFC7515]) Status List as specified in Section 4.

- aggregation_uri: OPTIONAL. JSON String that contains an URI to
retrieve a the Status List Aggregation for this credential
type. See section Section 9 for further detail.
retrieve the Status List Aggregation for this type of
Referenced Token. See section Section 9 for further detail.

The following example illustrates the JSON representation of the
Status List:
Expand Down Expand Up @@ -375,8 +375,8 @@ Table of Contents

- aggregation_uri: OPTIONAL. Text string (Major Type 3) that
contains an URI to retrieve the Status List Aggregation for
this credential type. See section Section 9 for further
detail.
this type of Referenced Token. See section Section 9 for
further detail.

The following example illustrates the CBOR representation of the
Status List:
Expand Down Expand Up @@ -533,9 +533,9 @@ Table of Contents
d28453a20126106e7374617475736c6973742b637774a1044231325866a602782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f310173
68747470733a2f2f6578616d706c652e636f6d061a648c5bea041a8898dfea19fffe
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840acef50
5dbbbcb0ecb2c63526d6fdbac99e9575e82be5970b99d36464cd1677efc4e92ab987
c01371f1d0a1ccc62a4b2186a14a589a1ce22e0b111abe5c0b3eaf
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840ef2f61
5f6dcf9990d68e14839b93307ef35a4e566477cef3a1c076eb2259e279774d0bbe31
16ee68912deb47992cbbd02ca22c902de16bfdd320d009bd5c22fc

The following is the CBOR diagnostic output of the example above:

Expand All @@ -559,12 +559,12 @@ d2 # tag(18)
747301636c73744a78dadbb9 # "ts\x01clstJxÚÛ¹"
18000217015d # "\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
acef505dbbbcb0ecb2c63526 # "¬ïP]»¼°ì²Æ5&"
d6fdbac99e9575e82be5970b # "ÖýºÉ\x9e\x95uè+å\x97\x0b"
99d36464cd1677efc4e92ab9 # "\x99ÓddÍ\x16wïÄé*¹"
87c01371f1d0a1ccc62a4b21 # "\x87À\x13qñСÌÆ*K!"
86a14a589a1ce22e0b111abe # "\x86¡JX\x9a\x1câ.\x0b\x11\x1a¾"
5c0b3eaf # "\\x0b>¯"
ef2f615f6dcf9990d68e1483 # "ï/a_mÏ\x99\x90Ö\x8e\x14\x83"
9b93307ef35a4e566477cef3 # "\x9b\x930~óZNVdwÎó"
a1c076eb2259e279774d0bbe # "¡Àvë"YâywM\x0b¾"
3116ee68912deb47992cbbd0 # "1\x16îh\x91-ëG\x99,»Ð"
2ca22c902de16bfdd320d009 # ",¢,\x90-ákýÓ Ð\x09"
bd5c22fc # "½\"ü"

6. Referenced Token

Expand Down Expand Up @@ -803,13 +803,13 @@ d2 # tag(18)

TBD

9. Batch Fetching
9. Status List Aggregation

To allow a Relying Party to fetch all Status Lists for a specific
Referenced Token or issuer, an optional mechanism is provided to
retrieve a list of URIs to all Status List Tokens called Status List
Aggregation. This mechanism is intended to support fetching and
caching mechanisms and allow offline validation of the status.
Status List Aggregation is an optional mechanism to retrieve a list
of URIs to all Status List Tokens, allowing a Relying Party to fetch
all relevant Status Lists for a specific type of Referenced Token or
issuer. This mechanism is intended to support fetching and caching
mechanisms and allow offline validation of the status.

There are two options for a Relying Party to retrieve the Status List
Aggregation. An issuer MAY support any of these mechanisms:
Expand Down Expand Up @@ -837,16 +837,16 @@ d2 # tag(18)
The URI to the Status List Aggregation MAY be provided as the
optional parameter aggregation_uri in the Status List itself as
explained inSection 4.2 and Section 4.1 respectively. A Relying
Party may use this link to retrieve an up-to-date list of relevant
Party may use this URI to retrieve an up-to-date list of relevant
Status Lists.

9.3. Status List Aggregation in JSON Format

This section defines the structure for a JSON-encoded Status List
Aggregation:

* status_lists: REQUIRED. The status_lists claim MUST be an array
of strings, each containing an URI to a Status List (Token).
* status_lists: REQUIRED. JSON array of strings that contains URIs
linking to Status List (Tokens).

The Status List Aggregation URI provides a list of Status List URIs.
This aggregation in JSON and the media type return SHOULD be
Expand Down

0 comments on commit 64800e9

Please sign in to comment.