IETF Logo Mail Archive

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

Igor Lubashev <notifications@github.com> Mon, 15 June 2020 19:57 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 3D6F03A0D3C for <quic-issues@ietfa.amsl.com>; Mon, 15 Jun 2020 12:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 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_28=1.404, 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 acFdqHHVwCen for <quic-issues@ietfa.amsl.com>; Mon, 15 Jun 2020 12:57:23 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 912243A0D37 for <quic-issues@ietf.org>; Mon, 15 Jun 2020 12:57:23 -0700 (PDT)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id BF55E660E52 for <quic-issues@ietf.org>; Mon, 15 Jun 2020 12:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592251042; bh=iEPotXBn7b57i3iFLEL+K0PC4wYqnnoZl3qY0h14QaA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PSUg2H2+zt7CKi1qo9sKFKX1ntLFk3wp6Ohjtwr1q4YUONrwTFm25JJI2vuw0v6DV POiUVaRPBnM6aNyIVPnvIKiw6Mv5tcYHQSW6bkP9WQu6KlDtkJT00MFzBdtAN13yqs 6qxWUIKpZe2Yqe6avUbI+8pnVJV8TX5cNy3D2uQI=
Date: Mon, 15 Jun 2020 12:57:22 -0700
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6NUD3HWJ2IPJHU56546OZ2FEVBNHHCMFSQTA@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/644346096@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_5ee7d2a2b08ae_29d53faf6bccd9685669bb"; 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/Uv-MUSfoYgsVVvTorigHgXkLwj8>
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: Mon, 15 Jun 2020 19:57:25 -0000

There is no problem in such deployment to do the right thing regarding Connection ID tracking, etc.  The problem that a change in network attachment provider is unlikely to work - you could either blackhole, get ICMP unreachable, or your performance would be slow.

If the client honors "disable_active_migration", they would open a new connection from the new network attachment provider (and maybe get a different deployment).  If the client ignores disable_active_migration, they are on their own.  (After path verification, the HTTP3 server would likely send GoAway or close the connection.)

>  it is my understanding that a client is allowed (and have to be allowed) to use any source tuple when migrating to SPA.

This is the consequence of #3608 (#3670), which breaks the deployment scenario in this issue.  (It used to be handled ok before.)

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

v2.23.0 | Report a Bug | By Email