Ipv6 help

Mark Tinka mark.tinka at seacom.com
Thu Aug 27 08:47:15 UTC 2020



On 27/Aug/20 10:33, Brian Johnson wrote:

> Let’s say that we switch to a model of all NAT444 for IPv4, with an exception for paid static IPv4 customers and that rate is linked to the current going rate for an IP address on the market. :)
>
> This is easily doable with any of the access platforms and routing vendors I have worked with.

This is happening today. The problem isn't that it can't work. The
problem is that as the days trudge on, private IPv4 will be the only
option, even for customers willing to pay top $$ for one public IPv4
address. You can't sell what you don't have.

So then you have to move from NAT44 to NAT444 to NAT4444 to NAT44444,
just to keep recycling your private pool, and all the pleasure & joy
that avenue brings along with it.


> If I do dual-stack, but provide private IPv4 to the customer and NAT444 them, isn’t this accomplishing the same thing?

It is, but even if NAT works, it scales poorly and has inherent issues,
as we all know. In the end, to scale it, you go CGN, which can be 10's
of millions of $$/year with vendors if you are a large network (pretty
much, every mobile provider today that didn't follow Cameron's route).


> So for 464XLAT I will need to install a PLAT capable device(s)...

PLAT support has been around already with the traditional vendors. It's
not new.


>  as well as replace all CPE with CLAT capable devices ($$$$). I will also need to deal with the infancy period as I will GUARANTEE that the CPE will break badly and will create additional cost ($$$$).
>
> For NAT444 I just need to install NAT444 router(s) . No additional cost for CPE or added troubleshooting as the existing CPE is fully baked. Agreed that customers will need help with IPv6, but that will be required either way. Also, the customer maintains a native IPv4 service (all be it NATed) until IPv4 does the dodo dance. In the end, the provider turns-off the NAT444 and disables IPv4 on their core, which has already been enabled for IPv6 when deploying dual-stack.

Well, you need to run the numbers on time, support and acquisition of
new revenue if you maintain NAT44, while the rest of the world (and your
competitors) are going as native IPv6 as they can.

You need to consider if it's worth taking the risk of being left behind,
or not.

Either way, your customers will, at some point or other, show you what
will work :-).

For me, my time is very limited, particularly on this rock we call
earth. I could spend it maintaining a CGN, but I'd rather spend it
chasing down CPE vendors to get CLAT support, or bad-mouthing Sony to
get with the program. If I have to lose a few customers in the process,
so be it. If I run out of breath before I reach my goal, well, hopefully
the work done along the way will help the next idiot that sees things
the same way I do :-).

Mark.




More information about the NANOG mailing list