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.
    When is a registrant NOT a registrant? | Log in/Create an Account | Top | 7 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.
    ICANN Is Over-Regulating .Pro
    by Anonymous on Friday February 17 2006, @01:31PM (#16615)
    The problem is not that "ICANN has done nothing".

    The problem is that they have done too much!

    They designed a tld that only supported three professions and four countries. Then they put themselves in the decision-making role to approve new professions and countries.

    After ICANN staff approved RegistryPro's application for three new professions: dentists, architects and engineers, they then changed their mind when a Board member objected, forcing RegistryPro to cancel the rollout after they had already made a public announcement.

    see http://www.registrypro.pro/pressreleasses/pressrel ease_2004_10_27.htm

    Several months later, RegistryPro was allowed to support just one of the professions -professional engineers, after an ICANN Board vote.

    Why is the ICANN Staff and Board involved in making these decisions?

    There is no way that this ICANN-decides-the professions-and-countries model can scale so that all licensed professionals and all countries are supported. ICANN needs to remove themselves from this process.

    Last year, ICANN overstepped their authority with their public objections to RegistryPro and EnCirca about EnCirca's leasing service, knowing full well it was allowed under their contracts with both RegistryPro and EnCirca.

    This is clear when ICANN asks RegistryPro "would you be open to "amendments" to your contract? In other words, there were no contract violations. Essentially, they were interfering with a legal service for domain names.

    Since then, they have stonewalled RegistryPro's attempts at communications to fix the governance model for .pro.

    The facts are these:
    - Domain leasing is not prohibited by ICANN in .pro or in any other ICANN tld
    - Curse words are not prohibited by ICANN in .pro or any other ICANN tld

    Simply put, all registrations under the EnCirca leasing model are legal. Even if a new ICANN consensus policy or bilateral agreement was adopted prohibiting leasing in .pro, precedence dictates that they would need to be grandfathered for perpetuity.

    (for example: single-letter domains in .com that were registered prior to ICANN's decision to reserve them were grandfathered to the original customers)

    There are important lessons here for ICANN in over-regulating a tld. Its time they took steps to remove themselves from micro-managing .pro.

    Hopefully, ICANN realizes their policy-making role in .pro is inappropriate and they extricate themselves from this role.

    [ Reply to This | Parent ]
    Re:ICANN Is Over-Regulating .Pro
    by Anonymous on Saturday February 18 2006, @09:59AM (#16616)
    Can't agree with you. ICANN were right to challenge the way the restricted TLD was being opened up, because by destroying the original purpose of .pro as a restricted TLD limited to verified individuals, EnCirca and RegistryPro knew very well they were trampling over the goals and intentions of the .pro as set out in the Agreement.

    .pro was not intended to be .com, and it was *NOT* intended to be open to anyone simply because one registrar decided to create a device to get round the verification requirements for customers.

    [ 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