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

Subodh Iyengar <notifications@github.com> Mon, 20 November 2017 17:47 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 30701129A89 for <quic-issues@ietfa.amsl.com>; Mon, 20 Nov 2017 09:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.395
X-Spam-Level:
X-Spam-Status: No, score=-3.395 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_28=1.404, 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 CgjC3S1GFIqt for <quic-issues@ietfa.amsl.com>; Mon, 20 Nov 2017 09:47:57 -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 B71E2129A97 for <quic-issues@ietf.org>; Mon, 20 Nov 2017 09:47:56 -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=iR0M3Js9bWmPQ6iqyQSVve+tqoo=; b=boNMAYNfdTdMTJoM JEjDqmgkEIw9jJjAMt7jnClihSUON3LXDb98ALKbf7N3zSU5LwkqL19SuW601LyS 58PFTKDnmJOb6QNAeXpS2R9cMRk46T2Ngpzo/g1iC2SPLktrgAqdrlg9NqULXhdq 4gEL0Ltx6KEmIYzjlze/iezWv6U=
Received: by filter0211p1iad2.sendgrid.net with SMTP id filter0211p1iad2-11066-5A13154B-6 2017-11-20 17:47:55.623904145 +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 ismtpd0007p1iad2.sendgrid.net (SG) with ESMTP id z4UYzkl4Ry-oTGwcRXMI5g for <quic-issues@ietf.org>; Mon, 20 Nov 2017 17:47:55.580 +0000 (UTC)
Date: Mon, 20 Nov 2017 17:47:55 +0000
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb8e37b9c445f95843171fc6becb554c36da9236d92cf00000001162ad74b92a169ce10662b3b@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/345773463@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_5a13154b7549c_713a3fcc47396f2c1894a0"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2xKXt4Mm0T2quIOky8f/aGoz6ImsWp5rUWRI gbkZcHHGEvVkJ1Ys+vt4ezksehmJDCsbFSObHqLIQx2j8H14ygY9WJqtMYblNJ5NNoYAP+7KclTy9F w0LwJJkVAkL1JQWHspHwjyfV47jLfEacMgVYqNRflSCxLmtr009wYSsS68v2eu+Iz/I7hRJqTcWIL7 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/T1VPnAxPFNAAFmf7d4tGQTqvZAI>
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 17:47:59 -0000

i don't think implementations will send the packets to the new address by default. In connection close state we have the choice of whether or not to bind to the new client address or not, or keep the old address. Implementations will probably bind to the old address by default, at least that's what I do by default, and while implementing close, this question came to me.

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