If you insist on prefix-length filtering I have proposed a soloution
for future address space allocated via the RIPE NCC several times:
- set your inbound prefix length filter to /19.
- The RIPE NCC will *guarantee* that we will not make more than
1024 non-aggregateable allocations from each /8.
Would the RIPE NCC provide such non-aggregatable allocations
irrespective of how many hosts would be covered by such an
Yakov Rekhter <firstname.lastname@example.org> writes:
> > - The RIPE NCC will *guarantee* that we will not make more than
> > 1024 non-aggregateable allocations from each /8.
> Would the RIPE NCC provide such non-aggregatable allocations
> irrespective of how many hosts would be covered by such an
> allocation ?
Sorry, lack of clarity because of failing neurons.
What I meant to say was "1024 CIDRable allocations".
Or simply "allocations".
The point is that we will guarantee that our allocation policy will
create no more than 1024 allocations per /8 and therefore not
necessitate by itself more routes than that. Currently our allocation
sizes are /19 - /16. If you think about it a little you will see that
it is easy to achieve.
And just in case: Yes the minimum allocation is /19 irrespective
of the number of hosts covered. Note: allocation != assignment.