Skip to content

Commit

Permalink
Script updating gh-pages from 3c7c5fe. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Nov 7, 2023
1 parent 9e26bf0 commit 647ab8e
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 17 deletions.
16 changes: 8 additions & 8 deletions draft-pauly-v6ops-happy-eyeballs-v3.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1047,7 +1047,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Pauly, et al.</td>
<td class="center">Expires 9 May 2024</td>
<td class="center">Expires 10 May 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1060,12 +1060,12 @@
<dd class="internet-draft">draft-pauly-v6ops-happy-eyeballs-v3-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2023-11-06" class="published">6 November 2023</time>
<time datetime="2023-11-07" class="published">7 November 2023</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-05-09">9 May 2024</time></dd>
<dd class="expires"><time datetime="2024-05-10">10 May 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1131,7 +1131,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 9 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 10 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1595,7 +1595,7 @@ <h3 id="name-determining-successful-conn">
to establish a connection, some cryptographic handshakes may be dependent on
ServiceMode SVCB RRs and could impose limitations on establishing a connection.
For instance, ECH-capable clients may become SVCB-reliant clients
(<span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12#section-3" class="relref">Section 3</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span>) when SVCB RRs contain the
(<span><a href="https://rfc-editor.org/rfc/rfc9460#section-3" class="relref">Section 3</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span>) when SVCB RRs contain the
"ech" SvcParamKey <span>[<a href="#ECH" class="cite xref">ECH</a>]</span>. If the client is either an SVCB-reliant client or a
SVCB-optional client that might switch to SVCB-reliant connection
establishment during the process, the client <span class="bcp14">MUST</span> wait for SVCB RRs before
Expand All @@ -1610,7 +1610,7 @@ <h3 id="name-handling-application-layer-">
<p id="section-6.2-1">The <code>alpn</code> and <code>no-default-alpn</code> SvcParamKeys in SVCB RRs indicate the
"SVCB ALPN set," which specifies the underlying transport protocols supported
by the associated service endpoint. When the client requests SVCB RRs, it
<span class="bcp14">SHOULD</span> perform the procedure specified in <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12#section-7.1.2" class="relref">Section 7.1.2</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span> to determine
<span class="bcp14">SHOULD</span> perform the procedure specified in <span><a href="https://rfc-editor.org/rfc/rfc9460#section-7.1.2" class="relref">Section 7.1.2</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span> to determine
the underlying transport protocols that both the client and the service endpoint
support. The client <span class="bcp14">SHOULD NOT</span> attempt to make a connection to a service
endpoint whose SVCB ALPN set does not contain any protocols that the client
Expand All @@ -1629,7 +1629,7 @@ <h3 id="name-handling-application-layer-">
<p id="section-6.2-4">If the client is an HTTP client that supports both Alt-Svc <span>[<a href="#AltSvc" class="cite xref">AltSvc</a>]</span>
and SVCB (HTTPS) RRs, the client <span class="bcp14">SHOULD</span> ensure that connection attempts are
consistent with both the Alt-Svc parameters and the SVCB ALPN set, as specified
in <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12#section-9.3" class="relref">Section 9.3</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span>.<a href="#section-6.2-4" class="pilcrow"></a></p>
in <span><a href="https://rfc-editor.org/rfc/rfc9460#section-9.3" class="relref">Section 9.3</a> of [<a href="#SVCB" class="cite xref">SVCB</a>]</span>.<a href="#section-6.2-4" class="pilcrow"></a></p>
</section>
</div>
</section>
Expand Down Expand Up @@ -1958,7 +1958,7 @@ <h3 id="name-normative-references">
<dd class="break"></dd>
<dt id="SVCB">[SVCB]</dt>
<dd>
<span class="refAuthor">Schwartz, B. M.</span>, <span class="refAuthor">Bishop, M.</span>, and <span class="refAuthor">E. Nygren</span>, <span class="refTitle">"Service binding and parameter specification via the DNS (DNS SVCB and HTTPS RRs)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-dnsop-svcb-https-12</span>, <time datetime="2023-03-11" class="refDate">11 March 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12">https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12</a>&gt;</span>. </dd>
<span class="refAuthor">Schwartz, B.</span>, <span class="refAuthor">Bishop, M.</span>, and <span class="refAuthor">E. Nygren</span>, <span class="refTitle">"Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)"</span>, <span class="seriesInfo">RFC 9460</span>, <span class="seriesInfo">DOI 10.17487/RFC9460</span>, <time datetime="2023-11" class="refDate">November 2023</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9460">https://www.rfc-editor.org/rfc/rfc9460</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="SVCB-ECH">[SVCB-ECH]</dt>
<dd>
Expand Down
16 changes: 7 additions & 9 deletions draft-pauly-v6ops-happy-eyeballs-v3.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@
Network Working Group T. Pauly
Internet-Draft Apple Inc
Intended status: Informational D. Schinazi
Expires: 9 May 2024 N. Jaju
Expires: 10 May 2024 N. Jaju
K. Ishibashi
Google LLC
6 November 2023
7 November 2023


Happy Eyeballs Version 3: Better Connectivity Using Concurrency
Expand Down Expand Up @@ -55,7 +55,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 9 May 2024.
This Internet-Draft will expire on 10 May 2024.

Copyright Notice

Expand Down Expand Up @@ -737,12 +737,10 @@ Table of Contents
DOI 10.17487/RFC9000, May 2021,
<https://www.rfc-editor.org/rfc/rfc9000>.

[SVCB] Schwartz, B. M., Bishop, M., and E. Nygren, "Service
binding and parameter specification via the DNS (DNS SVCB
and HTTPS RRs)", Work in Progress, Internet-Draft, draft-
ietf-dnsop-svcb-https-12, 11 March 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-
svcb-https-12>.
[SVCB] Schwartz, B., Bishop, M., and E. Nygren, "Service Binding
and Parameter Specification via the DNS (SVCB and HTTPS
Resource Records)", RFC 9460, DOI 10.17487/RFC9460,
November 2023, <https://www.rfc-editor.org/rfc/rfc9460>.

[SVCB-ECH] Schwartz, B. M., Bishop, M., and E. Nygren, "Bootstrapping
TLS Encrypted ClientHello with DNS Service Bindings", Work
Expand Down

0 comments on commit 647ab8e

Please sign in to comment.