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

janaiyengar <> Thu, 13 December 2018 01:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 22059128B14 for <>; Wed, 12 Dec 2018 17:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Status: No, score=-9.46 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_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 brm1ifko56np for <>; Wed, 12 Dec 2018 17:46:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6F6291313BF for <>; Wed, 12 Dec 2018 17:46:23 -0800 (PST)
Date: Wed, 12 Dec 2018 17:46:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544665582; bh=6kwvrQOeL1QRQxETC764J6RdP3PteUR/jMrHM6iR3f0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GWa6DLAP4ZBEXQuhrFMAUEjzqncK6AWQpDuY2djG6pPUsu3G5qkEroTImoHIFWyRV iIeILhh2powO3CbKajmFVoQOOCMVf2K7jozH+5m4pynQQ3H/kpvQh7F7DwGowNkAWK UK2ZTbELhYcWuUmZvotzi4HNFpGByyelL9HiUhY8=
From: janaiyengar <>
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_5c11b9ee26d09_6b7d3ff607ed45bc4297f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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 01:46:26 -0000

So, preferred_address has slightly different semantics than what you're asking for. It currently means that the server prefers that the client use the indicated address. What you want is an _alternate_ address, something that the client can use if it migrates to a network on a different address family.

I think we can get the low-hanging fruit here by having alternate_address_v4 and alternate_address_v6 transport parameters. That said, I'm not convinced of how important this is to solve in v1. This affects only migrations, and then only those that are from networks on one address family to a different one.

I'll note that an explicit ADD/DELETE_ADDR doesn't work because of NATs (as @mikkelfj notes).  That is fine; in the spec, we've basically used receiving a packet from a new address as an implicit ADD_ADDR signal. The problem you're running into right now is that we don't support server migration in v1, which doesn't allow a server to send a packet from an unknown address to a client.

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