Skip to content

Commit

Permalink
Script updating gh-pages from 3452821. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jan 27, 2021
1 parent dd215b7 commit da76229
Show file tree
Hide file tree
Showing 13 changed files with 605 additions and 590 deletions.
105 changes: 56 additions & 49 deletions draft-ietf-quic-http.html
View file

Large diffs are not rendered by default.

88 changes: 48 additions & 40 deletions draft-ietf-quic-http.txt
View file
Expand Up @@ -4,8 +4,8 @@

QUIC M. Bishop, Ed.
Internet-Draft Akamai
Intended status: Standards Track 26 January 2021
Expires: 30 July 2021
Intended status: Standards Track 27 January 2021
Expires: 31 July 2021


Hypertext Transfer Protocol Version 3 (HTTP/3)
Expand Down Expand Up @@ -51,7 +51,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 30 July 2021.
This Internet-Draft will expire on 31 July 2021.

Copyright Notice

Expand Down Expand Up @@ -392,22 +392,13 @@ Table of Contents

The "https" scheme associates authority with possession of a
certificate that the client considers to be trustworthy for the host
identified by the authority component of the URI.

If a server presents a valid certificate and proof that it controls
the corresponding private key, then a client will accept a secured
TLS session with that server as being authoritative for all origins
with the "https" scheme and a host identified in the certificate.
The host must be listed either as the CN field of the certificate
subject or as a dNSName in the subjectAltName field of the
certificate; see [RFC6125]. For a host that is an IP address, the
client MUST verify that the address appears as an iPAddress in the
subjectAltName field of the certificate.

If the hostname or address is not present in the certificate, the
client MUST NOT consider the server authoritative for origins
containing that hostname or address. See Section 4.3 of [SEMANTICS]
for more detail on authoritative access.
identified by the authority component of the URI. Upon receiving a
server certificate in the TLS handshake, the client MUST verify that
the certificate is an acceptable match for the URI's origin server
using the process described in Section 4.3.4 of [SEMANTICS]. If the
certificate cannot be verified with respect to the URI's origin
server, the client MUST NOT consider the server authoritative for
that origin.

A client MAY attempt access to a resource with an "https" URI by
resolving the host identifier to an IP address, establishing a QUIC
Expand Down Expand Up @@ -497,12 +488,31 @@ Table of Contents

Once a connection exists to a server endpoint, this connection MAY be
reused for requests with multiple different URI authority components.
Clients SHOULD NOT open more than one HTTP/3 connection to a given
host and port pair, where the host is derived from a URI, a selected
alternative service ([ALTSVC]), or a configured proxy. A client MAY
open multiple HTTP/3 connections to the same IP address and UDP port
using different transport or TLS configurations but SHOULD avoid
creating multiple connections with the same configuration.
To use an existing connection for a new origin, clients MUST validate
the certificate presented by the server for the new origin server
using the process described in Section 4.3.4 of [SEMANTICS]. This
implies that clients will need to retain the server certificate and
any additional information needed to verify that certificate; clients
which do not do so will be unable to reuse the connection for
additional origins.

If the certificate is not acceptable with regard to the new origin
for any reason, the connection MUST NOT be reused and a new
connection SHOULD be established for the new origin. If the reason
the certificate cannot be verified might apply to other origins
already associated with the connection, the client SHOULD re-validate
the server certificate for those origins. For instance, if
validation of a certificate fails because the certificate has expired
or been revoked, this might be used to invalidate all other origins
for which that certificate was used to establish authority.

Clients SHOULD NOT open more than one HTTP/3 connection to a given IP
address and UDP port, where the IP address and port might be derived
from a URI, a selected alternative service ([ALTSVC]), a configured
proxy, or name resolution of any of these. A client MAY open
multiple HTTP/3 connections to the same IP address and UDP port using
different transport or TLS configurations but SHOULD avoid creating
multiple connections with the same configuration.

Servers are encouraged to maintain open HTTP/3 connections for as
long as possible but are permitted to terminate idle connections if
Expand All @@ -515,7 +525,7 @@ Table of Contents
A server that does not wish clients to reuse HTTP/3 connections for a
particular origin can indicate that it is not authoritative for a
request by sending a 421 (Misdirected Request) status code in
response to the request; see Section 9.1.2 of [HTTP2].
response to the request; see Section 7.4 of [SEMANTICS].

