<div dir="ltr">ICANN and Google,<div><br></div><div>Thank you for the opportunity to review the redlined DPA for the Google TLDs. The RrSG has two points of substantive feedback and one note where we believe there to be a typographical error. You will find the specific questions for Google below, but primarily the request is to incorporate the UK SCCs (apparently now the UK IDTA) for registrars, where applicable. We understand that the Temporary Specification DPA text does not include a reference to the UK SCCs/IDTA, but as events have evolved, we'd ask the registries consider including them going forward.</div><div><br></div><div>Google folks - please let me know if you think it would be helpful to talk any of the questions below through or if you are comfortable making the requested changes without further conversation.</div><div><br></div><div><ol start="1" type="1" style="margin-bottom:0cm;color:rgb(0,0,0);margin-top:0cm"><li class="MsoNormal" style="margin-left:15px"><span style="font-size:10pt;font-family:Arial,sans-serif">Are Google aware of the UK’s IDTA, which effectively replaced/replaces the UK SCCs?<u></u><u></u></span></li><li class="MsoNormal" style="margin-left:15px"><span style="font-size:10pt;font-family:Arial,sans-serif">Are they aware of the 21 September 2022 deadline for using the UK SCCs after which the IDTA must be used to ensure appropriate safeguards for UK to US data transfers?<u></u><u></u></span></li><li class="MsoNormal" style="margin-left:15px"><span style="font-size:10pt;font-family:Arial,sans-serif">If yes to the above, would it make sense to try and incorporate the UK IDTA into the DPA in some form now to future-proof the DPA and save Google from amending and the RRA Team re-reviewing the RRA from 22 September onwards? This can be done similar to how they have incorporated the EU SCCs and UK SCCs.<u></u><u></u></span></li><li class="MsoNormal" style="margin-left:15px"><span style="font-size:10pt;font-family:Arial,sans-serif">To assist with future proofing, we would ask if Google would be willing to consider adding “or their successors” to Sections 2 (d) and (n)?<u></u><u></u></span></li><li class="MsoNormal" style="margin-left:15px"><span style="font-size:10pt;font-family:Arial,sans-serif">References in Section 5 (a) (ii.) and (iii.) need to be updated – both Sections refer to Section 5 (b)(i) but it appears this should be updated to Section 5 (a)(i).</span></li></ol><div><font color="#000000" face="Arial, sans-serif"><span style="font-size:13.3333px"><br></span></font></div><div>Thank you,<font color="#000000" face="Arial, sans-serif"><span style="font-size:13.3333px"><br></span></font></div><div>Catherine</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><table style="color:rgb(34,34,34);padding:0px;margin:10px 0px;border:none"><tbody><tr><td style="vertical-align:middle;padding:0px 7px 0px 0px"><b style="color:rgb(51,51,51);font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial">Catherine Merdinger </span></b><b style="font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial"><font color="#134f5c">|</font></span><span style="color:rgb(61,133,198);font-size:9pt;font-family:Arial"> </span></b><span style="color:rgb(51,51,51);font-size:9pt;font-family:Arial">Corporate Counsel </span><b style="font-family:"Times New Roman";font-size:16px"><font color="#134f5c"><span style="font-size:9pt;font-family:Arial">|</span><span style="font-size:9pt;font-family:Arial"> </span><span style="font-size:9pt;font-family:Arial">Identity Digital</span><span style="font-size:9pt;font-family:Arial"> </span></font></b><span style="font-size:9pt;font-family:Arial;color:rgb(102,102,102)">Inc.</span><span style="font-size:9pt;font-family:Arial"><font color="#3d85c6"> </font><b><font color="#134f5c">|</font></b><font color="#3d85c6"> </font></span><span style="color:rgb(51,51,51);font-size:9pt;font-family:Arial">+1.319.541.9416 </span><span style="font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial"><b><font color="#134f5c">|</font><font color="#3d85c6"> </font></b><font color="#000000">she/her</font></span></span><br></td><td style="vertical-align:middle;padding:0px 7px 0px 0px"></td></tr></tbody></table><div><p></p></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 6, 2022 at 5:19 PM Catherine Merdinger <catherine@donuts.email> 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 dir="ltr">ICANN,<div><br></div><div>I can confirm receipt on behalf of the RrSG. However, noting the upcoming ICANN meeting, we would like to prospectively request a one-week extension for our review, for a new response deadline of July 5, 2022 (noting the July 4 holiday in the US). Please let me know if this is acceptable to you.</div><div><br></div><div>Thanks,</div><div>Catherine<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><table style="padding:0px;margin:10px 0px;border:none"><tbody><tr><td style="vertical-align:middle;padding:0px 7px 0px 0px"><b style="color:rgb(51,51,51);font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial">Catherine Merdinger </span></b><b style="color:rgb(51,51,51);font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial;color:rgb(61,133,198)">| </span></b><span style="color:rgb(51,51,51);font-size:9pt;font-family:Arial">Corporate Counsel </span><b style="color:rgb(51,51,51);font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial;color:rgb(61,133,198)">| </span></b><b style="color:rgb(51,51,51);font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial"></span></b><span style="font-size:9pt;font-family:Arial;color:rgb(61,133,198)">Donuts</span><span style="color:rgb(51,51,51);font-size:9pt;font-family:Arial"> </span><span style="font-size:9pt;font-family:Arial;color:rgb(102,102,102)">Inc.</span><span style="font-size:9pt;font-family:Arial;color:rgb(61,133,198)"> <b>|</b> </span><span style="color:rgb(51,51,51);font-size:9pt;font-family:Arial">+1.319.541.9416 </span><span style="font-family:"Times New Roman";font-size:16px"><span style="font-size:9pt;font-family:Arial"><b style="color:rgb(61,133,198)">| </b><font color="#000000">she/her</font></span></span><br></td><td style="vertical-align:middle;padding:0px 7px 0px 0px;text-align:left">
</td></tr></tbody></table>
</div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 6, 2022 at 5:11 PM ICANN Global Support Center <<a href="mailto:globalsupport@icann.org" target="_blank">globalsupport@icann.org</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>Hello Ashley,<br>
<br>
Attached, please find the cover letter and the red-lined RRA Amendment for multiple (46) TLDs submitted by Charleston Road Registry Inc. to be shared with your Stakeholder Group:<br>
<br>
As indicated in their cover letter, Charleston Road Registry Inc. has shared a separate amendment (which they have labeled as “RRA SCC Data Processing Addendum Amendment”) of how they will incorporate the proposed changes with existing registrars. We are including this amendment for the RrSG’s consideration in its review.<br>
<br>
Please respond by 23:59 UTC on <u>Monday, 27 June 2022</u> to let us know if your Stakeholder Group has concerns, does not have concerns, or if additional review time is required. If the Stakeholder Group has concerns, ICANN org will continue with the next step of the RRA Amendment Procedure, which is to consult with the RrSG and the Registry Operator to attempt to resolve any such concerns.<br>
<br>
Warm Regards,<br>
<br>
Camia Frank<br>
GDS Service Delivery<img src="https://icann-nsp.my.salesforce.com/servlet/servlet.ImageServer?oid=00D610000006tJk&esid=0184M00000Q9lYA&from=ext"><br><br>ref:_00D616tJk._5004Ms9IBw:ref</div>
</blockquote></div>
</blockquote></div>