Gary T. Giesen <[email protected]> wrote: > That's obviously a consideration but I don't want to build an IPv6 > adoption model for my customers around something quite so fuzzy where > one customer could be approved and another be denied. I prefer > something a little more concrete that I can point a customer to an say > "apply under this" and it's plain to them (and ARIN) that they qualify.
I completely hear you. I've argued repeatedly (back to 2007) that this BS about routing slots is onsense, and that these kinds of policies are preventing adoption of IPv6 by small and middle sized enterprises. It's just not ARIN's job to protect routing slots. I'm not clear if the resulting /40 will be announced at all. If it will remain internal with IPVPN, and then, with a PI prefix from each *local* ISP, then you have the classic Non-Connected Network. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] [email protected] http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
