Re: Production-scale NAT64

[Jared Mauch <jared () puck Nether net>]

On Wed, Aug 26, 2015 at 04:39:11PM +0200, Mark Tinka wrote:
> On 26/Aug/15 16:32, Jared Mauch wrote:
> > This for me is an important note, because if your site only gives out an A address,
> > it’s going to be slowed by the NAT process.  I have noticed the IPv4 penalty getting
> > worse with many locations.
>
> But you only need to hit the NAT64 gateway "if" you are IPv6-only.

        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 you're dual-stacked, your route to an A record will not hit the NAT64
> gateway.

        Sure, but your v4 is likely to have issues regardless and face this
penalty/tax.

        - Jared

-- 
Jared Mauch  | pgp key available via finger from jared () puck nether net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.