Skip to content

Commit

Permalink
Script updating gh-pages from a8c1b44. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Dec 18, 2024
1 parent 4ea9fa7 commit 2b0d72a
Show file tree
Hide file tree
Showing 2 changed files with 77 additions and 77 deletions.
60 changes: 30 additions & 30 deletions unlinability/draft-ietf-oauth-status-list.html
Original file line number Diff line number Diff line change
Expand Up @@ -15,15 +15,15 @@
<meta content="draft-ietf-oauth-status-list-latest" name="ietf.draft">
<!-- Generator version information:
xml2rfc 3.25.0
Python 3.12.7
Python 3.12.8
ConfigArgParse 1.7
google-i18n-address 3.1.1
intervaltree 3.1.0
Jinja2 3.1.4
lxml 5.3.0
platformdirs 4.3.6
pycountry 22.3.5
PyYAML 6.0.1
pycountry 24.6.1
PyYAML 6.0.2
requests 2.32.3
setuptools 70.3.0
wcwidth 0.2.13
Expand Down Expand Up @@ -1049,7 +1049,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Looker, et al.</td>
<td class="center">Expires 18 June 2025</td>
<td class="center">Expires 21 June 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1062,12 +1062,12 @@
<dd class="internet-draft">draft-ietf-oauth-status-list-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-12-15" class="published">15 December 2024</time>
<time datetime="2024-12-18" class="published">18 December 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="2025-06-18">18 June 2025</time></dd>
<dd class="expires"><time datetime="2025-06-21">21 June 2025</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1119,7 +1119,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 18 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 21 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1836,9 +1836,9 @@ <h3 id="name-status-list-token-in-cwt-fo">
d28453a20126106e7374617475736c6973742b637774a1044231325850a502782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f31061a
648c5bea041a8898dfea19fffe19a8c019fffda2646269747301636c73744a78dadb
b918000217015d5840f505609ab6804b99bae3a9f64a4f5963d4873c43da7b48d5bd
b8b40c37e94d73e35551b8a76ec4c00af4d3d2101a2c84016d6c9f169e1cfb6542fe
ebefbf5097
b918000217015d58403170929b906c89d7d7f6f818e7d97cf478f0e6525ce7763bad
af42798024f8ba0b491c8e1501130bf8f1e5d5a0e5e6388da786d1c8234dd415be0d
4997776a3c
</pre><a href="#section-5.2-9" class="pilcrow"></a>
</div>
<p id="section-5.2-10">The following is the CBOR Annotated Hex output of the example above:<a href="#section-5.2-10" class="pilcrow"></a></p>
Expand All @@ -1862,12 +1862,12 @@ <h3 id="name-status-list-token-in-cwt-fo">
6269747301636c73744a78da # "bits\x01clstJxÚ"
dbb918000217015d # "Û¹\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
f505609ab6804b99bae3a9f6 # "õ\x05`\x9a¶\x80K\x99ºã©ö"
4a4f5963d4873c43da7b48d5 # "JOYcÔ\x87&lt;CÚ{HÕ"
bdb8b40c37e94d73e35551b8 # "½¸´\x0c7éMsãUQ¸"
a76ec4c00af4d3d2101a2c84 # "§nÄÀ\x0aôÓÒ\x10\x1a,\x84"
016d6c9f169e1cfb6542feeb # "\x01ml\x9f\x16\x9e\x1cûeBþë"
efbf5097 # "ï¿P\x97"
3170929b906c89d7d7f6f818 # "1p\x92\x9b\x90l\x89××öø\x18"
e7d97cf478f0e6525ce7763b # "çÙ|ôxðæR\çv;"
adaf42798024f8ba0b491c8e # "\xad¯By\x80$øº\x0bI\x1c\x8e"
1501130bf8f1e5d5a0e5e638 # "\x15\x01\x13\x0bøñåÕ\xa0åæ8"
8da786d1c8234dd415be0d49 # "\x8d§\x86ÑÈ#MÔ\x15¾\x0dI"
97776a3c # "\x97wj&lt;"
</pre><a href="#section-5.2-11" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -2009,9 +2009,9 @@ <h3 id="name-referenced-token-in-cose">
d28443a10126a1044231325866a502653132333435017368747470733a2f2f657861
6d706c652e636f6d061a648c5bea041a8898dfea19ffffa16b7374617475735f6c69
7374a2636964780063757269782168747470733a2f2f6578616d706c652e636f6d2f
7374617475736c697374732f3158406edc3e70cec3073dac35dd024fac3798eb860c
f1b32b32281c51a5e0d7416566e90a8c469463cf533d11979f0c5a81df9cdab166ad
1ce0e746ce977d78d61255
7374617475736c697374732f315840125c9f3d8f5b41c7c04cf5d47393ddb4b3b080
a3e93a1a5d156555b815e75f626dedbef73e6503abb68b7b01fb39e07d348a568f3f
97c69122f1563ea73dfcd6
</pre><a href="#section-6.3-6" class="pilcrow"></a>
</div>
<p id="section-6.3-7">The following is the CBOR Annotated Hex output of the example above:<a href="#section-6.3-7" class="pilcrow"></a></p>
Expand All @@ -2036,12 +2036,12 @@ <h3 id="name-referenced-token-in-cose">
2e636f6d2f7374617475736c # ".com/statusl"
697374732f31 # "ists/1"
58 40 # bytes(64)
6edc3e70cec3073dac35dd02 # "nÜ&gt;pÎÃ\x07=¬5Ý\x02"
4fac3798eb860cf1b32b3228 # "O¬7\x98ë\x86\x0cñ³+2("
1c51a5e0d7416566e90a8c46 # "\x1cQ¥à×Aefé\x0a\x8cF"
9463cf533d11979f0c5a81df # "\x94cÏS=\x11\x97\x9f\x0cZ\x81ß"
9cdab166ad1ce0e746ce977d # "\x9cÚ±f\xad\x1càçFÎ\x97}"
78d61255 # "xÖ\x12U"
125c9f3d8f5b41c7c04cf5d4 # "\x12\\x9f=\x8f[AÇÀLõÔ"
7393ddb4b3b080a3e93a1a5d # "s\x93Ý´³°\x80£é:\x1a]"
156555b815e75f626dedbef7 # "\x15eU¸\x15ç_bmí¾÷"
3e6503abb68b7b01fb39e07d # "&gt;e\x03«¶\x8b{\x01û9à}"
348a568f3f97c69122f1563e # "4\x8aV\x8f?\x97Æ\x91"ñV&gt;"
a73dfcd6 # "§=üÖ"
</pre><a href="#section-6.3-8" class="pilcrow"></a>
</div>
<p id="section-6.3-9">ISO mdoc <span>[<a href="#ISO.mdoc" class="cite xref">ISO.mdoc</a>]</span> may utilize the Status List mechanism by introducing the <code>status</code> parameter in the Mobile Security Object (MSO) as specified in Section 9.1.2. The <code>status</code> parameter uses the same encoding as a CWT as defined in <a href="#referenced-token-cose" class="auto internal xref">Section 6.3</a>.<a href="#section-6.3-9" class="pilcrow"></a></p>
Expand Down Expand Up @@ -2262,8 +2262,8 @@ <h3 id="name-status-list-request">
yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
nR0bCI6NDMyMDB9.cW5GlrWnnjC904yxOq-YgrvXd3jkvcyGDe8c3jPiB5hcWX0Posb2
dCh_1ZJbScJxURq_FSggLXzvE9bmSaWUaQ
nR0bCI6NDMyMDB9.HHYK_DrIsdDxh73uvZIvGlFn1BzuXyW4QlCmq6xW54FI3VyolTRW
ShxoRfKPKWdcC0sSS54GdqmEKfOT9zX1Cg
</pre><a href="#section-8.1-10" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -2369,8 +2369,8 @@ <h3 id="name-historical-resolution">
yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
nR0bCI6NDMyMDB9.cW5GlrWnnjC904yxOq-YgrvXd3jkvcyGDe8c3jPiB5hcWX0Posb2
dCh_1ZJbScJxURq_FSggLXzvE9bmSaWUaQ
nR0bCI6NDMyMDB9.HHYK_DrIsdDxh73uvZIvGlFn1BzuXyW4QlCmq6xW54FI3VyolTRW
ShxoRfKPKWdcC0sSS54GdqmEKfOT9zX1Cg
</pre><a href="#section-8.4-7" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -2640,7 +2640,7 @@ <h3 id="name-unlinkability">
<h4 id="name-colluding-relying-parties">
<a href="#section-12.5.1" class="section-number selfRef">12.5.1. </a><a href="#name-colluding-relying-parties" class="section-name selfRef">Colluding Relying Parties</a>
</h4>
<p id="section-12.5.1-1">Two or more colluding Relying Parties may link two transaction involving the same Referenced Tokens by comparing the status claims of received Referenced Tokens, and therefore determine that they have interacted with the same Holder.<a href="#section-12.5.1-1" class="pilcrow"></a></p>
<p id="section-12.5.1-1">Two or more colluding Relying Parties may link two transactions involving the same Referenced Token by comparing the status claims of received Referenced Tokens, and therefore determine that they have interacted with the same Holder.<a href="#section-12.5.1-1" class="pilcrow"></a></p>
<p id="section-12.5.1-2">To avoid privacy risks for colluding Relying Parties, it is <span class="bcp14">RECOMMENDED</span> that Issuers use batch issuance to issue multiple Referenced Tokens, see <a href="#implementation-lifecycle" class="auto internal xref">Section 13.1</a>. To avoid further correlatable information by the values of <code>uri</code> and <code>index</code>, Status Issuers are <span class="bcp14">RECOMMENDED</span> to:<a href="#section-12.5.1-2" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="section-12.5.1-3.1">
Expand Down
94 changes: 47 additions & 47 deletions unlinability/draft-ietf-oauth-status-list.txt
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@
Network Working Group T. Looker
Internet-Draft MATTR
Intended status: Informational P. Bastian
Expires: 18 June 2025
Expires: 21 June 2025
C. Bormann
Robert Bosch GmbH
15 December 2024
18 December 2024


