IETF Logo Mail Archive

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

Mike Bishop <notifications@github.com> Wed, 12 December 2018 17:55 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 31D5D13118E for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 09:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.459
X-Spam-Level:
X-Spam-Status: No, score=-4.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_NONE=-0.0001, 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 1NWNXzyOjK_U for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 09:55:12 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EF7B13118C for <quic-issues@ietf.org>; Wed, 12 Dec 2018 09:55:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=RfeLX9bXoNzpAHHfu+Ys7VqNPhg=; b=CIN6zT7qoLrjuFLR cI/LGsbhUt7DomUu7Eohrt+ydzzQQUOykrd+uls7GjlCEbqPsoIga8zZ+S0u0LOr y3DU97y4oc2HAnDMcWB3u4GBjj33Vhh3mUzlLoZdk36PQ8NboAnXILfFaoNBePdD EEtQCl1uN8U/0W032IMNngGMGqY=
Received: by filter0231p1iad2.sendgrid.net with SMTP id filter0231p1iad2-1926-5C114B7C-9 2018-12-12 17:55:08.546624499 +0000 UTC m=+152312.526276231
Received: from github-lowworker-fc273f0.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0033p1iad2.sendgrid.net (SG) with ESMTP id ACwzkaFdSJiuNsBy8rYjiQ for <quic-issues@ietf.org>; Wed, 12 Dec 2018 17:55:08.558 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-fc273f0.cp1-iad.github.net (Postfix) with ESMTP id 871BCC097A for <quic-issues@ietf.org>; Wed, 12 Dec 2018 09:55:08 -0800 (PST)
Date: Wed, 12 Dec 2018 17:55:08 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd08ceff5307aee23c86fe24949e9595e616831b492cf0000000118290d7c92a169ce1742d117@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/446681393@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_5c114b7c80896_62103fa7e44d45c41678a"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2J3UKUts4n9zgSsLfzP/f5WZ1x8oxCySVtuL QrshXI2e8/S0Bb/OF/X6MNu+mLJ50qxOBcvajGtaiTszOyjG3BvL0THIW4I2HPyPO2uK3fn6CiOg/e MCMinrPt4X1/imbWJwYzr1NZYUUc4bYvZBCflp6D1U4ipPm7Xg37pB4OIWeYkJt8nKPO+LOhruzu9z E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2A9H7NBHNhcBGOQYdvjDTMLSKCU>
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: Wed, 12 Dec 2018 17:55:14 -0000

@plakhera, my comment about addresses local to the client was thinking more about a server which is v4-only won't know how to construct a corresponding IPv6 address for the client network's NAT64.  The client would expect to discover those via DNS64 and needn't know that there's a relationship between the addresses.

Is there precedent for the NAT64 address mapping being (un)done on the client?

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

v2.23.0 | Report a Bug | By Email