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

Our Mission
ICANN for Beginners
About Us
How To Use This Site
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.
    As the Board Turns | Log in/Create an Account | Top | 4 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    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.
    Why does it take 6 days?
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday July 30 2003, @08:22AM (#12012)
    User #2810 Info
    I dunno, but that's nothing. Why does it take ICANN almost two years to post the minutes of some of their meetings? And yeah, the ExComm is the important one as they have historically made most of the decisions. And Michael Palage on the Conflict of Interest Committee, that's almost as rich as having Rob Blokzijl on it. -g
    [ Reply to This | Parent ]
    Re:Why does it take 6 days?
    by dmehus on Wednesday July 30 2003, @02:07PM (#12014)
    User #3626 Info | http://doug.mehus.info/
    Yeah ... totally. Plus, last I checked, Michael Palage is still on the .US Policy Committee for NeuStar, in addition to his ICANN board duties and registrar constituency obligations. That's like a double conflict of interest. ;)

    Doug Mehus http://doug.mehus.info/ [mehus.info]
    [ Reply to This | Parent ]
    Re:Why does it take 6 days?
    by KarlAuerbach on Thursday July 31 2003, @12:18AM (#12015)
    User #3243 Info | http://www.cavebear.com/
    Six days is a great improvement compared to the sixteen months that sometimes happened in the past.

    As for the point about M. Palage - Everybody has conflicts, there is nothing wrong or shameful about conflicts. The issue is not that they exist but, instead, how they are handled.

    ICANN's conflicts policy is in need of rewriting - but the fact that it wasn't rewritten is as much my own fault, and perhaps more (because I was aware of what needed rewriting) as anyone's.

    ICANN's conflicts policy needs to be rewriten to make the mechanics more clear - the obligation to make a yearly report is defined three different ways in the existing policy. And the conflicts policy needs to be expanded to cover a broader range of types of conflicts. And the policy ought to be expanded to preclude certain kinds of revolving door situations - like when an ex-president is associated with an entity that gets a TLD.
    [ 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