IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Thu, 18 May 2017 23:49 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 B8D2D1201F2 for <quic-issues@ietfa.amsl.com>; Thu, 18 May 2017 16:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.12
X-Spam-Level:
X-Spam-Status: No, score=-5.12 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 eC_dPvDkwCg3 for <quic-issues@ietfa.amsl.com>; Thu, 18 May 2017 16:49:57 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0031E129515 for <quic-issues@ietf.org>; Thu, 18 May 2017 16:45:15 -0700 (PDT)
Date: Thu, 18 May 2017 16:45:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1495151115; bh=TKGr45saGP1n/QEL9J5FmzWlT6j4N++Bd6rF/TZrav8=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1JPJ9aoTofmSw5AlDAWLpT39n/SmtjORh1jE4kEQzo0116cMQba6XdzgpoiYFfAe+ e2c2c6AipLvRqGVUSHBxDZ5mjKfbMPDuwS06MAMlv7YG+qNpPUqOAdDz4XIxQJwHxW o4dTb9S67non8W6LMkrQMfJxIPVvFGB/7X+3EwZ8=
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe71143d468f5d3c3b27399a01e2eb4e0afdfd65c92cf000000011535f40b92a169ce0d7229b3@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/302570869@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_591e320bdc5c_3e6c3fefb4051c3c11053a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/YrNCzoSRc5vtEEfCmUHiW2_FZyE>
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: Thu, 18 May 2017 23:49:59 -0000

@martinthomson 
>  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?

If each endpoint uses the rules:

1. "Send FROM your new address"
2. "Send TO the latest address you've heard from"

Then, after "A2 send to B1" and "B2 send to A1", A (on A1) will have heard from B (sent from B2).  Hence, A will send from A2 to B2.

By the way, I do not see NAT as a problem here.  When A sends from A2 (NAT exit point), NAT will associate A2 with A.

(Assumption here is that NAT does not validate an entire 5-tuple.  Instead, compatible NATs only care about the local address/port.)

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

v2.23.0 | Report a Bug | By Email