Re: [quicwg/base-drafts] IP Anycast with server IP+Port renegotiation (#560)

Martin Thomson <notifications@github.com> Mon, 14 August 2017 05:03 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 636AE124E15 for <quic-issues@ietfa.amsl.com>; Sun, 13 Aug 2017 22:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 SCyECLZO37ky for <quic-issues@ietfa.amsl.com>; Sun, 13 Aug 2017 22:03:52 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 75F451241F5 for <quic-issues@ietf.org>; Sun, 13 Aug 2017 22:03:52 -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=1s3dLPX61YSbQiyN2MTBBK5KF4k=; b=mP9t0Msxo74jtg0v Z7Gv9MtSU8P+9C48RRVT3EsA4vU+Lra4tiDFDz8jTFO0GeHBIHlT8BtlSedJKpLJ 8IBEKrHQQOxnWEtmz1kboNnV2j0cH/dIogGPa4CkB7aH49BuF8ZEPTRQX4UiyuOm NHsUCqg9k5G4zgJRCy389TWgxx4=
Received: by filter0609p1mdw1.sendgrid.net with SMTP id filter0609p1mdw1-2955-59912F1B-7 2017-08-14 05:03:23.140500447 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id 6EGTJ1SxRMir2Iyp9aMbZA for <quic-issues@ietf.org>; Mon, 14 Aug 2017 05:03:23.198 +0000 (UTC)
Date: Mon, 14 Aug 2017 05:03:23 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7a01f87724bda133ff0e786924959956a629ad8d92cf0000000115a8f11b92a169ce0dd2a43a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/560/322100982@github.com>
In-Reply-To: <quicwg/base-drafts/issues/560@github.com>
References: <quicwg/base-drafts/issues/560@github.com>
Subject: Re: [quicwg/base-drafts] IP Anycast with server IP+Port renegotiation (#560)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59912f1b14f4d_2be943fa6ff087c2c3893"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1rCIwA4zn1+F/8TFhdx0LWIje50BzDU8ojlP WbdyxQV5GV4abh9GEYEsD15yPtFfkw2QGIuRlnBTZ8Xk4l8JrbaAhGN6zdLcWVcjUAX6WW6U1aWfhL eqd+XI4zDnacNKtEQF+vhlefzL/GYrm+139FbvlR0W4QajyusdS1Vwuk9i+6Lbmyblp0cxX5M44hnO A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tHSE0y934QTcVgqW6FOfQWxpeik>
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, 14 Aug 2017 05:03:54 -0000

I'd like to hear from server operators whether they see the need for this sort of capability.  Otherwise I think that we should park this.

It's certainly possible to define a new frame type (call it MIGRATE) that acts much like the [HTTP Alt-Svc frame](https://tools.ietf.org/html/rfc7838).  An endpoint that receives it might move to the new transport endpoint as soon as feasibly possible.  For this, you would want to pair MIGRATE with NEW_CONNECTION_ID so that linkability could be broken.

We'd also have to be careful not to accidentally define multipath, because the natural reaction to this is to retain the old path until the new path has a sufficiently wide congestion window.

In any case, the frame that tests the new path for liveness is necessary before we address this.  See #161 for more on that.

-- 
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/560#issuecomment-322100982