[183311] in North American Network Operators' Group
Re: Production-scale NAT64
daemon@ATHENA.MIT.EDU (Mark Tinka)
Thu Aug 27 00:38:05 2015
X-Original-To: nanog@nanog.org
To: Jared Mauch <jared@puck.Nether.net>
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Thu, 27 Aug 2015 06:37:51 +0200
In-Reply-To: <20150827012114.GA15533@puck.nether.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 27/Aug/15 03:21, Jared Mauch wrote:
>
> Sure...
>
> For DS, I could send IPv6 native and IPv4 via NAT. I suspect this
> actually the most common home setup at this point. It's certainly the
> way mine looks.
>
> I have noticed that IPv4 "feels" slow on my t-mobile usa connected
> devices. This is only a problem when interacting with legacy players on the
> network, eg: financials, opensrs, airlines. I suspect this is a 64 CGN tax.
>
> Waiting to see my other devices/sims see IPv6 on them via VZ and AT&T.
If your IPv4 is public, you should not "feel slow". Of course, if your
IPv4 is private, then yes, some NAT44 may happen somewhere along the path.
> Sure, but your v4 is likely to have issues regardless and face this
> penalty/tax.
But that would be a function of NAT44 if you're on private IPv4, and
have nothing to do with the NAT64.
In our deployment, we do not offer customers private IPv4 addresses. I
suppose we can afford to do this because a) we still have lots of public
IPv4, b) we are not a mobile carrier. So any of our customers with IPv4
will never hit the NAT64 gateway.
When we do run out of public IPv4 addresses (and cannot get anymore from
AFRINIC), all new customers will be assigned IPv6 addresses. These will
hit a NAT64 gateway if they want to talk to legacy resources on the
Internet.
Mark.
