IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connection migration must be negotiated (#1271)

Tommy Pauly <notifications@github.com> Fri, 06 April 2018 17:08 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 404AD124D37 for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 10:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uqvbXw1XfMgw for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 10:08:00 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 689FB1200C5 for <quic-issues@ietf.org>; Fri, 6 Apr 2018 10:08:00 -0700 (PDT)
Date: Fri, 06 Apr 2018 10:07:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1523034479; bh=NpvS/ZrpecIVrQCMvKpfuj6Ai4SiQtxWKeN/Bc5VNls=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jRSwjYIEQiJ6Ta7fYFmH3YZnRVxtTm+U7DoGDwKNBnKqI4Jdg/ZbVqEZpXmiUFvgm 0Vy6B3ewodR/GVelS5wJ1KFvgyL0yoKMmzx/ODsjPhKhmjoHY/Te+DYYPTajhZUDzP 9l5CYu6YZRnQlmZkEdmwezAdFNuUbhvTWqikPqRg=
From: Tommy Pauly <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1e5460d5edf8982e005353c3f7cb58681da16f1a92cf0000000116df6b6f92a169ce129955d7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1271/379316349@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1271@github.com>
References: <quicwg/base-drafts/issues/1271@github.com>
Subject: Re: [quicwg/base-drafts] Connection migration must be negotiated (#1271)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ac7a96f2b817_e9f2b04e23faec8353e5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tfpauly
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/M3uVrjV038mxD6SLtT_QMWvEDwk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 06 Apr 2018 17:08:02 -0000

@pravb I disagree that this would be an uncommon client use case. It's important to distinguish migration from multipath; the former does not imply simultaneous use of two interfaces, just a transition between interfaces. This is exceedingly common on all mobile devices (moving between Wi-Fi, LTE, and back again), and even quite common for laptops that get plugged into Ethernet, and may be unplugged. The lack of support for resiliency at the transport layer has plagued many connections.

I agree that if there *is* an option to be negotiated, it should be an explicit disabling of the feature, and we should assume that migration is enabled by default. Opt-out is fine, opt-in is too limiting.

-- 
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/1271#issuecomment-379316349

v2.31.3 | Report a Bug | By Email | System Status