4. HTTP Request Lifecycle

Expand Down Expand Up @@ -997,7 +1007,12 @@ Table of Contents
* does not include a request body or trailer section

The server MUST include a value in the ":authority" pseudo-header
field for which the server is authoritative; see Section 3.3.
field for which the server is authoritative. If the client has not
yet validated the connection for the origin indicated by the pushed
request, it MUST perform the same verification process it would do
before sending a request for that origin on the connection; see
Section 3.3. If this verification fails, the client MUST NOT
consider the server authoritative for that origin.

Clients SHOULD send a CANCEL_PUSH frame upon receipt of a
PUSH_PROMISE frame carrying a request that is not cacheable, is not
Expand Down Expand Up @@ -2546,6 +2561,10 @@ Table of Contents

12.1. Normative References

[ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP
Alternative Services", RFC 7838, DOI 10.17487/RFC7838,
April 2016, <https://www.rfc-editor.org/info/rfc7838>.

[CACHING] Fielding, R., Nottingham, M., and J. Reschke, "HTTP
Caching", Work in Progress, Internet-Draft, draft-ietf-
httpbis-cache-14, 12 January 2021, <http://www.ietf.org/
Expand All @@ -2558,13 +2577,13 @@ Table of Contents

[QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK:
Header Compression for HTTP over QUIC", Work in Progress,
Internet-Draft, draft-ietf-quic-qpack, 26 January 2021,
Internet-Draft, draft-ietf-quic-qpack, 27 January 2021,
<https://tools.ietf.org/html/draft-ietf-quic-qpack>.

[QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", Work in Progress,
Internet-Draft, draft-ietf-quic-transport, 26 January
Internet-Draft, draft-ietf-quic-transport, 27 January
2021,
<https://tools.ietf.org/html/draft-ietf-quic-transport>.

Expand All @@ -2582,13 +2601,6 @@ Table of Contents
DOI 10.17487/RFC6066, January 2011,
<https://www.rfc-editor.org/info/rfc6066>.

[RFC6125] Saint-Andre, P. and J. Hodges, "Representation and
Verification of Domain-Based Application Service Identity
within Internet Public Key Infrastructure Using X.509
(PKIX) Certificates in the Context of Transport Layer
Security (TLS)", RFC 6125, DOI 10.17487/RFC6125, March
2011, <https://www.rfc-editor.org/info/rfc6125>.

[RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265,
DOI 10.17487/RFC6265, April 2011,
<https://www.rfc-editor.org/info/rfc6265>.
Expand Down Expand Up @@ -2621,10 +2633,6 @@ Table of Contents

12.2. Informative References

[ALTSVC] Nottingham, M., McManus, P., and J. Reschke, "HTTP
Alternative Services", RFC 7838, DOI 10.17487/RFC7838,
April 2016, <https://www.rfc-editor.org/info/rfc7838>.

[BREACH] Gluck, Y., Harris, N., and A. Prado, "BREACH: Reviving the
CRIME Attack", July 2013,
<http://breachattack.com/resources/
Expand Down
52 changes: 26 additions & 26 deletions draft-ietf-quic-invariants.html
View file
Expand Up @@ -841,7 +841,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Thomson</td>
<td class="center">Expires 30 July 2021</td>
<td class="center">Expires 31 July 2021</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -854,12 +854,12 @@
<dd class="internet-draft">draft-ietf-quic-invariants</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-01-26" class="published">26 January 2021</time>
<time datetime="2021-01-27" class="published">27 January 2021</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="2021-07-30">30 July 2021</time></dd>
<dd class="expires"><time datetime="2021-07-31">31 July 2021</time></dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -905,7 +905,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 30 July 2021.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 31 July 2021.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -933,60 +933,60 @@ <h2 id="name-copyright-notice">
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
</h2>
<nav class="toc"><ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.1">
<nav class="toc"><ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.1">
<p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-an-extremely-abstract-descr" class="xref">An Extremely Abstract Description of QUIC</a><a href="#section-toc.1-1.1.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.2">
<li class="ulEmpty toc compact" id="section-toc.1-1.2">
<p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-fixed-properties-of-all-qui" class="xref">Fixed Properties of All QUIC Versions</a><a href="#section-toc.1-1.2.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.3">
<li class="ulEmpty toc compact" id="section-toc.1-1.3">
<p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-conventions-and-definitions" class="xref">Conventions and Definitions</a><a href="#section-toc.1-1.3.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.4">
<li class="ulEmpty toc compact" id="section-toc.1-1.4">
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-notational-conventions" class="xref">Notational Conventions</a><a href="#section-toc.1-1.4.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.5">
<li class="ulEmpty toc compact" id="section-toc.1-1.5">
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-quic-packets" class="xref">QUIC Packets</a><a href="#section-toc.1-1.5.1" class="pilcrow"></a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.5.2.1">
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.1">
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-long-header" class="xref">Long Header</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.5.2.2">
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.2">
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-short-header" class="xref">Short Header</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.5.2.3">
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.3">
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-connection-id" class="xref">Connection ID</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.5.2.4">
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.4">
<p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-version" class="xref">Version</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.6">
<li class="ulEmpty toc compact" id="section-toc.1-1.6">
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-version-negotiation" class="xref">Version Negotiation</a><a href="#section-toc.1-1.6.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.7">
<li class="ulEmpty toc compact" id="section-toc.1-1.7">
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-security-and-privacy-consid" class="xref">Security and Privacy Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.8">
<li class="ulEmpty toc compact" id="section-toc.1-1.8">
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.9">
<li class="ulEmpty toc compact" id="section-toc.1-1.9">
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.9.1" class="pilcrow"></a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1">
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.9.2.1">
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2">
<li class="ulEmpty toc compact" id="section-toc.1-1.9.2.2">
<p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow"></a></p>
</li>
</ul>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.10">
<li class="ulEmpty toc compact" id="section-toc.1-1.10">
<p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-incorrect-assumptions" class="xref">Incorrect Assumptions</a><a href="#section-toc.1-1.10.1" class="pilcrow"></a></p>
</li>
<li class="ulEmpty compact toc" id="section-toc.1-1.11">
<li class="ulEmpty toc compact" id="section-toc.1-1.11">
<p id="section-toc.1-1.11.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a><a href="#section-toc.1-1.11.1" class="pilcrow"></a></p>
</li>
</ul>
Expand Down Expand Up @@ -1343,11 +1343,11 @@ <h3 id="name-informative-references">
<dl class="references">
<dt id="QUIC-TLS">[QUIC-TLS]</dt>
<dd>
<span class="refAuthor">Thomson, M., Ed.</span><span class="refAuthor"> and S. Turner, Ed.</span>, <span class="refTitle">"Using Transport Layer Security (TLS) to Secure QUIC"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-quic-tls</span>, <time datetime="2021-01-26" class="refDate">26 January 2021</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-quic-tls">https://tools.ietf.org/html/draft-ietf-quic-tls</a>&gt;</span>. </dd>
<span class="refAuthor">Thomson, M., Ed.</span><span class="refAuthor"> and S. Turner, Ed.</span>, <span class="refTitle">"Using Transport Layer Security (TLS) to Secure QUIC"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-quic-tls</span>, <time datetime="2021-01-27" class="refDate">27 January 2021</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-quic-tls">https://tools.ietf.org/html/draft-ietf-quic-tls</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="QUIC-TRANSPORT">[QUIC-TRANSPORT]</dt>
<dd>
<span class="refAuthor">Iyengar, J., Ed.</span><span class="refAuthor"> and M. Thomson, Ed.</span>, <span class="refTitle">"QUIC: A UDP-Based Multiplexed and Secure Transport"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-quic-transport</span>, <time datetime="2021-01-26" class="refDate">26 January 2021</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-quic-transport">https://tools.ietf.org/html/draft-ietf-quic-transport</a>&gt;</span>. </dd>
<span class="refAuthor">Iyengar, J., Ed.</span><span class="refAuthor"> and M. Thomson, Ed.</span>, <span class="refTitle">"QUIC: A UDP-Based Multiplexed and Secure Transport"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-quic-transport</span>, <time datetime="2021-01-27" class="refDate">27 January 2021</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-quic-transport">https://tools.ietf.org/html/draft-ietf-quic-transport</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5116">[RFC5116]</dt>
<dd>
Expand Down

0 comments on commit da76229

Please sign in to comment.