[quicwg/base-drafts] Use immediate close for application close (#854)

Martin Thomson <notifications@github.com> Tue, 10 October 2017 23:27 UTC

Date: Tue, 10 Oct 2017 23:27:34 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7912398a16d5950a3ebedb3a18121e020490caef92cf0000000115f5196692a169ce0fc28dd9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/854@github.com>
Subject: [quicwg/base-drafts] Use immediate close for application close (#854)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59dd5766106d3_4143fd097286f3421036"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Frl7l-9LbP1oVvNP1XC-mCOfRKQ>

At the Seattle interim we concluded that it was important to signal a close to intermediaries (those that have the keys, that is).  This allows application endpoints to reach an agreed close state and then terminate the transport without leaving the middlebox on a timer.

In short, once the application protocol has reached a terminal state, it will signal using APPLICATION_CLOSE (some code, maybe NO_ERROR).

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

[quicwg/base-drafts] Use immediate close for appl… Martin Thomson
Re: [quicwg/base-drafts] Use immediate close for … Ryan Hamilton
Re: [quicwg/base-drafts] Use immediate close for … Martin Thomson
Re: [quicwg/base-drafts] Use immediate close for … Ryan Hamilton
Re: [quicwg/base-drafts] Use immediate close for … Martin Thomson