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.
    Text of Joe Sims 'willing to advocate' e-mail | Log in/Create an Account | Top | 5 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.

    by lextext on Friday May 18 2001, @05:50AM (#608)
    User #6 Info | http://www.lextext.com
    OK, I'm missing something. Where, exactly, is the nefarious content in this message?

    It's not "nefarious," but it does underscore a frequent criticism of ICANN generally and one made about these agreements in particular -- namely, that significant new initiatives are not developed "bottom up," as required in the White Paper, but by Staff, usually not even in consultation with the elected Board. Here, if we believe the cover e-mail, Mr. Sims was working on his own, without the guidance or even knowledge of Staff, much less the Board.

    I honestly don't know many lawyers who would have sent the kind of e-mail written by Mr. Sims. It's the first salvo in a negotiation, and you've now set the parameters of the negotiations before you even know what your client wants. You can see how this played out by seeing how close the final deal was to what Sims placed in a "personal" "wish list." Of course, clients are all different in the way they supervise outside counsel, and Mr. Sims obviously knew his well. But the path for the negotiations was set by outside counsel working without policy guidance from the Board or Staff.

    Verisign's at fault too. Verisign knows well the way that new initiatives are created within the ICANN process. It worked constructively in the creation of the DNSO and, at least in the beginning, was the most outspoken advocate for bottom-up consultations that start in working groups and move up slowly to the Board level. Verisign also remembers well the firestorm that surrounded the initial presentation of these agreements in 1999. The community was frustrated and angry that it had little time to evaluate the agreements. Watch the Berkman archives of the November 1999 meeting.

    With the history of the 1999 agreements fresh in its mind, wouldn't it have been wise for Verisign to avoid the same problems when it wanted to renegotiate? Instead, it approached ICANN's outside counsel. And agreements were negotiated and presented to the community as completed deals, without ever asking the community what it would want, if anything, in a revised relationship with Verisign.

    There's nothing nefarious, illegal or unethical here. At most, it's a violation of the ICANN Bylaws that require bottom up consultative processes. But it does underscore a continuing problem with the way ICANN makes important decisions and vets those decisions with the relevant community.

    -- Bret
    [ Reply to This | Parent ]
    • Re: by larry Friday May 18 2001, @09:57AM
    • 1 reply beneath your current threshold.
  • 1 reply 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