 |
 |
I have BGPmon set up to notify me of the MICE IXP blocks (IPv4 and IPv6) are being announce in BGP by any other AS that MICE itself. The current BPC is to not even put a route in your IGP for for an exchange block, let alone originate a BGP route for it. http://www.bgp4all.com.au/dokuwiki/_media/conferences/apnic42-ixp-design-bcp.pdf See slide 45. In the last 2 or 3 months I have seen three different participant ASNs originate routes for 206.108.255.0/24, haven't seen any for do it for 2001:504:27::0/48. I'm not going to name and shame, at least for past events. But, what should we do about this going forward? 1. Ignore it 2. Notify transgressors PRIVATELY 3. Manually, Name and Shame transgressors 4. Automated, Name and Shame of transgressors (setup a BGPmon account to mail to MICE-DISCUSS) 5. Other ideas? (electro-shock for transgressors :) ) Thanks -- =============================================== David Farmer Email:[log in to unmask] Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================