IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Mon, 09 April 2018 01:00 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 3BDC4126C22 for <quic-issues@ietfa.amsl.com>; Sun, 8 Apr 2018 18:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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 MlsVOQbaqEJn for <quic-issues@ietfa.amsl.com>; Sun, 8 Apr 2018 18:00:07 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFE1A126BF0 for <quic-issues@ietf.org>; Sun, 8 Apr 2018 18:00:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; 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=xE7FlRuMMZU9mEMFp2majrQh/AM=; b=vGCXfK9Zjv9II1a/ dMwjX3UTRhCPM634XrpJGU1o3mPciTzBLAgqrygwHOfcqegZ5rPwoFyli4FdcnAL FDz6DKzp9AvnwxZaNkbpFb9WowJ0YBcq9LkcuBpF8D19ENYrqpnlert9sgsIO2zp ge6XptgS7FBlo4h/bNo1eJjkzOc=
Received: by filter0980p1mdw1.sendgrid.net with SMTP id filter0980p1mdw1-23937-5ACABB15-15 2018-04-09 01:00:05.697567824 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id LWzguN6gQ-uw1m4WdAOoeg for <quic-issues@ietf.org>; Mon, 09 Apr 2018 01:00:05.699 +0000 (UTC)
Date: Mon, 09 Apr 2018 01:00:05 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6e36497035df6d6fde5e653a5c2b655ee686e53c92cf0000000116e27d1592a169ce129955d7@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/379598503@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_5acabb1597e0e_4af03fdbaff5ef2c314868"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak13gUA988GGpQeFA5eBuRogjP13Iqp78dAZH3 Ikk1JkzutWAXI85218/1a+8kLc+e8rTUePgTBS9pkpjac87l+tw2JykHoL+pj8ie8nLWkU1nEzCbY+ 6mYR9n1MKel4MXUx05ic3qfjo95L58hZE74GwSVVfeAtvx+rqbl7xE+mZTokWfuIQBWc6ctNxw68Rm I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/zTAWCHiq6KoH_zV8Aht3sKrLEv8>
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: Mon, 09 Apr 2018 01:00:09 -0000

If the concern is that the server can't manage migrations, the server can simply not send NEW_CONNECTION_ID.

I tend to think that' would be a real shame though, because the cases that need migration are pretty significant as @tfpauly says.

If we are going to build a system that relies on client opt-in, and servers that potentially don't support the feature, then perhaps we should entertain a system whereby clients request new connection IDs rather than have them provided spontaneously.

Again, that would be unfortunate because now we have created a means by which clients are segregated based on capabilities.  Worse, that segregation might be based on their ability to pay for access, if a "metered" flag could disable migration.

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

v2.23.0 | Report a Bug | By Email