From 1d1dbce1bbb398de31f54f5d3e080c5e422898da Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 8 Aug 2018 15:51:48 -0700 Subject: [PATCH] Previous SETTINGS MUST be remembered, can't be reduced for 0-RTT --- draft-ietf-quic-http.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 4e3c686c7e..bfabfd223e 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -934,10 +934,18 @@ When a 0-RTT QUIC connection is being used, the client's initial requests will be sent before the arrival of the server's SETTINGS frame. Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the server's current settings are received. - -Servers MAY continue processing data from clients which exceed its current -configuration during the initial flight. In this case, the client MUST apply -the new settings immediately upon receipt. +Remembered settings apply to the new connection until the server's SETTINGS +frame is received. + +A server can remember the settings that it advertised, or store an +integrity-protected copy of the values in the ticket and recover the information +when accepting 0-RTT data. A server uses the HTTP/QUIC settings values in +determining whether to accept 0-RTT data. + +A server MAY accept 0-RTT and subsequently provide different settings in its +SETTINGS frame. If 0-RTT data is accepted by the server, its SETTINGS frame MUST +NOT reduce any limits or alter any values that might be violated by the client +with its 0-RTT data. When a 1-RTT QUIC connection is being used, the client MUST NOT send requests prior to receiving and processing the server's SETTINGS frame.