From ec45d4d0ae1ba095dd56304b4a003551e57f50cb Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Fri, 7 Jun 2019 13:43:25 -0700 Subject: [PATCH 1/2] Explain initial settings a little more --- draft-ietf-quic-http.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 4345ea5dc9..cf57104d5a 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1340,7 +1340,9 @@ setting is the default value. When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session. Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are -received. +received. A client uses these initial values in a situation where it wants to +send requests before the server's SETTINGS frame has arrived. This removes the +need for a client to wait for the SETTINGS frame before sending requests. 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 @@ -1350,7 +1352,8 @@ 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. +with its 0-RTT data. The server MAY omit settings from its SETTINGS frame which +are unchanged from the initial value. ### PUSH_PROMISE {#frame-push-promise} From 1b35ffe443d7145baa145d6bcd8e2fd79fb0e1fc Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 12 Jun 2019 13:46:00 -0700 Subject: [PATCH 2/2] Brevity --- draft-ietf-quic-http.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index cf57104d5a..4b745c4ba8 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1340,9 +1340,9 @@ setting is the default value. When a 0-RTT QUIC connection is being used, the initial value of each server setting is the value used in the previous session. Clients MUST store the settings the server provided in the session being resumed and MUST comply with stored settings until the current server settings are -received. A client uses these initial values in a situation where it wants to -send requests before the server's SETTINGS frame has arrived. This removes the -need for a client to wait for the SETTINGS frame before sending requests. +received. A client can use these initial values to send requests before the +server's SETTINGS frame has arrived. This removes the need for a client to wait +for the SETTINGS frame before sending requests. 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