IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Thu, 09 July 2020 16:55 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 74E203A0D04 for <quic-issues@ietfa.amsl.com>; Thu, 9 Jul 2020 09:55:09 -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 06KO9NYXsVox for <quic-issues@ietfa.amsl.com>; Thu, 9 Jul 2020 09:55:08 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C79F43A0D00 for <quic-issues@ietf.org>; Thu, 9 Jul 2020 09:55:07 -0700 (PDT)
Received: from github-lowworker-a27607f.ash1-iad.github.net (github-lowworker-a27607f.ash1-iad.github.net [10.56.18.61]) by smtp.github.com (Postfix) with ESMTP id 23D586A1D25 for <quic-issues@ietf.org>; Thu, 9 Jul 2020 09:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594313707; bh=z6vZg2h2jtT8DXh43yVfn2VoiaDT8u1FijFgmdKCAfE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iQTiUY3BomboEsEZz5CtIAxgD+qns+q5wl0kmBOPLB6xwVPBkRim69QTcdhhCyxDO Q/NVETs1stpSqTFkYvJfqm6h6icjQ4d3u2ZNTAPPHwuK+zi9pRSpXzUnbP/Y0juag+ A9g6Cz2kE6M9ef3h5eMiD/qWgvrq+dR/OeZ9w69w=
Date: Thu, 09 Jul 2020 09:55:07 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6UDCXFETIUOZEVET55CMWOXEVBNHHCMFSQTA@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/656239210@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_5f074beb15c16_5ab63f8b81acd964145451"; 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/gTHc4nAFSUamaQHcIZjqn5tTpLM>
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: Thu, 09 Jul 2020 16:55:10 -0000

I think we actually can **almost** support the use cases I presented without a change, actually.

A server that does not desire a client to actively migrate can just avoid sending NEW_CONNECTION_ID frames.  Since migration to the SPA requires a change in CID, and a CID sent in preferred_address is the only additional CID available, that CID will be used up during SPA migration and no additional active migrations will be possible.

This **almost** solves the problem, because the client can combine active migration with SPA migration.  If we prohibit such active migration at the same time with SPA migration, if disable_active_migration TP is present (and, possibly, no NEW_CONNECTION_IDs have been received), it would solve the problem completely.

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

v2.23.0 | Report a Bug | By Email