From 44a3ac279b6ad00ed7a93b9b60d49ea8ccdf0703 Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Wed, 15 Nov 2017 04:18:07 +0000 Subject: [PATCH 1/2] consistently send SETTINGS streams 2 and 3 This change just updates some text that seems to be overlooked, making consistent usage of stream ID 2 and 3 for SETTINGS frames. --- draft-ietf-quic-http.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 052c1e80f6..c8a23d8b36 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -150,9 +150,10 @@ token "hq" in the crypto handshake. While connection-level options pertaining to the core QUIC protocol are set in the initial crypto handshake, HTTP-specific settings are conveyed in the SETTINGS frame. After the QUIC connection is established, a SETTINGS -frame ({{frame-settings}}) MUST be sent as the initial frame of the HTTP control -stream (Stream ID 1, see {{stream-mapping}}). The server MUST NOT send data on -any other stream until the client's SETTINGS frame has been received. +frame ({{frame-settings}}) MUST be sent by each endpoint as the initial frame +of their respective HTTP control stream (Stream ID 2 or 3, see +{{stream-mapping}}). The server MUST NOT send data on any other stream until +the client's SETTINGS frame has been received. ## Draft Version Identification From 338f6ef7b5fa298154cdf6932ec284abb1ca8607 Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Wed, 15 Nov 2017 04:30:12 +0000 Subject: [PATCH 2/2] Fix trailing whitespace issue ... caused CI errors --- 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 c8a23d8b36..b0aa8ac91c 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -150,9 +150,9 @@ token "hq" in the crypto handshake. While connection-level options pertaining to the core QUIC protocol are set in the initial crypto handshake, HTTP-specific settings are conveyed in the SETTINGS frame. After the QUIC connection is established, a SETTINGS -frame ({{frame-settings}}) MUST be sent by each endpoint as the initial frame -of their respective HTTP control stream (Stream ID 2 or 3, see -{{stream-mapping}}). The server MUST NOT send data on any other stream until +frame ({{frame-settings}}) MUST be sent by each endpoint as the initial frame +of their respective HTTP control stream (Stream ID 2 or 3, see +{{stream-mapping}}). The server MUST NOT send data on any other stream until the client's SETTINGS frame has been received. ## Draft Version Identification