<html><head><base href="x-msg://44/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 9, 2011, at 7:01 PM, Imran Ahmed Shah wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-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: 0px; font-size: medium; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">><span class="Apple-converted-space"> </span></span>Unless ICANN can demonstrate that EITHER this is a technical problem<o:p></o:p></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><o:p> </o:p></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">Under the Fast Track program, there is no template or frame of work was given to ICANN to demonstrate to justify the DNS Panel recommendation and its own rejection.<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">We have to develop a proposal for ICANN to review the issue of lacking of the dispute resolution mechanism.</span></div></div></div></span></blockquote><div><br></div><div>In the IDN Fast Track documentation, there is flowchart and comments to the effect that if the panel has negative opinion of a string, ICANN staff can engage 3 member review panel to review this opinion.</div><div><br></div><div>My interpretation of this part of the process is that it exists as a corrective tool should the panel make any error in their findings. This panel is made of humans and humans do make errors. Further, whatever this panel decides is clearly no scientifically provable, or they could have proved their opinion so far -- this is yet another source of error, because they cannot rely on their colleagues linguists to correct their opinion.</div><div><br></div><div>ICANNs interpretation of this three member panel option is that it should only be invoked if the original panel decides it lacks necessary expertise and it is obvious that panel has so far claimed to be well aware that ".бг is confusingly similar. period."</div><div><br></div><div>I am curious as to what the opinion of Tina Dam is with regards to this option. Why it was not applied to the Bulgarian application and why everyone at ICANN thinks it need not be used.</div><div><br></div><div>It is very simple. ICANN does not have to admin any mistake. ICANN just needs to follow the IDN Fast Track process, to the letter, and request secondary review of the string.</div><div><br></div><div>Same for the Greek case, of course.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-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: 0px; font-size: medium; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><o:p> </o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">><span class="Apple-converted-space"> </span></span>problem OR that it has carried out a wide survey of a couple of billion people like me and the majority claims to be confused by the two strings<span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><o:p> </o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">We should not assume that ICANN has need to justify his decision or its power need balance, and if we want to resolve the issue in favor of applicant, we should follow some good governance.</span></div></div></div></span></blockquote><div><br></div><div>Unfortunately (for ICANN), they are not divine. Their "power" comes from two sources: the US Government and the Internet community. Displeasing either of these and ICANN may pretty much be forcibly dethroned. </div><div><br></div><div>Therefore ICANN has to justify any and all of their actions or inactions.</div><br><blockquote type="cite"><span class="Apple-style-span" style="font-family: Tahoma, sans-serif; font-size: 13px; "> </span><span class="Apple-style-span" style="border-collapse: separate; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-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: 0px; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">It is fact that these examples of the issues are new to the Internet for the world and for the world most prime brains as well. But the problem is becoming critical because there is no relaxation or appeal procedure available in the Fast Track Program to address the string re-evaluation request before its delegations or after the declaration of the results mid of the way.<o:p></o:p></span></div></div></div></span></blockquote><br></div><div>The Fast Track process is fine. There is nothing wrong with the process. The IDN Fast Track process needs not be fixed.</div><div><br></div><div>It is the way ICANN implements it, that is wrong. At least the following things are necessary to be fixed:</div><div><br></div><div>- ICANN should stop arguing and invoke the three member panels for both the Bulgarian and Greek applications. And for any further application that comes to similar situation.</div><div>- ICANN should follow the IDN Fast Track process as designed. In particular, as it relates to these issues, the procedure clearly says that it should loop after a 'confusability finding' with communication between the applicant, ICANN staff and the panel (presumably, this three member review panel) until either the application is successful or the applicant withdraws it.</div><div>- Any proceedings by the stability panel MUST be made public for review by the community and for the benefit of other applicants (to not make the same mistakes).</div><br><div>Daniel</div></body></html>