[33960] in North American Network Operators' Group
Re: MS explains
daemon@ATHENA.MIT.EDU (Greg A. Woods)
Thu Jan 25 15:30:03 2001
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: woods@weird.com (Greg A. Woods)
To: NANOG <nanog@nanog.org>
In-Reply-To: <20010125143020.1B9B135C42@smb.research.att.com>
Reply-To: nanog@merit.edu (North America Network Operators Group Mailing List)
Message-Id: <20010125202034.7B0FC5@proven.weird.com>
Date: Thu, 25 Jan 2001 15:20:34 -0500 (EST)
Errors-To: owner-nanog-outgoing@merit.edu
[ On Thursday, January 25, 2001 at 09:30:19 (-0500), Steven M. Bellovin wrote: ]
> Subject: Re: MS explains
>
> I'd love to see a detailed description of what went wrong, and I hope
> that those in the know will be allowed to post it or present it in
> Atlanta. But I'm willing to wager that it wasn't just (a) a single
> router configuration change, (b) brain-damage in Microsoft's DNS code,
> (c) malicious activity aimed at Microsoft, (d) RAMEN-induced
> misbehavior, or (e) any other single cause.
But there was a single root cause that made the problem possible in the
first place.... Analysis of the actual event will no doubt be
interesting to some, but for all their users out there on the Internet
all that matters is that proper deployment of their servers would have
never allowed the situation to occur in the first place.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
