IETF Logo Mail Archive

Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only NAT64/DNS64 Networks (#2122)

Christoph Paasch <notifications@github.com> Wed, 12 December 2018 17:13 UTC

Return-Path: <noreply@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 29F4E130F39 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 09:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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, RCVD_IN_DNSWL_HI=-5, 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 mIAh-5dMCizG for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 09:13:06 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DA34130F28 for <quic-issues@ietf.org>; Wed, 12 Dec 2018 09:13:04 -0800 (PST)
Date: Wed, 12 Dec 2018 09:13:03 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544634783; bh=3v7LC5DbUOpSLUz8kgjfsuiWJB1uisnpUr9tSVBMLj0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l1zE+uuygjcQ4ZsSSDcyICW7EQlRkxrtagi1SZedEGosamLfTrXvocrTcytnAwitQ ylZmTXI1I2/fyJLuD3lpeVIxAxE7LwVktTDg7sp0XF6cdQsV57fshiDPAHTZJpmC0B AFeO58x4wgh3qsScZrLTlSgVwTNqeT/HChmmIxq0=
From: Christoph Paasch <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5486319b4c9f4240286ac4b97b459309bc735d8c92cf000000011829039f92a169ce1742d117@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2122/446667137@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2122@github.com>
References: <quicwg/base-drafts/issues/2122@github.com>
Subject: Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only NAT64/DNS64 Networks (#2122)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c11419f2d5e5_be03fdeeead45b4275125"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: cpaasch
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/A0gxl8JGdbye0vKRZ4OG0iChwJ8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 12 Dec 2018 17:13:11 -0000

I agree that having a way for the server to signal its IP-addresses to the client is very important. Even in the v1 of Quic.

Otherwise, Quic migration will hardly be effective.

To easily deploy Quic behind a load-balancer one simply assigns unicast IPs to the servers and lets Quic announce these (v4 and v6) IPs to the client as "preferred address". Then the client can migrate by using the preferred address. There needs to be a way to announce the preferred address in both v4 *and* v6.

This should address Scenario 1 and Scenario 2 that @plakhera is describing.

-- 
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/2122#issuecomment-446667137

v2.23.0 | Report a Bug | By Email