Skip to content

Commit

Permalink
Script updating gh-pages from 543b2ba. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Sep 9, 2024
1 parent a995cf2 commit 86b8f7c
Show file tree
Hide file tree
Showing 2 changed files with 65 additions and 64 deletions.
38 changes: 19 additions & 19 deletions pb/considerations1/draft-ietf-oauth-status-list.html
Original file line number Diff line number Diff line change
Expand Up @@ -1738,9 +1738,9 @@ <h3 id="name-status-list-token-in-cwt-fo">
d28453a20126106e7374617475736c6973742b637774a1044231325866a602782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f310173
68747470733a2f2f6578616d706c652e636f6d061a648c5bea041a8898dfea19fffe
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840532d8d
038fcab4b27f1c8af7f0803d1ae99d9e37bcaa361d9cf943e9d1bde44b74ca07f08f
2e015ba1a942c6ae120d5c1620a296e234596aac7e9e7c865b2303
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d584078d72d
61a8370c0d13bab153a897573fd750f277eee9f574ef36c53c11b2c85c1215654a7a
df1bf964337a0d4de58687d33718e3c8a9ddcbda57e49fc82b5001
</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 @@ -1766,12 +1766,12 @@ <h3 id="name-status-list-token-in-cwt-fo">
747301636c73744a78dadbb9 # "ts\x01clstJxÚÛ¹"
18000217015d # "\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
532d8d038fcab4b27f1c8af7 # "S-\x8d\x03\x8fÊ´²\x7f\x1c\x8a÷"
f0803d1ae99d9e37bcaa361d # "ð\x80=\x1aé\x9d\x9e7¼ª6\x1d"
9cf943e9d1bde44b74ca07f0 # "\x9cùCéѽäKtÊ\x07ð"
8f2e015ba1a942c6ae120d5c # "\x8f.\x01[¡©BÆ®\x12\x0d\"
1620a296e234596aac7e9e7c # "\x16 ¢\x96â4Yj¬~\x9e|"
865b2303 # "\x86[#\x03"
78d72d61a8370c0d13bab153 # "x×-a¨7\x0c\x0d\x13º±S"
a897573fd750f277eee9f574 # "¨\x97W?×Pòwîéõt"
ef36c53c11b2c85c1215654a # "ï6Å&lt;\x11²È\\x12\x15eJ"
7adf1bf964337a0d4de58687 # "zß\x1bùd3z\x0dMå\x86\x87"
d33718e3c8a9ddcbda57e49f # "Ó7\x18ãÈ©ÝËÚWä\x9f"
c82b5001 # "È+P\x01"
</pre><a href="#section-5.2-11" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -1876,9 +1876,9 @@ <h3 id="name-referenced-token-in-cwt-for">
d28443a10126a1044231325866a502653132333435017368747470733a2f2f657861
6d706c652e636f6d061a648c5bea041a8898dfea19ffffa16b7374617475735f6c69
7374a2636964780063757269782168747470733a2f2f6578616d706c652e636f6d2f
7374617475736c697374732f315840406128c987f6cfc475b04702fe622fd59208d4
37fa6ab2fe4ff1202589a160343611886f3adaccf2766418df5ab3ac35f138894ffd
2650ab99e36c6d10499b79
7374617475736c697374732f315840a259fa15c206d5201087ded75063f1865713b5
0542f3893fffb0ca50f7ae0ca7b5974edd5289062ff9e06afe789941d33a13a68b84
1973964a320e8ba7673281
</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 @@ -1903,12 +1903,12 @@ <h3 id="name-referenced-token-in-cwt-for">
2e636f6d2f7374617475736c # ".com/statusl"
697374732f31 # "ists/1"
58 40 # bytes(64)
406128c987f6cfc475b04702 # "@a(É\x87öÏÄu°G\x02"
fe622fd59208d437fa6ab2fe # "þb/Õ\x92\x08Ô7új²þ"
4ff1202589a160343611886f # "Oñ %\x89¡`46\x11\x88o"
3adaccf2766418df5ab3ac35 # ":ÚÌòvd\x18ßZ³¬5"
f138894ffd2650ab99e36c6d # "ñ8\x89Oý&amp;P«\x99ãlm"
10499b79 # "\x10I\x9by"
a259fa15c206d5201087ded7 # "¢Yú\x15Â\x06Õ \x10\x87Þ×"
5063f1865713b50542f3893f # "Pcñ\x86W\x13µ\x05Bó\x89?"
ffb0ca50f7ae0ca7b5974edd # "ÿ°ÊP÷®\x0c§µ\x97NÝ"
5289062ff9e06afe789941d3 # "R\x89\x06/ùàjþx\x99AÓ"
3a13a68b841973964a320e8b # ":\x13¦\x8b\x84\x19s\x96J2\x0e\x8b"
a7673281 # "§g2\x81"
</pre><a href="#section-6.3-8" class="pilcrow"></a>
</div>
</section>
Expand Down Expand Up @@ -2209,7 +2209,7 @@ <h2 id="name-security-considerations">
<h3 id="name-correct-decoding-and-parsin">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-correct-decoding-and-parsin" class="section-name selfRef">Correct decoding and parsing of the encoded status list</a>
</h3>
<p id="section-11.1-1">Implementers should be particularly careful for the correct parsing and decoding of the status list. Incorrect implementations may check the index on the wrong data or misscalculate the bit and byte index leading to an erroneous status of the Referenced Token. Beware, that bits are indexed (bit order) from least signicant bit to most significant bit (also called "right to left") while bytes are indexed (byte order) in their natural incrementing byte order (usually written for display purpose from left to write). Endianess does not apply here because each status value fits within a single byte.<a href="#section-11.1-1" class="pilcrow"></a></p>
<p id="section-11.1-1">Implementers should be particularly careful for the correct parsing and decoding of the status list. Incorrect implementations might check the index on the wrong data or miscalculate the bit and byte index leading to an erroneous status of the Referenced Token. Beware, that bits are indexed (bit order) from least significant bit to most significant bit (also called "right to left") while bytes are indexed (byte order) in their natural incrementing byte order (usually written for display purpose from left to write). Endianness does not apply here because each status value fits within a single byte.<a href="#section-11.1-1" class="pilcrow"></a></p>
<p id="section-11.1-2">Implementations shall always verify correctness using the test vectors given by this specification.<a href="#section-11.1-2" class="pilcrow"></a></p>
</section>
</div>
Expand Down
91 changes: 46 additions & 45 deletions pb/considerations1/draft-ietf-oauth-status-list.txt
Original file line number Diff line number Diff line change
Expand Up @@ -537,9 +537,9 @@ Table of Contents
d28453a20126106e7374617475736c6973742b637774a1044231325866a602782168
747470733a2f2f6578616d706c652e636f6d2f7374617475736c697374732f310173
68747470733a2f2f6578616d706c652e636f6d061a648c5bea041a8898dfea19fffe
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d5840532d8d
038fcab4b27f1c8af7f0803d1ae99d9e37bcaa361d9cf943e9d1bde44b74ca07f08f
2e015ba1a942c6ae120d5c1620a296e234596aac7e9e7c865b2303
19a8c019ffff56a2646269747301636c73744a78dadbb918000217015d584078d72d
61a8370c0d13bab153a897573fd750f277eee9f574ef36c53c11b2c85c1215654a7a
df1bf964337a0d4de58687d33718e3c8a9ddcbda57e49fc82b5001

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

