<div dir="ltr">ICANN and RrSG,<div><br></div><div>Acknowledging receipt of this email. Google Registry is working to get answers to the RrSG points and will respond directly.</div><div><br>Crystal</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 12, 2022 at 2:55 PM Camia Frank <<a href="mailto:camia.frank@icann.org">camia.frank@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 lang="EN-US" style="overflow-wrap: break-word;">
<div class="gmail-m_-3606078071610481887WordSection1">
<p class="MsoNormal">Dear Catherine and All,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you to the RrSG for providing the feedback. We did receive both emails, and we will make the necessary adjustments moving forward. To continue this discussion, the registry operator is copied on this thread and can directly respond
to the RrSG with any questions, clarifications, or suggested modifications to the proposed amendments to address the points raised.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Warm Regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Camia Frank<u></u><u></u></p>
<p class="MsoNormal">GDS Service Delivery<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Catherine Merdinger <catherine@identity.digital><br>
<b>Date: </b>Tuesday, July 5, 2022 at 1:17 PM<br>
<b>To: </b>ICANN Global Support Center <<a href="mailto:globalsupport@icann.org" target="_blank">globalsupport@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:secretariat@icannregistrars.org" target="_blank">secretariat@icannregistrars.org</a>" <<a href="mailto:secretariat@icannregistrars.org" target="_blank">secretariat@icannregistrars.org</a>>, "<a href="mailto:rra@icann.org" target="_blank">rra@icann.org</a>" <<a href="mailto:rra@icann.org" target="_blank">rra@icann.org</a>>, "<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>" <<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>>, Andee Hill <<a href="mailto:andee.hill@icann.org" target="_blank">andee.hill@icann.org</a>>, Amanda Fessenden <<a href="mailto:amanda.fessenden@icann.org" target="_blank">amanda.fessenden@icann.org</a>>, Jeanne Gregg
<<a href="mailto:jeanne.gregg@icann.org" target="_blank">jeanne.gregg@icann.org</a>>, Morgan Govaars <<a href="mailto:morgan.govaars@icann.org" target="_blank">morgan.govaars@icann.org</a>>, Danielle Gordon <<a href="mailto:danielle.gordon@icann.org" target="_blank">danielle.gordon@icann.org</a>>, Camia Frank <<a href="mailto:camia.frank@icann.org" target="_blank">camia.frank@icann.org</a>>, Maritza Alarcon <<a href="mailto:maritza.alarcon@icann.org" target="_blank">maritza.alarcon@icann.org</a>>, "<a href="mailto:ondo@google.com" target="_blank">ondo@google.com</a>" <<a href="mailto:ondo@google.com" target="_blank">ondo@google.com</a>><br>
<b>Subject: </b>[Ext] Re: RRA Amendment Notification for Multiple (46) TLDs | Charleston Road Registry Inc. [ ref:_00D616tJk._5004Ms9IBw:ref ]<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">ICANN and Google, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:47.25pt">
<u></u><span style="color:black"><span>1.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Are Google aware of the UK’s IDTA, which effectively replaced/replaces the UK SCCs?</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:47.25pt">
<u></u><span style="color:black"><span>2.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">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?</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:47.25pt">
<u></u><span style="color:black"><span>3.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">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.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:47.25pt">
<u></u><span style="color:black"><span>4.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">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)?</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:47.25pt">
<u></u><span style="color:black"><span>5.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">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><span style="color:black"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thank you,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Catherine<u></u><u></u></p>
</div>
<div>
<div>
<div>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:0in 5.25pt 0in 0in">
<p class="MsoNormal" style="margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)">Catherine Merdinger </span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(19,79,92)">|</span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)"> </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)">Corporate
Counsel </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(19,79,92)">| Identity Digital </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(102,102,102)">Inc.</span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)"> </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(19,79,92)">|</span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)"> </span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)"><a href="tel:(319)%20541-9416" value="+13195419416" target="_blank">+1.319.541.9416</a> </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(19,79,92)">|</span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)"> </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:black">she/her</span><span style="color:rgb(34,34,34)"><u></u><u></u></span></p>
</td>
<td style="padding:0in 5.25pt 0in 0in"></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Mon, Jun 6, 2022 at 5:19 PM Catherine Merdinger <catherine@donuts.email> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">ICANN, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Catherine<br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:0in 5.25pt 0in 0in">
<p class="MsoNormal" style="margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)">Catherine Merdinger </span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)">| </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)">Corporate
Counsel </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)">| </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)">Donuts</span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)"> </span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(102,102,102)">Inc.</span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)"> <b>|</b> </span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)"><a href="tel:(319)%20541-9416" value="+13195419416" target="_blank">+1.319.541.9416</a> </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(61,133,198)">|
</span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:black">she/her</span><u></u><u></u></p>
</td>
<td style="padding:0in 5.25pt 0in 0in"></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">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:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">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<span style="border:1pt solid windowtext;padding:0in"><img border="0" width="32" height="32" style="width: 0.3333in; height: 0.3333in;" id="gmail-m_-3606078071610481887_x0000_i1025" alt="Image removed by sender."></span><br>
<br>
ref:_00D616tJk._5004Ms9IBw:ref<u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><table style="color:rgb(85,85,85);font-family:sans-serif;border:none;border-collapse:collapse"><tbody><tr style="height:0pt"><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Roboto,sans-serif;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:100px;height:100px"><img src="https://lh4.googleusercontent.com/7WGxR1lmIhaL17rYpKav5j3BUoPNHx1_1RBz5lWpK__WzB1IbR_FfowYMfivxgQhKQZljQzP2sSSNPu935hv9B0XDqFyQ72oh2fHFRPAeswYIzAOmAPFb6R1JxLYHuecB-B4DUHp" width="96" height="96" style="margin-left: 0px; margin-top: 0px;"></span></span></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.68;margin-top:0pt;margin-bottom:0pt"><span style="color:rgb(66,133,244);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap"><font face="arial, sans-serif">Crystal Ondo</font></span></p><p dir="ltr" style="line-height:1.68;margin-top:0pt;margin-bottom:0pt"><b style="color:rgb(102,102,102);font-family:arial,sans-serif;font-size:x-small;white-space:pre-wrap">Operations & Policy Lead</b><font color="#666666" face="arial, sans-serif" size="1"><span style="background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><b> </b></span></font></p><p dir="ltr" style="line-height:1.68;margin-top:0pt;margin-bottom:0pt"><font face="arial, sans-serif" size="1"><span style="background-color:transparent;color:rgb(67,67,67);vertical-align:baseline;white-space:pre-wrap">Google Domains & Registry </span><span style="background-color:transparent;color:rgb(67,67,67);white-space:pre-wrap"> </span></font></p><p dir="ltr" style="line-height:1.68;margin-top:0pt;margin-bottom:0pt"><span style="color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><font face="arial, sans-serif" size="1" style="color:rgb(17,85,204)"><a href="mailto:ondo@google.com" style="color:rgb(17,85,204)" target="_blank">ondo@google.com</a></font></span></p></td></tr></tbody></table></div></div>