Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
"Heatley, Nick" <nick.heatley@ee.co.uk> Mon, 11 November 2013 08:24 UTC
Return-Path: <nick.heatley@ee.co.uk>
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 3A1A921E81A3 for <v6ops@ietfa.amsl.com>; Mon, 11 Nov 2013 00:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level:
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, 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 ty8QseMDn45Q for <v6ops@ietfa.amsl.com>; Mon, 11 Nov 2013 00:24:14 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id C778F21E813F for <v6ops@ietf.org>; Mon, 11 Nov 2013 00:24:12 -0800 (PST)
Received: from [85.158.139.3:13663] by server-3.bemta-5.messagelabs.com id 14/C5-08905-B2490825; Mon, 11 Nov 2013 08:24:11 +0000
X-Env-Sender: nick.heatley@ee.co.uk
X-Msg-Ref: server-15.tower-90.messagelabs.com!1384158251!822698!1
X-Originating-IP: [193.36.79.211]
X-StarScan-Received:
X-StarScan-Version: 6.9.13; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9383 invoked from network); 11 Nov 2013 08:24:11 -0000
Received: from unknown (HELO autechre) (193.36.79.211) by server-15.tower-90.messagelabs.com with SMTP; 11 Nov 2013 08:24:11 -0000
Received: from UK30S005EXS02.EEAD.EEINT.CO.UK (Not Verified[10.246.208.14]) by autechre with MailMarshal (v6, 8, 2, 9371) id <B528095d90000>; Mon, 11 Nov 2013 08:31:21 +0000
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK30S005EXS02.EEAD.EEINT.CO.UK ([2002:62c:2a4f::62c:2a4f]) with mapi id 14.02.0318.004; Mon, 11 Nov 2013 08:24:10 +0000
From: "Heatley, Nick" <nick.heatley@ee.co.uk>
To: Gert Doering <gert@space.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
Thread-Index: AQHOyHB1/aS13ASbK0O9Jy+4NHt/ApoWDEUAgAAA1wCAAASNgIAAB+OAgAVLKMCAAFoFAIAA+3cAgABTXICAAs0ZMA==
Date: Mon, 11 Nov 2013 08:24:10 +0000
Message-ID: <6536E263028723489CCD5B6821D4B21303A157F2@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <20131013235941.31896.30276.idtracker@ietfa.amsl.com> <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>
In-Reply-To: <20131109132552.GQ81676@Space.Net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.246.208.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <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: Mon, 11 Nov 2013 08:24:20 -0000
Agree, the questions seem only relevant to the mobile use case (with a normal baseline of IPv4 privates + NAT44). Hopefully you can see that the questions are valid now. I seek arguments why, in an access network dominated by NAT why to prefer one flavour over another? - other than pushing my NAT vendor to achieve parity NAT64 <--> NAT44 (they claim both translations are in hardware). If NAT64 is good enough for IPv6-only clients its good enough for Dual Stack NAT? Nick -----Original Message----- From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering Sent: 09 November 2013 13:26 To: Mikael Abrahamsson Cc: v6ops@ietf.org Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt Hi, On Sat, Nov 09, 2013 at 09:27:32AM +0100, Mikael Abrahamsson wrote: > On Fri, 8 Nov 2013, Gert Doering wrote: > > > If you have NAT44 and native IPv6, I can't see why you would want to > > add > > DNS64+NAT64 to the mix. > > > > NAT64 is good when you do *not* want IPv4 at the customer edge. > > Mobile. You don't know if the client is v4 only, v6 only, or dual stack. > This is up to the client. Understood, and I see your issue here - you would want to announce a "normal" DNS server to a dual-stack client, not a DNS64 server, and you can't do that because you don't know whether he's v6 only or dual-stack. This is somewhat easier in other types of large-scale customer deployments, where you can control what the client can get - which will mostly be something like "NAT44+IPv6" for many subscribers for the time to come, so adding DNS64/NAT64 really does not have much benefit here. 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 NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. EE Limited Registered in England and Wales Company Registered Number: 02382161 Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Victor Kuarsingh
- [v6ops] I-D Action: draft-ietf-v6ops-nat64-experi… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Eric Vyncke (evyncke)
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Victor Kuarsingh
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Eric Vyncke (evyncke)
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… holger.metschulat
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Tim Chown
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Tim Chown
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Gert Doering
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Tim Chown
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Dan Wing
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… holger.metschulat
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Simon Perreault
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… Simon Perreault
- Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-ex… holger.metschulat