<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Seeing I was a member of that RT, I am, for propriety's sake, obliged to sit on my hands.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Carlton</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 29, 2020 at 6:17 PM Pam Little <<a href="mailto:pam.little@alibaba-inc.com">pam.little@alibaba-inc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="clear:both">Thank you Marie for your prompt response and <span>BC's</span> support for the revisions.</div><div style="clear:both"><br></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Dear Councilors - As we are aiming to send the correspondence to the Board this Friday, 3 July 2020, please provide any feedback or suggested edits by close of business Thursday 2 July 2020 (your local time). </span></div><div style="clear:both"><br></div><div style="clear:both">Kind regards,</div><div style="clear:both"><br></div><div style="clear:both">Pam <br></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)"><br></span></div><blockquote style="margin-right:0px;margin-top:0px;margin-bottom:0px"><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">------------------------------------------------------------------</span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Sender:Marie Pattullo <<a href="mailto:marie.pattullo@aim.be" target="_blank">marie.pattullo@aim.be</a>></span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Sent At:2020 Jun. 27 (Sat.) 00:13</span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Recipient:PAMELALITTLE <<a href="mailto:pam.little@alibaba-inc.com" target="_blank">pam.little@alibaba-inc.com</a>></span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Cc:Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org" target="_blank">caitlin.tubergen@icann.org</a>>; <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>></span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)">Subject:RE: [council] For your review: Draft Response - Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations</span></div><div style="clear:both"><span style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)"><br></span></div><div><p class="MsoNormal"><span style="font-size:15px;color:black">Thanks so much Pam – really appreciate your willingness to consider the <span>BC’s</span> comments. We’re happy with your redraft.</span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Wishing everyone a peaceful non-return home but return to your usual working hours!</span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Best</span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Marie</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p class="MsoNormal"><b><span style="font-size:15px">From:</span></b><span style="font-size:15px"> PAMELALITTLE <<a href="mailto:pam.little@alibaba-inc.com" target="_blank">pam.little@alibaba-inc.com</a>>
<br><b>Sent:</b> Thursday, June 25, 2020 6:59 AM<br><b>To:</b> Marie Pattullo <<a href="mailto:marie.pattullo@aim.be" target="_blank">marie.pattullo@aim.be</a>><br><b>Cc:</b> Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org" target="_blank">caitlin.tubergen@icann.org</a>>; <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br><b>Subject:</b> Re: [council] For your review: Draft Response - Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations</span></p><p class="MsoNormal"> </p><div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black">Dear Marie,</span></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thank you for the edits and comments from the BC. I have updated the draft for your further review and consideration.</p></div><div><p class="MsoNormal" style="font-variant-caps:normal;text-align:start"><span style="font-size:15px;color:black;border:1px none windowtext;padding:0px"> </span></p><p class="MsoNormal" style="font-variant-caps:normal;text-align:start"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;border:1px none windowtext;padding:0px">1.
</span><span style="font-size:9px;color:black;border:1px none windowtext;padding:0px"> </span><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;border:1px none windowtext;padding:0px">Recommendation CC.1 - </span><span style="font-size:14px;font-family:Tahoma,sans-serif">While
I agree the Council is actively working to identify the appropriate mechanisms or processes to deal with EPDP Phase 2 Priority 2 issues (including data accuracy), we have not reached any consensus or conclusion yet. I hope the updated language more accurately reflects
where things are right now. </span></p><p class="MsoNormal" style="font-variant-caps:normal;text-align:start">
</p></div><div><p class="MsoNormal">2. <span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;background-color:white">Recommendation</span><span style="font-size:15px;color:black;background-color:white"> CC.4 - I</span><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;background-color:white">
have added a sentence to address <span>BC's</span> comment, although I feel this is not within
<span>Council's</span> remit. Please feel free to add additional language or make further edits.</span></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;background-color:white">I would be happy to jump on a call to discuss if you think that would be helpful.
</span></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;background-color:white">Kind regards,</span></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black;background-color:white">Pam</span></p></div><div><p class="MsoNormal">------------------------------------------------------------------</p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black">Sender:Marie Pattullo <<a href="mailto:marie.pattullo@aim.be" target="_blank">marie.pattullo@aim.be</a>></span></p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black">Sent At:2020 Jun. 24 (Wed.) 02:07</span></p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black">Recipient:Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org" target="_blank">caitlin.tubergen@icann.org</a>>;
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>></span></p></div><div><p class="MsoNormal"><span style="font-size:14px;font-family:Tahoma,sans-serif;color:black">Subject:Re: [council] For your review: Draft Response - Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations</span></p></div><div><p class="MsoNormal"> </p></div><p class="MsoNormal"><span style="font-size:15px;color:black">Dear Caitlin, dear all</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Many thanks for the attached draft. On behalf of the BC:</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p style="margin-left:24px"><span style="font-size:15px;color:black">1.</span><span style="font-size:9px;font-family:"Times New Roman",serif;color:black">
</span><span style="font-size:15px;color:black">Recommendation CC.1: Our concerns around inaccurate registrant data, of which this is another aspect,are well known – as are those of other parts of the community, including the GAC (noting their comments and
letter during ICANN68).</span></p><p><span style="font-size:15px;font-family:Symbol;color:black">·</span><span style="font-size:9px;font-family:"Times New Roman",serif;color:black">
</span><span style="font-size:15px;color:black">Substance: As the RT said, if the WHOIS record is public then the true status should be on display with the notation: “<i>domain name is suspended due to incorrect data</i>”. Further, in such cases the registrar
should not be able to remove the suspension without receiving confirmation that the data was correct.
</span></p><p><span style="font-size:15px;font-family:Symbol;color:black">·</span><span style="font-size:9px;font-family:"Times New Roman",serif;color:black">
</span><span style="font-size:15px;color:black">Process: while your explanation that the wider subject of accuracy is (unfortunately) not going to be dealt with by the current EPDP is correct, the phrase “<i>If and when the Council decides to request an Issue
Report on data accuracy</i>” is quite dismissive and could be read as this subject being put permanently on ice. In the light of the concerns expressed, inter alia, by the BC and the GAC, could we be more proactive? Suggested amendment:</span></p><p class="MsoNormal" style="margin-left:96px"><span style="font-size:15px;color:black">“<s>If and when</s> [T]he Council
</span><span style="font-size:15px;color:red">is actively discussing the need for, and scope of,
</span><s><span style="font-size:15px;color:black">decides to request</span></s><span style="font-size:15px;color:black"> an Issue Report on data accuracy,
</span><span style="font-size:15px;color:red">in which </span><span style="font-size:15px;color:black">Recommendation CC.1 could be included for consideration, if this item has not been addressed in the next round of contractual negotiations between ICANN
<span>org</span> and the Contracted Parties (as directed by the Board).”</span></p><p class="MsoNormal"> </p><p style="margin-left:24px"><span style="font-size:15px;color:black">2.</span><span style="font-size:9px;font-family:"Times New Roman",serif;color:black">
</span><span style="font-size:15px;color:black">Recommendation CC.4: it should not be contentious that any adopted policy should be measured, audited, tracked, reported and enforced. Unfortunately, many policies have gone into effect without anyone in Compliance
tracking (etc.) whether they are complied with in practice, which does seem to render the effort to adopt those policies as redundant. Not stating that in our reply seems to be a missed opportunity.</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p class="MsoNormal"><span style="font-size:15px;color:black">As ever, we’re happy to discuss this further.</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Best</span></p><p class="MsoNormal"><span style="font-size:15px;color:black">Marie</span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><p class="MsoNormal"><span style="font-size:15px;color:black"> </span></p><div><div style="border-style:solid none none;border-top-width:1px;border-top-color:rgb(225,225,225);padding:0px"><p class="MsoNormal"><b><span style="font-size:15px">From:</span></b><span style="font-size:15px"> council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Caitlin Tubergen<br><b>Sent:</b> Friday, June 12, 2020 12:11 AM<br><b>To:</b> <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br><b>Subject:</b> [council] For your review: Draft Response - Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><b><span style="font-size:15px">SENT ON BEHALF OF COUNCIL LEADERSHIP
</span></b></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Dear Councilors:</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Please find attached a draft response to the ICANN Board re: the two Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations passed through to the GNSO Council from the ICANN Board.</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Keith, Pam, and Rafik have kindly provided a draft for your review.
</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Please review the draft and provide suggested edits (if any) by
<b>Thursday, 25 June</b>. </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Thank you.</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Best regards,</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px">Caitlin Tubergen</span></p><p class="MsoNormal"><span style="font-size:15px">Policy Senior Manager, GNSO Support</span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><p class="MsoNormal"><span style="font-size:15px"> </span></p><div style="border-style:solid none none;border-top-width:1px;border-top-color:rgb(181,196,223);padding:0px"><p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org" target="_blank">caitlin.tubergen@icann.org</a>><br><b>Date: </b>Wednesday, March 18, 2020 at 3:24 PM<br><b>To: </b><<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br><b>Subject: </b>Board action - Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations</span></p></div><div><p class="MsoNormal"><span style="font-size:15px"> </span></p></div><p class="MsoNormal"><b>Sent on behalf of the <span style="color:black">Multi-stakeholder Strategy & Strategic Initiatives (MSSI) department:</span></b></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><b><span style="color:rgb(166,28,0)">Dear GNSO Councillors,</span></b></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">The purpose of this note is to highlight the 25 February 2020 Board action on the Registration Directory Service Review Team (RDS-WHOIS2-RT) Final Recommendations - see
</span><a href="https://www.icann.org/resources/board-material/resolutions-2020-02-25-en" target="_blank"><span style="color:rgb(17,85,204)">https://www.icann.org/resources/board-material/resolutions-2020-02-25-en</span></a><span style="color:black">. </span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">ICANN
<span>org</span> wishes to notify you that the ICANN Board resolved to pass through two recommendations to the GNSO Council, in whole or in part, for your consideration, as documented in the
</span><a href="https://www.icann.org/en/system/files/files/resolutions-board-action-rds-whois2-final-recs-25feb20-en.pdf" target="_blank"><span style="color:rgb(17,85,204)">scorecard</span></a><span style="color:black"> associated with the
</span><a href="https://www.icann.org/resources/board-material/resolutions-2020-02-25-en" target="_blank"><span style="color:rgb(17,85,204)">Board resolution</span></a><span style="color:black">. Specifically, please see below Recommendations CC.1 and CC.4</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><b><span style="color:black">RDS-WHOIS2 Recommendation CC.1</span></b><span style="color:black">:
<i>“The ICANN Board should initiate action intended to ensure that gTLD domain names suspended due to RDS (WHOIS) contact data which the registrar knows to be incorrect, and that remains incorrect until the registration is due for deletion, should be treated
as follows: (1) The RDS (WHOIS) record should include a notation that the domain name is suspended due to incorrect data; and (2) Domain names with this notation should not be unsuspended without correcting the data.”</i></span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><u><span style="color:black">Board resolution</span></u><span style="color:black">: The Board approved this recommendation and directed this item “to be included in the next round of contractual negotiations with
the Contracted Parties”, with a note that “it cannot require or guarantee any negotiation outcomes”. The Board also noted that “this is an area that the GNSO Council might wish to take into a policy development process separate from any recourse to the policy
development process that might be incorporated into the negotiation process”, and passed through this recommendation to the GNSO Council “for purposes of considering such initiation”.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><b><span style="color:black">Recommendation CC.4: “</span></b><i><span style="color:black">The ICANN Board should recommend the GNSO adopt a risk-based approach to incorporating requirements for measurement, auditing,
tracking, reporting and enforcement in all new RDS policies.</span></i><span style="color:black">”</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><u><span style="color:black">Board resolution</span></u><span style="color:black">: The Board passed the recommendation through to the GNSO Council, “with reference to documentation of clarifications received from
RDS-WHOIS2 Implementation Shepherds in the 29 January 2020 discussion with the RDS Board Caucus Group”, i.e. “this recommendation could be directed to the GNSO”.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">Additionally, we would like to highlight the following language of the Board resolution: “in passing this recommendation through, the Board is neither accepting nor rejecting the recommendation.
The Board is careful to respect the remit and roles of the different parts of the ICANN community and is not directing Board or ICANN
<span>org</span> action that would usurp another
<span>group's</span> remit”</span><span style="color:rgb(51,51,51);background-color:white">.</span><span style="color:black"> These recommendations are for your consideration.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><b><u><span style="color:black">Background</span></u></b></p><p class="MsoNormal" style="background-color:white"><span style="font-family:"Times New Roman",serif;color:black"> </span></p><p style="margin:0px 0cm 0pt"><span style="color:black">The Registration Directory Service (RDS) Review is one of the four Specific Reviews anchored in Section 4.6 of the ICANN Bylaws. </span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">The RDS-WHOIS2 Review Team (RDS-WHOIS2-RT) produced 22 final recommendations for Board consideration and released its</span><a href="https://www.icann.org/en/system/files/files/rds-whois2-review-03sep19-en.pdf" target="_blank"><span style="color:rgb(17,85,204)">Final
Report</span></a><span style="color:black"> on 3 September 2019. The RDS-WHOIS2-RT Final Report is the culmination of over two years of work by 11 review team members, representing over 1,000 hours of meetings and countless more hours of work. </span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">As required by</span><a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article4.6" target="_blank"><span style="color:rgb(17,85,204)">section 4.6</span></a><span style="color:black">
of ICANN Bylaws, the Final Report was published for</span><a href="https://www.icann.org/public-comments/rds-whois2-rt-final-report-2019-10-08-en" target="_blank"><span style="color:rgb(17,85,204)">public comment</span></a><span style="color:black">to inform Board
action on the final recommendations.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">The Board took action on each of the 22 recommendations produced by the RDS-WHOIS2-RT
</span><a href="https://www.icann.org/resources/board-material/resolutions-2020-02-25-en" target="_blank"><span style="color:rgb(17,85,204)">https://www.icann.org/resources/board-material/resolutions-2020-02-25-en</span></a><span style="color:black">. The
<span>Board’s</span> action on each recommendation is documented in the scorecard published at
</span><a href="https://www.icann.org/en/system/files/files/resolutions-board-action-rds-whois2-final-recs-25feb20-en.pdf" target="_blank"><span style="color:rgb(17,85,204)">https://www.icann.org/en/system/files/files/resolutions-board-action-<span>rds</span>-whois2-final-<span>recs</span>-25feb20-en.<span>pdf</span></span></a><span style="color:black">.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">We thank you for your collaboration and would welcome any updates on your progress in addressing, as appropriate, these recommendations, to be included into ICANN
<span>org’s</span> reporting. </span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">Please let us know whether you have any questions.</span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">Thank you. </span></p><p class="MsoNormal"> </p><p style="margin:0px 0cm 0pt"><span style="color:black">Best regards,</span></p><p style="margin:0px 0cm 0pt"><span style="color:black"> </span></p><p style="margin:0px 0cm 0pt"><span style="color:black">Multi-stakeholder Strategy & Strategic Initiatives (MSSI) department</span></p><p class="MsoNormal"> </p><p class="MsoNormal"><b> </b></p><div><p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span></p></div></div></div></blockquote><div><br></div></div>_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>