Skip to content

Commit

Permalink
Script updating gh-pages from 176ea67. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Aug 20, 2024
1 parent dc68ea8 commit 72387e2
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 16 deletions.
16 changes: 8 additions & 8 deletions draft-ietf-acme-onion.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1038,7 +1038,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Misell</td>
<td class="center">Expires 20 February 2025</td>
<td class="center">Expires 21 February 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1051,12 +1051,12 @@
<dd class="internet-draft">draft-ietf-acme-onion-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-08-19" class="published">19 August 2024</time>
<time datetime="2024-08-20" class="published">20 August 2024</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-02-20">20 February 2025</time></dd>
<dd class="expires"><time datetime="2025-02-21">21 February 2025</time></dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1102,7 +1102,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 20 February 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 21 February 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1352,19 +1352,19 @@ <h4 id="name-existing-dns-01-challenge">
<h4 id="name-existing-http-01-challenge">
<a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-existing-http-01-challenge" class="section-name selfRef">Existing "http-01" Challenge</a>
</h4>
<p id="section-3.1.2-1">The "http-01" challenge is defined as in <span><a href="https://rfc-editor.org/rfc/rfc8555#section-8.3" class="relref">Section 8.3</a> of [<a href="#RFC8555" class="cite xref">RFC8555</a>]</span> can be used to validate a
<p id="section-3.1.2-1">The "http-01" challenge as defined in <span><a href="https://rfc-editor.org/rfc/rfc8555#section-8.3" class="relref">Section 8.3</a> of [<a href="#RFC8555" class="cite xref">RFC8555</a>]</span> can be used to validate a
".onion" Special-Use Domain Names, with the modifications defined in this standard, namely
<a href="#client-auth" class="internal xref">Client authentication to hidden services</a> and <a href="#caa" class="internal xref">Certification Authority Authorization (CAA)</a>.<a href="#section-3.1.2-1" class="pilcrow"></a></p>
<a href="#client-auth" class="internal xref">Client authentication to hidden services</a>, and <a href="#caa" class="internal xref">Certification Authority Authorization (CAA)</a>.<a href="#section-3.1.2-1" class="pilcrow"></a></p>
<p id="section-3.1.2-2">The ACME server <span class="bcp14">SHOULD</span> follow redirects; note that these <span class="bcp14">MAY</span> be redirects to
non ".onion" services, and the server <span class="bcp14">SHOULD</span> honour these.<a href="#section-3.1.2-2" class="pilcrow"></a></p>
</section>
<section id="section-3.1.3">
<h4 id="name-existing-tls-alpn-01-challe">
<a href="#section-3.1.3" class="section-number selfRef">3.1.3. </a><a href="#name-existing-tls-alpn-01-challe" class="section-name selfRef">Existing "tls-alpn-01" Challenge</a>
</h4>
<p id="section-3.1.3-1">The "tls-alpn-01" challenge is defined as in <span>[<a href="#RFC8737" class="cite xref">RFC8737</a>]</span> can be used to validate a ".onion"
<p id="section-3.1.3-1">The "tls-alpn-01" challenge as defined in <span>[<a href="#RFC8737" class="cite xref">RFC8737</a>]</span> can be used to validate a ".onion"
Special-Use Domain Names, with the modifications defined in this standard, namely
<a href="#client-auth" class="internal xref">Client authentication to hidden services</a> and <a href="#caa" class="internal xref">Certification Authority Authorization (CAA)</a>.<a href="#section-3.1.3-1" class="pilcrow"></a></p>
<a href="#client-auth" class="internal xref">Client authentication to hidden services</a>, and <a href="#caa" class="internal xref">Certification Authority Authorization (CAA)</a>.<a href="#section-3.1.3-1" class="pilcrow"></a></p>
</section>
</section>
<section id="section-3.2">
Expand Down
16 changes: 8 additions & 8 deletions draft-ietf-acme-onion.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@

Automated Certificate Management Environment Q. Misell, Ed.
Internet-Draft AS207960
Intended status: Standards Track 19 August 2024
Expires: 20 February 2025
Intended status: Standards Track 20 August 2024
Expires: 21 February 2025


Automated Certificate Management Environment (ACME) Extensions for
Expand Down Expand Up @@ -44,7 +44,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 20 February 2025.
This Internet-Draft will expire on 21 February 2025.

Copyright Notice

Expand Down Expand Up @@ -169,21 +169,21 @@ Table of Contents

3.1.2. Existing "http-01" Challenge

The "http-01" challenge is defined as in Section 8.3 of [RFC8555] can
be used to validate a ".onion" Special-Use Domain Names, with the
The "http-01" challenge as defined in Section 8.3 of [RFC8555] can be
used to validate a ".onion" Special-Use Domain Names, with the
modifications defined in this standard, namely Client authentication
to hidden services and Certification Authority Authorization (CAA).
to hidden services, and Certification Authority Authorization (CAA).

The ACME server SHOULD follow redirects; note that these MAY be
redirects to non ".onion" services, and the server SHOULD honour
these.

3.1.3. Existing "tls-alpn-01" Challenge

The "tls-alpn-01" challenge is defined as in [RFC8737] can be used to
The "tls-alpn-01" challenge as defined in [RFC8737] can be used to
validate a ".onion" Special-Use Domain Names, with the modifications
defined in this standard, namely Client authentication to hidden
services and Certification Authority Authorization (CAA).
services, and Certification Authority Authorization (CAA).

3.2. New "onion-csr-01" Challenge

Expand Down

0 comments on commit 72387e2

Please sign in to comment.