<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div style="width:100%; font-size:initial; font-family:Calibri,'Slate Pro',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; background-color:rgb(255,255,255)">
Sure. We need a rich discussion on the issues. Sorry to have missed your post, buried in stuff....</div>
<div style="width:100%; font-size:initial; font-family:Calibri,'Slate Pro',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; background-color:rgb(255,255,255)">
<br style="display:initial">
</div>
<div style="font-size:initial; font-family:Calibri,'Slate Pro',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; background-color:rgb(255,255,255)">
Sent from my BlackBerry 10 smartphone on the Bell network.</div>
<table width="100%" style="background-color:white; border-spacing:0px">
<tbody>
<tr>
<td colspan="2" style="font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
<div style="border-style:solid none none; border-top-color:rgb(181,196,223); border-top-width:1pt; padding:3pt 0in 0in; font-family:Tahoma,'BB Alpha Sans','Slate Pro'; font-size:10pt">
<div><b>From: </b>Rafik Dammak</div>
<div><b>Sent: </b>Wednesday, May 16, 2018 08:51</div>
<div><b>To: </b>Stephanie Perrin</div>
<div><b>Cc: </b>ncsg-pc</div>
<div><b>Subject: </b>Re: [NCSG-PC] Fwd: Re: [RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style="border-style:solid none none; border-top-color:rgb(186,188,209); border-top-width:1pt; font-size:initial; text-align:initial; background-color:rgb(255,255,255)">
</div>
<br>
<div>
<div dir="ltr">Thanks, Stephanie, I shared yesterday in the NCSG list the 2 public comments regarding the adjustments of reviews timelines and asked for volunteers to be penholders. can I assume that you are volunteering for the one covering ATRT and RDS RT?
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Rafik<br>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Le mer. 16 mai 2018 à 21:49, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">we need to respond to this. I can draft, once we discuss a bit. Has implications...so we need to consider carefully, much as I would like to curtail this stupid review .....<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">steph</font></font><br>
</p>
<div class="m_-9071931560532925453moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="m_-9071931560532925453moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="" align="RIGHT">Subject: </th>
<td>Re: [RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="" align="RIGHT">Date: </th>
<td>Wed, 16 May 2018 06:57:21 +0200</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="" align="RIGHT">From: </th>
<td>Erika Mann <a class="m_-9071931560532925453moz-txt-link-rfc2396E" href="mailto:erika@erikamann.com" target="_blank">
<erika@erikamann.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="" align="RIGHT">To: </th>
<td>Alan Greenberg <a class="m_-9071931560532925453moz-txt-link-rfc2396E" href="mailto:alan.greenberg@mcgill.ca" target="_blank">
<alan.greenberg@mcgill.ca></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="" align="RIGHT">CC: </th>
<td>RDS-WHOIS2-RT <a class="m_-9071931560532925453moz-txt-link-rfc2396E" href="mailto:rds-whois2-rt@icann.org" target="_blank">
<rds-whois2-rt@icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div>Hi Alan, hi All - </div>
<div>There's a complete reasoning for these 3 options included here: <a href="https://www.icann.org/en/system/files/files/specific-reviews-short-term-options-timeline-14may18-en.pdf" target="_blank">https://www.icann.org/en/system/files/files/specific-reviews-short-term-options-timeline-14may18-en.pdf</a></div>
<div><br>
</div>
<div>I'm traveling today with little time to think about these options. My understanding is that large part of our work, independently of the WHOIS model going to be selected in the future, is going to be relevant nonetheless. Insofar - currently! - I favor
option a). </div>
<div><br>
</div>
<div>Best,</div>
<div>Erika <br>
<br>
<div>Sent from my iPhone</div>
</div>
<div><br>
On May 16, 2018, at 4:30 AM, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>I call your attention to a Public Comment (PC) launched yesterday asking for input on alternatives to alter the RDS-WHOIS2-RT Scope and plans (as well possible changes to the not yet started ATRT3) -
<a href="https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en" target="_blank">
https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en</a>.</span><br>
<span></span><br>
<span>I proposes three possible scenarios for our RT:</span><br>
<span></span><br>
<span>a) Proceeds as planned;</span><br>
<span></span><br>
<span>b) reduce scope to just an analysis of the WHOIS1-RT Recommendations;</span><br>
<span></span><br>
<span>c) pause the review entirely for some as yet to be determined time.</span><br>
<span></span><br>
<span>If recommended by the community, b) and c) would require our agreement. The implications of a community recommendation that we refused to agree with are not known. If there is a pause, it is not clear when the unpause would happen and to what extent it
would be the same team moving forward.</span><br>
<span></span><br>
<span>The PC ends on 06 July 2018 and the report on input received is due on 23 July 2018, a few days before we are currently planning to meet in Brussels to close-to-finalize our report.</span><br>
<span></span><br>
<span>Although the PC was issues yesterday, neither I nor Susan and Cathrin had any prior knowledge of it and in fact we only heard of it today.</span><br>
<span></span><br>
<span>We have initiated discussions with MSSI on exactly what this means and will get back when I have a better understanding.</span><br>
<span></span><br>
<span>Alan</span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>RDS-WHOIS2-RT mailing list</span><br>
<span><a href="mailto:RDS-WHOIS2-RT@icann.org" target="_blank">RDS-WHOIS2-RT@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" target="_blank">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a></span><br>
</div>
</blockquote>
</div>
</div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote>
</div>
</div>
</div>
</body>
</html>