IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Wed, 17 June 2020 16:23 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 DC21C3A0A38 for <quic-issues@ietfa.amsl.com>; Wed, 17 Jun 2020 09:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 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, UNPARSEABLE_RELAY=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 HoUBv_2a4lw1 for <quic-issues@ietfa.amsl.com>; Wed, 17 Jun 2020 09:23:53 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997233A0A66 for <quic-issues@ietf.org>; Wed, 17 Jun 2020 09:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=fkjGX+VVREKhzsBmIAKPjEH04Lk2emk9d1VuarFAX3s=; b= q2Lu57SJjABF+7gxYK1x9xijeLopF9CQVZpyI/Iq1WOna6Ajr1wJuMRpLfyyjdYh 5BwLqTzLh5MAoshyeNDJ7i7fu50rCrjRgY8vKZ5cgqafsNDz7KBGpJcEfUQShk/R iKaJ28EuYVN2O0zZwPLD3/03KXoZnFW3cM2/KmAz4zA=
Received: by filter0209p1iad2.sendgrid.net with SMTP id filter0209p1iad2-23291-5EEA4391-35 2020-06-17 16:23:45.584292287 +0000 UTC m=+764666.070128419
Received: from github-lowworker-b19c547.va3-iad.github.net (unknown) by geopod-ismtpd-1-3 (SG) with ESMTP id -I7EEoHIQguRzox1eOSYHw for <quic-issues@ietf.org>; Wed, 17 Jun 2020 16:23:45.502 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b19c547.va3-iad.github.net (Postfix) with ESMTP id 6D2B08003D for <quic-issues@ietf.org>; Wed, 17 Jun 2020 09:23:45 -0700 (PDT)
Date: Wed, 17 Jun 2020 16:23:45 +0000
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4KJN3Q6DVNHKD24NF46YSJDEVBNHHCMFSQTA@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/645459858@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_5eea43916af54_2113fbe36ccd95c1719d"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3KpOvD1Y5R+Y1IQvubgs5yyfwDYTA+AjDuOR HqVIG0XFm8HeQIrPjp4nff/n2AIOKNqIK+9/rsX463R7mzDWJP+r8xcOKDop+V+C3qSyXL416CyAnj ihMDBCo0naBAf798Xb5xUd1gPw7YF7j9fW5jL0wyWfiKsJ964X7WMoPyGHHQ3pH4f13kathV/c0oeu w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZUp_HRA3Z3ItLfpDAtKN_fMCOxA>
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: Wed, 17 Jun 2020 16:24:00 -0000

Thanks for the analysis, @kazuho.  The case I described could, indeed, involve a simple 4-tuple legacy load balancer in front of QUIC-supporting backends.  But it could also involve a QUIC-aware load balancer and still benefit from SPA for improved reliability and performance (removal of one more system with its failure modes and removal of some internal forwarding step within a deployment).

And then there is still another case -- using an anycast address as the handshake address and landing on a server deep inside your provider network.  You will want to use SPA to avoid a risk of anycast route change during a long-lived connection.  But you do not want the client with a secondary connection to another provider trying to migrate.

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

v2.23.0 | Report a Bug | By Email