<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>There will be a public comment period for the draft RFP, but it is not determined when that will be, probably several months off. </div><div><br class="webkit-block-placeholder"></div><div>Perhaps we should make a request that ICANN accept public comment now on the work currently being done.</div><div><br class="webkit-block-placeholder"></div><div>I should also mention that ICANN is working on creating a computer algorithm to make determinations about string "similarity" and "likelihood of confusion". They are trying to use trademark terms with legal definitions in ways entirely unintended and that do not match the legal meanings. </div><div><br class="webkit-block-placeholder"></div><div>It would not surprise me if that ICANN board simply did not accept many of the GNSO/(icann-staff) recommendations as many of them are not implementable.</div><div><br class="webkit-block-placeholder"></div><div>Robin</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><br><div><div>On Apr 22, 2008, at 5:05 AM, Milton L Mueller wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div class="Section1"><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy; ">Thanks, Robin for this excellent summary of the challenging issues before us. Are there any impending public comment opportunities to raise these issues (especially the staff’s alarming reintroduction of beauty contests)?<o:p></o:p></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy; "><o:p> </o:p></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy; ">What we see here is a disturbing but somewhat predictable tendency to create what you call “carve-outs” – special, privileged rules tailored to specific interests that allow them to bypass the normal objections process. So in addition to the already Byzantine and unpredictable process we add another layer of carveouts. What a nightmare!<o:p></o:p></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy; "><o:p> </o:p></span></font></div><div style="border-top-style: none; border-right-style: none; border-bottom-style: none; border-width: initial; border-color: initial; border-left-style: solid; border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; "><div><div class="MsoNormal" align="center" style="text-align: center; margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><hr size="2" width="100%" align="center" tabindex="-1"></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold; ">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size: 10pt; font-family: Tahoma; "><span class="Apple-converted-space"> </span>Non-Commercial User Constituency [<a href="mailto:NCUC-DISCUSS@LISTSERV.SYR.EDU">mailto:NCUC-DISCUSS@LISTSERV.SYR.EDU</a>]<span class="Apple-converted-space"> </span><b><span style="font-weight: bold; ">On Behalf Of<span class="Apple-converted-space"> </span></span></b>Robin Gross<br><b><span style="font-weight: bold; ">Sent:</span></b><span class="Apple-converted-space"> </span>Monday, April 21, 2008 4:48 PM<br><b><span style="font-weight: bold; ">To:</span></b><span class="Apple-converted-space"> </span><a href="mailto:NCUC-DISCUSS@LISTSERV.SYR.EDU">NCUC-DISCUSS@LISTSERV.SYR.EDU</a><br><b><span style="font-weight: bold; ">Subject:</span></b><span class="Apple-converted-space"> </span>[NCUC-DISCUSS] new gtld policy update - 11 April mtg and staff notes</span></font><o:p></o:p></div></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">A few key issues were discussed at the new gtld policy meeting on 11 April in LA. <o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">Here are the 70 slides from the meeting:<o:p></o:p></span></font></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "> <a href="http://gnso.icann.org/correspondence/new-gtlds-policy-discussion-11apr08.pdf" style="color: blue; text-decoration: underline; ">http://gnso.icann.org/correspondence/new-gtlds-policy-discussion-11apr08.pdf</a><o:p></o:p></span></font></div></div><div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">1. There is a question as to whether a TLD operator can expand its business down the line in ways not outlines in its original application for a TLD. We have argued that TLD operators should not be straight jacketed into their business plan 1.0 and should be allowed to expand their use of the TLD in lawful ways. Some in the business and registry constituencies want for TLD operators to have to go back and receive approval from ICANN every time they want to use the TLD in a new way. <o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">2. Some want country names and their abbreviations to be off-limits to anyone for use in a top-level domain. There is a lot of pressure from GAC to reserve words they would want to own. The GNSO's response has been GAC can object to any application like anyone else and take the names it wants that way. But there are still calls for a reserved name list for country names and abbreviations.<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">3. When two applicants want the same string, ICANN is proposing a "beauty contest" method of determining who should be given the string. This "comparison evaluation" was not in the GNSO's recommendations and is something ICANN staff has created. Many in the GNSO expressed concern about this method, but it remains to be seen whether the GNSO will have final say in what its recommendations are. The beauty contest criteria for deciding who is awarded a domain name include very subjective and arbitrary evaluation criteria such as "provides value", or is "important" to ICANN.<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">4. The morality / public order string criteria continue to be problematic. There is some discussion as to who has standing to raise an objection to a domain name based on morality and public order. We have argued that only governments should have such standing, but the current wording of the recommendation opens it up for any one in the world to object to a string based on morality and public order. ICANN will adopt a "one-size-fits-all" for standards of morality and public order. Very little information on this issue was given at the 11 April mtg (only 1 slide of 70 slides).<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "><o:p> </o:p></span></font></div></div><div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">5. There will be a 3-part test for OBJECTIONS:<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; "> For an objection to be successful in killing an application for a domain name, the objector must prove that:<o:p></o:p></span></font></div></div><div style="text-indent: -0.25in; margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">-</span></font><font size="1"><span style="font-size: 7pt; "> <span class="Apple-converted-space"> </span></span></font>Community opposition to the application is substantial; AND<o:p></o:p></div><div style="text-indent: -0.25in; margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">-</span></font><font size="1"><span style="font-size: 7pt; "> <span class="Apple-converted-space"> </span></span></font>Community invoked is a coherent community; AND<o:p></o:p></div><div style="text-indent: -0.25in; margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" face="Times New Roman"><span style="font-size: 12pt; ">-</span></font><font size="1"><span style="font-size: 7pt; "> <span class="Apple-converted-space"> </span></span></font>There is a reasonable association between the community invoked and the TLD string applied for.<o:p></o:p></div><span style="orphans: 2; widows: 2; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-spacing: 0px; "><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; ">6. The trademark and business constituencies want special privileges for software companies that would prohibit a TLD if it corresponds to a file extension (like .doc or .pdf). ICANN staff said it was told that there were no technical problems with such a TLD, but the trademark industry is still pushing for this and may get the special carve out. At the meeting I argued that if there is a question of confusion, the objection process should be used to solve that question. Those companies can go through the same process that everyone else must go through to raise their objection based on likelihood of confusion. But the voices for the special carve-out are loud and well-funded; and the contracting parties don't care much one way or another so will likely give in to the pressure to create a presumption against a file extension as a TLD.<o:p></o:p></span></font></div></div></span><div><span style="orphans: 2; widows: 2; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-spacing: 0px; "><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; ">7. Chart of new gtld sting evaluation process:<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; "> <a href="http://gnso.icann.org/correspondence/gtld-process-simplified-10apr08.pdf" style="color: blue; text-decoration: underline; ">http://gnso.icann.org/correspondence/gtld-process-simplified-10apr08.pdf</a><o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; "><o:p> </o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; ">8. And see also the attached briefing notes from ICANN staff of 14 April.<o:p></o:p></span></font></div></div><div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="1" color="black" face="Helvetica"><span style="font-size: 9pt; font-family: Helvetica; color: black; "><o:p> </o:p></span></font></div></div></span></div></div></div></div></div></div></span></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>IP JUSTICE</div><div>Robin Gross, Executive Director</div><div>1192 Haight Street, San Francisco, CA 94117 USA</div><div>p: +1-415-553-6261 f: +1-415-462-6451</div><div>w: <a href="http://www.ipjustice.org">http://www.ipjustice.org</a> e: <a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </div><br></body></html>