Hi Tony;

Best practice is that Customers who wish to retain Ipv6 range persistence through an ISP change (and don't want to get their own AS and assignment0 number their internal networks using ULA IPv6 address blocks.

-Joel


On 2 October 2013 18:27, Tony Wicks <tony@wicks.co.nz> wrote:

Yeah that's not what I'm saying though - the point I was trying to make
is that you can switch on v6 now and it works great.

We're not going to solve the "we have no more v4 address space" problem
by putting it off indefinitely.

(Also, "v6-only" hosts work pretty well. I've got a few - they can
still access Debian repos, run torrents, get on IRC, chat with XMPP,
access Google, Facebook and Youtube. Application layer proxies or NAT444
do a good job with the rest.)


On this Topic and on my list of things to do, here is a question for the other network operators on this list. As we are well aware there is no NAT with V4 (to all intents and purposes). With IPv4 it is very easy for us to assign the bulk of the customers a single out of a pool and the internal NAT IP range is the customers business. With IPv6 the service provider provides a /48 or /52 or whatever seems good for the customers internal network. Now, if this internal network is assigned out of a pool and the router disconnects and a new network is assigned does this cause a problem ? Or should we be statically assigning this ip block for the customers internal network ?

cheers

_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog