Welcome to WebmasterWorld Guest from 22.214.171.124
ICANN today announced that in response to a request for proposals (RFP), it has received five applications to operate the .NET Top-Level Domain for a term no less than six years.
The proposals are from, Afilias Limited, CORE++, DENIC Domain Verwaltungs, Sentan Registry Services, Inc., and the current holder, VeriSign, Inc.
Apparently, a decision is due in March.
To save you the trouble, here's what bothers me:
VeriSign is now working with Bruce Tonkin, one of the Registrar Constituency's representatives to the GNSO Council, to facilitate the process of developing a solution for an industry-wide com/net deleted names handling process, which facilitates an open auction during the pending delete period.
In January 2005, VeriSign will begin surveying end users in the Internet community to get input on various types of auction house solutions and price sensitivity for deleted name auctions. VeriSign anticipates providing the feedback received from end users, along with a revised deleted names proposed auction model in February 2005. The proposed model will be further vetted with registrars and other stakeholders to ensure that it adequately addresses the needs of registrars, registrants, and other impacted parties.
This sounds frighteningly like the self-serving crap put out by some large corporations and governments.
I put 20 years of honest research into my work, now on a website with a .net domain name.
I demand clear assurances that this domain will not be affected adversely.
I want this in clear, simple language, and in readably large print. -Larry
[edited by: tedster at 5:06 pm (utc) on Jan. 22, 2005]
My site is a .net My registrar is Verisign dba NetworkSolutions.
VeriSign sold over 85% of its stake in NetSol to another group. From what I gather, NetSol's
enjoying it's almost newfound independence to the hilt.
What happens to my long-term registry (expires 2006) if somebody else takes over .net?
Note that it's the authoritative records for .net that's being bid on, so ideally it won't affect
your domain name registration necessarily.
Just remember the .org registry migration from VeriSign to PIR. That'll give you an idea, but
there was practically little to no problems.