Assuming you can't get enough ipv4 addresses to do option 4 for whatever reason (which is the best option, really), I would probably say the best way to go is CGN plus IPv6 dual stack.
On Wed, Oct 26, 2016 at 3:12 PM, Eric Kuhnke <[email protected]> wrote: > None of the above, unless a ridiculous number of ipv4 addresses are > required, I'd find the money to acquire a sufficient number of ipv4 /24s > (preferably in pieces like /22) through the official ARIN transfer process > and consider the per-customer IP cost paid as an NRC for the transfer as > part of the network build cost. > > Option 4) one ipv4 per customer and ipv6 dual stack > > > > On Wed, Oct 26, 2016 at 1:05 PM, Sam Morris <[email protected]> wrote: > >> If you were starting a new network from scratch, how would you do your IP >> addressing? >> >> Option 1) ipv6 - Doesn't appear that everything on the Internet supports >> pure v6, which would require... >> >> Option 2) ipv6 with NAT64 or dual stack (or whatever would be a patch to >> make Option 1 work)... or >> >> Option 3) ipv4 with private IP addresses and a single public v4 address >> at the edges (and use CGN for the calea stuff - CGN which evidently comes >> with its own set of problems...) >> >> Or is there a better option that I'm not thinking about? >> >> Deciding among these seems like picking which presidential candidate to >> vote for - They all stink, and trying to decide which one stinks the >> least... >> >> Thanks, >> Sam >> > >
