Point taken. Note that I am suggesting this goes a bit further than just filters that match registry allocation boundaries. I would suggest that the 'recommendation' could address all the things that often crop up in prefix filters - RFC1918 blocks - A class space now being allocated as /19 or /20 - 0.0.0.0 - TWD - sub /24 masks ...and so on. It is also worth noting that RIPE-210 is a 'recommendation'. Would your concerns also apply to this? Phil At 03:21 27.06.00 -0700, Randy Bush wrote:
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.
in my culture, due to legal considerations to do with things like restraint of trade, you would have to be extremely careful to phrase it NOT as 'recommendations' but maybe as "if you for some reason wanted to create filters to match rir allocation boundaries, this is what they would look like for vendors x, y, and z." i.e. technical coding advice, not filtering policy recommendations.
randy
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>