[140874] in North American Network Operators' Group
RE: Rogers Canada using 7.0.0.0/8 for internal address space
daemon@ATHENA.MIT.EDU (Leigh Porter)
Tue May 24 10:13:47 2011
From: Leigh Porter <leigh.porter@ukbroadband.com>
To: "byron@byronhicks.com" <byron@byronhicks.com>, Owen DeLong
<owen@delong.com>
Date: Tue, 24 May 2011 14:13:24 +0000
In-Reply-To: <4DDBBAF9.7010306@byronhicks.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> -----Original Message-----
> From: Byron L. Hicks [mailto:byron@byronhicks.com]
>=20
> I ran into this issue with a service provider that wanted to set up
> point of sale terminals on our campus. They were using DoD address
> space in their inside network, and they ordered ISDN connectivity from
> our site back to their network. The point of sale terminals were
> connected on our campus network. They wanted me to set a static route
> on my network backbone that pointed all of the hijacked DoD address
> space to this ISDN line. Of course, I told them no. The university I
> was working for at the time had some DoD contracts, and I was afraid
> that it might break legitimate traffic. Plus, I thought this was a
> really bad network design. The service provider was not very happy.
I see why they may do this. They have likely had issues with overlapping 1=
918=20
space in previous networks, so they thought "Oh, we'll nick this space, it=
's DoD
and nobody will ever use it..." and it's all fine, until somebody=20uses i=
t.
It's just a really lazy way of getting things done that is likely to come =
and bite
you sooner or later.
So you said NO, and what did they do about it ?
--
Leigh Porter
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email=20
______________________________________________________________________
