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

Mike Bishop <> Wed, 12 December 2018 14:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CA9671277C8 for <>; Wed, 12 Dec 2018 06:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Status: No, score=-8.056 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aHoI2oswmXVd for <>; Wed, 12 Dec 2018 06:47:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1EBBE127133 for <>; Wed, 12 Dec 2018 06:47:28 -0800 (PST)
Date: Wed, 12 Dec 2018 06:47:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544626047; bh=KJsZGW8GjZwy5tmw0WPIS43qpauL9t5IZelIHssQyJg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yiQFX2u2MunZtpk7DP1NfBKKmPy4sVygnM8D+pB1/CVAv+87Su/Ng6iRZzeQ0N/E1 DFn2Qs8iKAvUHbyo6BjcVFZGAqgeg+pEUi/4EWBTDUvD0aBuEpXXkIYDGA7ccM5Bsf Vxobvk+lZZlxhuVDMuqfmD0icOU52Rusc+1Wtltk=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2122/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5c111f7f45f08_49d83f8a34ad45b42171d6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Dec 2018 14:47:30 -0000

I doubt this is feasible in our current architecture.  It would effectively require the server not only to have multiple addresses from the client's perspective, but require the server to have addresses that it can't tell the client about because they're local to the client (NAT64).  I suspect the best we'll get for v1 is that migration fails, but the client successfully opens a new connection.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: