| At Large Membership and Civil Society Participation in ICANN |
|
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
Site Finder: Here We Go Again?
|
Log in/Create an Account
| Top
| 11 comments
|
Search Discussion
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
Let's do the math: ...the company might relaunch its "Site Finder" service as early as April. ~Stratton Sclavos, VeriSign CEO That was to investors last month so that presumably doesn't count as notice, nor does the current news article, but: VeriSign assured ICANN that it would give 60 to 90 days' warning to resolve any remaining technological problems. ~John Jeffrey, ICANN General Counsel Apart from the implication that they're leaving it up to ICANN to resolve remaining technological problems (a rather curious position), it is now Feb. 9/10 depending where you are, so they could easily give notice and go live again in April. Yikes!With ICANN now under fire from both the US Congress and some foreign governments, in addition to their usual legion of critics, perhaps VeriSign feels it is safely time to pile on. That is if VeriSign doesn't wait for the ICANN Security and Stability Advisory Committee, and VeriSign may be growing impatient, the SECSAC home page [icann.org], dealing prominently with Site Finder, hasn't been updated at all in the last four months (how quick would these folks be given a serious security/stability crisis?). And that's assuming VeriSign hasn't already given such notice to ICANN. We, of course, cannot expect prompt disclosure. -g
|
|
|
[ Reply to This | Parent
]
|
|
|
 |
This announcement finally got me to upgrade my BIND server to one with the delegation-only patch.
|
|
|
[ Reply to This | Parent
]
|
|
|
 |
It's worth noting that as recently as seven or eight days ago, the DNS entry in the "verisign.com" zone file for "sitefinder.verisign.com" still existed. The SiteFinder Web page also was up, several months after VeriSign removed the wildcard from the root.
As of today though, that DNS entry has been removed, and presumably, so has the Web site content for SiteFinder. It begs the question, why would VeriSign choose to shut down the SiteFinder website completely this week?
To be quite honest, I don't see VeriSign reviving SiteFinder, at least not until it gets permission, in writing, from ICANN. ICANN most likely won't give that permission until SECSAC issues its final report and the ICANN Board adopts the policy recommendations of SECSAC.
Remember, isn't NET up for redelegation this year? If VeriSign were to unilaterally revive SiteFinder simply by serving ICANN 60 days notice, it would pretty much seal its fate that it would not win the right to continue as the registry operator for dot-net. :)
Some thoughts, Doug Doug Mehus
http://doug.mehus.info/ [mehus.info]
|
|
|
[ Reply to This | Parent
]
|
| |
|
 |
My take is that the fate of sitefinder may well be decided by the courts. For example the following case by the Rothken Law Firm and Locks Law Firm as attorneys for plaintiffs.
Sitefinder Litigation [techfirm.com]
|
|
|
[ Reply to This | Parent
]
|
|
|
 |
Does anyone know if there were audit requirments to verify the $200,000,000 verisign was supposed to spend on infrastucture and universal WHois back when the 2001 agreements were signed.
|
|
|
[ Reply to This | Parent
]
|
| |

Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|