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

ianswett <> Thu, 13 December 2018 04:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 37C1E128CFD for <>; Wed, 12 Dec 2018 20:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.459
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yQpwEt8IZcw0 for <>; Wed, 12 Dec 2018 20:12:22 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 69DE2129C6B for <>; Wed, 12 Dec 2018 20:12:22 -0800 (PST)
Date: Wed, 12 Dec 2018 20:12:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544674341; bh=v1e16F1GnEtKJ13NcdqgMymvjP6OBYGCEF2hxFN4JRw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HH/FeFdHbZlXXx1bWZlqm+Abic9HszjyQVkQUCALuVbrvwZXxNzpA36uR1nSWAFSd MXF1dxu5rKEsLlpHrwS/GHC5bzakhCZIFyVvf3aYZF5IAsMmG0RGXPdQfa0kolpq/T iQgUt9GA9SFmegfdXC/SFiNm5GWjlHRjt5gB1Ciw=
From: ianswett <>
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_5c11dc25b1f8a_3b193ff788cd45b4224619"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Thu, 13 Dec 2018 04:12:24 -0000

To echo @cpaasch point, this could be a large problem for connection migration.

Without a way to communicate an alternate address to the peer, it seems like v6 to v4-only will consistently fail?

If connection migration is best effort(ie: expected to fail some user-visible fraction of the time), this may be Ok.  But if it's expected to work ~100% of the time when an alternate network is available, this is a real problem.

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