Expand All @@ -563,12 +563,12 @@ d2 # tag(18)
747301636c73744a78dadbb9 # "ts\x01clstJxÚÛ¹"
18000217015d # "\x18\x00\x02\x17\x01]"
58 40 # bytes(64)
532d8d038fcab4b27f1c8af7 # "S-\x8d\x03\x8fÊ´²\x7f\x1c\x8a÷"
f0803d1ae99d9e37bcaa361d # "ð\x80=\x1aé\x9d\x9e7¼ª6\x1d"
9cf943e9d1bde44b74ca07f0 # "\x9cùCéѽäKtÊ\x07ð"
8f2e015ba1a942c6ae120d5c # "\x8f.\x01[¡©BÆ®\x12\x0d\"
1620a296e234596aac7e9e7c # "\x16 ¢\x96â4Yj¬~\x9e|"
865b2303 # "\x86[#\x03"
78d72d61a8370c0d13bab153 # "x×-a¨7\x0c\x0d\x13º±S"
a897573fd750f277eee9f574 # "¨\x97W?×Pòwîéõt"
ef36c53c11b2c85c1215654a # "ï6Å<\x11²È\\x12\x15eJ"
7adf1bf964337a0d4de58687 # "zß\x1bùd3z\x0dMå\x86\x87"
d33718e3c8a9ddcbda57e49f # "Ó7\x18ãÈ©ÝËÚWä\x9f"
c82b5001 # "È+P\x01"

