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

Martin Thomson <notifications@github.com> Mon, 18 May 2020 02:44 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 54B473A0831 for <quic-issues@ietfa.amsl.com>; Sun, 17 May 2020 19:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.081
X-Spam-Level:
X-Spam-Status: No, score=0.081 tagged_above=-999 required=5 tests=[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.282, 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 uL6fXmp1upeG for <quic-issues@ietfa.amsl.com>; Sun, 17 May 2020 19:44:15 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058143A082E for <quic-issues@ietf.org>; Sun, 17 May 2020 19:44:14 -0700 (PDT)
Received: from github-lowworker-ca235ff.ash1-iad.github.net (github-lowworker-ca235ff.ash1-iad.github.net [10.56.110.15]) by smtp.github.com (Postfix) with ESMTP id 191E1A0841 for <quic-issues@ietf.org>; Sun, 17 May 2020 19:44:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1589769854; bh=SCUvna8QYMQNGeAAmYT9nOvg/t2rHZ8ky7tlYt+rQZc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l8dOn5Lxgha2GnBx8RpKsS8G4eBrbjFsN5Q5GS+vIxVfyctzKhK7uV/CLmsBprDFG CzYWCCB7C+Ji6qGQc9vckCApO/TSI7+2nh1f3uhLqzp4i88eYDMSl4gnljxFzMYWSM 4zFigH50SiG4zOMDY281wYTdSXrjLcqt0SHEQvZI=
Date: Sun, 17 May 2020 19:44:14 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7M7OFQ5ZO6BA2YIGN4ZXLX5EVBNHHCITYZTQ@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/629915539@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_5ec1f67e8faa_572f3fe58fccd9684366a3"; 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/-ffbePx5Kt3z4STZfxkGg423lAs>
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, 18 May 2020 02:44:16 -0000

As this has sat here a while, I'll reiterate my proposal again: we defer the ability to signal "I support migration, but only on my preferred address" to an extension.

Which means that disable_active_migration applies to both the original address and SPA, so answer the question (sorry Ian, I missed that).

I realize that you could change the meaning of disable_active_migration to apply to the address the server uses in the handshake, but there are interesting corner cases and I don't think we need to concern ourselves with those.  For instance, if you connect over V4 and get disable_active_migration and server_preferred_address.  If that SPA includes a V6 address you can't use, along with the same V4 address, what then?  Does the server really support migration?

I know that the current situation is unappealing, and I think that disable_active_migration is not good for the protocol.  But it exists for very good reasons.  Trying to limit the scope is admirable, but as we haven't seen a concrete proposal, I think we need to move on.

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