Re: [quicwg/base-drafts] 5-tuple routing and SPA (#3608)

Martin Thomson <notifications@github.com> Mon, 04 May 2020 05:41 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 D3B7A3A0C67 for <quic-issues@ietfa.amsl.com>; Sun, 3 May 2020 22:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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 nCoBK5-40KdX for <quic-issues@ietfa.amsl.com>; Sun, 3 May 2020 22:41:24 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BD703A0C66 for <quic-issues@ietf.org>; Sun, 3 May 2020 22:41:24 -0700 (PDT)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net [10.48.17.39]) by smtp.github.com (Postfix) with ESMTP id B17382C0CC9 for <quic-issues@ietf.org>; Sun, 3 May 2020 22:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1588570883; bh=zal30yNEPkf4coKzkk0VRRSFcMru4nWZGhpMV/qW0dY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=G7IBDW05v2NQ5VH5S2cfGqOltpkHsSftkAO3PsAWS9HR37ETbSAYppelOub5w10Vb SRqBfnz4A2C/64vAFbps3mjuXv8dAao8LlkynV6dbBxzhlkbuRGPbiAlOTruIsK5qs tfKEJK26ThIaAFNIHPflzjJiS/G69E7wPMRcu190=
Date: Sun, 03 May 2020 22:41:23 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7U5XQDBOJ6IQ3ZNT54XOGAHEVBNHHCITYZTQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3608/623267502@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3608@github.com>
References: <quicwg/base-drafts/issues/3608@github.com>
Subject: Re: [quicwg/base-drafts] 5-tuple routing and SPA (#3608)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eafab03a1a4e_5ac53ff87d4cd96024402"; 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/-_X5V4djo6x1NnR1tu051LlQg98>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 04 May 2020 05:41:26 -0000

A truth table might help here.

... | migration supported (no signal) | disable_active_migration set | 
---|---|---|
no preferred address | normal (migrate as you like);  | don't migrate |
preferred address | normal (migrate at your leisure) | don't migrate |

Right now, our definition of disable_active_migration is a simple "don't migrate".  But the argument here says that the server that provides a preferred address is *probably* capable of handling migrations on the basis that it has to support one.  We might insist on the source address not change, but the fact is that some NATs (those with address-dependent mappings) will change the source address.

Changing to a definition where disable_active_migration is instead "don't move to a new address unless you use a preferred address" is a little more complicated, but doable.

Is it worth the extra complexity this late in the process?  Is that complexity justified when it would be trivially possible to define another extension that said "I support migration on my preferred address"?

-- 
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/3608#issuecomment-623267502