IETF Logo Mail Archive

Re: [quicwg/base-drafts] What to do if address of client changes while in draining state (#946)

ianswett <notifications@github.com> Mon, 20 November 2017 22:23 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 779FD12EAE4 for <quic-issues@ietfa.amsl.com>; Mon, 20 Nov 2017 14:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.798
X-Spam-Level:
X-Spam-Status: No, score=-4.798 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=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 Fou7ltsA9pqR for <quic-issues@ietfa.amsl.com>; Mon, 20 Nov 2017 14:23:08 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA6912EAA8 for <quic-issues@ietf.org>; Mon, 20 Nov 2017 14:23:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zS8fi2SOSisGNUKNjHh9WYf13X0=; b=VLaSIQuDcq5i938I st5ENK9+AO2LEY+4MNW0qeov4ttJBRw/lgg3Q+Yjw1NgWRaM/eyu7Czx+iJ1KaN3 6YSE7+fNM8+vXxADpekTz5ZSJNlnjK0dLXYxezIVYqNv+q67xxueI1QIhILa+Bv5 GuV0gEqDqdD6wGTzikRj6PQ18Nk=
Received: by filter0509p1mdw1.sendgrid.net with SMTP id filter0509p1mdw1-28344-5A1355C7-5 2017-11-20 22:23:03.220144095 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id BRPCTbnsQxOE4YF-m3EfUQ for <quic-issues@ietf.org>; Mon, 20 Nov 2017 22:23:03.280 +0000 (UTC)
Date: Mon, 20 Nov 2017 22:23:03 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba7e9720e16745963d4c528a2437c05d168f09df692cf00000001162b17c792a169ce10662b3b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/946/345851495@github.com>
In-Reply-To: <quicwg/base-drafts/issues/946@github.com>
References: <quicwg/base-drafts/issues/946@github.com>
Subject: Re: [quicwg/base-drafts] What to do if address of client changes while in draining state (#946)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1355c732ceb_74f33fd10b72ef2c1841c1"; 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
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0GTDrg45ichFnjD9SVFJw47MOtKXvbIt3I3j AN83CAVDYPva9jdIEOXhsWyBgC2hvWNn832UkqkKGeZx6U9LbjJsXVkeG5wnuFmpXZhH3psRsVPUXy 1udd8AjiCflRPmfgPIy6+HkiSwxMTuHDFHkLfqsBdi/eFHIv0/d5SPrnxgmNHt4jH3/1s5VcMhmzEq 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pvQtkiTaxYfN_iG1zOw5tBYXLCU>
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, 20 Nov 2017 22:23:09 -0000

The stateless reset text says:
"A stateless reset is provided as an option of last resort for a server that does not have access to the state of a connection. A server crash or outage might result in clients continuing to send data to a server that is unable to properly continue the connection. A server that wishes to communicate a fatal connection error MUST use a CONNECTION_CLOSE or APPLICATION_CLOSE frame if it has sufficient state to do so."

To me, that indicates a server should send a connection close if it's possible/straightforward to look that up.  If not, send a stateless reset.  If you have editorial suggestions for this text, feel free to send out a PR.

-- 
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/946#issuecomment-345851495

v2.23.0 | Report a Bug | By Email