IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connection migration optional? (#1271)

Nick Banks <notifications@github.com> Tue, 17 April 2018 17:18 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 2183712D959 for <quic-issues@ietfa.amsl.com>; Tue, 17 Apr 2018 10:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.008
X-Spam-Level:
X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 PKz6YvUCU2AI for <quic-issues@ietfa.amsl.com>; Tue, 17 Apr 2018 10:17:59 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 0FD3E12D956 for <quic-issues@ietf.org>; Tue, 17 Apr 2018 10:17:55 -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=8HMPLK2AEBqPsFKlYdy4GVkbj6c=; b=I4somK5V2yY8jSXX 71XXHWzlbnJIXyDkBUy/jVdVKtIvvElb0FMz75jp43mx+kBmOYWruSHpXj5KBfkM WhcRa14QGcYZzgQYrLODaTnx/PbDh/9I4Ip9KvujgdOfNtI73eqjX36tDJqPuYDL naXvD2oR7HIJfEuUHj7llZjl3f4=
Received: by filter0387p1iad2.sendgrid.net with SMTP id filter0387p1iad2-16984-5AD62C42-19 2018-04-17 17:17:54.786603384 +0000 UTC
Received: from smtp.github.com (out-10.smtp.github.com [192.30.254.193]) by ismtpd0026p1las1.sendgrid.net (SG) with ESMTP id slzwl7mPRu6u2AkbMS6TYQ for <quic-issues@ietf.org>; Tue, 17 Apr 2018 17:17:54.715 +0000 (UTC)
Date: Tue, 17 Apr 2018 17:17:54 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd0d9d85f2aec1d94cb83708605fce9f34335b6f092cf0000000116edee4292a169ce129955d7@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/382072800@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 optional? (#1271)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ad62c42325a3_54252adf04d9ef5034015"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-CSA-Complaints: whitelist-complaints@eco.de
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0BDw9N/00RQ4EymU2DF4Nsg4CDfvJBEiNhSt hL9ImXYk1cVZxGIBdjfFq0KAdpTTXySrAsGg6UOVGppofYUJQRv80cCMOTOQhdm/wxAlUv+HILMnQA 65/kCweMZ1apf+yUfAHvLQF7pESLtIbXrvl6BKcTAlG6Ea7PQncB+ey05t1w39ixq2BiI6shoGpX6V A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/IsKY2oY2h0Qk71xRm_2Db9ANR20>
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: Tue, 17 Apr 2018 17:18:01 -0000

One down side of implicitly stating (explicit) migration is not supported, just by the server not providing NEW_CONNECTION_IDs, is that the connection can't use different connection IDs for the same path, even if the server and load balancer support that scenario. Recently, the spec was updated to allow for changing the CID after some period of quiescence, with the expectation that NAT rebinding will likely happen. That wouldn't work with this model.

My personal preference here is still an explicit indication (most likely via TP) that the server cannot support explicit migration / client IP address changes.

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

v2.23.0 | Report a Bug | By Email