Skip to content

Commit

Permalink
Script updating gh-pages from b66c69c. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Aug 2, 2019
1 parent 2c53081 commit 4f30589
Show file tree
Hide file tree
Showing 14 changed files with 5,330 additions and 5,090 deletions.

Large diffs are not rendered by default.

Large diffs are not rendered by default.

Expand Up @@ -305,7 +305,7 @@

<meta name="dct.creator" content="Thomson, M." />
<meta name="dct.identifier" content="urn:ietf:id:draft-ietf-quic-invariants-latest" />
<meta name="dct.issued" scheme="ISO8601" content="2019-07-03" />
<meta name="dct.issued" scheme="ISO8601" content="2019-08-02" />
<meta name="dct.abstract" content="This document defines the properties of the QUIC transport protocol that are expected to remain unchanged over time as new versions of the protocol are developed." />
<meta name="description" content="This document defines the properties of the QUIC transport protocol that are expected to remain unchanged over time as new versions of the protocol are developed." />

Expand All @@ -326,10 +326,10 @@
</tr>
<tr>
<td class="left">Intended status: Standards Track</td>
<td class="right">July 03, 2019</td>
<td class="right">August 02, 2019</td>
</tr>
<tr>
<td class="left">Expires: January 4, 2020</td>
<td class="left">Expires: February 3, 2020</td>
<td class="right"></td>
</tr>

