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

[afrind <[e-mail]>]

The current spec only allows GOAWAY to be sent from the server to the client and contains only the last processed bidirectional stream ID.  This makes sense for the vanilla HTTP use case, but may not play well with extensions.  Unidirectional streams are a flexible extension point, and it may be useful for each endpoint to communicate to the peer the last processed unidirectional stream id.  An HTTP extension may also define a use for server initiated bidirectional streams, and may want the GOAWAY signal for these also.

True if it's an extension then the extension author can also extend GOAWAY to cover these cases or introduce another mechanism, but it would be a shame if many extensions had to cover the same ground.

I suggest we allow GOAWAY to be sent by either endpoint, and that it should contain both the last processed peer initiated bidirectional and unidirectional 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/issues/2632