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

Martin Thomson <notifications@github.com> Fri, 05 May 2017 01:34 UTC

Return-Path: <noreply@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 77050127B57 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 18:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.497
X-Spam-Level:
X-Spam-Status: No, score=-6.497 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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_DNSWL_HI=-5, 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 jAWguEMmLdN4 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 18:34:03 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4287A120046 for <quic-issues@ietf.org>; Thu, 4 May 2017 18:34:03 -0700 (PDT)
Date: Thu, 04 May 2017 18:34:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1493948042; bh=LdpjGBx9Va0AHSttpWiOD0fpkm/Q7qvzm0pnnRtO9uk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oSSi/FU+m7dO3sERSsEQvh7nlDrt53fRMjwmnO7TGmWLq4wzM/zwg9l0vf6HLYZ94 BBLuV1g/9K4bvi6cX9n1YY7P0vf7lAjKhesnfO2jWPhHS5QMw8F99CahkRTPJodfGa nZgfgdAE/774Qq1r/COzJ1rUQHkUan5mprgPPisQ=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5b7b353a69dd0e3bf187e1fa7bdb3ea5ccdf2c4292cf000000011523988a92a169ce0d7229b3@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/299351549@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_590bd68a9e28c_e973f9f7d2cfc342304c1"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/yeQGpjhpKwEKqvFqQauJGm4ZXTI>
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 01:34:04 -0000

If you make before break, this *might* work.  You would need a trigger to cause the other side to start using the new address, which I don't think that we have.  It might be possible for a client to receive packets from a different remote address and start sending on that address, but how does it decide to switch over?  That suggests a new signal of some sort, which costs.  Also, many firewalls and NATs will stomp on packets from a new address, which would prevent spontaneous migrations at the server side.

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