Slashdot Mirror

← Back to Stories (view on slashdot.org)

ICANN Gives VeriSign 36 Hours to Pull Sitefinder

Posted by michael on from the or-else-we'll-say-stop-again dept.

Froomkin writes "ICANN this morning announced that it sent VeriSign an ultimatum: pull sitefinder by tomorrow evening or we'll sue. Details and links to discussion of the contractual and legal issues in ICANN Throws Down the Gauntlet to VeriSign on Sitefinder at ICANNWatch." Update: 10/03 19:29 GMT by M : Verisign blinked.

6 of 449 comments (clear)

  1. Now we wait and see... by NivenHuH · · Score: 3, Interesting

    What will happen when VeriSign doesn't do anything tomorrow? Is this just another "scare tactic"?

    --
    Just when you make it idiotproof, some idiot builds a better idiot.
  2. Nice by ruiner13 · · Score: 5, Interesting
    "If VeriSign does not comply with this demand by 6:00 PM PDT on 4 October 2003, ICANN will be forced to take the steps necessary to enforce VeriSign's contractual obligations."

    I'd be interested to see what those obligations were. If it is as bad as that sounds, I wonder if VeriSign could lose their Registrar priviledges as a result. This could have huge implications, and could help small(er) registrars get a leg up (finally) in the .com and .net domains. I guess only time will tell.

    --

    today is spelling optional day.

  3. T-Shirts! Get your VeriSlime T-shirts here! by wayne · · Score: 3, Interesting
    I forget where I saw these, but someone is selling two versions of VeriSlime t-shirts:

    VeriSlime t-shirt "No Values to Trust"
    VeriSlime t-shirt "The Abuse of Trust"

    --
    SPF support for most open source mail servers can be found at libspf2.
  4. It's FRAUD by Anonymous Coward · · Score: 5, Interesting
    Anyone noticed what they're using to redirect people who go to www.sldkfjdsdlkfgjsdlkjf.com? They use an HTTP 302 code. Ever looked that up? http://www.w3.org/Protocols/rfc2616/rfc2616-sec10. html:
    10.3.3 302 Found

    The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.


    When you say HTTP/302, you're saying the resource they're looking for exists somewhere else, in this case sitefinder.verisign.com. That is a lie. It is a gigantic, automated lie perpetrated automatically on the entire world. It's a class action suit waiting to happen.

    wget www.ssdlfkjsdf.com
    --04:51:57-- http://www.ssdlfkjsdf.com/
    => `index.html'
    Resolving www.ssdlfkjsdf.com... done.
    Connecting to www.ssdlfkjsdf.com[64.94.110.11]:80... connected.
    HTTP request sent, awaiting response... 302 Found
    Location: http://sitefinder.verisign.com/lpc?url=www.ssdlfkj sdf.com&host=www.ssdlfkjsdf.com [following]

    LIARS
    It's fraud.
  5. Mabye, but... by StringBlade · · Score: 5, Interesting
    If you give ICANN the power to create and implement the law without the need to use lawsuits, then you're effectively loading the gun with which to shoot yourself in the foot!

    What happens when ICANN fully realizes this power and makes changes to the obligated behavior of TLDs and uses their power to force change that may not be in the best interest of everyone concerned (read: ISPs and end users).

    Of all the lawsuits flying around this year, this one is actually valid and should occur with extreme prejudice.

    --
    ...and that's the way the cookie crumbles.
  6. Verisign broke archive.org by Animats · · Score: 4, Interesting
    Archive.org will no longer return pages from sites whose domain is not assigned. The problem is that archive.org checks the current "robots.txt" file for the site, and will obey it. Verisign's tampering causes archive.org to read "http://sitefinder.verisign.com/robots.txt", which reads
    • User-agent: *

    • Disallow: /
    thus causing archive.org to reject all requests for old sites.