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

MikkelFJ <> Wed, 12 December 2018 15:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 36016127133 for <>; Wed, 12 Dec 2018 07:19:49 -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 1q4l5rWNpUhf for <>; Wed, 12 Dec 2018 07:19:47 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 554031252B7 for <>; Wed, 12 Dec 2018 07:19:47 -0800 (PST)
Date: Wed, 12 Dec 2018 07:19:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544627986; bh=1xScbnk79wBh0JG466UACLyefF+Z9tYbdkZm2tSmxlE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bLA9cacwED/7LhWIgzRq7StS4IUwJlIQbUy8CrnxuAeCEZK9yPiq+H0y6HEq3bSgL 3yaHBIGPP042FcJ2fdKI+sVKhFgIQJ8BGY/fem3vjYPK9uRqNeUDQ8TXcxqQenYfX+ dLly9Lr6tS4ZPc8KBvW4524KZyq7EFMlOeW8mGbE=
From: MikkelFJ <>
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_5c1127121e197_46ab3fbc0fcd45b43765d3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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 15:19:49 -0000

Note that generally an endpoint does not know its own public address because it can sit behind load balancers and multiple layers of NAT devices. So having the endpoint publish alternative addresses will not the solve the problem in general.

In fact the scenario could be reformulated to load balancer on multiple stacks instead of the server endpoint. You end up needing some DNS service that can deal with it.

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