/
draft-ietf-quic-invariants.txt
504 lines (333 loc) · 19.2 KB
/
draft-ietf-quic-invariants.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
QUIC M. Thomson
Internet-Draft Mozilla
Intended status: Standards Track 7 January 2020
Expires: 10 July 2020
Version-Independent Properties of QUIC
draft-ietf-quic-invariants-latest
Abstract
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.
Note to Readers
Discussion of this draft takes place on the QUIC working group
mailing list (quic@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/search/?email_list=quic
(https://mailarchive.ietf.org/arch/search/?email_list=quic).
Working Group information can be found at https://github.com/quicwg
(https://github.com/quicwg); source code and issues list for this
draft can be found at https://github.com/quicwg/base-drafts/labels/-
invariants (https://github.com/quicwg/base-drafts/labels/-
invariants).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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/.
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."
This Internet-Draft will expire on 10 July 2020.
Thomson Expires 10 July 2020 [Page 1]
Internet-Draft QUIC Invariants January 2020
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. An Extremely Abstract Description of QUIC . . . . . . . . . . 3
4. QUIC Packet Headers . . . . . . . . . . . . . . . . . . . . . 3
4.1. Long Header . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Short Header . . . . . . . . . . . . . . . . . . . . . . 4
4.3. Connection ID . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Version . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Version Negotiation . . . . . . . . . . . . . . . . . . . . . 6
6. Security and Privacy Considerations . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Incorrect Assumptions . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
In addition to providing secure, multiplexed transport, QUIC
[QUIC-TRANSPORT] includes the ability to negotiate a version. This
allows the protocol to change over time in response to new
requirements. Many characteristics of the protocol will change
between versions.
This document describes the subset of QUIC that is intended to remain
stable as new versions are developed and deployed. All of these
invariants are IP-version-independent.
The primary goal of this document is to ensure that it is possible to
deploy new versions of QUIC. By documenting the properties that
can't change, this document aims to preserve the ability to change
Thomson Expires 10 July 2020 [Page 2]
Internet-Draft QUIC Invariants January 2020
any other aspect of the protocol. Thus, unless specifically
described in this document, any aspect of the protocol can change
between different versions.
Appendix A is a non-exhaustive list of some incorrect assumptions
that might be made based on knowledge of QUIC version 1; these do not
apply to every version of QUIC.
2. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
This document uses terms and notational conventions from
[QUIC-TRANSPORT].
3. An Extremely Abstract Description of QUIC
QUIC is a connection-oriented protocol between two endpoints. Those
endpoints exchange UDP datagrams. These UDP datagrams contain QUIC
packets. QUIC endpoints use QUIC packets to establish a QUIC
connection, which is shared protocol state between those endpoints.
4. QUIC Packet Headers
A QUIC packet is the content of the UDP datagrams exchanged by QUIC
endpoints. This document describes the contents of those datagrams.
QUIC defines two types of packet header: long and short. Packets
with long headers are identified by the most significant bit of the
first byte being set; packets with a short header have that bit
cleared.
Aside from the values described here, the payload of QUIC packets is
version-specific and of arbitrary length.
4.1. Long Header
Long headers take the form described in Figure 1. Bits that have
version-specific semantics are marked with an X.
Thomson Expires 10 July 2020 [Page 3]
Internet-Draft QUIC Invariants January 2020
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|1|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: QUIC Long Header
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.
The next four bytes include a 32-bit Version field (see Section 4.4).
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.
4.2. Short Header
Short headers take the form described in Figure 2. Bits that have
version-specific semantics are marked with an X.
Thomson Expires 10 July 2020 [Page 4]
Internet-Draft QUIC Invariants January 2020
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|0|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (*) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: QUIC Short Header
A QUIC packet with a short header has the high bit of the first byte
set to 0.
A QUIC packet with a short header includes a Destination Connection
ID immediately following the first byte. The short header does not
include the Connection ID Lengths, Source Connection ID, or Version
fields. The length of the Destination Connection ID is not specified
in packets with a short header and is not constrained by this
specification.
The remainder of the packet has version-specific semantics.
4.3. Connection ID
A connection ID is an opaque field of arbitrary length.
The primary function of a connection ID is to ensure that changes in
addressing at lower protocol layers (UDP, IP, and below) don't cause
packets for a QUIC connection to be delivered to the wrong endpoint.
The connection ID is used by endpoints and the intermediaries that
support them to ensure that each QUIC packet can be delivered to the
correct instance of an endpoint. At the endpoint, the connection ID
is used to identify which QUIC connection the packet is intended for.
The connection ID is chosen by each endpoint using version-specific
methods. Packets for the same QUIC connection might use different
connection ID values.
4.4. Version
QUIC versions are identified with a 32-bit integer, encoded in
network byte order. Version 0 is reserved for version negotiation
(see Section 5). All other version numbers are potentially valid.
The properties described in this document apply to all versions of
QUIC. A protocol that does not conform to the properties described
Thomson Expires 10 July 2020 [Page 5]
Internet-Draft QUIC Invariants January 2020
in this document is not QUIC. Future documents might describe
additional properties which apply to a specific QUIC version, or to a
range of QUIC versions.
5. Version Negotiation
A QUIC endpoint that receives a packet with a long header and a
version it either does not understand or does not support might send
a Version Negotiation packet in response. Packets with a short
header do not trigger version negotiation.
A Version Negotiation packet sets the high bit of the first byte, and
thus it conforms with the format of a packet with a long header as
defined in Section 4.1. A Version Negotiation packet is identifiable
as such by the Version field, which is set to 0x00000000.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|1|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCID Len (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0..2040) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Supported Version 1 (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| [Supported Version 2 (32)] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| [Supported Version N (32)] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Version Negotiation Packet
The Version Negotiation packet contains a list of Supported Version
fields, each identifying a version that the endpoint sending the
packet supports. The Supported Version fields follow the Version
field. A Version Negotiation packet contains no other fields. An
endpoint MUST ignore a packet that contains no Supported Version
fields, or a truncated Supported Version.
Thomson Expires 10 July 2020 [Page 6]
Internet-Draft QUIC Invariants January 2020
Version Negotiation packets do not use integrity or confidentiality
protection. A specific QUIC version might authenticate the packet as
part of its connection establishment process.
An endpoint MUST include the value from the Source Connection ID
field of the packet it receives in the Destination Connection ID
field. The value for Source Connection ID MUST be copied from the
Destination Connection ID of the received packet, which is initially
randomly selected by a client. Echoing both connection IDs gives
clients some assurance that the server received the packet and that
the Version Negotiation packet was not generated by an off-path
attacker.
An endpoint that receives a Version Negotiation packet might change
the version that it decides to use for subsequent packets. The
conditions under which an endpoint changes QUIC version will depend
on the version of QUIC that it chooses.
See [QUIC-TRANSPORT] for a more thorough description of how an
endpoint that supports QUIC version 1 generates and consumes a
Version Negotiation packet.
6. Security and Privacy Considerations
It is possible that middleboxes could use traits of a specific
version of QUIC and assume that when other versions of QUIC exhibit
similar traits the same underlying semantic is being expressed.
There are potentially many such traits (see Appendix A). Some effort
has been made to either eliminate or obscure some observable traits
in QUIC version 1, but many of these remain. Other QUIC versions
might make different design decisions and so exhibit different
traits.
The QUIC version number does not appear in all QUIC packets, which
means that reliably extracting information from a flow based on
version-specific traits requires that middleboxes retain state for
every connection ID they see.
The Version Negotiation packet described in this document is not
integrity-protected; it only has modest protection against insertion
by off-path attackers. QUIC versions MUST define a mechanism that
authenticates the values it contains.
7. IANA Considerations
This document makes no request of IANA.
8. References
Thomson Expires 10 July 2020 [Page 7]
Internet-Draft QUIC Invariants January 2020
8.1. Normative References
[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-latest, 7
January 2020, <https://tools.ietf.org/html/draft-ietf-
quic-transport-latest>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References
[QUIC-TLS] Thomson, M., Ed. and S. Turner, Ed., "Using Transport
Layer Security (TLS) to Secure QUIC", Work in Progress,
Internet-Draft, draft-ietf-quic-tls-latest, 7 January
2020,
<https://tools.ietf.org/html/draft-ietf-quic-tls-latest>.
[RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated
Encryption", RFC 5116, DOI 10.17487/RFC5116, January 2008,
<https://www.rfc-editor.org/info/rfc5116>.
Appendix A. Incorrect Assumptions
There are several traits of QUIC version 1 [QUIC-TRANSPORT] that are
not protected from observation, but are nonetheless considered to be
changeable when a new version is deployed.
This section lists a sampling of incorrect assumptions that might be
made based on knowledge of QUIC version 1. Some of these statements
are not even true for QUIC version 1. This is not an exhaustive
list, it is intended to be illustrative only.
The following statements are NOT guaranteed to be true for every QUIC
version:
* QUIC uses TLS [QUIC-TLS] and some TLS messages are visible on the
wire
Thomson Expires 10 July 2020 [Page 8]
Internet-Draft QUIC Invariants January 2020
* QUIC long headers are only exchanged during connection
establishment
* Every flow on a given 5-tuple will include a connection
establishment phase
* The first packets exchanged on a flow use the long header
* QUIC forbids acknowledgments of packets that only contain ACK
frames, therefore the last packet before a long period of
quiescence might be assumed to contain an acknowledgment
* QUIC uses an AEAD (AEAD_AES_128_GCM [RFC5116]) to protect the
packets it exchanges during connection establishment
* QUIC packet numbers appear after the Version field
* QUIC packet numbers increase by one for every packet sent
* QUIC has a minimum size for the first handshake packet sent by a
client
* QUIC stipulates that a client speaks first
* A QUIC Version Negotiation packet is only sent by a server
* A QUIC connection ID changes infrequently
* QUIC endpoints change the version they speak if they are sent a
Version Negotiation packet
* The version field in a QUIC long header is the same in both
directions
* Only one connection at a time is established between any pair of
QUIC endpoints
Author's Address
Martin Thomson
Mozilla
Email: mt@lowentropy.net
Thomson Expires 10 July 2020 [Page 9]