Re: Good Timing for .COM Problems ?

[Matthew Crosby <mcrosby () ms com>]

Jim Fleming wrote:
> People might want to look on the bright side
> of the recent failure by Network Solutions, Inc.
> to properly distribute the .COM zone information.
>
> This failure will likely make it clear that .COM, .NET
> and .ORG should be moved to a collection of private, NSI,
> TLD Name Servers and off of the legacy Root Name
> Servers operated by the U.S. Government and a few
> volunteers.
>
> The failure comes at a time when the NSF has made
> it clear that they are slipping out the back door of the
> "Registry Industry", at a time when Network Solutions,
> Inc. has recently relocated domain registration personnel
> to a new building, and at a time when Network Solutions, Inc.
> is raising more capital via an IPO and making it clear
> that they intend to continue registering .COM domains.
> <http://www.netsol.com>
>
> The timing could not be better for this "failure". The
> solution is clearly for NSI to harden the .COM, .NET
> and .ORG TLD servers with their own infrastructure.
>
> The various Root Name Server Confederations around
> the world have little choice but to point .COM, .NET
> and .ORG references to the NSI servers (currently
> the legacy roots). Until other States besides Virginia
> or other countries set up their own .COM servers, this
> will be the case and NSI will have what some people
> view as a "monopoly".

Let me see if I understand this logic.

_NSI_ screws up.  This proves that the volunteer and govt TLD name servers 
can't do their job, and that _NSI_ should do their job. 

Hmm.