IETF Logo Mail Archive

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

Praveen Balasubramanian <notifications@github.com> Fri, 06 April 2018 23:50 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 5B143126D45 for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 16:50:05 -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 9ErhBxs5Bix3 for <quic-issues@ietfa.amsl.com>; Fri, 6 Apr 2018 16:50:03 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 7E2FE126BF0 for <quic-issues@ietf.org>; Fri, 6 Apr 2018 16:50:03 -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=fuVPet03lm4vjKXpQ6njdkpcbVs=; b=Vz80RCL8rwpqXUuL fKgG3fXSeZHomvMyWNXFMLCSB4qYXNM9R+cPUM0+yKxlAzSt/xT9+kEDSaYff5RZ FOTHIJhi7jchaFvB/VZF2WsFTY++fw1+HPMD5XTsOeIS/9PzvINDVl8RtlETVYYf WuD/YfCi/wzJ8fHCIUS+SbmkRYA=
Received: by filter1182p1mdw1.sendgrid.net with SMTP id filter1182p1mdw1-20996-5AC807AA-16 2018-04-06 23:50:02.698735893 +0000 UTC
Received: from smtp.github.com (out-5.smtp.github.com [192.30.252.196]) by ismtpd0035p1mdw1.sendgrid.net (SG) with ESMTP id BUef9j3BQeuSk1r5SxYLzw for <quic-issues@ietf.org>; Fri, 06 Apr 2018 23:50:02.579 +0000 (UTC)
Date: Fri, 06 Apr 2018 23:50:02 +0000
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abacf5a2b67c557975e0458470dd40d79a1df7a12b92cf0000000116dfc9aa92a169ce129955d7@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/379413340@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_5ac807aa6858b_50c03fd70066ef381219e8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0EdHV0aymL3mwNCKKMjFkbFejShaxDvEJkeq H/3qwjGiKMPygT+IVwmx4FM5kkbTWWjlY3+9QH70CB0TrGrwYRwQSxadrRj3bV5PfWQJr6lncds9wS 4czzjTSvBGGZrh6JKeMGQZHJyGPMnovAARrXILrcYOuOR0AcQlw3/GPBbw2q+0dBeI9eS57Dgqj9t8 X6tstI1vZlU/W0gsSWq2Hg
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/YLG34vqwttumX44ylhWzVjgdtMU>
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 23:50:05 -0000

@RyanAtGoogle, yes this is strictly about explicit peer-initiated migration. As I mentioned before we have two possible options for dealing with NAT-rebinding and we cannot negotiate that anyways since it happens outside the control of the peers. The two options are: use 2-tuple load balancing OR do keep-alives and use 4-tuple load balancing. Please see my response before Ian's above. We cannot incrementally deploy peer-initiated migration with existing infra as Ian also pointed out. 

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

v2.23.0 | Report a Bug | By Email