Re: [quicwg/base-drafts] Refactor the section on connection termination (#721)

[Martin Thomson <[e-mail]>]

I've introduced the notion of a "draining period" after close.  This is like the TCP TIME_WAIT period, but what happens depends on how the connection was closed.  On Jana's advice, I've used 3*max(MIN_RTO, RTT), recognizing that this is probably just a starting point and we can refine the exact value later.

During the draining period, the baseline here is that the endpoint generates ACK frames, but nothing else.  That's all we need for an application close (the success case).  For an idle timeout, the text permits reviving of the connection if new packets are received.  In immediate close, the text requires that the CONNECTION_CLOSE be sent, and permits re-sending the last packet to save on state space.

@janaiyengar, can you check to see that I've captured the intent well-enough here?

-- 
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/pull/721#issuecomment-324217020