Re: Out of Date Bogon Prefix

[Jeroen Massar <jeroen () unfix org>]

Nick Downey wrote:
> This is an heads-up from the Mediacom Network Operations Center about an
> issue we are seeing. We             
>
> were recently given an IP scope from ARIN (American Registry for Internet
> Numbers) that still
[..]

Please fix your mailer as it seems to be broken with respect to 
line-breaks and that makes reading very annoying.

> The IP scope referenced is a 173.x.x.x. This IP scope was on the Bogon list
> and was blocked by all  

If you really want the block you have to be debogonized it would be 
handy if you:
 - provide the full prefix, including prefix length, and not just x.x.x
 - reference to the whois entry
 - the ASN you are announcing this from
 - an IP address in that prefix that replies to at least ICMP echo
   requests with an ICMP echo response so that people can check for
   you if they can reach it.

The people who care about these things would love to help you, but 
without proper information (173.0.0.0/8 is pretty big you know), that is 
very impossible, and why would they spend time on resolving your problem 
if you don't take the nice steps to provide proper information?

Please also do some work on your side, and read up on: 
http://www.ris.ripe.net/debogon/

Greets,
 Jeroen

PS: Most people here know what ARIN is and they also know what bogon 
routes are, repeating those terms is not very clueful ;)

Attachment: signature.asc
Description: OpenPGP digital signature