Re: [quicwg/base-drafts] Editorial suggestions on the Streams section (#2730)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



> @@ -187,8 +187,9 @@ QUIC:
 
 QUIC packet:
 
-: The smallest unit of QUIC that can be encapsulated in a UDP datagram. Multiple
-  QUIC packets can be encapsulated in a single UDP datagram.
+: A complete processable payload with a packet type, encryption level and

Structure?  Sequence of octets?  Or drop it entirely and define a packet as a header, payload, and authentication tag in that order.

> @@ -335,8 +337,9 @@ the flow control limits set by its peer.  Flow control is described in detail in
 Stream multiplexing can have a significant effect on application performance if
 resources allocated to streams are correctly prioritized.
 
-QUIC does not provide frames for exchanging prioritization information.  Instead
-it relies on receiving priority information from the application that uses QUIC.
+QUIC does not provide a mechanism for exchanging prioritization information.
+Instead it relies on receiving priority information from the application that

```suggestion
Instead, it relies on receiving priority information from the application that
```

> @@ -335,8 +337,9 @@ the flow control limits set by its peer.  Flow control is described in detail in
 Stream multiplexing can have a significant effect on application performance if
 resources allocated to streams are correctly prioritized.
 
-QUIC does not provide frames for exchanging prioritization information.  Instead
-it relies on receiving priority information from the application that uses QUIC.
+QUIC does not provide a mechanism for exchanging prioritization information.
+Instead it relies on receiving priority information from the application that
+uses QUIC.

implementation-specific, with the hyphen

> @@ -543,9 +546,9 @@ MAX_STREAM_DATA frames, it only receives any retransmissions of stream data.
 
 Once all data for the stream has been received, the receiving part enters the
 "Data Recvd" state.  This might happen as a result of receiving the same STREAM
-frame that causes the transition to "Size Known".  In this state, the endpoint
-has all stream data.  Any STREAM or STREAM_DATA_BLOCKED frames it receives for
-the stream can be discarded.
+frame that causes the transition to "Size Known".  After all data has been
+received, Any STREAM or STREAM_DATA_BLOCKED frames it receives for the stream

```suggestion
received, any STREAM or STREAM_DATA_BLOCKED frames for the stream
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2730#pullrequestreview-251820000