[106567] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Out of Date Bogon Prefix

daemon@ATHENA.MIT.EDU (Jeroen Massar)
Tue Aug 5 13:37:25 2008

Date: Tue, 05 Aug 2008 19:37:20 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: Nick Downey <ndowney@mediacomcc.com>
In-Reply-To: <00ae01c8f71f$0f397610$d135190a@mediacomcorp.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF683F2144DF66D616FB7FA8A
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

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

Please fix your mailer as it seems to be broken with respect to=20
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 =20

If you really want the block you have to be debogonized it would be=20
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=20
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:=20
http://www.ris.ripe.net/debogon/

Greets,
  Jeroen

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


--------------enigF683F2144DF66D616FB7FA8A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFImI/QKaooUjM+fCMRAkp/AJ4wHq8kbAple0G2lzVouLkJfUVKiQCcDX73
kTLQ0UQemuMxBzoRya67hCE=
=IMHC
-----END PGP SIGNATURE-----

--------------enigF683F2144DF66D616FB7FA8A--


home help back first fref pref prev next nref lref last post