<div dir="ltr">ICANN,<div><br></div><div>The RrSG has the following requests for clarification and potentially changes to the proposed RRAs submitted by XYZ. The RRA Review Team of the RrSG would be happy to discuss any of these requests with the registry, if that would be beneficial.</div><div><br></div><div>Thanks,</div><div>Catherine</div><div><br></div><div><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif">1.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The RrSG requests that the registry add back language that was deleted from Section 9.6(vi) which would require notification to the Disclosing Party if the Receiving Party is required by law to disclose the Disclosing Party’s Confidential Information. The specific language that was deleted is below:</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">a.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>"provided, that in the event the Receiving Party is required by Iaw, regulation or court order to disclose any of Disclosing Party's Confidential information, Receiving Party will promptly notify Disclosing Party in writing prior to making any such disclosure in order to facilitate Disclosing Party seeking a protective order or other appropriate remedy from the proper authority, at the Disclosing Party's expense. Receiving Party agrees to cooperate with Disclosing Party in seeking such order or other remedy. Receiving Party further agrees that if Disclosing Party is not successful in precluding the requesting legal body from requiring the disclosure of the Confidential Information, it will furnish only that portion of the Confidential Information that is legally required."</font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif"><br></font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif">2.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>While the RrSG is aware that the text of Section 5(b) of the Data Processing Addendum is from the Temporary Specification DPA model terms, we do have concerns about the referenced SCCs no longer being applicable to data transfers from the UK, which is no longer part of the European Union. Will the registry be incorporating the UK SCCs for UK based registrars party to the RRA to ensure the lawful transfer of data?</font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif"><br></font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif">3.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The RrSG requests clarification regarding Section 5.9.6 and the data elements listed there. Is the registry operator stating that “Public Access to Data on Registered Names” (subsection v) is a data element that “Registrar shall submit to, or shall place in the Registry Database via the Registry System”? Similarly, subsection vi. and vii. do not appear to list specific data elements for submission to the registry system. Furthermore, can you please confirm that the data elements listed in subsection vii. are consistent with the Board-approved EPDP Phase 1 recommendations?</font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif"><br></font></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif">4.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The RrSG requests clarification regarding text that appears to be erroneously repeated in Sections 6.3 and 6.5. The screenshot below shows the repeated texts highlighted. The repeated language also seems to contradict the language contained in Section 8.3.</font></p><font face="arial, sans-serif"><img src="cid:ii_l29eujus0" alt="image.png" width="450" height="147"></font><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif"><br></font></p><p class="MsoNormal" style="margin:0in"></p><p style="margin:0in 0in 0in 0.5in"><font face="arial, sans-serif">5.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>The RrSG noted the following typos that we would request be corrected before the agreement is finalized:</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">a.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>There are two section 4.4.1s</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">b.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>We believe there is text missing at the beginning of 5.5.3 (the section seems to pick up in the middle of a sentence)</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">c.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Section 5.13 is duplicative of Section 5.5</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">d.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Sections 8.1 and 8.3 contradict each other regarding the Term of the RRA; please confirm which section is correct and remove redundant language.</font></p><p style="margin:0in 0in 0in 1in"><font face="arial, sans-serif">e.<span style="font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;line-height:normal"> </span>Section 19 contains an extraneous “a” (“This <u>a</u> Agreement may be executed…”)</font></p><p class="MsoNormal" style="margin:0in"><font face="arial, sans-serif"> </font></p><p class="MsoNormal" style="margin:0in"><font face="arial, sans-serif">Finally, the RrSG is requesting that all registry operators going forward refrain from submitting as their redlined version of the existing RRA showing the proposed changes, a version that simply deletes the old RRA and inserts the text of the new RRA. This style of redline is not useful in our review of the changes and may delay our response. Instead, the RrSG requests that registry operators run a comparison of the current RRA against the proposed new RRA (or use some other method of tracking the changes to each section). Of course, if a registry operator has questions about what style of redline is most helpful to the RrSG, the RRA Review Team would be happy to consult as they prepare their documents. In the future, the RrSG will be unable to complete our review until the correct redlines are submitted by the registry operator.</font></p><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><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 Thu, Apr 7, 2022 at 10:43 AM 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">Thanks, ICANN. Confirming receipt on behalf of the RrSG.<div><br></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 Thu, Apr 7, 2022 at 10:31 AM 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 clear="none">
<br clear="none">
Attached, please find the cover letter and the red-lined RRA Amendment for the following TLD(s) submitted by <b><a href="http://XYZ.COM" target="_blank">XYZ.COM</a>, LLC</b> to be shared with your Stakeholder Group:
<ul>
<li><b>.audio</b></li>
<li><b>.christmas</b></li>
<li><b>.diet</b></li>
<li><b>.flowers</b></li>
<li><b>.game</b></li>
<li><b>.guitars</b></li>
<li><b>.hosting</b></li>
<li><b>.lol</b></li>
<li><b>.mom</b></li>
<li><b>.pics</b></li>
</ul>
Please respond by 23:59 UTC on <u><b>Thursday, 28 April 2022</b></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 clear="none">
<br clear="none">
Warm Regards,<br clear="none">
<br clear="none">
Camia Frank<br clear="none">
GDS Service Delivery<img src="https://icann-nsp.my.salesforce.com/servlet/servlet.ImageServer?oid=00D610000006tJk&esid=0184M00000PF5KL&from=ext"><br><br>ref:_00D616tJk._5004Mr4Eps:ref</div>
</blockquote></div>
</blockquote></div>