[quicwg/base-drafts] Draining after Idle Timeout? (#3798)

Mike Bishop <notifications@github.com> Tue, 30 June 2020 22:10 UTC

Date: Tue, 30 Jun 2020 15:10:37 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK52NHAVWQ6ZQSDCSQ55A6MV3EVBNHHCNJ6AZA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3798@github.com>
Subject: [quicwg/base-drafts] Draining after Idle Timeout? (#3798)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5efbb85db6c57_3ec63fe41eecd960177976"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0qysywU5kEa6xxG_kjGU8f18jcY>

10.2 says that after the idle timeout expires, "the connection is silently closed and its state is discarded."  However, 10.2.1 says that the peer "might enter its draining state."  Based on 10.2, I would not expect there to be a draining state; the connection is simply gone, and you would get a stateless reset.

Is the draining state used after the endpoints time out, or not?

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

[quicwg/base-drafts] Draining after Idle Timeout?… Mike Bishop
Re: [quicwg/base-drafts] Draining after Idle Time… Martin Thomson
Re: [quicwg/base-drafts] Draining after Idle Time… Martin Thomson
Re: [quicwg/base-drafts] Draining after Idle Time… Martin Thomson