Joao,
Joao Luis Silva Damas wrote: My questions so far have not been trying to find a way of giving any RIR arguments to fight against the deployment of IPv6 or anything else in the Internet. If the RIRs ever become a stumbling block for the development of the Internet you might just as well get rid of them (us).
On the other hand, RIRs have a role to play in controlling practices that lead to problems in the long run, such as the v4 swamp.
Currently, the policy refers to the concept of "site" which has been left intentionally "fuzzy". That is OK as a starting point, to be refined later, as we (all) gain experience. In practice, this fuzziness will be translated into acceptance of any definition of "site" that a requester puts forward. And each site is entitled to a /48 as per the IAB's recommendation, which seems to be widely accepted.
I think there is a de-facto definition of site, though. - No subnetting = /64 - Some subnetting = using what was used to be called the SLA bits = site = /48.
And we get to the magical word: multihoming. Organisations which fear not having their addresses routed when they multihome might generate requests that ensure they get a /32. If conservation is not a problem, this should also not be a problem.
It actually is in the long run, and there is a balance to find here: Even if saving IPv6 addresses is not the goal, one must be careful in not creating monstruosities. A /48 is overkill already for most multihomers. Making it a /32 is a monstruosity. In order to eliminate the fuzziness you mentioned above, the policy needs to either: a) Allocate a /32 to everyone. b) Have clear rules if multihomers get a different size (which I do not recommend at this point in time).
In practice the current policy is equivalent to the one suggested in January: When you have plans to use IPv6, become an LIR if you aren't one already. The RIR will register the numbers.
Again, this is not a rant about the new policy, I actually support it in the lack of a better one. Nevertheless, in practice the new policy is equivalent to giving a /32 PI to multihomers, as cheating to fulfill a legitimate business need is done. We have seen increases in 6bone pTLA requests, and we will see requests for LIR allocations for the same reason: Get a global prefix that will be seen in the global routing table. We have done that in the past already: it's called the pre-CIDR swamp. Having everyone become a LIR can _NOT_ continue forever. There is a limited time we collectively have before we have to define a new policy.
If the RIRs ever become a stumbling block for the development of the Internet And we get to the magical word: multihoming.
If a multihoming solution is not deployed during this limited time I just mentioned, I hope that everyone understands what will be the next RIR policy in order not to become a stumbling block for the development of the Internet: "Give a /48 PI to anyone that wants one" The writing is on the wall. I renew my call to people with a brain in working order to join the effort in developing a v6 multihoming solution before it is too late. Michel.