Re: [quicwg/base-drafts] STOP_SENDING on Critical Stream (#2509)

[Lucas Pardue <[e-mail]>]

SGTM mike

On Sat, 9 Mar 2019, 00:48 Ryan Hamilton, <[e-mail]> wrote:

> On Fri, Mar 8, 2019 at 4:43 PM Mike Bishop <[e-mail]>
> wrote:
>
> > Perhaps I'm missing it but the spec doesn't say how to handle a
> > STOP_SENDING received on a control stream. Should this peer issue a
> > RESET_STREAM in response (causing the other peer to blow up) or should it
> > just close the connection itself?
> >
> > *Originally posted by @LPardue <https://github.com/LPardue> in #2498
> > (comment)
> > <
> https://github.com/quicwg/base-drafts/issues/2498#issuecomment-470316968>*
> >
> > There are three reasonable places to blow up:
> >
> > - When you decide to stop reading a critical stream (i.e. when
> > STOP_SENDING is sent)
> > - When you discover the peer has stopped reading a critical stream
> > (i.e. when STOP_SENDING is received)
> > - When you discover the peer has closed a critical stream (when
> > RESET_STREAM or FIN is received)
> >
> > My inclination would be to advise against FIN/S_S/R_S on a critical
> stream
> > and mandate connection termination on receipt of any of them.
> >
> Completely agree. This seems like the simplest and most obvious solution.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/2509#issuecomment-471127297>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGRFtRhsQgPDbduCLj7FTaENXQkzkKwuks5vUwTEgaJpZM4bmXtm>
> .
>


-- 
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/2509#issuecomment-471127599