<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
p.style3, li.style3, div.style3
{mso-style-name:style3;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
text-align:justify;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
p.style4, li.style4, div.style4
{mso-style-name:style4;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:9.0pt;
font-family:"Verdana","sans-serif";}
span.style51
{mso-style-name:style51;
font-family:"Verdana","sans-serif";
font-weight:bold;}
span.style31
{mso-style-name:style31;
font-family:"Verdana","sans-serif";}
span.EmailStyle26
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello All,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Listed below is an article that I wrote in connection with
ICANN’s proposed new gTLD Expression of Interest initiative. While I
think there is some good that could come of this proposal, as I have tried to
articulate in this article there is potentially a lot of bad, especially when
you look at the public forum which has basically been flooded by prospective
TLD applicants. There is less than 10 days before ICANN staff summarizes
the public forum input for consideration by the ICANN Board at its early
December meeting.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As Mike Rodenbaugh previously noted there is probably not enough
time for the constituency to reach an opinion, and Ron Andruff has already
taken a position in line with the prospective TLD applicants which is kind of
the polar opposite to the position advocated in my paper.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is kind of a big issue which appears to be getting lost in
the DAG 3.0 comment period and the upcoming holiday season. I really do believe
individual BC members should weigh in on this important issue one way or
another.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Michael<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr style='height:42.75pt'>
<td width="46%" style='width:46.0%;padding:.75pt .75pt .75pt .75pt;
height:42.75pt'>
<p class=MsoNormal><span class=style51><span style='font-size:9.0pt'>FOR
IMMEDIATE RELEASE</span></span><b><span style='font-size:9.0pt;font-family:
"Verdana","sans-serif"'><br>
<span class=style51>November 18, 2009</span></span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td colspan=2 style='padding:.75pt .75pt .75pt .75pt'>
<p align=center style='text-align:center'><strong><span style='font-size:
13.5pt'>New gTLD Expressions of Interest: Proceed with Caution</span></strong><br>
<em><b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'>Palage
Offers Suggestions to Ensure Useful Insight is Gathered in Process</span></b></em><o:p></o:p></p>
<p class=style3><strong><span style='font-family:"Verdana","sans-serif"'>WASHINGTON
D.C. - </span></strong><span class=style31><span style='font-size:10.0pt'>The
Internet Corporation for Assigned Names and Numbers (ICANN) should look to
precedents if it chooses to move forward with soliciting Expressions of
Interests for new Generic Top Level Domains, states Adjunct Fellow Michael
Palage in "</span><a href="http://ga1.org/ct/-7Xbtas1Mm48/"><span
style='font-size:10.0pt'>New gTLD Expressions of Interest: Proceed with
Caution</span></a></span><span class=style31><span style='font-size:10.0pt'>,"
released today by The Progress & Freedom Foundation. Previous EOIs
were successful in helping ICANN gather pertinent data to judge likely gTLD
demand and make fact-based decisions.</span></span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>In the </span><a
href="http://ga1.org/ct/-7Xbtas1Mm48/"><span style='font-size:10.0pt'>paper</span></a><span
style='font-size:10.0pt'>, Palage, a former ICANN board member, states that
the Expression of Interest, if well executed, could help to address a number
of the remaining issues with implementation of new gTLDs. If executed
improperly, however, the initiative will likely erode confidence in the new
gTLD process and negatively impact ICANN's evaluation in the upcoming reviews
under ICANN's new Affirmation of Commitments.</span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>Palage warns against proposals
to make participation in the EOI a condition for participating in the first
new gTLD round. He also warns against instituting substantial fees to file,
stating that both proposals deviate from established precedent. Palage
explains that such actions would transform a fact-based gathering EOI into a
"front-running scheme for insiders to reserve their space at the front
of the new gTLD line." </span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>The proposal would fail to
create a level playing field for potential applicants. Moreover, this
proposed front-running approach would likely only increase ICANN's litigation
risks by appearing to grant a license or privilege in a process which may
ultimately diverge from present expectations.</span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>"The path forward for
ICANN is a road that it has previously traveled - and one which has served it
well," concludes Palage. "There is little benefit to
deviating from these established precedents to benefit the narrow interests
of a small number of TLD applicants whose business plans have been
jeopardized because of ICANN's decision to listen to the global community by
slowing down and getting things right."</span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>"</span><a
href="http://ga1.org/ct/-7Xbtas1Mm48/"><span style='font-size:10.0pt'>New
gTLD Expressions of Interest: Proceed with Caution</span></a><span
style='font-size:10.0pt'>" is available on the </span><a
href="http://www.pff.org/"><span style='font-size:10.0pt'>PFF website</span></a><span
style='font-size:10.0pt'>. </span><o:p></o:p></p>
<p class=style3><span style='font-size:10.0pt'>The Progress & Freedom
Foundation is a market-oriented think tank that studies the digital
revolution and its implications for public policy. It is a 501(c)(3) research
& educational organization.</span> <o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
</div>
</body>
</html>