Re: Policy Statement on Address Space Allocations

["Alex.Bligh" <amb () Xara NET>]

Daniel Karrenberg <Daniel.Karrenberg () ripe net> wrote:

> 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.
>
>   - The RIPE NCC will continue to work with the providers to 
>     maximise aggregation.  Our goal is a maximum of 1024 routes 
>     per /8 visible at major exchange points. Incidentally this 
>     is the same goal that you seem to have.

You are not distinguishing (initial) allocation from announcement.

Your guarantee is worthless in the sense that it only gurantees that
the announcements (as opposed to allocations) can be aggregated if
each window allocation is tied to a single AS, and thus, for instance that
none of the allocation is for PI space, or for allocation to customers
who aren't local-IRs but have their own AS etc. etc. You also have the problem
that currently it is impossible for local-IRs to allocate blocks
of IP numbers that wouldn't be filtered out to multihomed customers
(with their own AS - thus almost inevitably requiring a separate
announcement) where that customer under the RIPE rules isn't 'justified'
in getting a /19 (too small, for instance). Conservation vs. aggregation
again. What is your recommendation on this?

Alex Bligh
Xara Networks

PS: Here's Sprint's sister company's current announcement of routes
*originating* in its AS as I see them - I do hope Sprint takes the honest
path if it does refuse to carry short announcements and not route all bar
4 of these nets, as well as a similar long list from AS1239 :-) I'm
not convinced Sprint has the moral highground here....

    Network          Next Hop          Metric LocPrf Weight Path
*> 160.214.0.0      194.68.130.50                        0 4000 ?
*> 163.164.0.0      194.68.130.50                        0 4000 ?
*> 194.41.63.0      194.68.130.50                        0 4000 ?
*> 194.106.0.0/19   194.68.130.50                        0 4000 ?
*> 194.106.32.0     194.68.130.50                        0 4000 ?
*> 194.106.33.0     194.68.130.50                        0 4000 ?
*> 194.106.34.0     194.68.130.50                        0 4000 ?
*> 194.126.64.0/19  194.68.130.50                        0 4000 ?
*> 194.133.0.0/19   194.68.130.50                        0 4000 i
*> 194.133.4.0/23   194.68.130.50                        0 4000 ?
*> 194.133.6.0      194.68.130.50                        0 4000 ?
*> 194.133.7.0      194.68.130.50                        0 4000 ?
*> 194.133.8.0      194.68.130.50                        0 4000 ?
*> 194.133.15.0     194.68.130.50                        0 4000 ?
*> 194.133.24.0     194.68.130.50                        0 4000 ?
*> 194.133.28.0     194.68.130.50                        0 4000 ?
*> 194.140.128.0/19 194.68.130.50                        0 4000 ?
*> 194.140.224.0/21 194.68.130.50                        0 4000 ?
*> 194.149.192.0/18 194.68.130.50                        0 4000 ?
*> 194.158.0.0/20   194.68.130.50                        0 4000 ?
*> 194.176.96.0/19  194.68.130.50                        0 4000 ?
*> 194.204.96.0/23  194.68.130.50                        0 4000 ?
*> 196.27.0.0       194.68.130.50                        0 4000 ?
*> 196.27.1.0       194.68.130.50                        0 4000 ?
*> 198.169.26.0     194.68.130.50                        0 4000 ?
*> 204.59.0.0/16    194.68.130.50                        0 4000 i
*> 204.83.37.0      194.68.130.50                        0 4000 ?
*> 204.83.237.0     194.68.130.50                        0 4000 ?
*> 204.83.254.0     194.68.130.50                        0 4000 ?
*> 206.49.64.0/18   194.68.130.50                        0 4000 i
*> 206.49.65.0      194.68.130.50                        0 4000 ?