IETF Logo Mail Archive

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

plakhera <notifications@github.com> Thu, 13 December 2018 07:04 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 1D3AD128766 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 23:04:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
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: 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 s3GJD3Qmeh0Q for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 23:04:17 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D607912426E for <quic-issues@ietf.org>; Wed, 12 Dec 2018 23:04:16 -0800 (PST)
Date: Wed, 12 Dec 2018 23:04:16 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544684656; bh=A05m2E8UkZFmm5ZheSwv7isyC1qbzrecqJC5Cm9lBOM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AKJX95jW2Lcu7JnvPbbNwTDD3lhcTqDv+aAn8dPNOUDQNf8LQ1PNQXPyfNdF+t/gV 58uD5NoeT0Ya8obBP+9XzV4hB8Xte10nUN0t+FHDEdbiIxyBcFao0i/hCI6MkFr8y8 KoxL5Zf6ZgM8bg3dbZyqMzYIZvbecdMcNnMT3+do=
From: plakhera <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf74c1d7e4e199b48b4ed2498ccd3afcda37ea63592cf000000011829c67092a169ce1742d117@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/446863947@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_5c120470b42a_2c2a3fae58ed45b8775366"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: plakhera
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/qhZyxXW3bvTM2xsTEZLfstwTUmg>
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: Thu, 13 Dec 2018 07:04:19 -0000

@ekr 

> It seems like between (a) resolving both address families and potentially preferring the one matching the address family available on your other interface(s) and (b) address synthesis on-device, many of the cases are covered already.
> 

Most combinations of server configurations and network configurations work.
What does not is dual stack server deployment and starting on an interface that has ipv6 only Nat64/dns64 connectivity and moving to ipv4 only interface.

DNS may be configured for load-balancing itself, so to assume that A record points to the same node and AAAA record points to may not be correct.
Also, as you may be aware, some devices may suppress sending A query altogether on an interface that is connected to IPv6 only network (even with NAT64/DNS64).

-- 
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-446863947

v2.30.2 | Report a Bug | By Email | System Status