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

Subodh Iyengar <notifications@github.com> Sun, 19 November 2017 04: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 9EB10124D68 for <quic-issues@ietfa.amsl.com>; Sat, 18 Nov 2017 20:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.474
X-Spam-Level:
X-Spam-Status: No, score=-0.474 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_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 SH4mBr7dARby for <quic-issues@ietfa.amsl.com>; Sat, 18 Nov 2017 20:23:46 -0800 (PST)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 AC734120725 for <quic-issues@ietf.org>; Sat, 18 Nov 2017 20:23:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=IygMGUBlpBEX1r78TQoH9WhOPfw=; b=vXJnxruKq1cW9r6Z Kxbu4yKOH0YxXO4P8JOEotn1M6I+YdKuJo46FpoOZlhnG3u0qTQt67TdW4yW/hdD /2VsKyvzduyor8/fqLLU0orbioUgivQOxuVxpXPudHbYbdXL6sZomTLzaBgaBF2J 6BFS9HU5/jxZSHEUsUng0OJXQrw=
Received: by filter1096p1mdw1.sendgrid.net with SMTP id filter1096p1mdw1-13927-5A110751-2A 2017-11-19 04:23:45.750372048 +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 ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id Jy6zc_0pTsmqtGAPEqH6Iw for <quic-issues@ietf.org>; Sun, 19 Nov 2017 04:23:45.702 +0000 (UTC)
Date: Sun, 19 Nov 2017 04:23:45 +0000
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab703e0b49c0ec68464fd342b26356615baa2e998992cf000000011628c95192a169ce10662b3b@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@github.com>
Subject: [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_5a1107519b112_1b913fbdbc0c8f28197090"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3psFHyC4lh6yAiYrMyI9A4hGubu3EZxfT1X6 uIlPHpBmC1VCmd/Hqk7d9xhrFJ1oFO9C5TGAu7CtXOPJGLlRYj3952smwQgQYcLbi5gFCKR/jSsSek 10zv2yXSzC365cXUtYUZvS6xgUCYAWVd7n7yd2WDLrYQ8RMw9lLKSZRVPOvnHqd3ry4zuqhvsw576Z A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uuCDeuPQe2Q7KQC5JEqEx6GPFbg>
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 04:23:47 -0000

I think we have 3 potential options:

1. We could send the connection close to the new address 
2. We could just exit draining
3. We could ignore it completely.

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