IETF Logo Mail Archive

Re: [quicwg/base-drafts] Simultaneous connection migration (#490)

Martin Thomson <notifications@github.com> Fri, 05 May 2017 02:07 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 E0C4C127B57 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 19:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 pK3_6X_9fHl6 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 19:07:41 -0700 (PDT)
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 59943126579 for <quic-issues@ietf.org>; Thu, 4 May 2017 19:07:41 -0700 (PDT)
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=RoLKft+ImLhJ33OjiZNi7UrvKuw=; b=ZZeDFvFsiNKArAHM KOjGG9OsH5YJIcqWqjLeJOBLmoEgG6N5txaEmlHT3BK1+51XkYQxqvwK1Ntsl63u YpgbWZl2Q64vdR+qxoxuoU32rv+J5ydy+xiEOSEAle9pd2M7TTQt9ghv59hzX7No AxcfzPn1cKTRpxNffQ/W4AwklGg=
Received: by filter1107p1mdw1.sendgrid.net with SMTP id filter1107p1mdw1-2521-590BDE6B-59 2017-05-05 02:07:39.80775119 +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 P4BM-mc4RyOGpVnxDTdY1Q for <quic-issues@ietf.org>; Fri, 05 May 2017 02:07:39.843 +0000 (UTC)
Date: Thu, 04 May 2017 19:07:39 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8b731b791ae9e9b056b037cdbd92239c9f4ea86992cf000000011523a06b92a169ce0d7229b3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/490/299354753@github.com>
In-Reply-To: <quicwg/base-drafts/issues/490@github.com>
References: <quicwg/base-drafts/issues/490@github.com>
Subject: Re: [quicwg/base-drafts] Simultaneous connection migration (#490)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_590bde6bb9f35_1613fca336bdc34566f1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak360JFaeT/KQUHCQ4iWneojo8XkVOmP14DFX9 abJXEXcufMPyThkjaPnwGIH9RFjTBDJtMxxcujBGpw2EJCmQJNKq8f7xMkTsFNwxeJ8ndtbZhJ4hwR KvWyNkkCQdzZJdJorhKPz8ilqB5QCmV5WepsfC/Mt77Sh00llqqNoF7tUzrha9gc2jH0/tPAmxp225 M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2myvEEjUx3AwDExRjt8uWfI2WE8>
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: Fri, 05 May 2017 02:07:43 -0000

I understand how new address could be used, I even understand how one peer might choose to start using a new source address.  I just don't know how it might decide to start using a different remote address without first receiving packets on that address.

Leaving aside the NAT thing, which I don't think you can dismiss so casually, let's look at the scenario in the simple case where all addresses are equally reachable from all others.  In a simultaneous migration, you have A1->A2 simultaneous with B1->B2.  As the change happens, A2 sends to B1, B2 sends to A1.  How does A decide that A2 to B2 is the path it should use?

To be clear, I don't think we need to forbid any of this, but if we need to make it work, that will take effort, if only to write down where it works, how, caveats, etc...

-- 
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/490#issuecomment-299354753

v2.23.0 | Report a Bug | By Email