So going back to the original question really, which was multiple LIR accounts..
This has diverged into how/why people are taking them and that is that people
want to abuse the rules around limited remaining IPv4 resources set aside
for new entrants.
So we can disincentivise through cost, admin and technical approaches.
1. Time delay before a new LIR can be merged with another, 12 months?
This seems a reasonable option, why would anyone create a brand new
LIR and then want to merge it <12 months.
2. Make additional fees for multiple LIRs under one organisation, if you
want it fine, but pay for the additional admin burden.
3. Additional fees for six months once an LIR is merged. May seem
drastic but if people are abusing current rules then you have to combat
them.
4. If an LIR is opened it has AS and IP4/6, there should be some kind of
rule about this IP space having been visible through that AS number before
a merger is permitted. I am thinking about creating technical admin burden
for people creating many LIRs, so that they will have to go through the
technical hassle of setting up configurations before doing a merger,
ie. even if you are willing to pay extra fees to open 10x LIR to get
space then also be prepared to set up 10x BGP configs for it.
Not completely related to the original point, but if you want to reduce
motivation for people to still rely on IPv4 straight off then:
5. New LIR opens and is issued with IPv6 space immediately, then and only
once that IPv6 space is up and visible in routing tables can you apply for
your IPv4 space for that LIR. If you are not ready to run IPv6 at LIR opening,
will you ever be?
Just throwing out some ideas, may not be perfect of course..
Regards,
Paul.