IETF Logo Mail Archive

Re: [v6ops] combination of NAT64/DNS64 and NAT44

<mohamed.boucadair@orange.com> Wed, 17 April 2013 11:20 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381DA21F8D82 for <v6ops@ietfa.amsl.com>; Wed, 17 Apr 2013 04:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.332, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioG2CNkLhNwa for <v6ops@ietfa.amsl.com>; Wed, 17 Apr 2013 04:20:45 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id EC6F421F8D40 for <v6ops@ietf.org>; Wed, 17 Apr 2013 04:20:44 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 1A6E118C554; Wed, 17 Apr 2013 13:20:43 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id F284D4C017; Wed, 17 Apr 2013 13:20:42 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Wed, 17 Apr 2013 13:20:42 +0200
From: mohamed.boucadair@orange.com
To: Mikael Abrahamsson <swmike@swm.pp.se>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Wed, 17 Apr 2013 13:20:41 +0200
Thread-Topic: [v6ops] combination of NAT64/DNS64 and NAT44
Thread-Index: Ac47Vbd5saIub3dVR1Gx3IyHKJrZSwABtDwA
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC66217D9@PUEXCB1B.nanterre.francetelecom.fr>
References: <alpine.DEB.2.00.1304171206080.23668@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1304171206080.23668@uplift.swm.pp.se>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: "Tirumaleswar Reddy (tireddy) (tireddy@cisco.com)" <tireddy@cisco.com>
Subject: Re: [v6ops] combination of NAT64/DNS64 and NAT44
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 11:20:46 -0000

Hi Mikael,

Isn't your problem similar to what is discussed here: http://tools.ietf.org/html/draft-kaliwoda-sunset4-dual-ipv6-coexist-01?

This problem is also discussed at: http://tools.ietf.org/html/draft-wing-dhc-dns-reconfigure-00

Cheers,
Med

>-----Message d'origine-----
>De : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la part de
>Mikael Abrahamsson
>Envoyé : mercredi 17 avril 2013 12:23
>À : v6ops@ietf.org
>Objet : [v6ops] combination of NAT64/DNS64 and NAT44
>
>
>Hello.
>
>I would like to solicit some feedback on a deployment scenario.
>
>A device has dual stack access on its WAN access, with IPv4 RFC1918
>addresses or 100.64.0.0/10 address space on WAN side, and a CGN NAT44
>gateway for sharing these addresses towards the Internet, and GUA IPv6
>addresses. There is also a NAT64 gateway in the network, and a DNS64
>resolver reachable over IPv6. There is a regular resolver reachable over
>IPv4. A dual stack client will get both types of resolvers.
>
>Now, aim is to support all kinds of devices, IPv4 only, IPv6 only, and
>dual stack. The single stack cases are pretty obvious (IPv4 single stack
>will use NAT44, IPv6 single stack will use NAT64/DNS64 and require 464XLAT
>for "proper" function), but my question relates to the dual stack case.
>With a DNS64 based resolver, only IPv4 literals will go over the NAT44, if
>the device uses the IPv6 based resolver. If it uses the IPv4 based
>resolver, it will use the NAT44 device for IPv4 only sites.
>
>So my questions are:
>
>1. Is there a case where the above setup will cause problems?
>
>2. Does it make sense to turn on DNS64 even on the IPv4 based resolver?
>This would cause AAAA lookups over IPv4 to steer traffic towards the NAT64
>gateway, in case a client chooses to use the IPv4 based resolver for
>lookups even if it's dual stacked. As far as I understand, a DNS64 based
>resolver will forward A quaries unmodified so this shouldn't cause any
>problems for single stacked IPv4 clients?
>
>3. Did I miss anything?
>
>--
>Mikael Abrahamsson    email: swmike@swm.pp.se
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email