Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt

<holger.metschulat@telekom.de> Thu, 14 November 2013 06:45 UTC

Return-Path: <holger.metschulat@telekom.de>
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 728F211E811D for <v6ops@ietfa.amsl.com>; Wed, 13 Nov 2013 22:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 kPEGSrhymxrm for <v6ops@ietfa.amsl.com>; Wed, 13 Nov 2013 22:45:38 -0800 (PST)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 7922311E8101 for <v6ops@ietf.org>; Wed, 13 Nov 2013 22:45:37 -0800 (PST)
From: <holger.metschulat@telekom.de>
Received: from he111493.emea1.cds.t-internal.com ([10.206.92.96]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 14 Nov 2013 07:45:24 +0100
Received: from HE111490.emea1.cds.t-internal.com ([10.206.92.87]) by HE111493.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 14 Nov 2013 07:45:24 +0100
To: <gert@space.net>, <phdgang@gmail.com>
Date: Thu, 14 Nov 2013 07:45:22 +0100
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
Thread-Index: Ac7e7ieC4Pb3Pzx1RNO0RlkEICeJSgBpm7QA
Message-ID: <AFAB9759B1DE4F4187483FC509B50199011699555191@HE111490.emea1.cds.t-internal.com>
References: <97EB7536A2B2C549846804BBF3FD47E1237E18A6@xmb-aln-x02.cisco.com> <alpine.DEB.2.02.1311050329470.26054@uplift.swm.pp.se> <97EB7536A2B2C549846804BBF3FD47E1237E1941@xmb-aln-x02.cisco.com> <CAM+vMES=xhq7VF8SvqEZEz3ZCRN8p1zWiabkNnU6ucKVya6KQQ@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303A137B3@UK30S005EXS06.EEAD.EEINT.CO.UK> <20131108172730.GM81676@Space.Net> <alpine.DEB.2.02.1311090926500.26054@uplift.swm.pp.se> <20131109132552.GQ81676@Space.Net> <6536E263028723489CCD5B6821D4B21303A157F2@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAM+vMET6mqVQOm4GVnfkvNEGYuVSvTBVnrPOgFvj86Kmx8rnfw@mail.gmail.com> <20131111145452.GF81676@Space.Net>
In-Reply-To: <20131111145452.GF81676@Space.Net>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
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: Thu, 14 Nov 2013 06:45:44 -0000

Gert,

this needs to be resolved in the provider's network by applying DNS64 only to those UE that have an IPv6-only connection. Usually, IPv6-only connectivity means a separate APN with a dedicated IPv6 pool, so either IPv4 and IPv4v6 UE get a different DNS server than the IPv6-only UE, or the DNS server is the same and it can deduce from the client's IPv6 address whether it's an IPv4v6 or and IPv6-only client.

Holger

-----Ursprüngliche Nachricht-----
Von: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] Im Auftrag von Gert Doering
Gesendet: Montag, 11. November 2013 15:55
An: GangChen
Cc: v6ops@ietf.org
Betreff: Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt

Hi,

On Mon, Nov 11, 2013 at 10:46:42PM +0800, GangChen wrote:
> It doesn't expect that dual-stack UEs go to NAT64, because IPv4 native 
> connections are preferred over  IPv6+NAT64

How does the UE know that a target can be reached by native IPv4 if
DNS64 tells it "there is IPv6 for you" and IPv6 is preferred to IPv4?

Gert Doering
        -- NetMaster
--
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279