Seeing this mail, together with the cyclic discussions on NANOG about prefix filters and 'does anyone know if Provider X is filtering prefixes from block Y at mask Z' type problems, got me thinking that it might be a good idea for the RIPE community to come up with a set of recommendations for BGP prefix filters. It would have a number of advantages. - a standard prefix filter recommendation would always be in synch with Registry practices. - it would lower the effort barrier for people to implement prefix filtering in the first place, and therefore foster stability of the global routing system. - it would at least help to align the filtering practices of Providers a little bit, so that debugging routing problems becomes a little bit less like guesswork... hopefully fewer threads like 'does anyone know if Provider X is filtering prefixes from block Y at mask Z?' I am thinking of something broadly along the lines of RIPE-210 for route dampening. Feedback? Phil At 17:32 21.06.00 +0200, Joao Luis Silva Damas wrote:
During the RIPE 36 meeting in Budapest there was a request to publish the list of CIDR blocks allocated by the RIPE NCC and the smallest allocation issued from each of them.
This is it:
62/8: /19 193/8: /29 # Contain small PI assignments 194/8: /29 # Contain small PI assignments 195/8: /29 # Contain small PI assignments 212/8: /19 213/8: /19 217/8: /20
We shall put this information permanently on our website.
regards,
Joao Damas Head of External Services RIPE NCC
Philip Bridge Nextra (Schweiz) AG <www.nextra.ch> Tel: +41 031 985 88 06 / Mobile: +41 79 659 75 50 E-Mail: <mailto:bridge@nextra.ch> Disclaimer: <http://www.nextra.ch/signature_nw.html>