Re: [quicwg/base-drafts] H3 GOAWAY should be symmetric and cover bidi and uni streams (#2632)

[afrind <[e-mail]>]

Ah, I was trying to get the behavior @mt was after for pushes (eg: let the server keep pushing if it wants to), and didn't intend to allow the client to send more requests after receiving a GOAWAY -- that doesn't work.

But it sounds like we'd prefer to keep the push behavior symmetric with h2 (no more pushes after GOAWAY receipt) than introduce a new push semantic where the client can allow pushes to continue even after signaling its intent to close.  This is more along the lines that @LPardue was advocating for - where the intent to close and how pushes are wound down are completely decoupled frames.

The discussion on slack I thought was different - it was about what the *sender* of a GOAWAY should do with new incoming streams.  I intended the PR to reflect that the sender of a GOAWAY should continue allowing requests or pushes with ID's smaller than the sent GOAWAY value.  Do we agree this is the right behavior?

-- 
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/2632#issuecomment-546080954