Re: [quicwg/base-drafts] Rejection of 0-RTT: start over? (#761)

[MikkelFJ <[e-mail]>]

So I didn't define 1 or 2, but my understanding is:

Option 1 cancels the connection attempt with a specific error allowing the application at a high level loop to start a new connection with different arguments.

Option 2 just cancels streams, meaning the application remains, but suddenly certain streams start to fail. For some applications this might just be pulling a new stream, but for others complicated application state must be managed - for example some protocols might never fail the first 10 streams because, short of connection failure, there is nothing inherent that can fail - this because the transport layer does not arbitrarily fail streams - it at most blocks them on flow.

Thus, having transport cancelling a stream is highly disruptive whereas giving up a new connection attemt as in option 1, is to be expected for many reasons, and comparatively easy to deal with.

-- 
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/761#issuecomment-330868376