IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Tue, 16 June 2020 16:28 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 EF5533A1921 for <quic-issues@ietfa.amsl.com>; Tue, 16 Jun 2020 09:28:01 -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 pFevJN7Q9YN1 for <quic-issues@ietfa.amsl.com>; Tue, 16 Jun 2020 09:28:00 -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 B75873A191E for <quic-issues@ietf.org>; Tue, 16 Jun 2020 09:28:00 -0700 (PDT)
Received: from github-lowworker-275fa97.va3-iad.github.net (github-lowworker-275fa97.va3-iad.github.net [10.48.17.64]) by smtp.github.com (Postfix) with ESMTP id C9369A1ECC for <quic-issues@ietf.org>; Tue, 16 Jun 2020 09:27:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592324879; bh=TMqjsg8k8N7igbm3klLL+tdtXJLjJCFoA+YhiEQ/mrM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iUC8GcS+4PRfCnjfK4vMStHhq7ZsLg4Ac7c1O7AFwtsj1EsYln2ZU6eQDHzjyX3UG 1sXaiMKN+eoNoV/c5Z3+5Q0hzgEIu/xgLcQHMq6V3pKlTG4+pBLKk8niDaTPlCShPc JZ+WW9dyI9JKJGe0l2CBuavXyMlotKAIu2Cku7Lw=
Date: Tue, 16 Jun 2020 09:27:59 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4KZROO3EEERW2TWXN46TKA7EVBNHHCMFSQTA@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/644871386@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_5ee8f30fbae8a_627a3fa84d8cd964141979"; 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/VI3lnAUcX3Xs1A5sGwRZ9G7fMEI>
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, 16 Jun 2020 16:28:02 -0000

@MikeBishop I would think the new behaviour is better delegated to an extension.

The new language (w/o an extension) irreparably causes performance problems for the kind of very common deployments I've indicated -- if they use disable_active_migration w/ SPA, migrating clients will be affected after switching to SPA; if they use disable_active_migration w/o SPA, clients cannot use a more performant/reliable preferred address.

However, if you have a server deployment where client migration w/ SPA is fine, just provide SPA and do not set disable_active_migration.  The purpose of SPA is to tell the client "you will get better service using that other address".  So clients will just switch to SPA as soon as they can, and everyone will be happy.

The new behaviour is pandering to not-very-well-behaved clients that do not obey SPA at the expense of well-behaved ones.

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

v2.23.0 | Report a Bug | By Email