From 2c399950b01e5ca12148a0117e3952a56b83e55b Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 27 Apr 2017 16:40:33 +1000 Subject: [PATCH 1/2] Don't exempt stream 1 from congestion control Closes #248 --- draft-ietf-quic-transport.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 245700e9f1..e5cac7a8b8 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -2329,10 +2329,10 @@ ordered byte-stream. Data received out of order MUST be buffered for later delivery, as long as it is not in violation of the receiver's flow control limits. -The cryptographic handshake stream, stream 0, MUST NOT be subject to congestion -control or connection-level flow control, but MUST be subject to stream-level -flow control. An endpoint MUST NOT send data on any other stream without -consulting the congestion controller and the flow controller. +An endpoint MUST NOT send data on any stream without ensuring that it is within +the data limits set by its peer. The cryptographic handshake stream, Stream 0, +is exempt from the limits imposed by connection-level data limits. Stream 0 is +still subject to stream-level data limits. Flow control is described in detail in {{flow-control}}, and congestion control is described in the companion document {{QUIC-RECOVERY}}. From 699e52813bbef330163886ca5c500b12be063c71 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 27 Apr 2017 16:42:55 +1000 Subject: [PATCH 2/2] Reference MAX_DATA/MAX_STREAM_DATA to make it clearer --- draft-ietf-quic-transport.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index e5cac7a8b8..51b19a4499 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -2331,8 +2331,8 @@ limits. An endpoint MUST NOT send data on any stream without ensuring that it is within the data limits set by its peer. The cryptographic handshake stream, Stream 0, -is exempt from the limits imposed by connection-level data limits. Stream 0 is -still subject to stream-level data limits. +is exempt from the connection-level data limits established by MAX_DATA. Stream +0 is still subject to stream-level data limits and MAX_STREAM_DATA. Flow control is described in detail in {{flow-control}}, and congestion control is described in the companion document {{QUIC-RECOVERY}}.