<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Amr,<br>
<br>
To keep it simple, both .doctor and .sucks are situations where
ICANN has remained completely mute. That is both a corporate risk
to ICANN and does nothing to bolster the role of the
multistakeholder process in addressing (here) DNS issues. Please
note that there is a difference between being engaged in the
dialogue around issues and taking policy positions. <br>
<br>
For example, had ICANN, as ICANN, entered into the discussions
around .health with the global health community, the global
community would have been more aware and better informed about the
issues and where they should be dealt with (for the most part
outside ICANN). I suspect that had there been that dialogue the
global health community would have said "Go ahead with .health and
we will deal with the issues, as they arise, elsewhere". By not
engaging that discussion, the learning process suffers, ICANN runs
the real risk as being seen as part of the problem, and in the
process the multistakeholder model can suffer collateral damage. <br>
<br>
Sam L.<br>
<br>
<br>
On 30/03/2015 10:59 AM, Amr Elsadr wrote:<br>
</div>
<blockquote
cite="mid:9C7B1DA0-014B-4CEE-A70A-8B8130DAD031@egyptig.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Sam,
<div><br>
</div>
<div>I’m confused about how you’re conflating and comparing the
two issues of .doctor and .sucks.</div>
<div><br>
</div>
<div>More inline:</div>
<div><br>
<div>
<div>On Mar 30, 2015, at 4:15 PM, Sam Lanfranco <<a
moz-do-not-send="true" href="mailto:Lanfran@yorku.ca">Lanfran@yorku.ca</a>>
wrote:</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>