draft-ietf-quic-invariants-00.txt   draft-ietf-quic-invariants-01.txt 
QUIC M. Thomson QUIC M. Thomson
Internet-Draft Mozilla Internet-Draft Mozilla
Intended status: Standards Track February 28, 2018 Intended status: Standards Track March 20, 2018
Expires: September 1, 2018 Expires: September 21, 2018
Version-Independent Properties of QUIC Version-Independent Properties of QUIC
draft-ietf-quic-invariants-00 draft-ietf-quic-invariants-01
Abstract Abstract
This document defines the properties of the QUIC transport protocol This document defines the properties of the QUIC transport protocol
that are expected to remain unchanged over time as new versions of that are expected to remain unchanged over time as new versions of
the protocol are developed. the protocol are developed.
Note to Readers Note to Readers
Discussion of this draft takes place on the QUIC working group Discussion of this draft takes place on the QUIC working group
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 1, 2018. This Internet-Draft will expire on September 21, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. An Extremely Abstract Description of QUIC . . . . . . . . . . 3 3. An Extremely Abstract Description of QUIC . . . . . . . . . . 3
4. QUIC Packet Headers . . . . . . . . . . . . . . . . . . . . . 3 4. QUIC Packet Headers . . . . . . . . . . . . . . . . . . . . . 3
4.1. Long Header . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Long Header . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Short Header . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Short Header . . . . . . . . . . . . . . . . . . . . . . 4
4.3. Connection ID . . . . . . . . . . . . . . . . . . . . . . 5 4.3. Connection ID . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Version . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.4. Version . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Version Negotiation . . . . . . . . . . . . . . . . . . . . . 5 5. Version Negotiation . . . . . . . . . . . . . . . . . . . . . 6
6. Security and Privacy Considerations . . . . . . . . . . . . . 7 6. Security and Privacy Considerations . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 8
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Incorrect Assumptions . . . . . . . . . . . . . . . 8 Appendix A. Incorrect Assumptions . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
In addition to providing secure, multiplexed transport, QUIC In addition to providing secure, multiplexed transport, QUIC
[QUIC-TRANSPORT] includes the ability to negotiate a version. This [QUIC-TRANSPORT] includes the ability to negotiate a version. This
allows the protocol to change over time in response to new allows the protocol to change over time in response to new
requirements. Many characteristics of the protocol will change requirements. Many characteristics of the protocol will change
between versions. between versions.
This document describes the subset of QUIC that is intended to remain This document describes the subset of QUIC that is intended to remain
stable as new versions are developed and deployed. 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 The primary goal of this document is to ensure that it is possible
deploy new versions of QUIC. By documenting the things that can't deploy new versions of QUIC. By documenting the things that can't
change, this document aims to preserve the ability to change any change, this document aims to preserve the ability to change any
other aspect of the protocol. Thus, unless specifically described in other aspect of the protocol. Thus, unless specifically described in
this document, any aspect of the protocol can change between this document, any aspect of the protocol can change between
different versions. different versions.
Appendix A is a non-exhaustive list of some incorrect assumptions 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 that might be made based on knowledge of QUIC version 1; these do not
skipping to change at page 4, line 10 skipping to change at page 4, line 10
4.1. Long Header 4.1. Long Header
Long headers take the form described in Figure 1. Bits that have Long headers take the form described in Figure 1. Bits that have
version-specific semantics are marked with an X. version-specific semantics are marked with an X.
0 1 2 3 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 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| |1|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Connection ID (64) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) | | Version (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 ... |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 Figure 1: QUIC Long Header
A QUIC packet with a long header has the high bit of the first octet A QUIC packet with a long header has the high bit of the first octet
set to 1. set to 1. All other bits in that octet are version specific.
A QUIC packet with a long header has two fixed fields immediately The next four octets include a 32-bit Version field (see
following the first octet: a 64-bit Connection ID (see Section 4.3) Section 4.4).
and a 32-bit Version (see Section 4.4).
The next octet contains the length in octets 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 octet and the length of the Source
Connection ID (SCIL) occupying the low bits of the octet. An encoded
length of 0 indicates that the connection ID is also 0 octets 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 octets in length (inclusive). For example, an octet
with the value 0xe0 describes a 17 octet Destination Connection ID
and a zero octet Source Connection ID.
The connection ID lengths are followed by a 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 remainder of the packet contains version-specific content.
4.2. Short Header 4.2. Short Header
Short headers take the form described in Figure 2. Bits that have Short headers take the form described in Figure 2. Bits that have
version-specific semantics are marked with an X. version-specific semantics are marked with an X.
0 1 2 3 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 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|C|X X X X X X| |0|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | Destination Connection ID (0..144) ...
+ [Connection ID (64)] +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 ... |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 Figure 2: QUIC Short Header
A QUIC packet with a short header has the high bit of the first octet A QUIC packet with a short header has the high bit of the first octet
set to 0. set to 0.
A QUIC packet with a short header includes an optional connection ID A QUIC packet with a short header includes an optional Destination
and no version field. The second bit of that octet (that is, 0x40) Connection ID. The short header does not include the Connection ID
determines whether the connection ID is present. If the second bit Lengths, Source Connection ID, or Version fields.
is cleared, a 64-bit connection ID immediately follows the first
octet. If the second bit is set, the remainder of the packet has The remainder of the packet has version-specific semantics.
version-specific semantics.
4.3. Connection ID 4.3. Connection ID
A connection ID is an opaque 64-bit field. A connection ID is an opaque field. A connection ID can be 0 octets
in length, or between 4 and 18 octets (inclusive).
The primary function of a connection ID is to ensure that changes in 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 addressing at lower protocol layers (UDP, IP, and below) don't cause
packets for a QUIC connection to be delivered to the wrong endpoint. packets for a QUIC connection to be delivered to the wrong endpoint.
The connection ID is used by endpoints and the intermediaries that The connection ID is used by endpoints and the intermediaries that
support them to ensure that each QUIC packet can be delivered to the support them to ensure that each QUIC packet can be delivered to the
correct instance of an endpoint. At the endpoint, the connection ID correct instance of an endpoint. At the endpoint, the connection ID
is used to identify which QUIC connection the packet is intended for. is used to identify which QUIC connection the packet is intended for.
The connection ID is chosen by endpoints using version-specific The connection ID is chosen by each endpoint using version-specific
methods. Packets for the same QUIC connection might use different methods. Packets for the same QUIC connection might use different
connection ID values. connection ID values.
4.4. Version 4.4. Version
QUIC versions are identified with a 32-bit integer, encoded in QUIC versions are identified with a 32-bit integer, encoded in
network byte order. Version 0 is reserved for version negotiation network byte order. Version 0 is reserved for version negotiation
(see Section 5). All other version numbers are potentially valid. (see Section 5). All other version numbers are potentially valid.
5. Version Negotiation 5. Version Negotiation
A QUIC endpoint that receives a packet with a long header and a A QUIC endpoint that receives a packet with a long header and a
version it either does not understand or does not support sends a version it either does not understand or does not support might send
Version Negotiation packet in response. Packets with a short header a Version Negotiation packet in response. Packets with a short
do not trigger version negotiation and are always associated with an header do not trigger version negotiation and are always associated
existing connection. with an existing connection.
Consequently, until an endpoint has confirmed that its peer supports Consequently, until an endpoint has confirmed that its peer supports
the QUIC version it has chosen, it can only send packets that use the the QUIC version it has chosen, it can only send packets that use the
long header. long header.
A Version Negotiation packet sets the high bit of the first octet, A Version Negotiation packet sets the high bit of the first octet,
and thus it conforms with the format of a packet with a long header and thus it conforms with the format of a packet with a long header
as defined in this document. A Version Negotiation packet is as defined in Section 4.1. A Version Negotiation packet is
identifiable as such by the Version field, which is set to identifiable as such by the Version field, which is set to
0x00000000. 0x00000000.
0 1 2 3 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 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| |1|X X X X X X X|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Connection ID (64) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version (32) = 0 | | Version (32) = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|DCIL(4)|SCIL(4)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Connection ID (0/32..144) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Connection ID (0/32..144) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Supported Version 1 (32) | | Supported Version 1 (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| [Supported Version 2 (32)] | | [Supported Version 2 (32)] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| [Supported Version N (32)] | | [Supported Version N (32)] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Version Negotiation Packet Figure 3: Version Negotiation Packet
skipping to change at page 6, line 38 skipping to change at page 7, line 9
fields, each identifying a version that the endpoint sending the fields, each identifying a version that the endpoint sending the
packet supports. The Supported Version fields follow the Version packet supports. The Supported Version fields follow the Version
field. A Version Negotiation packet contains no other fields. An field. A Version Negotiation packet contains no other fields. An
endpoint MUST ignore a packet that contains no Supported Version endpoint MUST ignore a packet that contains no Supported Version
fields, or a truncated Supported Version. fields, or a truncated Supported Version.
Version Negotiation packets do not use integrity or confidentiality Version Negotiation packets do not use integrity or confidentiality
protection. A specific QUIC version might authenticate the packet as protection. A specific QUIC version might authenticate the packet as
part of its connection establishment process. part of its connection establishment process.
The Connection ID field in a Version Negotiation packet contains the The server MUST include the value from the Source Connection ID field
Connection ID from the packet that was received. This provides some of the packet it receives in the Destination Connection ID field.
protection against injection of Version Negotiation packets by off- The value for Source Connection ID MUST be copied from the
path attackers. 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 An endpoint that receives a Version Negotiation packet might change
the version that it decides to use for subsequent packets. The the version that it decides to use for subsequent packets. The
conditions under which an endpoint changes QUIC version will depend conditions under which an endpoint changes QUIC version will depend
on the version of QUIC that it chooses. on the version of QUIC that it chooses.
See [QUIC-TRANSPORT] for a more thorough description of how an See [QUIC-TRANSPORT] for a more thorough description of how an
endpoint that supports QUIC version 1 generates and consumes a endpoint that supports QUIC version 1 generates and consumes a
Version Negotiation packet. Version Negotiation packet.
skipping to change at page 7, line 37 skipping to change at page 8, line 12
This document makes no request of IANA. This document makes no request of IANA.
8. References 8. References
8.1. Normative References 8.1. Normative References
[QUIC-TRANSPORT] [QUIC-TRANSPORT]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", draft-ietf-quic- Multiplexed and Secure Transport", draft-ietf-quic-
transport-09 (work in progress), February 2018. transport-10 (work in progress), March 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[QUIC-TLS] [QUIC-TLS]
Thomson, M., Ed. and S. Turner, Ed., "Using Transport Thomson, M., Ed. and S. Turner, Ed., "Using Transport
Layer Security (TLS) to Secure QUIC", draft-ietf-quic- Layer Security (TLS) to Secure QUIC", draft-ietf-quic-
tls-09 (work in progress), February 2018. tls-10 (work in progress), March 2018.
[RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated [RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated
Encryption", RFC 5116, DOI 10.17487/RFC5116, January 2008, Encryption", RFC 5116, DOI 10.17487/RFC5116, January 2008,
<https://www.rfc-editor.org/info/rfc5116>. <https://www.rfc-editor.org/info/rfc5116>.
8.3. URIs 8.3. URIs
[1] https://mailarchive.ietf.org/arch/search/?email_list=quic [1] https://mailarchive.ietf.org/arch/search/?email_list=quic
[2] https://github.com/quicwg [2] https://github.com/quicwg
skipping to change at page 9, line 15 skipping to change at page 9, line 37
o QUIC has a minimum size for the first handshake packet sent by a o QUIC has a minimum size for the first handshake packet sent by a
client client
o QUIC stipulates that a client speaks first o QUIC stipulates that a client speaks first
o A QUIC Version Negotiation packet is only sent by a server o A QUIC Version Negotiation packet is only sent by a server
o A QUIC connection ID changes infrequently o A QUIC connection ID changes infrequently
o The same connection ID is used for packets sent by both endpoints
o A QUIC server chooses the connection ID
o QUIC endpoints change the version they speak if they are sent a o QUIC endpoints change the version they speak if they are sent a
Version Negotiation packet Version Negotiation packet
o The version field in a QUIC long header is the same in both
directions
o Only one connection at a time is established between any pair of o Only one connection at a time is established between any pair of
QUIC endpoints QUIC endpoints
Author's Address Author's Address
Martin Thomson Martin Thomson
Mozilla Mozilla
Email: martin.thomson@gmail.com Email: martin.thomson@gmail.com
 End of changes. 24 change blocks. 
48 lines changed or deleted 72 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/