|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical [no subject]
Hi Owen, This is exactly the service Team Cymru is currently offering with the bogon route-server project. Specific details and instructions on how to request access can be found at the following URL: http://www.cymru.com/BGP/bogon-rs.html In a nutshell, this is a reliable and secure method of ensuring your bogon routes are kept up-to-date. Changes to the bogon route-server are validated by at least two other individuals. Team Cymru validate all changes to the bogon lists and supporting documents prior to implementation of such changes. That said, bogons are updated almost immediately and at no cost to you. This is a *FREE* offering, as such there are NO guarantees or SLAs. The current list of 15 peers have been quite pleased with the reliability and service. We are also working on adding redundant bogon route-servers in the very near future. If anyone is willing to donate gear or bandwidth to the cause, please don�t hesitate to contact us. As always, the master bogon reference page can be found here: http://www.cymru.com/Bogons/index.html Feel free to send any queries, suggestions, or concerns to the entire team at [email protected] Thanks! Steve, for Team Cymru. -- Stephen Gill [email protected] -----Original Message----- Date: Tue, 11 Mar 2003 08:48:07 -0800 From: Owen DeLong <[email protected]> Subject: RE: 69/8...this sucks -- Centralizing filtering.. � Thanks for your support Jim.� I've gotten mixed feedback to my proposal here for a centralized bogon filter from the RIRs via BGP, but I will say there's been more support than opposition.� (Most of the support has been sent to me, not the list, while most of the opposition has been to the list, however). � I know it's too late to get it into the Memphis meeting, but I think, based on the amount of support it has received, that I will submit a policy proposal to ARIN in support of creating the requisite BGP feeds.� I realize that an ARIN policy alone won't do this (the other RIRs would have to follow suit), but, if ARIN adopts it, I don't think it will be too hard to get the other RIRs to follow.� I'm also not familiar with the policy process in the other RIRs. � I absolutely agree with you about the whois contact stuff.� I think it might make sense eventually to put a similar requirement for current information on the admin and tech contact, although I don't see putting the same response and performance strictures on them.� For now, I'm trying to address large issues in small enogh pieces to get rough consensus around the solution to each small piece.� Trying to solve the big problems all at once never seems to achieve rough consensus. � Owen
|