Token Status List
Expand Down Expand Up @@ -50,7 +50,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 18 June 2025.
This Internet-Draft will expire on 21 June 2025.

Copyright Notice

Expand Down Expand Up @@ -593,9 +593,9 @@ Table of Contents
d28453a20126106e7374617475736c6973742b637774a1044231325850a502782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f31061a
648c5bea041a8898dfea19fffe19a8c019fffda2646269747301636c73744a78dadb
b918000217015d5840f505609ab6804b99bae3a9f64a4f5963d4873c43da7b48d5bd
b8b40c37e94d73e35551b8a76ec4c00af4d3d2101a2c84016d6c9f169e1cfb6542fe
ebefbf5097
b918000217015d58403170929b906c89d7d7f6f818e7d97cf478f0e6525ce7763bad
af42798024f8ba0b491c8e1501130bf8f1e5d5a0e5e6388da786d1c8234dd415be0d
4997776a3c

The following is the CBOR Annotated Hex output of the example above:

Expand All @@ -617,12 +617,12 @@ d2 # tag(18)
6269747301636c73744a78da # "bits\x01clstJxÚ"
dbb918000217015d # "Û¹\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
f505609ab6804b99bae3a9f6 # "õ\x05`\x9a¶\x80K\x99ºã©ö"
4a4f5963d4873c43da7b48d5 # "JOYcÔ\x87<CÚ{HÕ"
bdb8b40c37e94d73e35551b8 # "½¸´\x0c7éMsãUQ¸"
a76ec4c00af4d3d2101a2c84 # "§nÄÀ\x0aôÓÒ\x10\x1a,\x84"
016d6c9f169e1cfb6542feeb # "\x01ml\x9f\x16\x9e\x1cûeBþë"
efbf5097 # "ï¿P\x97"
3170929b906c89d7d7f6f818 # "1p\x92\x9b\x90l\x89××öø\x18"
e7d97cf478f0e6525ce7763b # "çÙ|ôxðæR\çv;"
adaf42798024f8ba0b491c8e # "\xad¯By\x80$øº\x0bI\x1c\x8e"
1501130bf8f1e5d5a0e5e638 # "\x15\x01\x13\x0bøñåÕ\xa0åæ8"
8da786d1c8234dd415be0d49 # "\x8d§\x86ÑÈ#MÔ\x15¾\x0dI"
97776a3c # "\x97wj<"

