Re: [quicwg/base-drafts] Stream closed state and acknowledgments (#743)

[Mike Bishop <[e-mail]>]

Thinking modularly, I'd argue that it should happen when the frames are submitted for transmission; the stream state machine shouldn't be dependent on ACKs and retransmissions.  The receiver is necessarily going to lag a little bit due to those things, but the situation of there being a lag is not remedied by making the lagging party be the sender instead.  This also mirrors flow control, where the window is consumed as soon as the frames are submitted, even if they haven't been sent yet.

As you note, the reason we considered switching the lag was to make the sender more conservative about which streams are in which state to avoid accidentally violating max_concurrent_streams.  That's no longer an issue, since the receiver is the one controlling that now.

-- 
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/743#issuecomment-324162922