Re: [quicwg/base-drafts] Silent close (#61)

[Martin Thomson <[e-mail]>]

It's probably timely that we have the "how do you close a connection" discussion.

@janaiyengar and I were discussing one possibility.  In that model, the transport only has an explicit message for error-related closes.  The transport also has an idle timer that starts as soon as there are no open streams (note that this means nothing to send, nothing to receive).  The connection silently closes if that timer runs down without a new stream being opened.

The application protocol could define a message that could negotiate a graceful close to trigger this.  HTTP would need this, otherwise stream 3 would hold the connection open indefinitely.  To speed things up, the application protocol could force the timer to be shortened to basically FIN_WAIT2 (a couple of RTOs) by telling the transport that it was done.  (You need to wait around a little for retransmissions and reordering.)

-- 
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/61#issuecomment-285566401