[quicwg/base-drafts] STOP_SENDING in Ready state (#1797)

[Kazuho Oku <[e-mail]>]

Section 7.15 of the current editor's draft states:
> Receiving a STOP_SENDING frame for a send stream that is “Ready” or non-existent MUST be treated as a connection error of type PROTOCOL_VIOLATION.

To put it another way, if an endpoint wants to abruptly discard a bidirectional stream that it has opened, it needs to either:
* wait for the peer to send a STREAM frame before sending STOP_SENDING
* bundle an empty STREAM frame (offset=0, len=0, FIN not set) when sending a STOP_SENDING frame

However, either of the two solution seems like an unnecessary complexity.

Can't we simply state that a STOP_SENDING frame implicitly creates a send stream before it is applied?

-- 
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/issues/1797