Expand All @@ -349,7 +349,7 @@ <h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on January 4, 2020.</p>
<p>This Internet-Draft will expire on February 3, 2020.</p>
<h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
<p>Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
Expand Down Expand Up @@ -431,20 +431,22 @@ <h2 id="rfc.section.4.1">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
| SCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre>
<p class="figure">Figure 1: QUIC Long Header</p>
<p id="rfc.section.4.1.p.2">A QUIC packet with a long header has the high bit of the first byte set to 1. All other bits in that byte are version specific.</p>
<p id="rfc.section.4.1.p.3">The next four bytes include a 32-bit Version field (see <a href="#version" class="xref">Section 4.4</a>).</p>
<p id="rfc.section.4.1.p.4">The next byte contains the length in bytes of the two Connection IDs (see <a href="#connection-id" class="xref">Section 4.3</a>) that follow. Each length is encoded as a 4-bit unsigned integer. The length of the Destination Connection ID (DCIL) occupies the high bits of the byte and the length of the Source Connection ID (SCIL) occupies the low bits of the byte. An encoded length of 0 indicates that the connection ID is also 0 bytes in length. Non-zero encoded lengths are increased by 3 to get the full length of the connection ID; the final value is therefore either 0 or between 4 and 18 bytes in length (inclusive). For example, an byte with the value 0xe0 describes a 17 byte Destination Connection ID and a zero byte Source Connection ID.</p>
<p id="rfc.section.4.1.p.5">The connection ID lengths are followed by two connection IDs. The connection ID associated with the recipient of the packet (the Destination Connection ID) is followed by the connection ID associated with the sender of the packet (the Source Connection ID).</p>
<p id="rfc.section.4.1.p.4">The next byte contains the length in bytes of the Destination Connection ID (see <a href="#connection-id" class="xref">Section 4.3</a>) field that follows it. This length is encoded as an 8-bit unsigned integer. The Destination Connection ID field follows the DCID Len field and is between 0 and 255 bytes in length.</p>
<p id="rfc.section.4.1.p.5">The next byte contains the length in bytes of the Source Connection ID field that follows it. This length is encoded as a 8-bit unsigned integer. The Source Connection ID field follows the SCID Len field and is between 0 and 255 bytes in length.</p>
<p id="rfc.section.4.1.p.6">The remainder of the packet contains version-specific content.</p>
<h2 id="rfc.section.4.2">
<a href="#rfc.section.4.2">4.2.</a> <a href="#short-header" id="short-header">Short Header</a>
Expand Down Expand Up @@ -493,11 +495,13 @@ <h1 id="rfc.section.5">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
| SCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
| Source Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Supported Version 1 (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Expand Down Expand Up @@ -532,7 +536,7 @@ <h2 id="rfc.references.1">
<tr>
<td class="reference"><b id="QUIC-TRANSPORT">[QUIC-TRANSPORT]</b></td>
<td class="top">
<a title="Google">Iyengar, J.</a> and <a title="Mozilla">M. Thomson</a>, "<a href="https://tools.ietf.org/html/draft-ietf-quic-transport">QUIC: A UDP-Based Multiplexed and Secure Transport</a>", Internet-Draft draft-ietf-quic-transport, July 2019.</td>
<a title="Google">Iyengar, J.</a> and <a title="Mozilla">M. Thomson</a>, "<a href="https://tools.ietf.org/html/draft-ietf-quic-transport">QUIC: A UDP-Based Multiplexed and Secure Transport</a>", Internet-Draft draft-ietf-quic-transport, August 2019.</td>
</tr>
<tr>
<td class="reference"><b id="RFC2119">[RFC2119]</b></td>
Expand All @@ -551,7 +555,7 @@ <h2 id="rfc.references.2">
<tr>
<td class="reference"><b id="QUIC-TLS">[QUIC-TLS]</b></td>
<td class="top">
<a title="Mozilla">Thomson, M.</a> and <a title="sn3rd">S. Turner</a>, "<a href="https://tools.ietf.org/html/draft-ietf-quic-tls">Using Transport Layer Security (TLS) to Secure QUIC</a>", Internet-Draft draft-ietf-quic-tls, July 2019.</td>
<a title="Mozilla">Thomson, M.</a> and <a title="sn3rd">S. Turner</a>, "<a href="https://tools.ietf.org/html/draft-ietf-quic-tls">Using Transport Layer Security (TLS) to Secure QUIC</a>", Internet-Draft draft-ietf-quic-tls, August 2019.</td>
</tr>
<tr>
<td class="reference"><b id="RFC5116">[RFC5116]</b></td>
Expand Down
Expand Up @@ -4,8 +4,8 @@

QUIC M. Thomson
Internet-Draft Mozilla
Intended status: Standards Track July 03, 2019
Expires: January 4, 2020
Intended status: Standards Track August 02, 2019
Expires: February 3, 2020


Version-Independent Properties of QUIC
Expand Down Expand Up @@ -42,7 +42,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 January 4, 2020.
This Internet-Draft will expire on February 3, 2020.

Copyright Notice

Expand All @@ -53,9 +53,9 @@ Copyright Notice



Thomson Expires January 4, 2020 [Page 1]
Thomson Expires February 3, 2020 [Page 1]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


This document is subject to BCP 78 and the IETF Trust's Legal
Expand Down Expand Up @@ -109,9 +109,9 @@ Table of Contents



Thomson Expires January 4, 2020 [Page 2]
Thomson Expires February 3, 2020 [Page 2]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


Appendix A is a non-exhaustive list of some incorrect assumptions
Expand Down Expand Up @@ -165,9 +165,9 @@ Internet-Draft QUIC Invariants July 2019



Thomson Expires January 4, 2020 [Page 3]
Thomson Expires February 3, 2020 [Page 3]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


0 1 2 3
Expand All @@ -177,11 +177,13 @@ Internet-Draft QUIC Invariants July 2019
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
| SCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Expand All @@ -193,22 +195,16 @@ Internet-Draft QUIC Invariants July 2019

The next four bytes include a 32-bit Version field (see Section 4.4).

The next byte contains the length in bytes of the two Connection IDs
(see Section 4.3) that follow. Each length is encoded as a 4-bit
unsigned integer. The length of the Destination Connection ID (DCIL)
occupies the high bits of the byte and the length of the Source
Connection ID (SCIL) occupies the low bits of the byte. An encoded
length of 0 indicates that the connection ID is also 0 bytes in
length. Non-zero encoded lengths are increased by 3 to get the full
length of the connection ID; the final value is therefore either 0 or
between 4 and 18 bytes in length (inclusive). For example, an byte
with the value 0xe0 describes a 17 byte Destination Connection ID and
a zero byte Source Connection ID.

The connection ID lengths are followed by two connection IDs. The
connection ID associated with the recipient of the packet (the
Destination Connection ID) is followed by the connection ID
associated with the sender of the packet (the Source Connection ID).
The next byte contains the length in bytes of the Destination
Connection ID (see Section 4.3) field that follows it. This length
is encoded as an 8-bit unsigned integer. The Destination Connection
ID field follows the DCID Len field and is between 0 and 255 bytes in
length.

The next byte contains the length in bytes of the Source Connection
ID field that follows it. This length is encoded as a 8-bit unsigned
integer. The Source Connection ID field follows the SCID Len field
and is between 0 and 255 bytes in length.

The remainder of the packet contains version-specific content.

Expand All @@ -221,9 +217,13 @@ Internet-Draft QUIC Invariants July 2019



Thomson Expires January 4, 2020 [Page 4]




Thomson Expires February 3, 2020 [Page 4]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


0 1 2 3
Expand Down Expand Up @@ -277,9 +277,9 @@ Internet-Draft QUIC Invariants July 2019



Thomson Expires January 4, 2020 [Page 5]
Thomson Expires February 3, 2020 [Page 5]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


5. Version Negotiation
Expand All @@ -301,11 +301,13 @@ Internet-Draft QUIC Invariants July 2019
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
| SCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
| Source Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Supported Version 1 (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Expand All @@ -331,11 +333,9 @@ Internet-Draft QUIC Invariants July 2019





Thomson Expires January 4, 2020 [Page 6]
Thomson Expires February 3, 2020 [Page 6]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


An endpoint MUST include the value from the Source Connection ID
Expand Down Expand Up @@ -389,17 +389,17 @@ Internet-Draft QUIC Invariants July 2019



Thomson Expires January 4, 2020 [Page 7]
Thomson Expires February 3, 2020 [Page 7]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


8.1. Normative References

[QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", draft-ietf-quic-
transport (work in progress), July 2019.
transport (work in progress), August 2019.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
Expand All @@ -415,7 +415,7 @@ Internet-Draft QUIC Invariants July 2019
[QUIC-TLS]
Thomson, M., Ed. and S. Turner, Ed., "Using Transport
Layer Security (TLS) to Secure QUIC", draft-ietf-quic-tls
(work in progress), July 2019.
(work in progress), August 2019.

[RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated
Encryption", RFC 5116, DOI 10.17487/RFC5116, January 2008,
Expand Down Expand Up @@ -445,9 +445,9 @@ Appendix A. Incorrect Assumptions



Thomson Expires January 4, 2020 [Page 8]
Thomson Expires February 3, 2020 [Page 8]

Internet-Draft QUIC Invariants July 2019
Internet-Draft QUIC Invariants August 2019


o QUIC uses TLS [QUIC-TLS] and some TLS messages are visible on the
Expand Down Expand Up @@ -501,4 +501,4 @@ Author's Address



Thomson Expires January 4, 2020 [Page 9]
Thomson Expires February 3, 2020 [Page 9]

0 comments on commit 4f30589

Please sign in to comment.