From 21fa422a534619f0fa142b5648607f24ff40a715 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 8 Mar 2019 12:27:12 +1100 Subject: [PATCH 1/2] Suggestion for #2499 --- draft-ietf-quic-transport.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index cc9c4656bf..c923056c5c 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -269,9 +269,10 @@ data in one direction: from the initiator of the stream to its peer. Bidirectional streams allow for data to be sent in both directions. Streams are identified within a connection by a numeric value, referred to as -the stream ID. Stream IDs are unique to a stream. A QUIC endpoint MUST NOT -reuse a stream ID within a connection. Stream IDs are encoded as -variable-length integers (see {{integer-encoding}}). +the stream ID. A stream ID is a 62-bit integer (0 to 2^62-1) that is unique for +all streams on a connection. A QUIC endpoint MUST NOT reuse a stream ID within a +connection. Stream IDs are encoded as variable-length integers (see +{{integer-encoding}}). The least significant bit (0x1) of the stream ID identifies the initiator of the stream. Client-initiated streams have even-numbered stream IDs (with the bit @@ -851,11 +852,10 @@ limits are set in the transport parameters (see using MAX_STREAMS frames ({{frame-max-streams}}). Separate limits apply to unidirectional and bidirectional streams. -If a max_streams transport parameter or MAX_STREAMS frame is received with a -value greater than 2^60, this allows a maximum stream ID that cannot be -expressed as a variable-length integer (see {{integer-encoding}}). -If either is received, the connection MUST be immediately closed with a -connection error of type STREAM_LIMIT_ERROR (see {{immediate-close}}). +A max_streams transport parameter or MAX_STREAMS frame is invalid if it has a +value greater than 2^60, which would allow for an invalid maximum stream ID. +If an invalid value is received, the connection MUST be immediately closed with +a connection error of type STREAM_LIMIT_ERROR (see {{immediate-close}}). Endpoints MUST NOT exceed the limit set by their peer. An endpoint that receives a STREAM frame with a stream ID exceeding the limit it has sent MUST From 18c9450b2668fa839f40e486b243885475e1df24 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 1 May 2019 08:41:38 +1000 Subject: [PATCH 2/2] Reorder sentences --- draft-ietf-quic-transport.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index e9ae94f7ef..19ec09bb76 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -270,9 +270,9 @@ Bidirectional streams allow for data to be sent in both directions. Streams are identified within a connection by a numeric value, referred to as the stream ID. A stream ID is a 62-bit integer (0 to 2^62-1) that is unique for -all streams on a connection. A QUIC endpoint MUST NOT reuse a stream ID within a -connection. Stream IDs are encoded as variable-length integers (see -{{integer-encoding}}). +all streams on a connection. Stream IDs are encoded as variable-length integers +(see {{integer-encoding}}). A QUIC endpoint MUST NOT reuse a stream ID within a +connection. The least significant bit (0x1) of the stream ID identifies the initiator of the stream. Client-initiated streams have even-numbered stream IDs (with the bit