6. Referenced Token

Expand Down Expand Up @@ -675,37 +675,37 @@ d2 # tag(18)
d28443a10126a1044231325866a502653132333435017368747470733a2f2f657861
6d706c652e636f6d061a648c5bea041a8898dfea19ffffa16b7374617475735f6c69
7374a2636964780063757269782168747470733a2f2f6578616d706c652e636f6d2f
7374617475736c697374732f315840406128c987f6cfc475b04702fe622fd59208d4
37fa6ab2fe4ff1202589a160343611886f3adaccf2766418df5ab3ac35f138894ffd
2650ab99e36c6d10499b79
7374617475736c697374732f315840a259fa15c206d5201087ded75063f1865713b5
0542f3893fffb0ca50f7ae0ca7b5974edd5289062ff9e06afe789941d33a13a68b84
1973964a320e8ba7673281

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)
406128c987f6cfc475b04702 # "@a(É\x87öÏÄu°G\x02"
fe622fd59208d437fa6ab2fe # "þb/Õ\x92\x08Ô7új²þ"
4ff1202589a160343611886f # "Oñ %\x89¡`46\x11\x88o"
3adaccf2766418df5ab3ac35 # ":ÚÌòvd\x18ßZ³¬5"
f138894ffd2650ab99e36c6d # "ñ8\x89Oý&P«\x99ãlm"
10499b79 # "\x10I\x9by"
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)
a259fa15c206d5201087ded7 # "¢Yú\x15Â\x06Õ \x10\x87Þ×"
5063f1865713b50542f3893f # "Pcñ\x86W\x13µ\x05Bó\x89?"
ffb0ca50f7ae0ca7b5974edd # "ÿ°ÊP÷®\x0c§µ\x97NÝ"
5289062ff9e06afe789941d3 # "R\x89\x06/ùàjþx\x99AÓ"
3a13a68b841973964a320e8b # ":\x13¦\x8b\x84\x19s\x96J2\x0e\x8b"
a7673281 # "§g2\x81"

6.4. Referenced Token in other COSE/CBOR Format

Expand Down Expand Up @@ -1003,14 +1003,15 @@ d2 # tag(18)
11.1. Correct decoding and parsing of the encoded status list

Implementers should be particularly careful for the correct parsing
and decoding of the status list. Incorrect implementations may check
the index on the wrong data or misscalculate the bit and byte index
leading to an erroneous status of the Referenced Token. Beware, that
bits are indexed (bit order) from least signicant bit to most
significant bit (also called "right to left") while bytes are indexed
(byte order) in their natural incrementing byte order (usually
written for display purpose from left to write). Endianess does not
apply here because each status value fits within a single byte.
and decoding of the status list. Incorrect implementations might
check the index on the wrong data or miscalculate the bit and byte
index leading to an erroneous status of the Referenced Token.
Beware, that bits are indexed (bit order) from least significant bit
to most significant bit (also called "right to left") while bytes are
indexed (byte order) in their natural incrementing byte order
(usually written for display purpose from left to write). Endianness
does not apply here because each status value fits within a single
byte.

Implementations shall always verify correctness using the test
vectors given by this specification.
Expand Down

0 comments on commit 86b8f7c

Please sign in to comment.