ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    VeriSign's SiteFinder & ICANN Contracts--A Second Opinion | Log in/Create an Account | Top | 23 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re:I like your suggestion
    by jimrutt on Monday September 29 2003, @08:26AM (#12324)
    User #3264 Info
    how is this "resolver contamination" any different different than that for a name that expires and goes back into inventory?

    If VRSN added a mention of such theoretical "contamination" to the user agreeement, would you then support Sitefinder? Somehow I doubt it.===================== been there, done that
    [ Reply to This | Parent ]
    Re:I like your suggestion by jimrutt
    Re:I like your suggestion
    by KarlAuerbach on Monday September 29 2003, @11:21AM (#12325)
    User #3243 Info | http://www.cavebear.com/
    The contamination is the same - however there is a difference in the knowledge of that contamination that we can impute to the person who acquires the name.

    A user who acquires a name hot from a previous user(i.e. via a snapback or wait-list service) is more likely to be considered as knowing that there are residual affects.

    But someone who comes along to the Verisign registrar's web page that says "this name is available, wanna buy it?" is far less easily imputed to have a knowledge that the name is actually in play (via the wildcard) at that time and that, consequently, it will come with some baggage.

    I am particularly concerned about emergency use of names for disaster recovery. The existance of prior-use resource records laying around because of site-finder can really disrupt a disaster recovery use during those critical first hours and first days. (Having had my city knocked flat by an earthquake kinda woke me up to these kinds of issues.)

    (By-the-way, nobody has mentioned that a prior owner, just before relinquishing a name, could crank up the TTLs in his/her zone file to astounding levels and thus leave a possible legacy of cached records, particularly for popular third level names such as "www", that lasts for months and months and months. And with that kind of long-lived MX records, it is a technique for the prior-owner to capture some of the inbound e-mail stream of the new owner.)
    [ Reply to This | Parent ]


    Search ICANNWatch.org:


    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