diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
index 245700e9f1..51b19a4499 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 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}}.