[40553] in North American Network Operators' Group

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

Re: AS2548... Do you care?

daemon@ATHENA.MIT.EDU (Christopher Johnston)
Sun Aug 12 13:24:25 2001

Date: Sun, 12 Aug 2001 13:23:46 -0400
From: Christopher Johnston <cjohnston@intermedia.com>
To: John Fraizer <nanog@Overkill.EnterZone.Net>,
	Alex Rubenstein <alex@nac.net>, nanog@nanog.org
Message-ID: <20010812132346.B1926@digex.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.21.0108120257550.24222-100000@Overkill.EnterZone.Net>; from nanog@Overkill.EnterZone.Net on Sun, Aug 12, 2001 at 03:15:58AM -0400
Errors-To: owner-nanog-outgoing@merit.edu


On Sun, Aug 12 2001 at 03:15:58%P -0400, John Fraizer wrote:
> 
> 
> On Sun, 12 Aug 2001, Alex Rubenstein wrote:
> 
> > 
> > This may sound odd, coming from me who is a halfway alarmist, but:
> > 
> > 1) how is this really a 'problem'? Don't get me wrong, announcing a
> > reserved AS is as bad as announcing 10/8, but, what did it break? Is it
> > enough of a problem to spam nanog about it?
> 
> > 
> > 2) Did you call/email/page/carrier-pidgeon Digex/ICI about this?
> 
> 1) I don't consider my post SPAM or fluf or anything else other than
> operational content.  A well known and respected carrier is announcing a
> reserved AS.  It didn't break anything here but, the announcement wouldn't
> make it into anyones tables who was using 64620 in a confederation and as 
> a result, it very well could be breaking something somewhere.  Beyond
> that, it doesn't set a very good example for others.  I guess I'll have to
> rethink my "lower AS = higher clue" theory.
>
> 2) It's not what it broke but, what's broken that is allowing it to happen
> to begin with.  It's fairly apparent that someone neglected to add 64620
> to a confederation statement. (And doesn't have anything in place to
> prevent leaking reserved AS's either.)

This has nothing to do with confederations. This was a misconfigured peer
that was a mistake anyone could have made. It was fixed and hopefully nobody
was hurt to badly by this error.

> 
> 3) No.  I did not contact Digex/ICI directly because:
> 
> a) I'm not a direct customer.
> b) I'm not a direct peer.
> c) The leak has shown up in the IPMA (http://www.merit.edu/ipma/)listings
> for the past 4 days and it's obvious that they're not monitoring IPMA or
> don't care.

I assure you we do care and we do try to keep up on the merit pages but
things can get hectic and things can get missed. I thank you for the
heads-up post that did in-fact lead to the problem solved. I frown upon
the technical speculation and the name bashing.

> 
> ---
> John Fraizer
> EnterZone, Inc
> 

----
Christopher Johnston - cjohnston@intermedia.com
Manager, Tier III & Network Operations 
Intermedia Business Internet
24-hour Support 888-297-1400


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