RE: Where are static bogon filters appropriate? was: 96.2.0.0/16 Bogons

I think Sean raises a good point. I guess the larger picture is what are we trying to protect and what are trying to protect that from. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Donelan Sent: Friday, March 02, 2007 3:19 PM To: Roland Dobbins

Msn.com

Can someone from msn.com contact me offlist? Thanks! Eric Ortega Midcontinent Communications Network Engineer 605.357.5720 [EMAIL PROTECTED]

RE: 96.2.0.0/16 Bogons

I'd like to thank the group for the responses and help with this issue. I find it ironic that Randy's study actually uses 96 space. Thanks again! Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Ortega Sent: Monday, February 26, 2007 12:17 PM

96.2.0.0/16 Bogons

looking to hit as many direct network engineers/operators as possible. Would it be possible to have people do a quick check on their inbound filters? Thanks! Eric Ortega Midcontinent Communications Network Engineer 605.357.5720 [EMAIL PROTECTED]

RE: 96.2.0.0/16 Bogons

After I sent that mail I realized that I didn't give enough information. 96.2.0.1 is pingable from the net. Thank you all for your quick response! -Original Message- From: James Blessing [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 11:28 AM To: Eric Ortega Cc: nanog

Datapipe.net

Can someone from Datapipe.net contact me off list? Thanks, Eric Ortega Midcontinent Communications Network Engineer 605.357.5720 [EMAIL PROTECTED] -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.441 / Virus Database: 268.18.2/692 - Release