<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsolistparagraph, li.xmsolistparagraph, div.xmsolistparagraph
{mso-style-name:x_msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:100494313;
mso-list-template-ids:1366717254;}
@list l0:level1
{mso-level-start-at:7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:362098913;
mso-list-template-ids:-789570536;}
@list l1:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:435953943;
mso-list-template-ids:1052966096;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:683020800;
mso-list-template-ids:1558211576;}
@list l3:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:792990140;
mso-list-template-ids:447513492;}
@list l5
{mso-list-id:899756628;
mso-list-template-ids:372278212;}
@list l5:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6
{mso-list-id:989555579;
mso-list-template-ids:469801696;}
@list l6:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7
{mso-list-id:1067537072;
mso-list-template-ids:-390710118;}
@list l7:level1
{mso-level-start-at:6;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8
{mso-list-id:1492865139;
mso-list-template-ids:1200666844;}
@list l8:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9
{mso-list-id:1596093819;
mso-list-template-ids:-1994079976;}
@list l9:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10
{mso-list-id:1671637066;
mso-list-template-ids:-1025708136;}
@list l10:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11
{mso-list-id:1723092464;
mso-list-template-ids:-2097532700;}
@list l11:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear ICANN, all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Apologies for being a day late. Please find below the RrSG response to BOTH the Non-Afilias AND the Afilias related TLD RRA amendment batches. This response is in lieu of responding to each individually.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="xmsonormal">We applaud Donuts’ efforts to come up with a common form of agreement to cover all of their numerous TLDs, including those formerly operated by Afilias. That said, there are a number of areas which have raised some concerns amongst registrars.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal"><u>Donuts Agreements (Non-Afiias TLDs)</u><o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l4 level1 lfo1">
The Preamble to the new RRA contains references to a “Terms and Conditions” document which is now explicitly incorporated into the main RRA. Unfortunately, unlike the main RRA, the Terms and Conditions document can be amended and/or modified with or without
notice (as determined by Donuts).<o:p></o:p></li></ol>
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
The Terms and Conditions document not only contains some additional details regarding Sunrise, Landrush, General Availability, DPML, etc., but also includes a number of additional elements normally reserved for the RRA itself including (a) additional reps and
warranties, (b) additional limitations of liability (for Donuts only), essentially wiping out any meaningful recovery (c) Additional provisions on confidentiality, (d) and additional items that amount to “Material Breach” not included in the RRA.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
There are also many definitions that are in the RRA, that are subsequently defined in the Ts and Cs document often with very different definitions making it difficult to understand which definition is applicable.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
Although the Ts and Cs do state that the terms of the RRA control where there are conflicts, the issue is that Donuts’ additional rights, disclaimers and limitations in the Ts and Cs document may not be viewed as conflicting, but rather as a supplement to their
rights and obligations.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
Again, the Ts and Cs for each of the services can be changed at Donuts’ discretion without notice by simply posting a copy of the new Ts and Cs on their Website.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
Despite not being required to give the registrars notice of any changes, the Ts and Cs are very clear that
<b>failure to include all of the relevant Ts and Cs in Registrars’ agreements with registrants would be a Material Breach</b> by the Registrar and result in a suspension of services by the Registry.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l8 level2 lfo2">
<b>The primary concern we had was that Donuts’ can essentially get around the requirement to have amendments to the RRA reviewed by ICANN and/or the registrars by simply always putting new Ts and Cs on their website and calling them changes to the Ts and Cs
and not the RRA. The new requirements and legal conditions are binding on the Registrars without any notice and are required to be passed through by registrars to registrants.</b><o:p></o:p></li></ol>
</ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;line-height:105%">
<o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l11 level1 lfo3">
Section 3.2 of the proposed RRA now adds a reference to Donuts’ “Acceptable Use Policy.” This Acceptable Use Policy is on Donuts website and can be changed with or without notice to the Registrars by simply posting the new AUP on its Website.
<b><i>Donuts now also adds that it is the Registrar that is primarily responsible for handling remediation and takedowns for abuse activities in violation of Donuts’ AUP.</i></b><o:p></o:p></li></ol>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l5 level2 lfo4">
To summarize, this new AUP is created by Donuts, can say whatever Donuts wants it to say, can change without notice, but it is the Registrars’ responsibility to enforce this policy.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l5 level2 lfo4">
Donuts also adds a reference to other “Registry Policies” which also can change without notice, and also becomes the Registrars’ responsibility to enforce.<o:p></o:p></li></ol>
</ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;line-height:105%">
<o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l10 level1 lfo5">
Similarly, Section 3.3 formerly required Registrars to have a registration agreement in place with registrants stating the normal things that Registrars are required to have in the Agreement.<o:p></o:p></li></ol>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l1 level2 lfo6">
However, <b>Donuts has added a requirement to “reasonably enforce” this Registration Agreement.</b><o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l1 level2 lfo6">
Two concerns here:<o:p></o:p></li></ol>
</ol>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="2" type="a">
<ol style="margin-top:0in" start="1" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l2 level3 lfo7">
Donuts now potentially can find registrars in material breach if it believes the registrar is NOT enforcing its registration agreement.<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l2 level3 lfo7">
Donuts also includes their “AUP” and other (undefined) “Registry Policies” in this provision making it clear that Registrars must enforce all Donuts’ policies (which can change with or without notice by placing a new version on its website).<o:p></o:p></li></ol>
</ol>
</ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:1.0in;line-height:105%">
<o:p></o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l9 level1 lfo8">
<u>Section 3.5</u>. Donuts has added a new right to suspend Registrars “to ensure ongoing operation of a secure, stable, and reliant registry system.” There is no definition in the RRA as to what this means.<o:p></o:p></li></ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;line-height:105%">
<b> </b><o:p></o:p></p>
<ol style="margin-top:0in" start="5" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l6 level1 lfo9">
<u>Section 3.6</u> now requires Registrars to get permission to use, copy, etc. of registrant’s personal data in the way that Donuts’ sets out in its “Donuts Privacy Policy.”
<o:p></o:p></li></ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;line-height:105%">
<b> </b><o:p></o:p></p>
<ol style="margin-top:0in" start="5" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l3 level2 lfo10">
There is no other information about Donuts’ Privacy Policy other than it being on their Website. Again, this policy can change with or without notice to Registrars (who are now responsible for enforcing Donuts’ policy)<o:p></o:p></li><li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l3 level2 lfo10">
There is no reference in this section to the Data Processing Addendum, but simply a requirement that Registrars ensure that Registrars’ get permission from their customers for Donuts to use the data however it sees fit in its Privacy Policy.<o:p></o:p></li></ol>
</ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;line-height:105%">
<b> </b><o:p></o:p></p>
<ol style="margin-top:0in" start="6" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l7 level1 lfo11">
<u>Section 3.9</u> – now gives Donuts the right to suspend a registrar temporarily due to “excessive failed domain create requests”. There is no definition of what it considers “excessive.” Although there is a provision 7.2 in the Ts and Cs where it states
that Donuts can suspend a Registrar for submitting 1,000+ failed domain creates in any 24 hour period. Is “excessive” supposed to mean 1,000 or something else?
<o:p></o:p></li></ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;line-height:105%">
<b> </b><o:p></o:p></p>
<ol style="margin-top:0in" start="7" type="1">
<li class="xmsolistparagraph" style="margin-top:0in;margin-bottom:0in;line-height:105%;mso-list:l0 level1 lfo12">
<u>Section 6.1.1</u>: Now adds an indemnification obligations for Registrars to indemnify Donuts for any “threatened” claim as opposed to just “actual” claims. This needs to be evaluated by individual legal teams.<o:p></o:p></li></ol>
<p class="xmsolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:8.0pt;margin-left:.5in;line-height:105%">
<b> </b><o:p></o:p></p>
<p class="xmsonormal"><u>Donuts (Afilias Related TLD)</u><o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">The former Afilias TLDs now owned and operated by Donuts have all of the above issues, however, Unlike the above Donuts TLDs, these TLDs have never had a “Terms and Conditions” document. The Registrars do not want to see any additional
Terms and Conditions document that add any legal terms and conditions to an RRA unless those terms and conditions are (a) consistent with the RRA terms and (b) can only be changed in the manner in which RRAs are changed.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">It is unfair for registries to be allowed to add legal terms and conditions above and beyond those in their RRA in a separate document when those Terms and Conditions can be changed at their discretion without notice and which we, as registrars,
are required to not only follow but enforce. We see this as nothing more than a way to circumvent the RRA requirements and the process by which those terms may be amended.
<o:p></o:p></p>
<p class="xmsonormal"><o:p> </o:p></p>
<p class="xmsonormal">Please let me know if you have any questions regarding this response and/or if you would like to discuss further.
<o:p></o:p></p>
<p class="xmsonormal"><o:p> </o:p></p>
<p class="xmsonormal">Thanks,<o:p></o:p></p>
<p class="xmsonormal"><o:p> </o:p></p>
<p class="xmsonormal">Ashley Heineman<o:p></o:p></p>
<p class="xmsonormal">Chair, RrSG<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Rob Gomez <robert.gomez@icann.org> <br>
<b>Sent:</b> Friday, August 27, 2021 3:39 PM<br>
<b>To:</b> Ashley Heineman <aheineman@godaddy.com>; ICANN Global Support Center <globalsupport@icann.org>; secretariat@icannregistrars.org; rra@icann.org<br>
<b>Cc:</b> Andee Hill <andee.hill@icann.org>; Andrew Dickson <andrew.dickson@icann.org>; Jeanne Gregg <jeanne.gregg@icann.org>; Camia Frank <camia.frank@icann.org>; dessa@donuts.email<br>
<b>Subject:</b> Re: [Ext] RE: Amendment Notification for Afilias Limited [ ref:_00D616tJk._5004MjmOWG:ref ]<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid #B94A48 4.5pt;padding:0in 0in 0in 14.0pt">
<p class="MsoNormal" style="background:#F2DEDE"><span style="font-family:"Tahoma",sans-serif;color:#B94A48">Caution:</span><span style="color:black">
</span><span style="font-family:"Tahoma",sans-serif;color:#B94A48">This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span><o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">Dear Ashley,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thank you for the follow-up message to inform us that you require additional review time. We approve your request for an extension beyond the original due date.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">We look forward to hearing back from you by <u>Monday, 11 October 2021</u>.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Rob Gomez</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">GDS Service Delivery</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"<a href="mailto:aheineman@godaddy.com">aheineman@godaddy.com</a>" <<a href="mailto:aheineman@godaddy.com">aheineman@godaddy.com</a>><br>
<b>Date: </b>Friday, August 27, 2021 at 10:20 AM<br>
<b>To: </b>ICANN Global Support Center <<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a>>, "<a href="mailto:secretariat@icannregistrars.org">secretariat@icannregistrars.org</a>" <<a href="mailto:secretariat@icannregistrars.org">secretariat@icannregistrars.org</a>>,
"<a href="mailto:rra@icann.org">rra@icann.org</a>" <<a href="mailto:rra@icann.org">rra@icann.org</a>><br>
<b>Cc: </b>Andee Hill <<a href="mailto:andee.hill@icann.org">andee.hill@icann.org</a>>, Andrew Dickson <<a href="mailto:andrew.dickson@icann.org">andrew.dickson@icann.org</a>>, Jeanne Gregg <<a href="mailto:jeanne.gregg@icann.org">jeanne.gregg@icann.org</a>>,
Rob Gomez <<a href="mailto:robert.gomez@icann.org">robert.gomez@icann.org</a>>, Camia Frank <<a href="mailto:camia.frank@icann.org">camia.frank@icann.org</a>>, "<a href="mailto:dessa@donuts.email">dessa@donuts.email</a>" <<a href="mailto:dessa@donuts.email">dessa@donuts.email</a>><br>
<b>Subject: </b>[Ext] RE: Amendment Notification for Afilias Limited [ ref:_00D616tJk._5004MjmOWG:ref ]<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Due the high volume of RRA Amendment Notification Requests and the corresponding amount of time necessary to conduct a proper review, the RrSG requests and extension of 45 days.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you in advance.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ashley Heineman<o:p></o:p></p>
<p class="MsoNormal">Chair, RrSG<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ICANN Global Support Center <<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a>>
<br>
<b>Sent:</b> Thursday, August 5, 2021 1:43 PM<br>
<b>To:</b> <a href="mailto:secretariat@icannregistrars.org">secretariat@icannregistrars.org</a>;
<a href="mailto:rra@icann.org">rra@icann.org</a>; Ashley Heineman <<a href="mailto:aheineman@godaddy.com">aheineman@godaddy.com</a>><br>
<b>Cc:</b> <a href="mailto:andee.hill@icann.org">andee.hill@icann.org</a>; <a href="mailto:andrew.dickson@icann.org">
andrew.dickson@icann.org</a>; <a href="mailto:jeanne.gregg@icann.org">jeanne.gregg@icann.org</a>;
<a href="mailto:robert.gomez@icann.org">robert.gomez@icann.org</a>; <a href="mailto:camia.frank@icann.org">
camia.frank@icann.org</a>; <a href="mailto:dessa@donuts.email">dessa@donuts.email</a><br>
<b>Subject:</b> Amendment Notification for Afilias Limited [ ref:_00D616tJk._5004MjmOWG:ref ]<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid #B94A48 4.5pt;padding:0in 0in 0in 14.0pt">
<p class="MsoNormal" style="background:#F2DEDE"><span style="font-family:"Tahoma",sans-serif;color:#B94A48">Caution:</span><span style="color:black">
</span><span style="font-family:"Tahoma",sans-serif;color:#B94A48">This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span><o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<div>
<p class="MsoNormal">Hello Ashley, <br>
<br>
Attached, please find the cover letter and the red-lined RRA Amendments for 22 TLDs submitted by <b>Afilias Limited</b> to be shared with your Stakeholder Group.<br>
<br>
Please respond by <u>23:59 UTC on Thursday, 26 August 2021</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:solid windowtext 1.0pt;padding:0in"><img border="0" width="1" height="1" style="width:.0083in;height:.0083in" id="_x0000_i1025" src="cid:~WRD1956.jpg" alt="Image removed by sender."></span><br>
<br>
ref:_00D616tJk._5004MjmOWG:ref <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>