Hi Sander, On 10/7/13 1:18 AM, Sander Steffann wrote:
Hi,
RIPE NCC reserves a /29 for every /32 allocation, right?
No, they don't. It used to be like that a long time ago, but these days it is just sparse allocation. The change was announced at RIPE-61 (http://ripe61.ripe.net/presentations/331-Update_RIPE_NCC_R61.pdf) which was in November 2010.
I think they still reserve 3 bits, even with the sparse allocation algorithm.
However: the current policy for IPv6 PI assignments specifies "Assignments will be made from a separate 'designated block' to facilitate filtering practices.". Is that worth keeping?
As Gert also mentioned, I think that all 'special cases' allocations should still be made from a designated block. I am not sure if we should also request the RIPE NCC to make the /32s to the organisations (previously known as PI users) from a designated block. I do not see what the advantage would be. The organisations chosing to request a /48 allocation (instead of the /32) would not be any different than the ones actually getting the /32. So, I do not think these /48s should be made from different blocks either. I do agree that the allocations made for special purposes should still be made from a separate 'designated block'. And the current proposal states that. cheers, elvis