Re: Out of Date Bogon Prefix

* Heather Schiller · * Wed Aug 06 16:13:45 2008

Nick,
 You might want to take a closer look at who is really bogon filtering
you. Emailing their upstream providers may not be the most effective
method for getting endsites to update their bogon filters. They don't
have to listen to us when we forward your note on. We can't force them
to accept traffic from you or update their filters. As someone else
pointed out, directly contacting the folks who are filtering you may be
time consuming but typically draws the best results.
 I agree with the other comments that if you are going to use a form
letter please provide more details about the IP's you are using and your
ASN. Please also pass this on to your colleagues Eric and Kevin, who
I've heard from lately :)
 --Heather
~*~*~*~*~*~*~*~*~*~*~*~
 Heather Schiller
 Customer Security
 IP Address Management
 1.800.900.0241
~*~*~*~*~*~*~*~*~*~*~*~
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
exists on older Bogon lists many web providers are currently using.

A Bogon prefix is a route that should never appear in the Internet routing

table. A packet routed 
over the public Internet (not including over VPN or other tunnels) should
never have a source
address in a Bogon range. These are commonly found as the source addresses
of DDoS attacks.

The IP scope referenced is a 173.x.x.x. This IP scope was on the Bogon list

and was blocked by all 
websites using a Bogon prefix up until February of 2008, when it was

released by IANA (Internet 
Assigned Numbers Authority) for public use and an updated Bogon prefix was
provided. Mediacom
customers that are within this IP range are not able to reach a website

hosted by many organizations. 

Mediacom is individually requesting that these providers update their Bogon
prefix to the most current version
to resolve this issue immediately. We are requesting assistance from this

community to make this issue known

and to advise administrators to update to the most current Bogon list.

We have provided some reference material that many may find helpful in

resolving this issue.
Bogons are defined as Martians (private and reserved addresses defined by

<http://www.ietf.org/rfc/rfc1918.txt> RFC 1918 <

<http://www.faqs.org/rfcs/rfc1918.html>

http://www.faqs.org/rfcs/rfc1918.html> and

<http://www.ietf.org/rfc/rfc3330.txt> RFC 3330 <

<http://www.faqs.org/rfcs/rfc3330.html>

http://www.faqs.org/rfcs/rfc3330.html>) and netblocks that have not been

allocated to a regional internet registry (RIR) by the Internet Assigned

Numbers Authority < <http://www.iana.org/> http://www.iana.org/>. IANA

maintains a convenient IPv4 summary page <

<http://www.iana.org/assignments/ipv4-address-space>

http://www.iana.org/assignments/ipv4-address-space> listing allocated and

reserved netblocks.

Please help to spread the word.

Nick Downey

Director

Network Operations Center

Mediacom Communications

Main (800)308-6715

Secondary (515)267-1167

[email protected]

============================================================================

================================================================

LEGAL DISCLAIMER

============================================================================

================================================================
This E-mail and any attachments are strictly confidential and intended

solely for the addressee. You must not disclose, forward or copy this E-mail

or attachments to any third party without the prior consent of the sender or

Mediacom Communications Corporation. If you are not the intended addressee

please notify the sender by return E-mail and delete this E-mail and its

attachments.

============================================================================

================================================================