title: Using Transport Layer Security (TLS) to Secure QUIC abbrev: QUIC over TLS docname: draft-ietf-quic-tls-latest date: {DATE} category: std ipr: trust200902 area: Transport workgroup: QUIC
stand_alone: yes pi: [toc, sortrefs, symrefs, docmapping]
ins: M. Thomson
name: Martin Thomson
org: Mozilla
email: martin.thomson@gmail.com
role: editor
- ins: S. Turner name: Sean Turner org: sn3rd email: sean@sn3rd.com role: editor
normative:
QUIC-TRANSPORT: title: "QUIC: A UDP-Based Multiplexed and Secure Transport" date: {DATE} seriesinfo: Internet-Draft: draft-ietf-quic-transport-latest author: - ins: J. Iyengar name: Jana Iyengar org: Google role: editor - ins: M. Thomson name: Martin Thomson org: Mozilla role: editor
FIPS180: title: NIST FIPS 180-4, Secure Hash Standard author: name: NIST ins: National Institute of Standards and Technology, U.S. Department of Commerce date: 2012-03 target: http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf
informative:
AEBounds: title: "Limits on Authenticated Encryption Use in TLS" author: - ins: A. Luykx - ins: K. Paterson date: 2016-03-08 target: "http://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf"
QUIC-HTTP: title: "Hypertext Transfer Protocol (HTTP) over QUIC" date: {DATE} seriesinfo: Internet-Draft: draft-ietf-quic-http-latest author: - ins: M. Bishop name: Mike Bishop org: Microsoft role: editor
QUIC-RECOVERY: title: "QUIC Loss Detection and Congestion Control" date: {DATE} seriesinfo: Internet-Draft: draft-ietf-quic-recovery-latest author: - ins: J. Iyengar name: Jana Iyengar org: Google role: editor - ins: I. Swett name: Ian Swett org: Google role: editor
--- abstract
This document describes how Transport Layer Security (TLS) is used to secure QUIC.
--- note_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.
Working Group information can be found at https://github.com/quicwg; source code and issues list for this draft can be found at https://github.com/quicwg/base-drafts/labels/-tls.
--- middle
This document describes how QUIC {{QUIC-TRANSPORT}} is secured using Transport Layer Security (TLS) version 1.3 {{!TLS13=I-D.ietf-tls-tls13}}. TLS 1.3 provides critical latency improvements for connection establishment over previous versions. Absent packet loss, most new connections can be established and secured within a single round trip; on subsequent connections between the same client and server, the client can often send application data immediately, that is, using a zero round trip setup.
This document describes how the standardized TLS 1.3 acts a security component of QUIC. The same design could work for TLS 1.2, though few of the benefits QUIC provides would be realized due to the handshake latency in versions of TLS prior to 1.3.
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 the terminology established in {{QUIC-TRANSPORT}}.
For brevity, the acronym TLS is used to refer to TLS 1.3.
TLS terminology is used when referring to parts of TLS. Though TLS assumes a continuous stream of octets, it divides that stream into records. Most relevant to QUIC are the records that contain TLS handshake messages, which are discrete messages that are used for key agreement, authentication and parameter negotiation. Ordinarily, TLS records can also contain application data, though in the QUIC usage there is no use of TLS application data.
QUIC {{QUIC-TRANSPORT}} assumes responsibility for the confidentiality and integrity protection of packets. For this it uses keys derived from a TLS 1.3 connection {{!TLS13}}; QUIC also relies on TLS 1.3 for authentication and negotiation of parameters that are critical to security and performance.
Rather than a strict layering, these two protocols are co-dependent: QUIC uses the TLS handshake; TLS uses the reliability and ordered delivery provided by QUIC streams.
This document defines how QUIC interacts with TLS. This includes a description of how TLS is used, how keying material is derived from TLS, and the application of that keying material to protect QUIC packets. {{schematic}} shows the basic interactions between TLS and QUIC, with the QUIC packet protection being called out specially.
+------------+ +------------+
| |------ Handshake ------>| |
| |<-- Validate Address ---| |
| |-- OK/Error/Validate -->| |
| |<----- Handshake -------| |
| QUIC |------ Validate ------->| TLS |
| | | |
| |<------ 0-RTT OK -------| |
| |<------ 1-RTT OK -------| |
| |<--- Handshake Done ----| |
+------------+ +------------+
| ^ ^ |
| Protect | Protected | |
v | Packet | |
+------------+ / /
| QUIC | / /
| Packet |-------- Get Secret -------' /
| Protection |<-------- Secret -----------'
+------------+
{: #schematic title="QUIC and TLS Interactions"}
The initial state of a QUIC connection has packets exchanged without any form of protection. In this state, QUIC is limited to using stream 0 and associated packets. Stream 0 is reserved for a TLS connection. This is a complete TLS connection as it would appear when layered over TCP; the only difference is that QUIC provides the reliability and ordering that would otherwise be provided by TCP.
At certain points during the TLS handshake, keying material is exported from the TLS connection for use by QUIC. This keying material is used to derive packet protection keys. Details on how and when keys are derived and used are included in {{packet-protection}}.
TLS provides two endpoints with a way to establish a means of communication over an untrusted medium (that is, the Internet) that ensures that messages they exchange cannot be observed, modified, or forged.
TLS features can be separated into two basic functions: an authenticated key exchange and record protection. QUIC primarily uses the authenticated key exchange provided by TLS but provides its own packet protection.
The TLS authenticated key exchange occurs between two entities: client and server. The client initiates the exchange and the server responds. If the key exchange completes successfully, both client and server will agree on a secret. TLS supports both pre-shared key (PSK) and Diffie-Hellman (DH) key exchanges. PSK is the basis for 0-RTT; the latter provides perfect forward secrecy (PFS) when the DH keys are destroyed.
After completing the TLS handshake, the client will have learned and authenticated an identity for the server and the server is optionally able to learn and authenticate an identity for the client. TLS supports X.509 {{?RFC5280}} certificate-based authentication for both server and client.
The TLS key exchange is resistent to tampering by attackers and it produces shared secrets that cannot be controlled by either participating peer.
TLS 1.3 provides two basic handshake modes of interest to QUIC:
-
A full 1-RTT handshake in which the client is able to send application data after one round trip and the server immediately responds after receiving the first handshake message from the client.
-
A 0-RTT handshake in which the client uses information it has previously learned about the server to send application data immediately. This application data can be replayed by an attacker so it MUST NOT carry a self-contained trigger for any non-idempotent action.
A simplified TLS 1.3 handshake with 0-RTT application data is shown in {{tls-full}}, see {{!TLS13}} for more options and details.
Client Server
ClientHello
(0-RTT Application Data) -------->
ServerHello
{EncryptedExtensions}
{Finished}
<-------- [Application Data]
(EndOfEarlyData)
{Finished} -------->
[Application Data] <-------> [Application Data]
{: #tls-full title="TLS Handshake with 0-RTT"}
This 0-RTT handshake is only possible if the client and server have previously communicated. In the 1-RTT handshake, the client is unable to send protected application data until it has received all of the handshake messages sent by the server.
Two additional variations on this basic handshake exchange are relevant to this document:
-
The server can respond to a ClientHello with a HelloRetryRequest, which adds an additional round trip prior to the basic exchange. This is needed if the server wishes to request a different key exchange key from the client. HelloRetryRequest is also used to verify that the client is correctly able to receive packets on the address it claims to have (see {{QUIC-TRANSPORT}}).
-
A pre-shared key mode can be used for subsequent handshakes to reduce the number of public key operations. This is the basis for 0-RTT data, even if the remainder of the connection is protected by a new Diffie-Hellman exchange.
QUIC reserves stream 0 for a TLS connection. Stream 0 contains a complete TLS connection, which includes the TLS record layer. Other than the definition of a QUIC-specific extension (see {{quic_parameters}}), TLS is unmodified for this use. This means that TLS will apply confidentiality and integrity protection to its records. In particular, TLS record protection is what provides confidentiality protection for the TLS handshake messages sent by the server.
QUIC permits a client to send frames on streams starting from the first packet. The initial packet from a client contains a stream frame for stream 0 that contains the first TLS handshake messages from the client. This allows the TLS handshake to start with the first packet that a client sends.
QUIC packets are protected using a scheme that is specific to QUIC, see {{packet-protection}}. Keys are exported from the TLS connection when they become available using a TLS exporter (see Section 7.5 of {{!TLS13}} and {{key-expansion}}). After keys are exported from TLS, QUIC manages its own key schedule.
The integration of QUIC with a TLS handshake is shown in more detail in
{{quic-tls-handshake}}. QUIC STREAM frames on stream 0 carry the TLS
handshake. QUIC performs loss recovery {{QUIC-RECOVERY}} for this stream and
ensures that TLS handshake messages are delivered in the correct order.
Client Server
@H QUIC STREAM Frame(s) <0>:
ClientHello
+ QUIC Extension
-------->
0-RTT Key => @0
@0 QUIC STREAM Frame(s) <any stream>:
Replayable QUIC Frames
-------->
QUIC STREAM Frame <0>: @H
ServerHello
{TLS Handshake Messages}
<--------
1-RTT Key => @1
QUIC Frames <any> @1
<--------
@H QUIC STREAM Frame(s) <0>:
(EndOfEarlyData)
{Finished}
-------->
@1 QUIC Frames <any> <-------> QUIC Frames <any> @1
{: #quic-tls-handshake title="QUIC over TLS Handshake"}
In {{quic-tls-handshake}}, symbols mean:
-
"<" and ">" enclose stream numbers.
-
"@" indicates the keys that are used for protecting the QUIC packet (H = handshake, using keys from the well-known cleartext packet secret; 0 = 0-RTT keys; 1 = 1-RTT keys).
-
"(" and ")" enclose messages that are protected with TLS 0-RTT handshake or application keys.
-
"{" and "}" enclose messages that are protected by the TLS Handshake keys.
If 0-RTT is not attempted, then the client does not send packets protected by the 0-RTT key (@0). In that case, the only key transition on the client is from handshake packets (@H) to 1-RTT protection (@1), which happens after it sends its final set of TLS handshake messages.
Note: two different types of packet are used during the handshake by both client and server. The Initial packet carries a TLS ClientHello message; the remainder of the TLS handshake is carried in Handshake packets. The Retry packet carries a TLS HelloRetryRequest, if it is needed, and Handshake packets carry the remainder of the server handshake.
The server sends TLS handshake messages without protection (@H). The server transitions from no protection (@H) to full 1-RTT protection (@1) after it sends the last of its handshake messages.
Some TLS handshake messages are protected by the TLS handshake record protection. These keys are not exported from the TLS connection for use in QUIC. QUIC packets from the server are sent in the clear until the final transition to 1-RTT keys.
The client transitions from handshake (@H) to 0-RTT keys (@0) when sending 0-RTT data, and subsequently to to 1-RTT keys (@1) after its second flight of TLS handshake messages. This creates the potential for unprotected packets to be received by a server in close proximity to packets that are protected with 1-RTT keys.
More information on key transitions is included in {{hs-protection}}.
As shown in {{schematic}}, the interface from QUIC to TLS consists of four primary functions: Handshake, Source Address Validation, Key Ready Events, and Secret Export.
Additional functions might be needed to configure TLS.
In order to drive the handshake, TLS depends on being able to send and receive handshake messages on stream 0. There are two basic functions on this interface: one where QUIC requests handshake messages and one where QUIC provides handshake packets.
Before starting the handshake QUIC provides TLS with the transport parameters (see {{quic_parameters}}) that it wishes to carry.
A QUIC client starts TLS by requesting TLS handshake octets from TLS. The client acquires handshake octets before sending its first packet.
A QUIC server starts the process by providing TLS with stream 0 octets.
Each time that an endpoint receives data on stream 0, it delivers the octets to TLS if it is able. Each time that TLS is provided with new data, new handshake octets are requested from TLS. TLS might not provide any octets if the handshake messages it has received are incomplete or it has no data to send.
Once the TLS handshake is complete, this is indicated to QUIC along with any final handshake octets that TLS needs to send. TLS also provides QUIC with the transport parameters that the peer advertised during the handshake.
Once the handshake is complete, TLS becomes passive. TLS can still receive data from its peer and respond in kind, but it will not need to send more data unless specifically requested - either by an application or QUIC. One reason to send data is that the server might wish to provide additional or updated session tickets to a client.
When the handshake is complete, QUIC only needs to provide TLS with any data that arrives on stream 0. In the same way that is done during the handshake, new data is requested from TLS after providing received data.
Important:
: Until the handshake is reported as complete, the connection and key exchange are not properly authenticated at the server. Even though 1-RTT keys are available to a server after receiving the first handshake messages from a client, the server cannot consider the client to be authenticated until it receives and validates the client's Finished message.
: The requirement for the server to wait for the client Finished message creates a dependency on that message being delivered. A client can avoid the potential for head-of-line blocking that this implies by sending a copy of the STREAM frame that carries the Finished message in multiple packets. This enables immediate server processing for those packets.
During the processing of the TLS ClientHello, TLS requests that the transport make a decision about whether to request source address validation from the client.
An initial TLS ClientHello that resumes a session includes an address validation token in the session ticket; this includes all attempts at 0-RTT. If the client does not attempt session resumption, no token will be present. While processing the initial ClientHello, TLS provides QUIC with any token that is present. In response, QUIC provides one of three responses:
-
proceed with the connection,
-
ask for client address validation, or
-
abort the connection.
If QUIC requests source address validation, it also provides a new address validation token. TLS includes that along with any information it requires in the cookie extension of a TLS HelloRetryRequest message. In the other cases, the connection either proceeds or terminates with a handshake error.
The client echoes the cookie extension in a second ClientHello. A ClientHello that contains a valid cookie extension will always be in response to a HelloRetryRequest. If address validation was requested by QUIC, then this will include an address validation token. TLS makes a second address validation request of QUIC, including the value extracted from the cookie extension. In response to this request, QUIC cannot ask for client address validation, it can only abort or permit the connection attempt to proceed.
QUIC can provide a new address validation token for use in session resumption at any time after the handshake is complete. Each time a new token is provided TLS generates a NewSessionTicket message, with the token included in the ticket.
See {{client-address-validation}} for more details on client address validation.
TLS provides QUIC with signals when 0-RTT and 1-RTT keys are ready for use. These events are not asynchronous, they always occur immediately after TLS is provided with new handshake octets, or after TLS produces handshake octets.
When TLS completed its handshake, 1-RTT keys can be provided to QUIC. On both client and server, this occurs after sending the TLS Finished message.
This ordering means that there could be frames that carry TLS handshake messages ready to send at the same time that application data is available. An implementation MUST ensure that TLS handshake messages are always sent in packets protected with handshake keys (see {{handshake-secrets}}). Separate packets are required for data that needs protection from 1-RTT keys.
If 0-RTT is possible, it is ready after the client sends a TLS ClientHello message or the server receives that message. After providing a QUIC client with the first handshake octets, the TLS stack might signal that 0-RTT keys are ready. On the server, after receiving handshake octets that contain a ClientHello message, a TLS server might signal that 0-RTT keys are available.
1-RTT keys are used for packets in both directions. 0-RTT keys are only used to protect packets sent by the client.
Details how secrets are exported from TLS are included in {{key-expansion}}.
{{exchange-summary}} summarizes the exchange between QUIC and TLS for both client and server.
Client Server
Get Handshake
0-RTT Key Ready
--- send/receive --->
Handshake Received
0-RTT Key Ready
Get Handshake
1-RTT Keys Ready
<--- send/receive ---
Handshake Received
Get Handshake
Handshake Complete
1-RTT Keys Ready
--- send/receive --->
Handshake Received
Get Handshake
Handshake Complete
<--- send/receive ---
Handshake Received
Get Handshake
{: #exchange-summary title="Interaction Summary between QUIC and TLS"}
This document describes how TLS 1.3 {{!TLS13}} is used with QUIC.
In practice, the TLS handshake will negotiate a version of TLS to use. This could result in a newer version of TLS than 1.3 being negotiated if both endpoints support that version. This is acceptable provided that the features of TLS 1.3 that are used by QUIC are supported by the newer version.
A badly configured TLS implementation could negotiate TLS 1.2 or another older version of TLS. An endpoint MUST terminate the connection if a version of TLS older than 1.3 is negotiated.
QUIC requires that the initial handshake packet from a client fit within the payload of a single packet. The size limits on QUIC packets mean that a record containing a ClientHello needs to fit within 1171 octets.
A TLS ClientHello can fit within this limit with ample space remaining. However, there are several variables that could cause this limit to be exceeded. Implementations are reminded that large session tickets or HelloRetryRequest cookies, multiple or large key shares, and long lists of supported ciphers, signature algorithms, versions, QUIC transport parameters, and other negotiable parameters and extensions could cause this message to grow.
For servers, the size of the session tickets and HelloRetryRequest cookie extension can have an effect on a client's ability to connect. Choosing a small value increases the probability that these values can be successfully used by a client.
The TLS implementation does not need to ensure that the ClientHello is sufficiently large. QUIC PADDING frames are added to increase the size of the packet as necessary.
The requirements for authentication depend on the application protocol that is in use. TLS provides server authentication and permits the server to request client authentication.
A client MUST authenticate the identity of the server. This typically involves verification that the identity of the server is included in a certificate and that the certificate is issued by a trusted entity (see for example {{?RFC2818}}).
A server MAY request that the client authenticate during the handshake. A server MAY refuse a connection if the client is unable to authenticate when requested. The requirements for client authentication vary based on application protocol and deployment.
A server MUST NOT use post-handshake client authentication (see Section 4.6.2 of {{!TLS13}}).
Errors in the TLS connection SHOULD be signaled using TLS alerts on stream 0. A failure in the handshake MUST be treated as a QUIC connection error of type TLS_HANDSHAKE_FAILED. Once the handshake is complete, an error in the TLS connection that causes a TLS alert to be sent or received MUST be treated as a QUIC connection error of type TLS_FATAL_ALERT_GENERATED or TLS_FATAL_ALERT_RECEIVED respectively.
QUIC packet protection provides authenticated encryption of packets. This provides confidentiality and integrity protection for the content of packets (see {{aead}}). Packet protection uses keys that are exported from the TLS connection (see {{key-expansion}}).
Different keys are used for QUIC packet protection and TLS record protection. TLS handshake messages are protected solely with TLS record protection, but post-handshake messages are redundantly proteted with both both the QUIC packet protection and the TLS record protection. These messages are limited in number, and so the additional overhead is small.
As TLS reports the availability of keying material, the packet protection keys and initialization vectors (IVs) are updated (see {{key-expansion}}). The selection of AEAD function is also updated to match the AEAD negotiated by TLS.
For packets other than any handshake packets (see {{hs-protection}}), once a change of keys has been made, packets with higher packet numbers MUST be sent with the new keying material. The KEY_PHASE bit on these packets is inverted each time new keys are installed to signal the use of the new keys to the recipient (see {{key-phases}} for details).
An endpoint retransmits stream data in a new packet. New packets have new packet numbers and use the latest packet protection keys. This simplifies key management when there are key updates (see {{key-update}}).
QUIC uses a system of packet protection secrets, keys and IVs that are modelled on the system used in TLS {{!TLS13}}. The secrets that QUIC uses as the basis of its key schedule are obtained using TLS exporters (see Section 7.5 of {{!TLS13}}).
QUIC uses HKDF with the same hash function negotiated by TLS for key derivation. For example, if TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is used.
Packets that carry the TLS handshake (Initial, Retry, and Handshake) are protected with secrets derived from the connection ID used in the client's Initial packet. Specifically:
quic_version_1_salt = afc824ec5fc77eca1e9d36f37fb2d46518c36639
handshake_secret = HKDF-Extract(quic_version_1_salt,
client_connection_id)
client_handshake_secret =
QHKDF-Expand(handshake_secret, "client hs", Hash.length)
server_handshake_secret =
QHKDF-Expand(handshake_secret, "server hs", Hash.length)
The HKDF for the handshake secrets and keys derived from them uses the SHA-256 hash function {{FIPS180}}.
The salt value is a 20 octet sequence shown in the figure in hexadecimal notation. Future versions of QUIC SHOULD generate a new salt value, thus ensuring that the keys are different for each version of QUIC. This prevents a middlebox that only recognizes one version of QUIC from seeing or modifying the contents of handshake packets from future versions.
0-RTT keys are those keys that are used in resumed connections prior to the completion of the TLS handshake. Data sent using 0-RTT keys might be replayed and so has some restrictions on its use, see {{using-early-data}}. 0-RTT keys are used after sending or receiving a ClientHello.
The secret is exported from TLS using the exporter label "EXPORTER-QUIC 0rtt" and an empty context. The size of the secret MUST be the size of the hash output for the PRF hash function negotiated by TLS. This uses the TLS early_exporter_secret. The QUIC 0-RTT secret is only used for protection of packets sent by the client.
client_0rtt_secret
= TLS-Exporter("EXPORTER-QUIC 0rtt", "", Hash.length)
1-RTT keys are used by both client and server after the TLS handshake completes. There are two secrets used at any time: one is used to derive packet protection keys for packets sent by the client, the other for packet protection keys on packets sent by the server.
The initial client packet protection secret is exported from TLS using the exporter label "EXPORTER-QUIC client 1rtt"; the initial server packet protection secret uses the exporter label "EXPORTER-QUIC server 1rtt". Both exporters use an empty context. The size of the secret MUST be the size of the hash output for the PRF hash function negotiated by TLS.
client_pp_secret_0 =
TLS-Exporter("EXPORTER-QUIC client 1rtt", "", Hash.length)
server_pp_secret_0 =
TLS-Exporter("EXPORTER-QUIC server 1rtt", "", Hash.length)
These secrets are used to derive the initial client and server packet protection keys.
After a key update (see {{key-update}}), these secrets are updated using the QHKDF-Expand function. The QHKDF-Expand function is similar in definition to HKDF-Expand-Label defined in Section 7.1 of {{!TLS13}}, but it has a different base label and omits the hash argument. QHKDF-Expand uses the PRF hash function negotiated by TLS. The replacement secret is derived using the existing Secret, a Label of "client 1rtt" for the client and "server 1rtt" for the server, and the same output Length as the PRF hash function selected by TLS.
client_pp_secret_<N+1> =
QHKDF-Expand(client_pp_secret_<N>, "client 1rtt", Hash.length)
server_pp_secret_<N+1> =
QHKDF-Expand(server_pp_secret_<N>, "server 1rtt", Hash.length)
This allows for a succession of new secrets to be created as needed.
HKDF-Expand-Label uses HKDF-Expand {{!RFC5869}} as shown:
QHKDF-Expand(Secret, Label, Length) =
HKDF-Expand(Secret, QuicHkdfLabel, Length)
Where the info parameter, QuicHkdfLabel, is specified as:
struct {
uint16 length = Length;
opaque label<6..255> = "QUIC " + Label;
uint8 hashLength = 0;
} QuicHkdfLabel;
For example, the client packet protection secret uses an info parameter of:
info = (HashLen / 256) || (HashLen % 256) || 0x1f ||
"QUIC client 1rtt" || 0x00
The complete key expansion uses an identical process for key expansion as defined in Section 7.3 of {{!TLS13}}, using different values for the input secret and labels. QUIC uses the AEAD function negotiated by TLS.
The packet protection key and IV used to protect the 0-RTT packets sent by a client are derived from the QUIC 0-RTT secret. The packet protection keys and IVs for 1-RTT packets sent by the client and server are derived from the current generation of client and server 1-RTT secrets (client_pp_secret_<i> and server_pp_secret_<i>) respectively. The length of the output is determined by the requirements of the AEAD function selected by TLS. All ciphersuites currently used for QUIC have a 16-byte authentication tag and produce an ouput 16 bytes larger than their input. The key length is the AEAD key size. As defined in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have N_MIN set to 12). For any secret S, the corresponding key and IV are derived as shown below:
key = QHKDF-Expand(S, "key", key_length)
iv = QHKDF-Expand(S, "iv", iv_length)
The QUIC record protection initially starts without keying material. When the TLS state machine reports that the ClientHello has been sent, the 0-RTT keys can be generated and installed for writing. When the TLS state machine reports completion of the handshake, the 1-RTT keys can be generated and installed for writing.
The Authentication Encryption with Associated Data (AEAD) {{!AEAD}} function used for QUIC packet protection is AEAD that is negotiated for use with the TLS connection. For example, if TLS is using the TLS_AES_128_GCM_SHA256, the AEAD_AES_128_GCM function is used.
All QUIC packets other than Version Negotiation and Stateless Reset packets are protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shared secret, packets are protected with AEAD_AES_128_GCM and a key derived from the client's connection ID (see {{handshake-secrets}}). This provides protection against off-path attackers and robustness against QUIC version unaware middleboxes, but not against on-path attackers.
Once TLS has provided a key, the contents of regular QUIC packets immediately after any TLS messages have been sent are protected by the AEAD selected by TLS.
The key, K, is either the client packet protection key (client_pp_key_<i>) or the server packet protection key (server_pp_key_<i>), derived as defined in {{key-expansion}}.
The nonce, N, is formed by combining the packet protection IV (either client_pp_iv_<i> or server_pp_iv_<i>) with the packet number. The 64 bits of the reconstructed QUIC packet number in network byte order is left-padded with zeros to the size of the IV. The exclusive OR of the padded packet number and the IV forms the AEAD nonce.
The associated data, A, for the AEAD is the contents of the QUIC header, starting from the flags octet in either the short or long header.
The input plaintext, P, for the AEAD is the content of the QUIC frame following the header, as described in {{QUIC-TRANSPORT}}.
The output ciphertext, C, of the AEAD is transmitted in place of P.
QUIC has a single, contiguous packet number space. In comparison, TLS restarts its sequence number each time that record protection keys are changed. The sequence number restart in TLS ensures that a compromise of the current traffic keys does not allow an attacker to truncate the data that is sent after a key update by sending additional packets under the old key (causing new packets to be discarded).
QUIC does not assume a reliable transport and is required to handle attacks where packets are dropped in other ways. QUIC is therefore not affected by this form of truncation.
The QUIC packet number is not reset and it is not permitted to go higher than its maximum value of 2^64-1. This establishes a hard limit on the number of packets that can be sent.
Some AEAD functions have limits for how many packets can be encrypted under the same key and IV (see for example {{AEBounds}}). This might be lower than the packet number limit. An endpoint MUST initiate a key update ({{key-update}}) prior to exceeding any limit set for the AEAD that is in use.
TLS maintains a separate sequence number that is used for record protection on the connection that is hosted on stream 0. This sequence number is not visible to QUIC.
Once an endpoint successfully receives a packet with a given packet number, it MUST discard all packets with higher packet numbers if they cannot be successfully unprotected with either the same key, or - if there is a key update
- the next packet protection key (see {{key-update}}). Similarly, a packet that appears to trigger a key update, but cannot be unprotected successfully MUST be discarded.
Failure to unprotect a packet does not necessarily indicate the existence of a protocol error in a peer or an attack. The truncated packet number encoding used in QUIC can cause packet numbers to be decoded incorrectly if they are delayed significantly.
Section 7.7.1.1 of {{QUIC-TRANSPORT}} also requires a secret to compute packet number gaps on connection ID transitions. That secret is computed as:
packet_number_secret =
TLS-Exporter("EXPORTER-QUIC packet number", "", Hash.length)
As TLS reports the availability of 0-RTT and 1-RTT keys, new keying material can be exported from TLS and used for QUIC packet protection. At each transition during the handshake a new secret is exported from TLS and packet protection keys are derived from that secret.
Every time that a new set of keys is used for protecting outbound packets, the KEY_PHASE bit in the public flags is toggled. 0-RTT protected packets use the QUIC long header, they do not use the KEY_PHASE bit to select the correct keys (see {{first-keys}}).
Once the connection is fully enabled, the KEY_PHASE bit allows a recipient to detect a change in keying material without necessarily needing to receive the first packet that triggered the change. An endpoint that notices a changed KEY_PHASE bit can update keys and decrypt the packet that contains the changed bit, see {{key-update}}.
The KEY_PHASE bit is included as the 0x20 bit of the QUIC short header.
Transitions between keys during the handshake are complicated by the need to ensure that TLS handshake messages are sent with the correct packet protection.
The initial exchange of packets that carry the TLS handshake are AEAD-protected using the handshake secrets generated as described in {{handshake-secrets}}. All TLS handshake messages up to the TLS Finished message sent by either endpoint use packets protected with handshake keys.
Any TLS handshake messages that are sent after completing the TLS handshake do not need special packet protection rules. Packets containing these messages use the packet protection keys that are current at the time of sending (or retransmission).
Like the client, a server MUST send retransmissions of its unprotected handshake messages or acknowledgments for unprotected handshake messages sent by the client in packets protected with handshake keys.
Once the TLS handshake is complete, keying material is exported from TLS and used to protect QUIC packets.
Packets protected with 1-RTT keys initially have a KEY_PHASE bit set to 0. This bit inverts with each subsequent key update (see {{key-update}}).
If the client sends 0-RTT data, it uses the 0-RTT packet type. The packet that contains the TLS EndOfEarlyData and Finished messages are sent in packets protected with handshake keys.
Using distinct packet types during the handshake for handshake messages, 0-RTT data, and 1-RTT data ensures that the server is able to distinguish between the different keys used to remove packet protection. All of these packets can arrive concurrently at a server.
A server might choose to retain 0-RTT packets that arrive before a TLS ClientHello. The server can then use those packets once the ClientHello arrives. However, the potential for denial of service from buffering 0-RTT packets is significant. These packets cannot be authenticated and so might be employed by an attacker to exhaust server resources. Limiting the number of packets that are saved might be necessary.
The server transitions to using 1-RTT keys after sending its first flight of TLS handshake messages, ending in the Finished. From this point, the server protects all packets with 1-RTT keys. Future packets are therefore protected with 1-RTT keys. Initially, these are marked with a KEY_PHASE of 0.
TLS handshake messages from both client and server are critical to the key exchange. The contents of these messages determines the keys used to protect later messages. If these handshake messages are included in packets that are protected with these keys, they will be indecipherable to the recipient.
Even though newer keys could be available when retransmitting, retransmissions of these handshake messages MUST be sent in packets protected with handshake keys. An endpoint MUST generate ACK frames for these messages and send them in packets protected with handshake keys.
A HelloRetryRequest handshake message might be used to reject an initial ClientHello. A HelloRetryRequest handshake message is sent in a Retry packet; any second ClientHello that is sent in response uses a Initial packet type. These packets are only protected with a predictable key (see {{handshake-secrets}}). This is natural, because no shared secret will be available when these messages need to be sent. Upon receipt of a HelloRetryRequest, a client SHOULD cease any transmission of 0-RTT data; 0-RTT data will only be discarded by any server that sends a HelloRetryRequest.
The packet type ensures that protected packets are clearly distinguished from unprotected packets. Loss or reordering might cause unprotected packets to arrive once 1-RTT keys are in use, unprotected packets are easily distinguished from 1-RTT packets using the packet type.
Once 1-RTT keys are available to an endpoint, it no longer needs the TLS handshake messages that are carried in unprotected packets. However, a server might need to retransmit its TLS handshake messages in response to receiving an unprotected packet that contains ACK frames. A server MUST process ACK frames in unprotected packets until the TLS handshake is reported as complete, or it receives an ACK frame in a protected packet that acknowledges all of its handshake messages.
To limit the number of key phases that could be active, an endpoint MUST NOT initiate a key update while there are any unacknowledged handshake messages, see {{key-update}}.
Once the TLS handshake is complete, the KEY_PHASE bit allows for refreshes of keying material by either peer. Endpoints start using updated keys immediately without additional signaling; the change in the KEY_PHASE bit indicates that a new key is in use.
An endpoint MUST NOT initiate more than one key update at a time. A new key cannot be used until the endpoint has received and successfully decrypted a packet with a matching KEY_PHASE. Note that when 0-RTT is attempted the value of the KEY_PHASE bit will be different on packets sent by either peer.
A receiving endpoint detects an update when the KEY_PHASE bit doesn't match what it is expecting. It creates a new secret (see {{key-expansion}}) and the corresponding read key and IV. If the packet can be decrypted and authenticated using these values, then the keys it uses for packet protection are also updated. The next packet sent by the endpoint will then use the new keys.
An endpoint doesn't need to send packets immediately when it detects that its peer has updated keys. The next packet that it sends will simply use the new keys. If an endpoint detects a second update before it has sent any packets with updated keys it indicates that its peer has updated keys twice without awaiting a reciprocal update. An endpoint MUST treat consecutive key updates as a fatal error and abort the connection.
An endpoint SHOULD retain old keys for a short period to allow it to decrypt packets with smaller packet numbers than the packet that triggered the key update. This allows an endpoint to consume packets that are reordered around the transition between keys. Packets with higher packet numbers always use the updated keys and MUST NOT be decrypted with old keys.
Keys and their corresponding secrets SHOULD be discarded when an endpoint has received all packets with sequence numbers lower than the lowest sequence number used for the new key. An endpoint might discard keys if it determines that the length of the delay to affected packets is excessive.
This ensures that once the handshake is complete, packets with the same KEY_PHASE will have the same packet protection keys, unless there are multiple key updates in a short time frame succession and significant packet reordering.
Initiating Peer Responding Peer
@M QUIC Frames
New Keys -> @N
@N QUIC Frames
-------->
QUIC Frames @M
New Keys -> @N
QUIC Frames @N
<--------
{: #ex-key-update title="Key Update"}
As shown in {{quic-tls-handshake}} and {{ex-key-update}}, there is never a situation where there are more than two different sets of keying material that might be received by a peer. Once both sending and receiving keys have been updated,
A server cannot initiate a key update until it has received the client's Finished message. Otherwise, packets protected by the updated keys could be confused for retransmissions of handshake messages. A client cannot initiate a key update until all of its handshake messages have been acknowledged by the server.
A packet that triggers a key update could arrive after successfully processing a packet with a higher packet number. This is only possible if there is a key compromise and an attack, or if the peer is incorrectly reverting to use of old keys. Because the latter cannot be differentiated from an attack, an endpoint MUST immediately terminate the connection if it detects this condition.
Two tools are provided by TLS to enable validation of client source addresses at a server: the cookie in the HelloRetryRequest message, and the ticket in the NewSessionTicket message.
The cookie extension in the TLS HelloRetryRequest message allows a server to perform source address validation during the handshake.
When QUIC requests address validation during the processing of the first ClientHello, the token it provides is included in the cookie extension of a HelloRetryRequest. As long as the cookie cannot be successfully guessed by a client, the server can be assured that the client received the HelloRetryRequest if it includes the value in a second ClientHello.
An initial ClientHello never includes a cookie extension. Thus, if a server constructs a cookie that contains all the information necessary to reconstruct state, it can discard local state after sending a HelloRetryRequest. Presence of a valid cookie in a ClientHello indicates that the ClientHello is a second attempt from the client.
An address validation token can be extracted from a second ClientHello and passed to the transport for further validation. If that validation fails, the server MUST fail the TLS handshake and send an illegal_parameter alert.
Combining address validation with the other uses of HelloRetryRequest ensures that there are fewer ways in which an additional round-trip can be added to the handshake. In particular, this makes it possible to combine a request for address validation with a request for a different client key share.
If TLS needs to send a HelloRetryRequest for other reasons, it needs to ensure that it can correctly identify the reason that the HelloRetryRequest was generated. During the processing of a second ClientHello, TLS does not need to consult the transport protocol regarding address validation if address validation was not requested originally. In such cases, the cookie extension could either be absent or it could indicate that an address validation token is not present.
A server can use the cookie extension to store all state necessary to continue the connection. This allows a server to avoid committing state for clients that have unvalidated source addresses.
For instance, a server could use a statically-configured key to encrypt the information that it requires and include that information in the cookie. In addition to address validation information, a server that uses encryption also needs to be able recover the hash of the ClientHello and its length, plus any information it needs in order to reconstruct the HelloRetryRequest.
A server does not need to maintain state for the connection when sending a HelloRetryRequest message. This might be necessary to avoid creating a denial of service exposure for the server. However, this means that information about the transport will be lost at the server. This includes the stream offset of stream 0, the packet number that the server selects, and any opportunity to measure round trip time.
A server MUST send a TLS HelloRetryRequest in a Retry packet. Using a Retry packet causes the client to reset stream offsets. It also avoids the need for the server select an initial packet number, which would need to be remembered so that subsequent packets could be correctly numbered.
A HelloRetryRequest message MUST NOT be split between multiple Retry packets. This means that HelloRetryRequest is subject to the same size constraints as a ClientHello (see {{clienthello-size}}).
A client might send multiple Initial packets in response to loss. If a server sends a Retry packet in response to an Initial packet, it does not have to generate the same Retry packet each time. Variations in Retry packet, if used by a client, could lead to multiple connections derived from the same ClientHello. Reuse of the client nonce is not supported by TLS and could lead to security vulnerabilities. Clients that receive multiple Retry packets MUST use only one and discard the remainder.
The ticket in the TLS NewSessionTicket message allows a server to provide a client with a similar sort of token. When a client resumes a TLS connection - whether or not 0-RTT is attempted - it includes the ticket in the handshake message. As with the HelloRetryRequest cookie, the server includes the address validation token in the ticket. TLS provides the token it extracts from the session ticket to the transport when it asks whether source address validation is needed.
If both a HelloRetryRequest cookie and a session ticket are present in the ClientHello, only the token from the cookie is passed to the transport. The presence of a cookie indicates that this is a second ClientHello - the token from the session ticket will have been provided to the transport when it appeared in the first ClientHello.
A server can send a NewSessionTicket message at any time. This allows it to update the state - and the address validation token - that is included in the ticket. This might be done to refresh the ticket or token, or it might be generated in response to changes in the state of the connection. QUIC can request that a NewSessionTicket be sent by providing a new address validation token.
A server that intends to support 0-RTT SHOULD provide an address validation token immediately after completing the TLS handshake.
TLS MUST provide integrity protection for address validation token unless the transport guarantees integrity protection by other means. For a NewSessionTicket that includes confidential information - such as the resumption secret - including the token under authenticated encryption ensures that the token gains both confidentiality and integrity protection without duplicating the overheads of that protection.
Implementations MUST NOT exchange data on any stream other than stream 0 without packet protection. QUIC requires the use of several types of frame for managing loss detection and recovery during this phase. In addition, it might be useful to use the data acquired during the exchange of unauthenticated messages for congestion control.
This section generally only applies to TLS handshake messages from both peers and acknowledgments of the packets carrying those messages. In many cases, the need for servers to provide acknowledgments is minimal, since the messages that clients send are small and implicitly acknowledged by the server's responses.
The actions that a peer takes as a result of receiving an unauthenticated packet needs to be limited. In particular, state established by these packets cannot be retained once record protection commences.
There are several approaches possible for dealing with unauthenticated packets prior to handshake completion:
- discard and ignore them
- use them, but reset any state that is established once the handshake completes
- use them and authenticate them afterwards; failing the handshake if they can't be authenticated
- save them and use them when they can be properly authenticated
- treat them as a fatal error
Different strategies are appropriate for different types of data. This document proposes that all strategies are possible depending on the type of message.
-
Transport parameters are made usable and authenticated as part of the TLS handshake (see {{quic_parameters}}).
-
Most unprotected messages are treated as fatal errors when received except for the small number necessary to permit the handshake to complete (see {{pre-hs-unprotected}}).
-
Protected packets can either be discarded or saved and later used (see {{pre-hs-protected}}).
This section describes the handling of messages that are sent and received prior to the completion of the TLS handshake.
Sending and receiving unprotected messages is hazardous. Unless expressly permitted, receipt of an unprotected message of any kind MUST be treated as a fatal error.
STREAM frames for stream 0 are permitted. These carry the TLS handshake
messages. Once 1-RTT keys are available, unprotected STREAM frames on stream
0 can be ignored.
Receiving unprotected STREAM frames for other streams MUST be treated as a
fatal error.
ACK frames are permitted prior to the handshake being complete. Information
learned from ACK frames cannot be entirely relied upon, since an attacker is
able to inject these packets. Timing and packet retransmission information from
ACK frames is critical to the functioning of the protocol, but these frames
might be spoofed or altered.
Endpoints MUST NOT use an ACK frame in an unprotected packet to acknowledge
packets that were protected by 0-RTT or 1-RTT keys. An endpoint MUST treat
receipt of an ACK frame in an unprotected packet that claims to acknowledge
protected packets as a connection error of type OPTIMISTIC_ACK. An endpoint
that can read protected data is always able to send protected data.
Note:
: 0-RTT data can be acknowledged by the server as it receives it, but any packets containing acknowledgments of 0-RTT data cannot have packet protection removed by the client until the TLS handshake is complete. The 1-RTT keys necessary to remove packet protection cannot be derived until the client receives all server handshake messages.
An endpoint SHOULD use data from ACK frames carried in unprotected packets or
packets protected with 0-RTT keys only during the initial handshake. All ACK
frames contained in unprotected packets that are received after successful
receipt of a packet protected with 1-RTT keys MUST be discarded. An endpoint
SHOULD therefore include acknowledgments for unprotected and any packets
protected with 0-RTT keys until it sees an acknowledgment for a packet that is
both protected with 1-RTT keys and contains an ACK frame.
MAX_DATA, MAX_STREAM_DATA, BLOCKED, STREAM_BLOCKED, and MAX_STREAM_ID
frames MUST NOT be sent unprotected.
Though data is exchanged on stream 0, the initial flow control window on that stream is sufficiently large to allow the TLS handshake to complete. This limits the maximum size of the TLS handshake and would prevent a server or client from using an abnormally large certificate chain.
Stream 0 is exempt from the connection-level flow control window.
Consequently, there is no need to signal being blocked on flow control.
Similarly, there is no need to increase the number of allowed streams until the handshake completes.
The CONNECTION_CLOSE frame MAY be sent by either endpoint in a Handshake
packet. This allows an endpoint to signal a fatal error with connection
establishment. A STREAM frame carrying a TLS alert MAY be included in the
same packet.
Accepting unprotected - specifically unauthenticated - packets presents a denial of service risk to endpoints. An attacker that is able to inject unprotected packets can cause a recipient to drop even protected packets with a matching sequence number. The spurious packet shadows the genuine packet, causing the genuine packet to be ignored as redundant.
Once the TLS handshake is complete, both peers MUST ignore unprotected packets. From that point onward, unprotected messages can be safely dropped.
Since only TLS handshake packets and acknowledgments are sent in the clear, an attacker is able to force implementations to rely on retransmission for packets that are lost or shadowed. Thus, an attacker that intends to deny service to an endpoint has to drop or shadow protected packets in order to ensure that their victim continues to accept unprotected packets. The ability to shadow packets means that an attacker does not need to be on path.
In addition to causing valid packets to be dropped, an attacker can generate packets with an intent of causing the recipient to expend processing resources. See {{useless}} for a discussion of these risks.
To avoid receiving TLS packets that contain no useful data, a TLS implementation MUST reject empty TLS handshake records and any record that is not permitted by the TLS state machine. Any TLS application data or alerts that is received prior to the end of the handshake MUST be treated as a fatal error.
If 0-RTT keys are available, the lack of replay protection means that restrictions on their use are necessary to avoid replay attacks on the protocol.
A client MUST only use 0-RTT keys to protect data that is idempotent. A client MAY wish to apply additional restrictions on what data it sends prior to the completion of the TLS handshake. A client otherwise treats 0-RTT keys as equivalent to 1-RTT keys.
A client that receives an indication that its 0-RTT data has been accepted by a server can send 0-RTT data until it receives all of the server's handshake messages. A client SHOULD stop sending 0-RTT data if it receives an indication that 0-RTT data has been rejected.
A server MUST NOT use 0-RTT keys to protect packets.
Due to reordering and loss, protected packets might be received by an endpoint before the final TLS handshake messages are received. A client will be unable to decrypt 1-RTT packets from the server, whereas a server will be able to decrypt 1-RTT packets from the client.
Packets protected with 1-RTT keys MAY be stored and later decrypted and used once the handshake is complete. A server MUST NOT use 1-RTT protected packets before verifying either the client Finished message or - in the case that the server has chosen to use a pre-shared key - the pre-shared key binder (see Section 4.2.8 of {{!TLS13}}). Verifying these values provides the server with an assurance that the ClientHello has not been modified.
A server could receive packets protected with 0-RTT keys prior to receiving a TLS ClientHello. The server MAY retain these packets for later decryption in anticipation of receiving a ClientHello.
Receiving and verifying the TLS Finished message is critical in ensuring the integrity of the TLS handshake. A server MUST NOT use protected packets from the client prior to verifying the client Finished message if its response depends on client authentication.
QUIC uses the TLS handshake for more than just negotiation of cryptographic parameters. The TLS handshake validates protocol version selection, provides preliminary values for QUIC transport parameters, and allows a server to perform return routeability checks on clients.
The QUIC version negotiation mechanism is used to negotiate the version of QUIC that is used prior to the completion of the handshake. However, this packet is not authenticated, enabling an active attacker to force a version downgrade.
To ensure that a QUIC version downgrade is not forced by an attacker, version information is copied into the TLS handshake, which provides integrity protection for the QUIC negotiation. This does not prevent version downgrade prior to the completion of the handshake, though it means that a downgrade causes a handshake failure.
TLS uses Application Layer Protocol Negotiation (ALPN) {{!RFC7301}} to select an application protocol. The application-layer protocol MAY restrict the QUIC versions that it can operate over. Servers MUST select an application protocol compatible with the QUIC version that the client has selected.
If the server cannot select a compatible combination of application protocol and QUIC version, it MUST abort the connection. A client MUST abort a connection if the server picks an incompatible combination of QUIC version and ALPN identifier.
QUIC transport parameters are carried in a TLS extension. Different versions of QUIC might define a different format for this struct.
Including transport parameters in the TLS handshake provides integrity protection for these values.
enum {
quic_transport_parameters(26), (65535)
} ExtensionType;
The extension_data field of the quic_transport_parameters extension contains a
value that is defined by the version of QUIC that is in use. The
quic_transport_parameters extension carries a TransportParameters when the
version of QUIC defined in {{QUIC-TRANSPORT}} is used.
The quic_transport_parameters extension is carried in the ClientHello and the EncryptedExtensions messages during the handshake. The extension MAY be included in a NewSessionTicket message.
QUIC uses TLS without modification. Therefore, it is possible to use a pre-shared key that was established in a TLS handshake over TCP to enable 0-RTT in QUIC. Similarly, QUIC can provide a pre-shared key that can be used to enable 0-RTT in TCP.
All the restrictions on the use of 0-RTT apply, with the exception of the ALPN label, which MUST only change to a label that is explicitly designated as being compatible. The client indicates which ALPN label it has chosen by placing that ALPN label first in the ALPN extension. In order to be usable for 0-RTT, the NewSessionTicket MUST contain the "max_early_data" extension with the value 0xffffffff; the amount of data which the client can send in 0-RTT is controlled by the "initial_max_data" transport parameter supplied by the server. A client MUST treat receipt of a NewSessionTicket that contains a "max_early_data" extension with any other value as a connection error of type PROTOCOL_VIOLATION.
The certificate that the server uses MUST be considered valid for both connections, which will use different protocol stacks and could use different port numbers. For instance, HTTP/1.1 and HTTP/2 operate over TLS and TCP, whereas QUIC operates over UDP.
Source address validation is not completely portable between different protocol stacks. Even if the source IP address remains constant, the port number is likely to be different. Packet reflection attacks are still possible in this situation, though the set of hosts that can initiate these attacks is greatly reduced. A server might choose to avoid source address validation for such a connection, or allow an increase to the amount of data that it sends toward the client without source validation.
There are likely to be some real clangers here eventually, but the current set of issues is well captured in the relevant sections of the main text.
Never assume that because it isn't in the security considerations section it doesn't affect security. Most of this document does.
A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker.
Certificate caching {{?RFC7924}} can reduce the size of the server's handshake messages significantly.
QUIC requires that the packet containing a ClientHello be padded to a minimum size. A server is less likely to generate a packet reflection attack if the data it sends is a small multiple of this size. A server SHOULD use a HelloRetryRequest if the size of the handshake messages it sends is likely to significantly exceed the size of the packet containing the ClientHello.
QUIC, TLS and HTTP/2 all contain a messages that have legitimate uses in some contexts, but that can be abused to cause a peer to expend processing resources without having any observable impact on the state of the connection. If processing is disproportionately large in comparison to the observable effects on bandwidth or state, then this could allow a malicious peer to exhaust processing capacity without consequence.
QUIC prohibits the sending of empty STREAM frames unless they are marked with
the FIN bit. This prevents STREAM frames from being sent that only waste
effort.
TLS records SHOULD always contain at least one octet of a handshake messages or alert. Records containing only padding are permitted during the handshake, but an excessive number might be used to generate unnecessary work. Once the TLS handshake is complete, endpoints SHOULD NOT send TLS application data records unless it is to hide the length of QUIC records. QUIC packet protection does not include any allowance for padding; padded TLS application data records can be used to mask the length of QUIC frames.
While there are legitimate uses for some redundant packets, implementations SHOULD track redundant packets and treat excessive volumes of any non-productive packets as indicative of an attack.
This section defines error codes from the error code space used in {{QUIC-TRANSPORT}}.
The following error codes are defined when TLS is used for the crypto handshake:
TLS_HANDSHAKE_FAILED (0x201): : The TLS handshake failed.
TLS_FATAL_ALERT_GENERATED (0x202): : A TLS fatal alert was sent, causing the TLS connection to end prematurely.
TLS_FATAL_ALERT_RECEIVED (0x203): : A TLS fatal alert was received, causing the TLS connection to end prematurely.
This document does not create any new IANA registries, but it registers the values in the following registries:
-
QUIC Transport Error Codes Registry {{QUIC-TRANSPORT}} - IANA is to register the three error codes found in {{errors}}, these are summarized in {{iana-errors}}.
-
TLS ExtensionsType Registry {{!TLS-REGISTRIES=I-D.ietf-tls-iana-registry-updates}} - IANA is to register the quic_transport_parameters extension found in {{quic_parameters}}. Assigning 26 to the extension would be greatly appreciated. The Recommended column is to be marked Yes.
-
TLS Exporter Label Registry {{!TLS-REGISTRIES}} - IANA is requested to register "EXPORTER-QUIC 0-RTT Secret" from {{zero-rtt-secrets}}; "EXPORTER-QUIC client 1-RTT Secret" and "EXPORTER-QUIC server 1-RTT Secret" from {{one-rtt-secrets}}; "EXPORTER-QUIC Packet Number Secret" {{packet-number-gaps}}. The DTLS column is to be marked No. The Recommended column is to be marked Yes.
| Value | Error | Description | Specification |
|---|---|---|---|
| 0x201 | TLS_HANDSHAKE_FAILED | TLS handshake failure | {{errors}} |
| 0x202 | TLS_FATAL_ALERT_GENERATED | Sent TLS alert | {{errors}} |
| 0x203 | TLS_FATAL_ALERT_RECEIVED | Receives TLS alert | {{errors}} |
| {: #iana-errors title="QUIC Transport Error Codes for TLS"} |
--- back
Ryan Hamilton was originally an author of this specification.
This document has benefited from input from Dragana Damjanovic, Christian Huitema, Jana Iyengar, Adam Langley, Roberto Peon, Eric Rescorla, Ian Swett, and many others.
RFC Editor's Note: Please remove this section prior to publication of a final version of this document.
Issue and pull request numbers are listed with a leading octothorp.
No significant changes.
- Handshake errors can be reported with CONNECTION_CLOSE (#608, #891)
No significant changes.
- Update labels used in HKDF-Expand-Label to match TLS 1.3 (#642)
No significant changes.
- Updates to match changes in transport draft
- Use TLS alerts to signal TLS errors (#272, #374)
- Require ClientHello to fit in a single packet (#338)
- The second client handshake flight is now sent in the clear (#262, #337)
- The QUIC header is included as AEAD Associated Data (#226, #243, #302)
- Add interface necessary for client address validation (#275)
- Define peer authentication (#140)
- Require at least TLS 1.3 (#138)
- Define transport parameters as a TLS extension (#122)
- Define handling for protected packets before the handshake completes (#39)
- Decouple QUIC version and ALPN (#12)
- Changed bit used to signal key phase
- Updated key phase markings during the handshake
- Added TLS interface requirements section
- Moved to use of TLS exporters for key derivation
- Moved TLS error code definitions into this document
- Adopted as base for draft-ietf-quic-tls
- Updated authors/editors list
- Added status note