6. Referenced Token

Expand Down Expand Up @@ -767,37 +767,37 @@ d2 # tag(18)
d28443a10126a1044231325866a502653132333435017368747470733a2f2f657861
6d706c652e636f6d061a648c5bea041a8898dfea19ffffa16b7374617475735f6c69
7374a2636964780063757269782168747470733a2f2f6578616d706c652e636f6d2f
7374617475736c697374732f3158406edc3e70cec3073dac35dd024fac3798eb860c
f1b32b32281c51a5e0d7416566e90a8c469463cf533d11979f0c5a81df9cdab166ad
1ce0e746ce977d78d61255
7374617475736c697374732f315840125c9f3d8f5b41c7c04cf5d47393ddb4b3b080
a3e93a1a5d156555b815e75f626dedbef73e6503abb68b7b01fb39e07d348a568f3f
97c69122f1563ea73dfcd6

The following is the CBOR Annotated Hex output of the example above:

d2 # tag(18)
84 # array(4)
43 # bytes(3)
a10126 # "¡\x01&"
a1 # map(1)
04 # uint(4)
42 # bytes(2)
3132 # "12"
58 66 # bytes(102)
a50265313233343501736874 # "¥\x02e12345\x01sht"
7470733a2f2f6578616d706c # "tps://exampl"
652e636f6d061a648c5bea04 # "e.com\x06\x1ad\x8c[ê\x04"
1a8898dfea19ffffa16b7374 # "\x1a\x88\x98ßê\x19ÿÿ¡kst"
617475735f6c697374a26369 # "atus_list¢ci"
647800637572697821687474 # "dx\x00curix!htt"
70733a2f2f6578616d706c65 # "ps://example"
2e636f6d2f7374617475736c # ".com/statusl"
697374732f31 # "ists/1"
58 40 # bytes(64)
6edc3e70cec3073dac35dd02 # "nÜ>pÎÃ\x07=¬5Ý\x02"
4fac3798eb860cf1b32b3228 # "O¬7\x98ë\x86\x0cñ³+2("
1c51a5e0d7416566e90a8c46 # "\x1cQ¥à×Aefé\x0a\x8cF"
9463cf533d11979f0c5a81df # "\x94cÏS=\x11\x97\x9f\x0cZ\x81ß"
9cdab166ad1ce0e746ce977d # "\x9cÚ±f\xad\x1càçFÎ\x97}"
78d61255 # "xÖ\x12U"
d2 # tag(18)
84 # array(4)
43 # bytes(3)
a10126 # "¡\x01&"
a1 # map(1)
04 # uint(4)
42 # bytes(2)
3132 # "12"
58 66 # bytes(102)
a50265313233343501736874 # "¥\x02e12345\x01sht"
7470733a2f2f6578616d706c # "tps://exampl"
652e636f6d061a648c5bea04 # "e.com\x06\x1ad\x8c[ê\x04"
1a8898dfea19ffffa16b7374 # "\x1a\x88\x98ßê\x19ÿÿ¡kst"
617475735f6c697374a26369 # "atus_list¢ci"
647800637572697821687474 # "dx\x00curix!htt"
70733a2f2f6578616d706c65 # "ps://example"
2e636f6d2f7374617475736c # ".com/statusl"
697374732f31 # "ists/1"
58 40 # bytes(64)
125c9f3d8f5b41c7c04cf5d4 # "\x12\\x9f=\x8f[AÇÀLõÔ"
7393ddb4b3b080a3e93a1a5d # "s\x93Ý´³°\x80£é:\x1a]"
156555b815e75f626dedbef7 # "\x15eU¸\x15ç_bmí¾÷"
3e6503abb68b7b01fb39e07d # ">e\x03«¶\x8b{\x01û9à}"
348a568f3f97c69122f1563e # "4\x8aV\x8f?\x97Æ\x91"ñV>"
a73dfcd6 # "§=üÖ"

