Posts tagged as:
Louis XVI

Louis XVI

Americans often quote, or allude to, the French expression ” Le Roi est mort, vive le Roi!” But few realize that this apparent paradox was meant quite literally by the French:From its first official proclamation in 1422 upon the coronation of Charles VII to 1774, when Louis XV finally died, the term expressed the abstract constitutional concept that sovereignty transfered from the old king (the first “Le Roi“) to the new king (the second  “Le Roi“) the very instant the old king died. Thus, France was literally never without a king until until the monarchy was finally dis-established in early 1793. When Louis XVI was guillotined later that year, his death was acclaimed simply with “Le Roi est mort!

Tomorrow, September 30, ICANN’s Joint Project Agreement with the Department of Commerce finally terminates. Le JPA est mort!” But a new agreement (the “Affirmation”) will take its place, apparently providing more accountability than the JPA ever did. Vive l’Affirmation! There may come a day when, like Louis XVI, ICANN’s JPA-like agreement with Commerce terminates and nothing is there to replace it, but that day has not yet come.

Grant Gross has a great piece on this new agreement. Grant extensively quotes my PFF Adjunct Fellow (my ICANN mentor and former ICANN board member) Mike Palage, who explained that the JPA’s successor (JPA II?):

will tell [ICANN] what it should do, but it can’t legally bind them [much like past agreements]… It gives the appearance in the global community that the U.S. government has recognized that ICANN has done what is was supposed to do. What it’s also doing is … it’s putting in some accountability mechanisms.”

Continue reading →

PFF Adjunct Fellow Mike Palage, who served on the ICANN board from 2003 to 2006, filed these comments (PDF) on the NTIA’s recent Notice of Inquiry regarding ICANN’s future.  Mike’s four key points were as follows:

  1. ICANN’s Periodic Review of its internal operations and supporting organizations has failed, and has become nothing more than a “perpetual motion machine of public comments and documentation producing no meaningful results.” Only a second Evolution and Reform Process can solve ICANN’s current deficiencies;
  2. ICANN must hardcode into its policies and its contracts the principle that its policies cannot supersede national laws;
  3. ICANN must cease any operational role in technical infrastructure as required by its bylaws and focus instead on its mission as a technical coordinator; and
  4. Congress must avoid “kicking the JPA can down the road” and instead provide much-needed leadership by creating a solid foundation for ICANN 3.0 in legislation after proper consultation with the Government Accountability Office.

Continue reading →

I’ve been working closely with PFF’s new Adjunct Fellow Michael Palage on ICANN issues.  Here is his latest note , from the PFF blog.

ICANN recently proclaimed that the “Joint Project Agreement” (one of two contractual arrangements that ICANN has with the U.S. Department of Commerce (DoC) governing ICANN’s operations) will come to an end in September 2009. ICANN’s insistence on this point first became clear back in October 2008 at ICANN’s Washington, D.C. public forum on Improving Institutional Confidence when Peter Dengate Thrush, Chair of ICANN’s Board declared:

the Joint Project Agreement will conclude in September 2009. This is a legal fact, the date of expiry of the agreement. It’s not that anyone’s declared it or cancelled it; it was set up to expire in September 2009.

ICANN’s recently published 2008 Annual Report stuck to this theme:

“As we approach the conclusion of the Joint Project Agreement between the United States Department of Commerce and ICANN in September 2009…” – His Excellency Dr. Tarek Kamel, Minister of Communications and Information Technology, Arab Republic of Egypt
“Concluding the JPA in September 2009 is the next logical step in transition of the DNS to private sector management.” – ICANN Staff
“This consultation’s aim was for the community to discuss possible changes to ICANN in the lead-up to the completion of the JPA in September 2009.” – ICANN Staff

ICANN’s effort to make the termination of the JPA seem inevitable is concerning on two fronts. First, ICANN fails to mention that the current JPA appears to be merely an extension/revision of the original 1998 Memorandum of Understand (MoU) with DoC, which was set to expire in September 2000. Thus, because the JPA does not appear to be a free-standing agreement, but merely a continuation of MOU-as Bret Fausset argues in his excellent analysis of the relationship between the MoU and the JPA (also discussed by Milton Mueller). Therefore, it would be more correct to talk about whether the “MoU/JPA”-meaning the entire agreement as modified by the most current JPA-will expire or be extended. Continue reading →