Re: [quicwg/base-drafts] Remap STOPPING to something other than zero (#1804)

[Nick Banks <[e-mail]>]

Ideally, I'd leave the entire space for the application layer. I just looked through the spec and it receiver of a RST_STREAM with STOPPING error code doesn't seem to do anything special, compared to receiving a RST_STREAM with any other error code. The goal of the STOP_SENDING frame is just to get your peer to RST_STREAM the stream. The best I could come up with is that if you get a STOPPING error code, you don't pass that up to the app layer directly, and internally just treat it as a confirmation of your STOP_SENDING. But, at least with my implementation, if the app layer has already shutdown it's receive direction on a stream, and I receive any RST_STREAM, I never indicate the event up, because it was shutdown locally first. With that design, the actual error code becomes irrelevant.

That being said, if someone comes up with a valid reason to keep a specific STOPPING error code, I'd prefer to use 0xFFFF instead of 0, 1 or any other value.

-- 
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/1804#issuecomment-424773773