Subject: [quicwg/base-drafts] Connections SHOULD Respond to Connection Close Frames (#1029)

From: Nick Banks <[email-masked]>
Date: Wed, 20 Dec 2017 08:33:29 -0800

The spec currently says the following:

>    After receiving a closing frame, endpoints enter the draining state.
   An endpoint that receives a closing frame **MAY** send a single packet
   containing a closing frame before entering the draining state, using
   a CONNECTION_CLOSE frame and a NO_ERROR code if appropriate.  An
   endpoint MUST NOT send further packets, which could result in a
   constant exchange of closing frames until the closing period on
   either peer ended.

I'd like to make a case for changing that MAY to a SHOULD.

If we are recommending that the sender of the initial CONNECTION_CLOSE wait the closing/draining period, why not recommend the receiver try to always respond to its frame with a CONNECTION_CLOSE of its own? Assuming it then obeys the rule about not sending any other packets, when (if) the initial closer receives the corresponding close frame, it now know that it shouldn't be receiving any other packets (other than possible reordered packets).

In response to receiving the close response, the initial closer can then chose to either continue waiting the draining period to handle reordered packets or just immediately cleanup.

-- 
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/1029