Skip to content

Commit 8667c37

Browse files
author
ID Bot
committed
Script updating gh-pages from b3ade9f. [ci skip]
1 parent 33f1541 commit 8667c37

3 files changed

Lines changed: 91 additions & 115 deletions

File tree

‎draft-ietf-anima-rfc8366bis.html‎

Lines changed: 49 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@
3434
Jinja2 3.1.6
3535
lxml 6.1.1
3636
natsort 8.4.0
37-
platformdirs 4.10.0
37+
platformdirs 4.10.1
3838
pycountry 24.6.1
3939
PyYAML 6.0.3
4040
requests 2.33.1
@@ -1061,7 +1061,7 @@
10611061
</tr></thead>
10621062
<tfoot><tr>
10631063
<td class="left">Watsen, et al.</td>
1064-
<td class="center">Expires 6 January 2027</td>
1064+
<td class="center">Expires 19 January 2027</td>
10651065
<td class="right">[Page]</td>
10661066
</tr></tfoot>
10671067
</table>
@@ -1080,12 +1080,12 @@
10801080
<a href="https://www.rfc-editor.org/rfc/rfc8995" class="eref">8995</a> (if approved)</dd>
10811081
<dt class="label-published">Published:</dt>
10821082
<dd class="published">
1083-
<time datetime="2026-07-05" class="published">5 July 2026</time>
1083+
<time datetime="2026-07-18" class="published">18 July 2026</time>
10841084
</dd>
10851085
<dt class="label-intended-status">Intended Status:</dt>
10861086
<dd class="intended-status">Standards Track</dd>
10871087
<dt class="label-expires">Expires:</dt>
1088-
<dd class="expires"><time datetime="2027-01-06">6 January 2027</time></dd>
1088+
<dd class="expires"><time datetime="2027-01-19">19 January 2027</time></dd>
10891089
<dt class="label-authors">Authors:</dt>
10901090
<dd class="authors">
10911091
<div class="author">
@@ -1160,7 +1160,7 @@ <h2 id="name-status-of-this-memo">
11601160
time. It is inappropriate to use Internet-Drafts as reference
11611161
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
11621162
<p id="section-boilerplate.1-4">
1163-
This Internet-Draft will expire on 6 January 2027.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
1163+
This Internet-Draft will expire on 19 January 2027.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
11641164
</section>
11651165
</div>
11661166
<div id="copyright">
@@ -2529,7 +2529,7 @@ <h3 id="name-voucher-extensions">
25292529
The name <span class="bcp14">MUST</span> be the same as the YANG extension module name.
25302530
The '<code>extensions</code>' list Attribute allows for new standard extensions to be defined without changes to the '<code>ietf-voucher</code>' YANG module.
25312531
Items within that list are either strings (in JSON serialization), or integers (in CBOR serialization using SIDs);
2532-
both are always defined in the entries of the Voucher Extensions Registry (see <a href="#voucher-ext-reg" class="auto internal xref">Section 12.5</a>).<a href="#section-8.5-5" class="pilcrow"></a></p>
2532+
both are always defined in the entries of the Voucher Extensions registry (see <a href="#voucher-ext-reg" class="auto internal xref">Section 12.5</a>).<a href="#section-8.5-5" class="pilcrow"></a></p>
25332533
<p id="section-8.5-6">Extensions are full YANG modules, which are subject to the SID allocation process described in <span>[<a href="#RFC9254" class="cite xref">RFC9254</a>]</span>.
25342534
When an extension is serialized, the extension is placed in a sub-map in the value of a new key/value pair in the '<code>voucher</code>' container element.
25352535
In JSON serialization, the corresponding key is the name of the extension, prefixed by the string "extension:".
@@ -3162,36 +3162,33 @@ <h3 id="name-the-yang-module-names-regis">
31623162
</dl>
31633163
</li>
31643164
</ul>
3165-
<p id="section-12.2-3">This reference should be updated to point to this document and the "File" entry should be updated to point to the
3166-
new module revision in <a href="#voucher-yang-module" class="auto internal xref">Section 8.3</a>.<a href="#section-12.2-3" class="pilcrow"></a></p>
31673165
<ul class="normal ulEmpty">
3168-
<li class="normal ulEmpty" id="section-12.2-4.1">
3169-
<span class="break"></span><dl class="dlCompact dlParallel" id="section-12.2-4.1.1">
3170-
<dt id="section-12.2-4.1.1.1">name:</dt>
3171-
<dd style="margin-left: 1.5em" id="section-12.2-4.1.1.2">
3172-
<p id="section-12.2-4.1.1.2.1">ietf-voucher-request<a href="#section-12.2-4.1.1.2.1" class="pilcrow"></a></p>
3166+
<li class="normal ulEmpty" id="section-12.2-3.1">
3167+
<span class="break"></span><dl class="dlCompact dlParallel" id="section-12.2-3.1.1">
3168+
<dt id="section-12.2-3.1.1.1">name:</dt>
3169+
<dd style="margin-left: 1.5em" id="section-12.2-3.1.1.2">
3170+
<p id="section-12.2-3.1.1.2.1">ietf-voucher-request<a href="#section-12.2-3.1.1.2.1" class="pilcrow"></a></p>
31733171
</dd>
31743172
<dd class="break"></dd>
3175-
<dt id="section-12.2-4.1.1.3">namespace:</dt>
3176-
<dd style="margin-left: 1.5em" id="section-12.2-4.1.1.4">
3177-
<p id="section-12.2-4.1.1.4.1">urn:ietf:params:xml:ns:yang:ietf-voucher-request<a href="#section-12.2-4.1.1.4.1" class="pilcrow"></a></p>
3173+
<dt id="section-12.2-3.1.1.3">namespace:</dt>
3174+
<dd style="margin-left: 1.5em" id="section-12.2-3.1.1.4">
3175+
<p id="section-12.2-3.1.1.4.1">urn:ietf:params:xml:ns:yang:ietf-voucher-request<a href="#section-12.2-3.1.1.4.1" class="pilcrow"></a></p>
31783176
</dd>
31793177
<dd class="break"></dd>
3180-
<dt id="section-12.2-4.1.1.5">prefix:</dt>
3181-
<dd style="margin-left: 1.5em" id="section-12.2-4.1.1.6">
3182-
<p id="section-12.2-4.1.1.6.1">vcr<a href="#section-12.2-4.1.1.6.1" class="pilcrow"></a></p>
3178+
<dt id="section-12.2-3.1.1.5">prefix:</dt>
3179+
<dd style="margin-left: 1.5em" id="section-12.2-3.1.1.6">
3180+
<p id="section-12.2-3.1.1.6.1">vcr<a href="#section-12.2-3.1.1.6.1" class="pilcrow"></a></p>
31833181
</dd>
31843182
<dd class="break"></dd>
3185-
<dt id="section-12.2-4.1.1.7">reference:</dt>
3186-
<dd style="margin-left: 1.5em" id="section-12.2-4.1.1.8">
3187-
<p id="section-12.2-4.1.1.8.1">RFC 8995<a href="#section-12.2-4.1.1.8.1" class="pilcrow"></a></p>
3183+
<dt id="section-12.2-3.1.1.7">reference:</dt>
3184+
<dd style="margin-left: 1.5em" id="section-12.2-3.1.1.8">
3185+
<p id="section-12.2-3.1.1.8.1">RFC 8995<a href="#section-12.2-3.1.1.8.1" class="pilcrow"></a></p>
31883186
</dd>
31893187
<dd class="break"></dd>
31903188
</dl>
31913189
</li>
31923190
</ul>
3193-
<p id="section-12.2-5">This reference should be updated to point to this document and the "File" entry should be updated to point to the new module revision in <a href="#voucher-request-yang-module" class="auto internal xref">Section 9.2</a>.
3194-
Please note the change to the "prefix" field.<a href="#section-12.2-5" class="pilcrow"></a></p>
3191+
<p id="section-12.2-4">(Please note the change to the "prefix" field)<a href="#section-12.2-4" class="pilcrow"></a></p>
31953192
</section>
31963193
</div>
31973194
<div id="vcj">
@@ -3321,59 +3318,49 @@ <h3 id="name-the-smi-security-for-s-mime">
33213318
<h3 id="name-the-voucher-extensions-regi">
33223319
<a href="#section-12.5" class="section-number selfRef">12.5. </a><a href="#name-the-voucher-extensions-regi" class="section-name selfRef">The Voucher Extensions Registry</a>
33233320
</h3>
3324-
<p id="section-12.5-1">IANA is asked to create a registry of Voucher extensions as follows:<a href="#section-12.5-1" class="pilcrow"></a></p>
3321+
<p id="section-12.5-1">IANA is asked to create a registry of Voucher extensions within the <em>Bootstrapping Remote Secure Key Infrastructures (BRSKI) Parameters</em> as follows.<a href="#section-12.5-1" class="pilcrow"></a></p>
3322+
<p id="section-12.5-2">The name is: Voucher Extensions, and the Registration Policy is Expert Review.<a href="#section-12.5-2" class="pilcrow"></a></p>
33253323
<ul class="normal ulEmpty">
3326-
<li class="normal ulEmpty" id="section-12.5-2.1">
3327-
<span class="break"></span><dl class="dlCompact dlParallel" id="section-12.5-2.1.1">
3328-
<dt id="section-12.5-2.1.1.1">Registry name:</dt>
3329-
<dd style="margin-left: 1.5em" id="section-12.5-2.1.1.2">
3330-
<p id="section-12.5-2.1.1.2.1">Voucher Extensions Registry<a href="#section-12.5-2.1.1.2.1" class="pilcrow"></a></p>
3324+
<li class="normal ulEmpty" id="section-12.5-3.1">
3325+
<span class="break"></span><dl class="dlCompact dlParallel" id="section-12.5-3.1.1">
3326+
<dt id="section-12.5-3.1.1.1">Reference:</dt>
3327+
<dd style="margin-left: 1.5em" id="section-12.5-3.1.1.2">
3328+
<p id="section-12.5-3.1.1.2.1">an optional document<a href="#section-12.5-3.1.1.2.1" class="pilcrow"></a></p>
33313329
</dd>
33323330
<dd class="break"></dd>
3333-
<dt id="section-12.5-2.1.1.3">Registry policy:</dt>
3334-
<dd style="margin-left: 1.5em" id="section-12.5-2.1.1.4">
3335-
<p id="section-12.5-2.1.1.4.1">Expert Review<a href="#section-12.5-2.1.1.4.1" class="pilcrow"></a></p>
3331+
<dt id="section-12.5-3.1.1.3">Extension name:</dt>
3332+
<dd style="margin-left: 1.5em" id="section-12.5-3.1.1.4">
3333+
<p id="section-12.5-3.1.1.4.1">UTF-8-encoded string, not to exceed 40 characters.<a href="#section-12.5-3.1.1.4.1" class="pilcrow"></a></p>
33363334
</dd>
33373335
<dd class="break"></dd>
3338-
<dt id="section-12.5-2.1.1.5">Reference:</dt>
3339-
<dd style="margin-left: 1.5em" id="section-12.5-2.1.1.6">
3340-
<p id="section-12.5-2.1.1.6.1">an optional document<a href="#section-12.5-2.1.1.6.1" class="pilcrow"></a></p>
3341-
</dd>
3342-
<dd class="break"></dd>
3343-
<dt id="section-12.5-2.1.1.7">Extension name:</dt>
3344-
<dd style="margin-left: 1.5em" id="section-12.5-2.1.1.8">
3345-
<p id="section-12.5-2.1.1.8.1">UTF-8-encoded string, not to exceed 40 characters.<a href="#section-12.5-2.1.1.8.1" class="pilcrow"></a></p>
3346-
</dd>
3347-
<dd class="break"></dd>
3348-
<dt id="section-12.5-2.1.1.9">Extension SID:</dt>
3349-
<dd style="margin-left: 1.5em" id="section-12.5-2.1.1.10">
3350-
<p id="section-12.5-2.1.1.10.1">the YANG module SID value that defines the extension per <a href="#voucher-ext" class="auto internal xref">Section 8.5</a>.<a href="#section-12.5-2.1.1.10.1" class="pilcrow"></a></p>
3336+
<dt id="section-12.5-3.1.1.5">Extension SID:</dt>
3337+
<dd style="margin-left: 1.5em" id="section-12.5-3.1.1.6">
3338+
<p id="section-12.5-3.1.1.6.1">the YANG module SID value that defines the extension per <a href="#voucher-ext" class="auto internal xref">Section 8.5</a>.<a href="#section-12.5-3.1.1.6.1" class="pilcrow"></a></p>
33513339
</dd>
33523340
<dd class="break"></dd>
33533341
</dl>
33543342
</li>
33553343
</ul>
3356-
<p id="section-12.5-3">Each extension <span class="bcp14">MUST</span> follow the rules specified in this specification.
3357-
As is usual, the IANA issues early allocations in accordance with <span>[<a href="#RFC7120" class="cite xref">RFC7120</a>]</span>.<a href="#section-12.5-3" class="pilcrow"></a></p>
3358-
<p id="section-12.5-4">Note that the SID module value is allocated as part of a <span>[<a href="#CORESID" class="cite xref">CORESID</a>]</span> process.
3344+
<p id="section-12.5-4">Each extension <span class="bcp14">MUST</span> follow the rules specified in this specification.<a href="#section-12.5-4" class="pilcrow"></a></p>
3345+
<p id="section-12.5-5">Note that the SID module value is allocated as part of a <span>[<a href="#CORESID" class="cite xref">CORESID</a>]</span> process.
33593346
This may be from a SID range managed by IANA, or from any other MegaRange.
33603347
Future work may allow for PEN based allocations.
3361-
IANA does not need to separately allocate a SID value for this column.<a href="#section-12.5-4" class="pilcrow"></a></p>
3362-
<p id="section-12.5-5">Extension name strings for standards track documents are single words, given by the YANG Module Name.
3363-
They do not contain dots.
3364-
For vendor proprietary extensions, the string <span class="bcp14">SHOULD</span> be made unique by putting the extension name in the form a fully-qualified domain name (FQDN) <span>[<a href="#RFC3696" class="cite xref">RFC3696</a>]</span>, such as "fuubar.example.com"<a href="#section-12.5-5" class="pilcrow"></a></p>
3365-
<p id="section-12.5-6">Vendor proprietary extensions do not need to be registered with IANA, but vendors <span class="bcp14">MAY</span> do so.<a href="#section-12.5-6" class="pilcrow"></a></p>
3366-
<p id="section-12.5-7">Designated Experts should review for standards track documents for clarity, but the choices are tied to WG and IESG processes:<a href="#section-12.5-7" class="pilcrow"></a></p>
3348+
IANA does not need to separately allocate a SID value for this column.<a href="#section-12.5-5" class="pilcrow"></a></p>
3349+
<p id="section-12.5-6">Extension name strings for standards track documents are single words, given by the YANG Module Name. They do not contain dots.<a href="#section-12.5-6" class="pilcrow"></a></p>
3350+
<p id="section-12.5-7">For vendor proprietary extensions, the string <span class="bcp14">SHOULD</span> be made unique by putting the extension name in the form a fully-qualified domain name (FQDN) <span>[<a href="#RFC3696" class="cite xref">RFC3696</a>]</span>, such as "fuubar.example.com"<a href="#section-12.5-7" class="pilcrow"></a></p>
3351+
<p id="section-12.5-8">Vendor proprietary extensions do not need to be registered with IANA, but vendors <span class="bcp14">MAY</span> do so.<a href="#section-12.5-8" class="pilcrow"></a></p>
3352+
<p id="section-12.5-9">Designated Experts should review for standards track documents for clarity, but the choices are tied to WG and IESG processes:<a href="#section-12.5-9" class="pilcrow"></a></p>
33673353
<ul class="normal">
3368-
<li class="normal" id="section-12.5-8.1">
3369-
<p id="section-12.5-8.1.1">There are no choices in the extension names (which is always the YANG module name), or SID value (which is from another IANA process).<a href="#section-12.5-8.1.1" class="pilcrow"></a></p>
3354+
<li class="normal" id="section-12.5-10.1">
3355+
<p id="section-12.5-10.1.1">There are no choices in the extension names (which is always the YANG module name), or SID value (which is from another IANA process).<a href="#section-12.5-10.1.1" class="pilcrow"></a></p>
33703356
</li>
3371-
<li class="normal" id="section-12.5-8.2">
3372-
<p id="section-12.5-8.2.1">For non-standards track extensions, the Designated Expert should review whatever document is provided, if any.
3373-
The stability of the reference may be of concern. The Designated Expert should determine if the work overlaps with existing efforts; and if so suggest merging/coordinating.
3374-
However, as registration is optional, the Designated Expert should not block any vendor registrations.<a href="#section-12.5-8.2.1" class="pilcrow"></a></p>
3357+
<li class="normal" id="section-12.5-10.2">
3358+
<p id="section-12.5-10.2.1">For non-standards track extensions, the Designated Expert should review whatever document is provided, if any.
3359+
The stability of the reference may be of concern.<a href="#section-12.5-10.2.1" class="pilcrow"></a></p>
33753360
</li>
33763361
</ul>
3362+
<p id="section-12.5-11">The Designated Expert should determine if the work overlaps with existing efforts; and if so suggest merging/coordinating.
3363+
However, as registration is optional, the Designated Expert should not block any vendor registrations.<a href="#section-12.5-11" class="pilcrow"></a></p>
33773364
</section>
33783365
</div>
33793366
<div id="the-ietf-yang-sid-ranges-registry">
@@ -3530,10 +3517,6 @@ <h3 id="name-normative-references">
35303517
<dd>
35313518
<span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6020</span>, <span class="seriesInfo">DOI 10.17487/RFC6020</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc6020">https://www.rfc-editor.org/rfc/rfc6020</a>&gt;</span>. </dd>
35323519
<dd class="break"></dd>
3533-
<dt id="RFC7120">[RFC7120]</dt>
3534-
<dd>
3535-
<span class="refAuthor">Cotton, M.</span>, <span class="refTitle">"Early IANA Allocation of Standards Track Code Points"</span>, <span class="seriesInfo">BCP 100</span>, <span class="seriesInfo">RFC 7120</span>, <span class="seriesInfo">DOI 10.17487/RFC7120</span>, <time datetime="2014-01" class="refDate">January 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7120">https://www.rfc-editor.org/rfc/rfc7120</a>&gt;</span>. </dd>
3536-
<dd class="break"></dd>
35373520
<dt id="RFC7250">[RFC7250]</dt>
35383521
<dd>
35393522
<span class="refAuthor">Wouters, P., Ed.</span>, <span class="refAuthor">Tschofenig, H., Ed.</span>, <span class="refAuthor">Gilmore, J.</span>, <span class="refAuthor">Weiler, S.</span>, and <span class="refAuthor">T. Kivinen</span>, <span class="refTitle">"Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">RFC 7250</span>, <span class="seriesInfo">DOI 10.17487/RFC7250</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7250">https://www.rfc-editor.org/rfc/rfc7250</a>&gt;</span>. </dd>
@@ -3599,7 +3582,7 @@ <h3 id="name-informative-references">
35993582
<dd class="break"></dd>
36003583
<dt id="I-D.ietf-lake-authz">[I-D.ietf-lake-authz]</dt>
36013584
<dd>
3602-
<span class="refAuthor">Selander, G.</span>, <span class="refAuthor">Mattsson, J. P.</span>, <span class="refAuthor">Vučinić, M.</span>, <span class="refAuthor">Fedrecheski, G.</span>, and <span class="refAuthor">M. Richardson</span>, <span class="refTitle">"Lightweight Authorization using Ephemeral Diffie-Hellman Over COSE (ELA)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-lake-authz-07</span>, <time datetime="2026-03-02" class="refDate">2 March 2026</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-authz-07">https://datatracker.ietf.org/doc/html/draft-ietf-lake-authz-07</a>&gt;</span>. </dd>
3585+
<span class="refAuthor">Selander, G.</span>, <span class="refAuthor">Mattsson, J. P.</span>, <span class="refAuthor">Vučinić, M.</span>, <span class="refAuthor">Fedrecheski, G.</span>, and <span class="refAuthor">M. Richardson</span>, <span class="refTitle">"Lightweight Authorization using Ephemeral Diffie-Hellman Over COSE (ELA)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-lake-authz-08</span>, <time datetime="2026-07-06" class="refDate">6 July 2026</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-lake-authz-08">https://datatracker.ietf.org/doc/html/draft-ietf-lake-authz-08</a>&gt;</span>. </dd>
36033586
<dd class="break"></dd>
36043587
<dt id="I-D.vangeest-lamps-cms-euf-cma-signeddata">[I-D.vangeest-lamps-cms-euf-cma-signeddata]</dt>
36053588
<dd>

0 commit comments

Comments
 (0)