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

ianswett <notifications@github.com> Sun, 19 November 2017 17:08 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 B31BD126E64 for <quic-issues@ietfa.amsl.com>; Sun, 19 Nov 2017 09:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.182
X-Spam-Level:
X-Spam-Status: No, score=-3.182 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_MSPIKE_H2=-2.8, 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 gZMuLGqJ96N4 for <quic-issues@ietfa.amsl.com>; Sun, 19 Nov 2017 09:08:55 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 AA428126DCA for <quic-issues@ietf.org>; Sun, 19 Nov 2017 09:08:55 -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=kYE8FzPeP4JK8XvknowxkyVlv5g=; b=TA1tenHpH63+BhWR dLdukPnNQwqsstgmKR7d7irO47hlCs1LLNIyNc9hOLC5AepMD3LNx2hm/cK+XTpq xmBvQvO9I7vLMGFhm09EdJg97K6ZCr72SAj3tsQtceVLCAAZOY0bHQmxN+9aQn6x XUUqRDEZm2XzfE4tIK1TqY4MfPE=
Received: by filter1112p1mdw1.sendgrid.net with SMTP id filter1112p1mdw1-26183-5A11BAA6-2D 2017-11-19 17:08:54.604472334 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id dwl8EZX1RAi7lyxqSRQ1PQ for <quic-issues@ietf.org>; Sun, 19 Nov 2017 17:08:54.595 +0000 (UTC)
Date: Sun, 19 Nov 2017 17:08:54 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab829859c5a5ad8f76dd4d60d8ed1614e31ae2429a92cf0000000116297ca692a169ce10662b3b@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/345532622@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_5a11baa67ec83_20f23fe201738f341286932"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2YVUMCVwzDlAmgMbOoU2/NSisCNDHO2D5KYv vrmu5Exe4sdQfA8WuC56m5A0rOuYbZwuNP6tEuOuci/xsMaUcOpgL0EDQFMyKYJDK5WHzMnIaAQcEX xq7XT0TNetPJaIGMauHeM3Im8nm5Tx867u+j910tvpPjLMm6oHF4mfATL3O2yDqvhG+UJME2pJPWIK g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/xFU40Nuh1-N6_qVrY1X2zOi6Fd8>
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: Sun, 19 Nov 2017 17:08:57 -0000

Two options seem equally reasonable to me:
 1) Send the connection close to the new address
 2) Send a public reset and change nothing about the draining state

Ignoring it completely seems bad, and I'm not sure why we'd exit draining due to an address change?

-- 
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-345532622