ISO mdoc [ISO.mdoc] may utilize the Status List mechanism by
introducing the status parameter in the Mobile Security Object (MSO)
Expand Down Expand Up @@ -1032,8 +1032,8 @@ d2 # tag(18)
yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
nR0bCI6NDMyMDB9.cW5GlrWnnjC904yxOq-YgrvXd3jkvcyGDe8c3jPiB5hcWX0Posb2
dCh_1ZJbScJxURq_FSggLXzvE9bmSaWUaQ
nR0bCI6NDMyMDB9.HHYK_DrIsdDxh73uvZIvGlFn1BzuXyW4QlCmq6xW54FI3VyolTRW
ShxoRfKPKWdcC0sSS54GdqmEKfOT9zX1Cg

8.2. Status List Response

Expand Down Expand Up @@ -1170,8 +1170,8 @@ d2 # tag(18)
yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
nR0bCI6NDMyMDB9.cW5GlrWnnjC904yxOq-YgrvXd3jkvcyGDe8c3jPiB5hcWX0Posb2
dCh_1ZJbScJxURq_FSggLXzvE9bmSaWUaQ
nR0bCI6NDMyMDB9.HHYK_DrIsdDxh73uvZIvGlFn1BzuXyW4QlCmq6xW54FI3VyolTRW
ShxoRfKPKWdcC0sSS54GdqmEKfOT9zX1Cg

9. Status List Aggregation

Expand Down Expand Up @@ -1455,9 +1455,9 @@ d2 # tag(18)

12.5.1. Colluding Relying Parties

Two or more colluding Relying Parties may link two transaction
involving the same Referenced Tokens by comparing the status claims
of received Referenced Tokens, and therefore determine that they have
Two or more colluding Relying Parties may link two transactions
involving the same Referenced Token by comparing the status claims of
received Referenced Tokens, and therefore determine that they have
interacted with the same Holder.

To avoid privacy risks for colluding Relying Parties, it is
Expand Down

0 comments on commit 2b0d72a

Please sign in to comment.