[72315] in North American Network Operators' Group

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

RE: concern over public peering points [WAS: Peering point speed publicly available?]

daemon@ATHENA.MIT.EDU (Mark Borchers)
Tue Jul 6 11:37:42 2004

From: "Mark Borchers" <mborchers@igillc.com>
To: "'vijay gill'" <vgill@vijaygill.com>, <nanog@merit.edu>
Date: Tue, 6 Jul 2004 10:31:26 -0500
In-Reply-To: <175D4A0638C54501AEC61C76@vjp5k>
Errors-To: owner-nanog-outgoing@merit.edu


> Thanks. Precisely the issue. Being humans involved in this, there is a
> tendency to sometimes hack around a problem and then leave it in
> place. I know I am susceptible to this and have to be on guard against
> this mentality at all times. And I've seen plenty of this in 
> various orgs.
> The key here is to maintain an engineering discipline and be 
> on constant
> guard against 'just this once' kind of thought. There should be no 
> negotiations
> with yourself.
> 
> Even the best of intentions lead to massive entropy when 
> doing hacks around 
> issues.
> 
> Temporary fixes aren't.
> 
> /vijay

Setting aside the issue of abandoning media after you stop
using it, a cable run based on a handshake between two tenants
in a telco hotel CAN lead to nightmares when it goes down.  
On the other hand, if you figure out a way to document it, and
have field support lined up, it may turn out to be more easily
restored than an "official" interconnect.  :-)



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