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

Kazuho Oku <notifications@github.com> Tue, 14 July 2020 01:30 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 8217A3A0C82 for <quic-issues@ietfa.amsl.com>; Mon, 13 Jul 2020 18:30:34 -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 JqaW9RDHRCsB for <quic-issues@ietfa.amsl.com>; Mon, 13 Jul 2020 18:30:33 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CB353A0C15 for <quic-issues@ietf.org>; Mon, 13 Jul 2020 18:30:33 -0700 (PDT)
Received: from github-lowworker-d31a065.va3-iad.github.net (github-lowworker-d31a065.va3-iad.github.net [10.48.17.70]) by smtp.github.com (Postfix) with ESMTP id 7E38B8C10E4 for <quic-issues@ietf.org>; Mon, 13 Jul 2020 18:30:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594690232; bh=/5Q4x+GiJB4Hz+kuphDLKASW0asF7hdLaBDq7wVZ+xA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2IXRWUKgGYZ4tWLKMqT/ncCk46W4DIV6DsLq9eN9hbrHxslu+l998JDbSubkr1a/o xYcG6sG7vIXykXCZu1mwM6l7XPBHYD+8DDXfgLSa0Dqx/uYebAIC8zoJK9672SyFsh 6JoycxfvQLuDOtQmJrFflZnJX2emXuZoUsKV29Hk=
Date: Mon, 13 Jul 2020 18:30:32 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5NIEPADQTZEZXAZM55DDV3REVBNHHCMFSQTA@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/657913670@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_5f0d0ab86effd_72753fea300cd9601843923"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/MJ3ahaRjzZDX0epmi4gMnDw6lHo>
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 01:30:34 -0000

@igorlord 
> In terms of practical considerations, embedded CDN nodes are certainly examples of deployments with high risk to reachability and fitness-for-service due to migrations after network attachment changes. However, even public-facing anycast CDN nodes can have a similar fitness-for-service risk due to attachment changes in areas with poor network interconnections (some parts of Asia, for example).

Thank you for elaborating. Good to know that we agree that the if the client should be using the same source address is an orthogonal issue to if the server disables migration for the preferred address.

My argument is, based on our shared view, that the issue should be discussed separately from disabling active migration the preferred address, because it is a separate problem (and that the current state of PR is incorrect in sense that it requires the client to use the same source address _only when_ migration is disabled for the 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/3765#issuecomment-657913670