<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="script-src 'self'; img-src * cid: data:;">
<div style="background-color:rgb(255,255,255); line-height:initial">
<div id="x_response_container_BBPPID" dir="auto" style="outline:none; font-size:initial; font-family:"Calibri","Slate Pro",sans-serif,"sans-serif"">
<div name="x_BB10" dir="auto" style="width:100%; padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
Let's discuss on this week's call. </div>
<div name="x_BB10" dir="auto" style="width:100%; padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
<br style="display:initial">
</div>
<div id="x_blackberry_signature_BBPPID" name="x_BB10" dir="auto">
<div name="x_BB10" dir="auto" style="padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
Sent from my BlackBerry - the most secure mobile device</div>
</div>
</div>
<div id="x__original_msg_header_BBPPID" dir="auto">
<table width="100%" style="background-color:white; border-spacing:0px; display:table; outline:none">
<tbody>
<tr>
<td colspan="2" style="padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
<div style="border-right:none; border-bottom:none; border-left:none; border-top:1pt solid rgb(181,196,223); padding:3pt 0in 0in; font-family:Tahoma,"BB Alpha Sans","Slate Pro"; font-size:10pt">
<div id="x_from"><b>From:</b> icann@leap.com</div>
<div id="x_sent"><b>Sent:</b> August 1, 2017 6:23 PM</div>
<div id="x_to"><b>To:</b> gnso-igo-ingo-crp@icann.org</div>
<div id="x_subject"><b>Subject:</b> Re: [Gnso-igo-ingo-crp] - ACTION ITEM: Update Impact Analysis Document</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style="border-right:none; border-bottom:none; border-left:none; border-top:1pt solid rgb(186,188,209); display:block; padding:initial; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
</div>
<br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi folks,<br>
<br>
I can't speak for everyone, but it would be my expectation that *all*<br>
the options be analyzed for their pros/cons to stakeholders via the<br>
formal Risk Assessment and would appear in a final document as having<br>
been considered, rather than removing any from consideration.<br>
<br>
Indeed, the entire purpose of the Risk Assessment is to actually<br>
*assist* in paring down the options, by providing a structured method<br>
to analyze the options. Paring down the options prematurely *without*<br>
doing the Risk Assessment seems to me to be a step in the wrong<br>
direction.<br>
<br>
Sincerely,<br>
<br>
George Kirikos<br>
416-588-0269<br>
<a href="http://www.leap.com/">http://www.leap.com/</a><br>
<br>
<br>
On Tue, Aug 1, 2017 at 6:15 PM, Steve Chan <steve.chan@icann.org> wrote:<br>
> Dear WG Members,<br>
><br>
><br>
><br>
> During last week’s WG meeting on 27 July, it was suggested that the impact<br>
> analysis document be updated to include additional options that have been<br>
> raised beyond just options one and two. However, staff’s understanding is<br>
> that this action item is expected once the WG pares down the options, which<br>
> are now up to six, to a core set of options that it feels are worth<br>
> consideration for final recommendation. If this understanding is incorrect<br>
> and for instance, the WG is anticipating that the document would include all<br>
> six options and should be made available in the near future, please do let<br>
> us know.<br>
><br>
><br>
><br>
> Best,<br>
><br>
> Steve<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Steven Chan<br>
><br>
> Policy Director, GNSO Support<br>
><br>
><br>
><br>
> ICANN<br>
><br>
> 12025 Waterfront Drive, Suite 300<br>
><br>
> Los Angeles, CA 90094-2536<br>
><br>
> steve.chan@icann.org<br>
><br>
> mobile: +1.310.339.4410<br>
><br>
> office tel: +1.310.301.5800<br>
><br>
> office fax: +1.310.823.8649<br>
><br>
><br>
><br>
> Find out more about the GNSO by taking our interactive courses and visiting<br>
> the GNSO Newcomer pages.<br>
><br>
><br>
><br>
> Follow @GNSO on Twitter: <a href="https://twitter.com/ICANN_GNSO">https://twitter.com/ICANN_GNSO</a><br>
><br>
> Follow the GNSO on Facebook: <a href="https://www.facebook.com/icanngnso/">https://www.facebook.com/icanngnso/</a><br>
><br>
> <a href="http://gnso.icann.org/en/">http://gnso.icann.org/en/</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Gnso-igo-ingo-crp mailing list<br>
> Gnso-igo-ingo-crp@icann.org<br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp">https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp</a><br>
_______________________________________________<br>
Gnso-igo-ingo-crp mailing list<br>
Gnso-igo-ingo-crp@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp">https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp</a></div>
</span></font>
</body>
</html>