Out of Date Bogon Prefix

Nick Downey ndowney at mediacomcc.com
Tue Aug 5 13:32:18 CDT 2008


Thanks for the input.

Currently, we are receiving 173.16.x.x /19 and /18, with plans to get
additional IPs within the same range.

ASN 6478 or 7018 - Through AT&T

You can test access to this network by ping this gateway: 173.16.28.1

Whois information:

 173.16.28.1
Record Type: 	  	IP Address

OrgName:    Mediacom Communications Corp 
OrgID:      MCC-244
Address:    100 Crystal Run Rd.
City:       Middletown
StateProv:  NY
PostalCode: 10941
Country:    US

ReferralServer: rwhois://rwhois.mediacomcc.com:4321

NetRange:   173.16.0.0 - 173.17.31.255 
CIDR:       173.16.0.0/16, 173.17.0.0/19 
NetName:    MEDIACOM-RESIDENTIAL-CUST
NetHandle:  NET-173-16-0-0-1
Parent:     NET-173-0-0-0-0
NetType:    Direct Allocation
NameServer: NS1.MCHSI.COM
NameServer: NS2.MCHSI.COM
Comment:    
RegDate:    2008-05-19
Updated:    2008-07-29

OrgTechHandle: JSE90-ARIN
OrgTechName:   Selvage, Joe 
OrgTechPhone:  +1-845-695-2706
OrgTechEmail:  jselvage at mediacomcc.com




-----Original Message-----
From: Jeroen Massar [mailto:jeroen at unfix.org] 
Sent: Tuesday, August 05, 2008 12:37 PM
To: Nick Downey
Cc: nanog at nanog.org
Subject: Re: Out of Date Bogon Prefix

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 ;)






More information about the NANOG mailing list