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.
    Intentional & Widespread Whois Errors - Some Specific Examples | Log in/Create an Account | Top | 11 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.
    So, what to do about this?
    by BenEdelman on Monday May 13 2002, @09:40AM (#6302)
    User #3219 Info | http://cyber.law.harvard.edu/edelman
    I'm sure the congressmen -- not to mention ICANN staff and the more respectable of registrars -- are anxious to fix this problem. In that context, what specific advise can we offer them?

    ICANN's Registrar Advisory Concerning Whois Data Accuracy makes a few suggestions -- that registrars should require that registrants use basic validation methods on contact details at the time of registration; that registrars investigate inaccurate information after notification; that domains with invalid registration "should" be cancelled after 15 days of notice; that resellers should be bound by the same rules.

    Is there more that ICANN and the regsitrars could or should do? For example, if a registrant has registered many domains with the same (or nearly the same) invalid address, should the others be canceled too (if the registrar attempts to contact the registrant and the registrant doesn't respond)? Or the registrar should have to receive a separate notification for each domain at issue?

    Could there be some central list of "known offenders"? What risks would be entailed in the creation of such a list? What cost and complexity? What benefits?
    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.
    Re: Intentional & Widespread Whois Errors - Some S
    by BenEdelman on Monday May 13 2002, @08:30AM (#6300)
    User #3219 Info | http://cyber.law.harvard.edu/edelman
    Yes, I'm told that Doctor John is a musician. (Had I known this when I drafted my report, perhaps I would have chosen a different example!) But the domain was indeed previously held by, as best I can tell, a genuine doctor. See archive.org listings for details.

    My own music taste? Suffice it to say that I've actually never heard of Lawrence Welk.
    [ Reply to This | Parent ]
    Re: Intentional & Widespread Whois Errors - Some S
    by fnord (groy2kNO@SPAMyahoo.com) on Monday May 13 2002, @03:17PM (#6308)
    User #2810 Info
    Very well said, I only have one quibble. In the olden days it was handy to have a public technical contact for a domain name. That long predates the IP lobby waking up to the internet. It also long predates the namespace including millions of entries, many of which could now individually or even collectively go down with no other network loss of functionality. Domain names once approximately corresponded to critical nodes, now they can and do point to home connections. It also long predates the 'public' coming to include scammers and spammers. The public WHOIS didn't scale for a number of reasons.

    It's past time for a better WHOIS, and a thick 24/7 global public WHOIS (that must be accurate under penalty of losing the domain name, or even facing charges) will be better for the IP folks, scammers and spammers, worse for everyone else. I'd like to think the latter is still a clear majority. A private WHOIS is part of a better WHOIS for most. -g

    [ Reply to This | Parent ]
  • 5 replies beneath your current threshold.

  • 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