Problems with removing NAT from a network

Thu Jan 6 09:00:04 UTC 2011

In message <AANLkTik47D9ur2xTJTzhG3_izEq3oRK90ecVzkOtHY8k at mail.gmail.com>, Came
ron Byrne writes:
> On Wed, Jan 5, 2011 at 9:55 PM, Mark Andrews <marka at isc.org> wrote:
> >
> > In message <AANLkTikS_EnACm2BfYx=3DB=3DM=3DkhejAqJKvdbwX2hwmqHh at mail.gmai=
> l.com>, Came
> > ron Byrne writes:
> >> As long as dual-stack is around, the app vendors don't have to move
> >> and network guys have to dream up hacks to support these legacy apps
> >> (CGN ....).
> >
> > NAT64 is CGN expecially when it is being implemented by the cellular
> > carriers.
> >
> 
> Agreed.  And, the NAT44 that 99% of my customer use to today is also a CGN.
> 
> It's status quo, all v4 flows require state in my network, NAT44 or NAT64.
> 
> But, NAT64 has an exit strategy.  With every new AAAA that comes out,
> that is one less destination requiring state in my network.

I will give you that it is easy to see with NAT64 when the target
space has moved.  It also forces you to upgrade all client applications
to support IPv6 from the start.

Anyway its horses for courses.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org