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

Nick Banks <notifications@github.com> Fri, 06 April 2018 17:59 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 13772124D6C for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 10:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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, 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 w9U9vPaWZFRl for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 10:59:27 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 E9493124D68 for <quic-issues@ietf.org>; Fri, 6 Apr 2018 10:59:26 -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=mWzra7nLuqdswnbbfB4+swAk5ZI=; b=qQ1qQHhnm60Ty/f7 KYQen3DhCixS0LOgL1/frxZKzBllbYnlbncx9tZB1KWYaMCviWM6Rwk+guvswhk8 m4k1Zbxtc+sqS2Vb6+djm8G17sdoWIIYo4tyKbYI4Y5KGjA08TrqKeBXdEhx2Myp 0+VVDdv2iElMNDMyD2TF14k92LA=
Received: by filter0600p1las1.sendgrid.net with SMTP id filter0600p1las1-20652-5AC7B560-2 2018-04-06 17:58:56.152139101 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0038p1mdw1.sendgrid.net (SG) with ESMTP id -ErobRsoQ_G_u0e75szSyA for <quic-issues@ietf.org>; Fri, 06 Apr 2018 17:58:55.860 +0000 (UTC)
Date: Fri, 06 Apr 2018 17:58:56 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0a9e0d1d4d756765f624c66d319d9006b7ccdfb792cf0000000116df775f92a169ce129955d7@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/379329991@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_5ac7b55fa9d0b_1c4e3fb1dac94f34229876"; 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-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Y19v0RD6Y8Fs/vpy2dGN25KfSHe2hSPis9f v9yB79+MUGBVAtpQQpjm/sEgsp9r3bETMre1CGUFZO7uD8pmNzbDo3D7RtypTXKKM+t+WGzcRB96Pf q1eqzRedOC6g5LgaJXSl3gx83A4s4YyboYS7/NKjry5+2byhQU4msGlmE83JsRpS3s+4mOJySwWVi1 I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/C1vSV9zuplXhjF0JcZYpFGzisHA>
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:59:29 -0000

One problem that this is trying to address is a load balancer that does 4-tuple load balancing. In that case, even a NAT rebind might end up sending the client's new traffic to a new server. So in that case, if the client really need to keep the connection bound properly, keep alives must be used.

I agree that this option shouldn't be a copout for servers to just not support migration. Though it will be in their best interest to support it (if their infrastructure does) to provide the best experience to their clients.

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