[33898] in North American Network Operators' Group
RE: Microsoft spokesperson blames ICANN
daemon@ATHENA.MIT.EDU (Roeland Meyer)
Thu Jan 25 00:17:11 2001
Message-ID: <9DC8BBAD4FF100408FC7D18D1F092286039B7D@condor.mhsc.com>
From: Roeland Meyer <rmeyer@mhsc.com>
To: "'Steven M. Bellovin'" <smb@research.att.com>,
Jim Duncan <jnduncan@cisco.com>
Cc: Sean Donelan <sean@donelan.com>, nanog@merit.edu
Date: Wed, 24 Jan 2001 20:39:46 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Errors-To: owner-nanog-outgoing@merit.edu
> Sorry, Jim; I think it's not that much of a stretch. They said that
> (a) it's a DNS problem, (b) they don't understand the cause, but (c)
> they don't manage the DNS, ICANN does. OK -- the problem is
> therefore
> in a piece they don't manage, so they're not at fault. But ICANN
> *does* manage it (or so the direct quote says). There's a decent
> implication there that the manager is at fault, though not
> (of course)
> a direct statement. I would also note that the article
> quotes De Jonge
> as saying "The *Internet's* Domain Name System (DNS) does
> does not return
> the correct response when it is queried for a Microsoft Web site"
> [emphasis added]. In other words, it's not *Microsoft's* DNS
> servers,
> it's the "Internet's".
You overlooked the prime facae error. ICANN most certainly does NOT manage
the DNS. The US Department of Commerce does. That's actually been proven in
court.
