IETF Logo Mail Archive

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

janaiyengar <notifications@github.com> Fri, 05 May 2017 01:54 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 7AA8E128BA2 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 18:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.9
X-Spam-Level:
X-Spam-Status: No, score=-7.9 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 FTfXIJ3GYBSb for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 18:54:36 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B923126CBF for <quic-issues@ietf.org>; Thu, 4 May 2017 18:54:36 -0700 (PDT)
Date: Thu, 04 May 2017 18:54:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1493949275; bh=OTAetE8TSUKjr9iSlaPMbnNCnXi+XAh8Oo0bGrVZJGw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mZ9Szqeo6s+ptrItYSS/bVyiPjMSliM4NUompm5zRDKChJXiSWuqrn4+X1VzpiehK LQDWZKIiOwfpONofk/iwP41sk2gpOCxbM3FaoakZEiJ5+KXqBe69baX5EgYtO611DU a6rJhVdbcVp/OwLowBB+MOUSunAcsPgeRyJD821U=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab628af122ae03b5d1479fef9ce52ed39f9f6b1d8792cf0000000115239d5b92a169ce0d7229b3@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/299353546@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_590bdb5b6b0af_59b33fa7f7d71c3c95165"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/RAb3DiqQqHxn2oTQsiOBFW3Oa8g>
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:54:37 -0000

It does work. So, say both sides use a new IP to send new data, but are able to receive on the old and the new IP (because the interfaces are cellular and wifi, say, and both are active, but the devices would prefer to switch from using cellular to using wifi.) I agree that NATs are an issue, but that just means that if you're brave enough to try to do simultaneous migration, it's very unlikely to work due to NATs.

Forbidding has costs -- endpoints will need to write code to disallow certain things. If they never happen, it's even worse, since it's largely unused code. If we agree that simultaneous migration doesn't hurt us, then let's leave it out. 

 

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

v2.23.0 | Report a Bug | By Email