Michael,
Here's a decision table for you:
1. Do you need addresses that are routable from the global
Internet, from anywhere?
(Its not clear to me that you do, because you only need to
do that within your own network and a couple of well
known external sites perhaps.)
a. If not, maybe you should look at ULAs. RFC 4193 allows
you to get these addresses randomly, and you do not
need to ask permission from anyone to do it. You could
have your addresses today if you wanted to.
b. Proposals have been floated about non-random ULAs
as well. Right now we do not have one, but I'm not
sure you need this for your particular case.
2. If you do need addresses that are routable, is it
sufficient for you to work with provider-aggregated
addresses that you get from your ISP (not from ARIN)?
If yes, get the addresses and use them!
3. If you do need addresses that are routable AND
you have multiple ISP connections and want to stay
away from an address renumbering if you need
to change ISPs, then you need PI. You are starting
to get PI space, but as numerous PI items in the
global routing table cause pain for routers, this
will likely be available only for larger enterprises.
There is ongoing work to try to design a better
routing system that would be capable of keeping
tens of millions of prefixes or more, in the IRTF.
If and when that work succeeds, it would be possible
to allocate everyone their own PI prefix. We are
not there yet.
In any case, FWIW, I think it would make sense for RIR
address allocation rules to allow IPv6-only operations
and not just those that need both IPv4 and IPv6 address
space.
Jari
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
