<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi,</div><div><br></div><div>Coming back to this thread, there was an expression to see references to the ICANN Board’s decisions on this topic. From what I can tell there was a discussion on the topic of “Category 1 Safeguards for Highly Regulated Strings” on the February 5th meeting of the New gTLD Program Committee (NGPC) of the ICANN Board. It looks like there was no resolution taken during that meeting (<a href="https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-02-05-en">https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-02-05-en</a>).</div><div><br></div><div>However, there was a reference to that meeting in another meeting that took place on February 12th, in which the NGPC seemed to agree on <i><b>“</b></i><span style="background-color: rgb(255, 255, 255);"><font color="#333333"><span style="line-height: 22.399999618530273px;"><i><b>staff to continue to move forward with implementation of its 5 February 2014 resolution on the matter</b></i></span><span style="line-height: 22px;"><i><b>”</b></i>. (</span></font></span><a href="https://www.icann.org/resources/board-material/prelim-report-new-gtld-2015-02-12-en">https://www.icann.org/resources/board-material/prelim-report-new-gtld-2015-02-12-en</a>)</div><div><br></div><div>I’m not sure what resolution was being referred to, as the report of the February 5th meeting indicated that there were no resolutions taken.</div><div><br></div><div>I’ll provide any updated info I come across.</div><div><br></div><div>Thanks.</div><div><br></div><div>Amr</div><br><div><div>On Mar 18, 2015, at 7:54 PM, Sam Lanfranco <<a href="mailto:Lanfran@yorku.ca">Lanfran@yorku.ca</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">All,<br>
<br>
I too would like to know the source of this. I did not reference
it in my comments. But true or not the overall problem exists.<br>
I am focused on the overall problem, which should have been clear
at the start of the new-gTLD program. <br>
I had already written about the overall problem in my blog on
.health several months ago. <br>
<br>
Sam<br>
<br>
On 18/03/2015 2:37 PM, Amr Elsadr wrote:<br>
</div>
<blockquote cite="mid:68E63A07-0A5B-473C-9370-AD6F2FC051B0@egyptig.org" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>Hi,</div>
<br>
<div>
<div>On Mar 18, 2015, at 3:11 PM, Seun Ojedeji <<a moz-do-not-send="true" href="mailto:seun.ojedeji@GMAIL.COM">seun.ojedeji@GMAIL.COM</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: TrebuchetMS; font-size: 14px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Mar 18, 2015 at 1:39
PM, Sam Lanfranco<span class="Apple-converted-space"> </span><span dir="ltr"><<a moz-do-not-send="true" href="mailto:lanfran@yorku.ca" target="_blank">lanfran@yorku.ca</a>></span><span class="Apple-converted-space"> </span>wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px
0px 0.8ex; border-left-width: 1px;
border-left-style: solid; border-left-color:
rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#FFFFFF" text="#000000">
<div><small>On 18/03/2015 7:56 AM, Timothe Litt
wrote:<br>
</small></div>
<blockquote type="cite">
<pre><small>Doctor, doctor give me the news:
<a moz-do-not-send="true" href="http://www.theregister.co.uk/2015/03/15/icann_doctors/" target="_blank">http://www.theregister.co.uk/2015/03/15/icann_doctors/</a>
Sigh.</small>
</pre>
</blockquote><p class="MsoNormal">What I do not understand is
why ICANN could not see these problems coming
from the start.</p>
</div>
</blockquote>
<div><br>
</div>
<div>Before i add a strong +1 to this, i quote the
intro of the article below:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0px
0px 0px 0.8ex; border-left-width: 1px;
border-left-style: solid; border-left-color:
rgb(204, 204, 204); padding-left: 1ex; position:
static; z-index: auto;">Domain-name overseer ICANN
has decided that only one kind of doctor may be
allowed online – and that is a medical doctor. In
a<span class="Apple-converted-space"> </span><b>decision</b><span class="Apple-converted-space"> </span>made late
last month.<br>
</blockquote>
</div>
<div><br>
</div>
<div>Could someone kindly refer me to where i can find
that decision statement?</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>I did a quick search on recent board resolutions, and
actually couldn’t find anything. In fact, according to the
published activity of the ICANN board, this was discussed during
a meeting on February 12th, but no resolution seems to have been
taken.</div>
<div><br>
</div>
<div><a moz-do-not-send="true" href="https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-02-12-en">https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-02-12-en</a></div>
<div><br>
</div>
<div>I would also like to see a resolution and rationale on this.</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div>Amr</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
------------------------------------------------
"It is a disgrace to be rich and honoured
in an unjust state" -Confucius
------------------------------------------------
Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)
Econ, York U., Toronto, Ontario, CANADA - M3J 1P3
email: <a class="moz-txt-link-abbreviated" href="mailto:Lanfran@Yorku.ca">Lanfran@Yorku.ca</a> Skype: slanfranco
blog: <a class="moz-txt-link-freetext" href="http://samlanfranco.blogspot.com/">http://samlanfranco.blogspot.com</a>
Phone: +1 613-476-0429 cell: +1 416-816-2852</pre>
</div>
</blockquote></div><br></body></html>