PFF Adjunct Fellow Mike Palage led this extraordinary discussion of ICANN’s origins, evolution and future with four of ICANN’s “Founding Fathers”: Milton Mueller (author of Ruling the Root), law professor David Johnson, ICANN’s first CEO Mike Roberts and then ICANN CEO Paul Twomey. In particular, the group discussed ICANN’s mission, governance structure, and accountability; the difficult issue of new generic Top Level Domain names (gTLDs) and trademark concerns; and ICANN’s future relationship with the U.S. government. Be sure to check out the handy ICANN Glossary on page 33. The audio can be downloaded here.

Here’s the transcript (PDF):

My PFF colleague Mike Palage just released a paper about a series of recent applications for national trademark rights in terms that correspond to likely strings for new top-level domain names, or TLDs, (e.g., “.BLOG”). These attempts highlight just one way in which ICANN’s new generic TLD (gTLD) application process is likely to be “gamed.” But it is also a strategy to which some trademark holders may feel compelled to resort to defend their rights to that string. Unfortunately, it does not appear that ICANN is addressing these important public policy considerations. In fact, based upon some of the provisions in the proposed draft registry agreements, it appears that ICANN staff’s actions may increase, rather than decrease, the ambiguity that opens the door to such gaming of the system.

http://d.scribd.com/ScribdViewer.swf?document_id=17847370&access_key=key-17v70dtd7qa1zrmq3z6x&page=1&version=1&viewMode=list

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.