<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks for attending!<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On 29 Sep 2020, at 18:40, Alejandra Reynoso <alejandra.reynoso@cctld.gt> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Hi Amy and all<div><br></div><div>After reading the most useful explanation given by Amy and after seeing the presentation given by the IFRT in today's webinar, I don't have any objection in removing the sentence in recommendation #4.</div><div><br></div><div>Best regards,</div><div>Alejandra</div><div><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br><div style="font-size:small;color:rgb(7,55,99)"><font face="monospace, monospace">--</font></div><div style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(7,55,99)"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(7,55,99)"><table cellpadding="0" cellspacing="0" style="border-collapse:collapse;font-size:10pt;color:rgb(68,68,68);width:410px;font-family:ARIAL"><tbody><tr><td valign="top" rowspan="6" align="center" style="font-family:Arial;padding:0px 10px 0px 0px;font-size:10pt;border-right:1px solid rgb(0,121,172);width:105px;vertical-align:top;text-align:center"><img alt="Photograph" width="132" border="0" src="https://www.gt/sitio/img/logos/LogoGTyUVG.png" style="border:0px;vertical-align:middle;height:auto;width:132px" data-unique-identifier=""></td></tr><tr><td valign="top" style="font-family:Arial;padding:0px 0px 5px 10px;font-size:10pt;width:305px;vertical-align:top;line-height:25px"><strong><span style="font-size:14pt;color:rgb(0,121,172)">Alejandra Reynoso<br></span></strong><span style="font-size:10pt">Investigación & Desarrollo</span> <span style="font-size:10pt">| </span><span style="font-size:10pt">Dominios .gt</span></td></tr><tr><td valign="top" style="font-family:Arial;padding:5px 0px 5px 10px;font-size:10pt;vertical-align:top"><span><span style="color:rgb(0,121,172)"><strong>P:</strong></span><span style="font-size:10pt"> +502 23688565<br></span></span><span><span style="color:rgb(0,121,172)"><strong>E:</strong></span><span style="font-size:10pt"> <a href="mailto:alejandra.reynoso@cctld.gt" style="color:rgb(17,85,204)" target="_blank">alejandra.reynoso@cctld.gt</a></span></span></td></tr><tr><td valign="top" style="font-family:Arial;padding:5px 0px 5px 10px;font-size:10pt;vertical-align:top;color:rgb(0,121,172)"><span style="font-size:10pt">18 Ave. 11-42 Zona 15, V.H. III.<span><br></span></span><span style="font-size:10pt">Guatemala, Guatemala</span></td></tr><tr><td valign="top" style="font-family:Arial;padding:5px 0px 5px 10px;font-size:10pt;vertical-align:top;color:rgb(0,121,172)"><a href="http://www.gt/" style="color:rgb(0,140,186);background-color:transparent" target="_blank"><span style="font-size:10pt;color:rgb(0,121,172)">www.gt</span></a></td></tr></tbody></table></div><div style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(7,55,99)"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 25, 2020 at 9:59 AM Amy Creamer <<a href="mailto:amy.creamer@icann.org" target="_blank">amy.creamer@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">
<div>
<p class="MsoNormal"><span style="font-size:11pt">Thank you Nigel,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">The IFRT co-chairs were cced on this email, so I will take that discussion up with them!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Your questions and input are very valuable.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Amy<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></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="color:black">From: </span></b><span style="color:black">Nigel Cassimire <<a href="mailto:Nigel.Cassimire@ctu.int" target="_blank">Nigel.Cassimire@ctu.int</a>><br>
<b>Date: </b>Friday, September 25, 2020 at 06:21<br>
<b>To: </b>Amy Creamer <<a href="mailto:amy.creamer@icann.org" target="_blank">amy.creamer@icann.org</a>>, "<a href="mailto:icann-csc@icann.org" target="_blank">icann-csc@icann.org</a>" <<a href="mailto:icann-csc@icann.org" target="_blank">icann-csc@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:ifrt-leadership@icann.org" target="_blank">ifrt-leadership@icann.org</a>" <<a href="mailto:ifrt-leadership@icann.org" target="_blank">ifrt-leadership@icann.org</a>><br>
<b>Subject: </b>RE: [Ext] RE: Letter from the IFRT to the CSC<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Thank you, Amy,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">This background helps a lot. It appears to me then that the substantive justification for the change is that implementation of the requirement has long been recognised as being operationally
impracticable, even since the time of the NTIA contract, and the IFRT is satisfied that its continued inclusion in the bylaws adds no value to the reports. If correct, my suggestion therefore is that this point be brought out more plainly in the explanations
given.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<table border="0" cellspacing="0" cellpadding="0" width="354" style="width:265.25pt;border-collapse:collapse">
<tbody>
<tr style="height:8.5pt">
<td width="354" colspan="3" valign="top" style="width:265.25pt;padding:0in 5.4pt;height:8.5pt">
<p class="MsoNormal"><b><span style="font-size:11pt;color:rgb(46,49,146)">Nigel Cassimire | Ag. Secretary General</span></b><u></u><u></u></p>
</td>
</tr>
<tr style="height:63.85pt">
<td width="78" nowrap="" valign="top" style="width:58.25pt;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><div><image001.jpg></div>[<a href="http://ctu.int" target="_blank">ctu.int</a>]<u></u><u></u></p>
</td>
<td width="228" nowrap="" valign="top" style="width:171pt;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><b><span style="font-size:6pt;color:rgb(46,49,146)"> </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Caribbean </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Telecommunications </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Union </span></b><u></u><u></u></p>
</td>
<td width="48" valign="top" style="width:0.5in;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><div><image002.jpg></div>[<a href="http://facebook.com" target="_blank">facebook.com</a>]
<div><image003.jpg></div>[<a href="http://twitter.com" target="_blank">twitter.com</a>]
<div><image004.jpg></div>[<a href="http://youtube.com" target="_blank">youtube.com</a>]<u></u><u></u></p>
</td>
</tr>
<tr style="height:40pt">
<td width="354" nowrap="" colspan="3" valign="top" style="width:265.25pt;padding:0in 5.4pt;height:40pt">
<p class="MsoNormal"><span style="font-size:10pt;color:rgb(46,49,146)">4 Mary Street, St. Clair<b> |</b> Port of Spain<b> |</b> Trinidad and Tobago
</span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10pt;color:rgb(46,49,146)">Tel:</span></b><span style="font-size:10pt;color:rgb(46,49,146)"> (+1 868) 628-0281 ext. 235
<b>| Fax:</b> (+1 868) 622-6523 Website: </span><span style="font-size:11pt;color:rgb(31,73,125)"><a href="https://urldefense.com/v3/__http:/ctu.int/__;!!PtGJab4!oaopKWHGhelnqs6UdxWcRu5vSEzFd6wrC_tdhqh0KfprvjXZDnzkj4dvpfgbD3eNm0u39sA$" target="_blank"><span style="font-size:10pt">http://ctu.int</span>
[ctu.int]</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;color:rgb(46,49,146)"> </span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt">From:</span></b><span style="font-size:11pt"> Amy Creamer [mailto:<a href="mailto:amy.creamer@icann.org" target="_blank">amy.creamer@icann.org</a>]
<br>
<b>Sent:</b> Friday, September 25, 2020 12:17 AM<br>
<b>To:</b> Nigel Cassimire <<a href="mailto:Nigel.Cassimire@ctu.int" target="_blank">Nigel.Cassimire@ctu.int</a>>; <a href="mailto:icann-csc@icann.org" target="_blank">icann-csc@icann.org</a><br>
<b>Cc:</b> <a href="mailto:ifrt-leadership@icann.org" target="_blank">ifrt-leadership@icann.org</a><br>
<b>Subject:</b> Re: [Ext] RE: Letter from the IFRT to the CSC</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Hi Nigel,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Thank you for your question. Here is the detailed history behind this contractual requirement and why the IFRT recommends removing it:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">This provision is inherited from a requirement that existed in the previous NTIA contract (</span><a href="https://urldefense.com/v3/__https:/www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_and_sacs.pdf__;!!PtGJab4!oaopKWHGhelnqs6UdxWcRu5vSEzFd6wrC_tdhqh0KfprvjXZDnzkj4dvpfgbD3eNGHjLD8o$" target="_blank"><span style="font-size:14pt;font-family:Roboto,serif;background:white">https://www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_and_sacs.pdf</span>
[ntia.doc.gov]</a><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">): "The audit report shall identify each root zone file and root zone “WHOIS” database change request and the relevant policy under which the change was
made as well as identify change rejections and the relevant policy under which the change request was rejected."</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">In implementing this requirement, IANA Services had a discussion with NTIA and noted the lack of specific policies that govern our work to site. The
outcome agreed was that IANA Services would fulfill the requirement by adding boilerplate text that referenced policy sources at a high-level, which can be seen in the very first root audit report in September 2013: All requests were processed according to
RFC 1591, ISO 3166-1, and the GAC Principles. (</span><a href="https://www.iana.org/performance/root-audit/201309" target="_blank"><span style="font-size:14pt;font-family:Roboto,serif;background:white">https://www.iana.org/performance/root-audit/201309</span></a><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">In late 2015, NTIA requested a format change to the report to add a section pertaining to pending delegation and transfer activity. In that process the
format changed and the revised format NTIA agreed to no longer contained that wording, and instead read: “All requests were processed according to relevant policies and procedures.” (</span><a href="https://www.iana.org/performance/root-audit/201512" target="_blank"><span style="font-size:14pt;font-family:Roboto,serif;background:white">https://www.iana.org/performance/root-audit/201512</span></a><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">)”</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">Upon the IANA stewardship transition, the format was modified to remove references to NTIA and the specific provision of the IANA contract (C.5.2), and
in that process the language was tightened slightly but was fundamentally unchanged: “The following requests were implemented during the report period according to the relevant policies and procedures.” (</span><a href="https://www.iana.org/performance/root-audit/201610" target="_blank"><span style="font-size:14pt;font-family:Roboto,serif;background:white">https://www.iana.org/performance/root-audit/201610</span></a><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">The reason this approach was agreed upon is because it is very difficult to directly connect the policy basis for any given change request to a specific
policy. RFC 1591 is an informational document written by former IANA staff that has some concepts in it that are retrospectively deemed policy today, but the specific procedural elements in the document are clearly not in practice today. The GAC Principles
similarly talks in high-level concepts. There is no formal policy that the ccNSO or GNSO has yet developed that specifically applies to the IANA functions. Therefore the aggregate operational tasks IANA implements are essentially derived from the fundamental
tasks that are described in the IANA Naming Function Contract, the execution of which is largely inherited from past practices, and designed to fall within the parameters of these high-level requirements, but are not directly derived from specific policy requirements.<span> </span></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">To give an illustration — if a TLD manager requests to change a telephone number in a WHOIS record in the root zone, it is hard to say where we would
draw a line to a specific policy that governs that, other than broadly that it is consistent with existing policy and in fulfilment of the requirements of the contract. IANA is in full support of transparency, but it is hard to envision a practical way the
audit report could be more specific without fundamental associated changes in the sources of our policies.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">Thank you,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Roboto,serif;color:black;background:white">Amy</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><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="color:black">From: </span></b><span style="color:black">Nigel Cassimire <</span><a href="mailto:Nigel.Cassimire@ctu.int" target="_blank">Nigel.Cassimire@ctu.int</a><span style="color:black">><br>
<b>Date: </b>Thursday, September 24, 2020 at 18:43<br>
<b>To: </b>Amy Creamer <</span><a href="mailto:amy.creamer@icann.org" target="_blank">amy.creamer@icann.org</a><span style="color:black">>, "</span><a href="mailto:icann-csc@icann.org" target="_blank">icann-csc@icann.org</a><span style="color:black">" <</span><a href="mailto:icann-csc@icann.org" target="_blank">icann-csc@icann.org</a><span style="color:black">><br>
<b>Cc: </b>"</span><a href="mailto:ifrt-leadership@icann.org" target="_blank">ifrt-leadership@icann.org</a><span style="color:black">" <</span><a href="mailto:ifrt-leadership@icann.org" target="_blank">ifrt-leadership@icann.org</a><span style="color:black">><br>
<b>Subject: </b>[Ext] RE: Letter from the IFRT to the CSC</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Dear Amy,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Thanks for this. I am really not clear on the merits of the proposed change.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">The explanations given are “it is a legacy statement from the NTIA contract that is no longer required” and also “Since the IANA Stewardship Transition, any change request may fall under more
than one policy, and the initial purpose of this requirement adds no value to the reports.”</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Looking back at the audit reports though (</span><a href="https://www.iana.org/performance/root-audit" target="_blank"><span style="font-size:11pt">https://www.iana.org/performance/root-audit</span></a><span style="font-size:11pt;color:rgb(31,73,125)">
), up ‘til November 2015 the tabulated list of changes was headed with a statement that read in part: “All requests were processed according to RFC 1591, ISO 3166-1, and the GAC Principles” which (i) I assume identified the relevant policies in accordance
with the existing bylaw and (ii) already seems to me to identify multiple applicable policies. Since December 2015 however, which I think well precedes the stewardship transition, the statement has been amended to more vaguely say: “…..according to the relevant
policies and procedures”. So unless I’m looking in the wrong place, which is entirely possible, it appears that specific policies have not been identified in the monthly reports since December 2015.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Identification of the governing policy(ies) seems a simple and informative inclusion in the report to my mind. If however there is a useful operational reason for the current practice that justifies
the proposed bylaw change, I’m not seeing it in the letter provided.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">I long to be guided.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)">Regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<table border="0" cellspacing="0" cellpadding="0" width="354" style="width:265.25pt;border-collapse:collapse">
<tbody>
<tr style="height:8.5pt">
<td width="354" colspan="3" valign="top" style="width:265.25pt;padding:0in 5.4pt;height:8.5pt">
<p class="MsoNormal"><b><span style="font-size:11pt;color:rgb(46,49,146)">Nigel Cassimire | Ag. Secretary General</span></b><u></u><u></u></p>
</td>
</tr>
<tr style="height:63.85pt">
<td width="78" nowrap="" valign="top" style="width:58.25pt;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><div><image005.jpg></div>[<a href="http://ctu.int" target="_blank">ctu.int</a>]<u></u><u></u></p>
</td>
<td width="228" nowrap="" valign="top" style="width:171pt;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><b><span style="font-size:6pt;color:rgb(46,49,146)"> </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Caribbean </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Telecommunications </span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(46,49,146)">Union </span></b><u></u><u></u></p>
</td>
<td width="48" valign="top" style="width:0.5in;padding:0in 5.4pt;height:63.85pt">
<p class="MsoNormal"><div><image006.jpg></div>[<a href="http://facebook.com" target="_blank">facebook.com</a>]
<div><image007.jpg></div>[<a href="http://twitter.com" target="_blank">twitter.com</a>]
<div><image008.jpg></div>[<a href="http://youtube.com" target="_blank">youtube.com</a>]<u></u><u></u></p>
</td>
</tr>
<tr style="height:40pt">
<td width="354" nowrap="" colspan="3" valign="top" style="width:265.25pt;padding:0in 5.4pt;height:40pt">
<p class="MsoNormal"><span style="font-size:10pt;color:rgb(46,49,146)">4 Mary Street, St. Clair<b> |</b> Port of Spain<b> |</b> Trinidad and Tobago
</span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10pt;color:rgb(46,49,146)">Tel:</span></b><span style="font-size:10pt;color:rgb(46,49,146)"> (+1 868) 628-0281 ext. 235
<b>| Fax:</b> (+1 868) 622-6523 Website: </span><a href="https://urldefense.com/v3/__http:/ctu.int/__;!!PtGJab4!rcr0wzPQEuSb9d_4bbvIyfWAVs2ngmZ62cgoVr5xdDL2nOZPvmA0SEq82cDureNKOEF6_0g$" target="_blank"><span style="font-size:10pt">http://ctu.int</span><span style="font-size:11pt">
[ctu.int]</span></a><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;color:rgb(46,49,146)"> </span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt">From:</span></b><span style="font-size:11pt"> ICANN-CSC [</span><a href="mailto:icann-csc-bounces@icann.org" target="_blank"><span style="font-size:11pt">mailto:icann-csc-bounces@icann.org</span></a><span style="font-size:11pt">]
<b>On Behalf Of </b>Amy Creamer<br>
<b>Sent:</b> Monday, September 21, 2020 2:13 PM<br>
<b>To:</b> </span><a href="mailto:icann-csc@icann.org" target="_blank"><span style="font-size:11pt">icann-csc@icann.org</span></a><span style="font-size:11pt"><br>
<b>Cc:</b> </span><a href="mailto:ifrt-leadership@icann.org" target="_blank"><span style="font-size:11pt">ifrt-leadership@icann.org</span></a><span style="font-size:11pt"><br>
<b>Subject:</b> [ICANN-CSC] Letter from the IFRT to the CSC</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Dear CSC,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Please find attached a letter providing more detail on the IFRT’s Recommendation that will remove a line from the IANA Naming Functions Contract.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">In addition, the IFRT will be hosting a webinar on 29 Sept 2020 to introduce their recommendations to the community prior to the Public Comment. The IFRT would appreciate you sharing this announcement with
your constituencies:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><a href="https://urldefense.com/v3/__https:/www.icann.org/news/announcement-2020-04-30-en__;!!PtGJab4!rcr0wzPQEuSb9d_4bbvIyfWAVs2ngmZ62cgoVr5xdDL2nOZPvmA0SEq82cDureNK9Um7Zpw$" target="_blank"><span style="font-size:11pt">https://www.icann.org/news/announcement-2020-04-30-en
[icann.org]</span></a><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Thank you for your time and attention to this matter.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Amy Creamer</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Sr. Project Manager</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Office of the Chief Technical Officer (OCTO)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Internet Corporation for Assigned Names and Numbers (</span><a href="https://urldefense.com/v3/__http:/www.icann.org/__;!!PtGJab4!rcr0wzPQEuSb9d_4bbvIyfWAVs2ngmZ62cgoVr5xdDL2nOZPvmA0SEq82cDureNK95ysGLI$" target="_blank"><span style="font-size:11pt">ICANN
[icann.org]</span></a><span style="font-size:11pt">)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Mobile: +1 424-537-8917</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Direct Line: +1 310-578-8910</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Email: </span><a href="mailto:amy.creamer@icann.org" target="_blank"><span style="font-size:11pt">amy.creamer@icann.org</span></a><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
ICANN-CSC mailing list<br>
<a href="mailto:ICANN-CSC@icann.org" target="_blank">ICANN-CSC@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/icann-csc" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/icann-csc</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>
<span>_______________________________________________</span><br><span>ICANN-CSC mailing list</span><br><span>ICANN-CSC@icann.org</span><br><span>https://mm.icann.org/mailman/listinfo/icann-csc</span><br><span></span><br><span>_______________________________________________</span><br><span>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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.</span></div></blockquote></body></html>