IETF Logo Mail Archive

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

ianswett <notifications@github.com> Mon, 08 January 2018 16:40 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EED6126579 for <quic-issues@ietfa.amsl.com>; Mon, 8 Jan 2018 08:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.382
X-Spam-Level:
X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C48RM_UhPvtG for <quic-issues@ietfa.amsl.com>; Mon, 8 Jan 2018 08:40:43 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA951241F5 for <quic-issues@ietf.org>; Mon, 8 Jan 2018 08:40:42 -0800 (PST)
Date: Mon, 08 Jan 2018 08:40:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1515429642; bh=/Hdn9pic1KJOlsuahtQRYVZEh6Vpx1Fz34wc24U+2BQ=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=s4lhPrMWBdKeo+NrQ5NQEayLJNNz2NkLi6U6lH9YzW7JSdTIlcNzxTycmvm6420hi gOKLZ+6UHn9Xc8JciId+899DFrrakr7j4o0Mu/I3Sbq27I1lfd5kIqZJPhezj3g7yB hWcXQ/s6N3NPNf64TSr3XXV5P683yNZmvFs4UmTs=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfdce743a182240a05fd397d31fae2ccd4345fc6892cf00000001166b610a92a169ce10e7bb4d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1029/356020679@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1029@github.com>
References: <quicwg/base-drafts/issues/1029@github.com>
Subject: Re: [quicwg/base-drafts] Connections SHOULD Respond to Connection Close Frames (#1029)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a539f0a19b59_7ebb3fba73aeef3027348c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Kok4SQ8Crh6afVYgXe8NI015_jk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 16:40:44 -0000

Agreed.  In practice, I expect a lot of HTTP/QUIC clients to destroy all state after sending a connection close, so they wouldn't store anything.  But it likely depends upon the application.  

-- 
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#issuecomment-356020679

v2.31.3 | Report a Bug | By Email | System Status