IETF Logo Mail Archive

Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)

Jana Iyengar <notifications@github.com> Tue, 14 July 2020 22:03 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 A68E33A0827 for <quic-issues@ietfa.amsl.com>; Tue, 14 Jul 2020 15:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 FWQ3ZjvCzmya for <quic-issues@ietfa.amsl.com>; Tue, 14 Jul 2020 15:03:02 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F4A3A0826 for <quic-issues@ietf.org>; Tue, 14 Jul 2020 15:03:02 -0700 (PDT)
Received: from github-lowworker-5825cd4.ac4-iad.github.net (github-lowworker-5825cd4.ac4-iad.github.net [10.52.22.68]) by smtp.github.com (Postfix) with ESMTP id 65F9DE1856 for <quic-issues@ietf.org>; Tue, 14 Jul 2020 15:03:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594764181; bh=tUvFU06NsClpPVnvwp01rfdiXUrNBkgneEhALtUhWBk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PPyZd1PgcLxB5GK/a/bmBYDfjUR582FceZQvqAQjXtCKXWvI2ktUTVwT00xrXgzRD Osde2GqSSackQb6WVL+gZbSLnNVVJU0ZuICZTzjBPDHO8dFM/iFhg8Gd4aa1wA18wb SlgzPWOvuSKTWVhCtAk6Nwg3m63FaQP4ANz82ZEo=
Date: Tue, 14 Jul 2020 15:03:01 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY756ERZHCHXZTSZ555DIGJLEVBNHHCMFSQTA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3765/658435935@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3765@github.com>
References: <quicwg/base-drafts/issues/3765@github.com>
Subject: Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0e2b9556712_6f833fb7076cd95c1891f"; 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/0HizUFMIpTLBxITZMwpLfDtxAyA>
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: Tue, 14 Jul 2020 22:03:04 -0000

@MikeBishop's PR exposes this issue that I don't see how we can get around trivially: Yeah, this is getting tricky. A server that wants to use SPA with a different address family and _does not support_ migration has to deal with the case of the client's address changing when speaking to the SPA on a different address family. This is not different than migration, FWIW, and you'd have to do (i) the PATH_CHALLENGE/RESPONSE dance, (ii) ensure that the interface is the same as it was (how does a server ensure this anyway?)

I'm not sure that we _need_ to take on this larger problem, which can be made into an extension, this late in the process.

-- 
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/3765#issuecomment-658435935

v2.23.0 | Report a Bug | By Email