<div dir="ltr"><div dir="ltr"><font face="arial, sans-serif">Dear all , </font></div><div dir="ltr"><font face="arial, sans-serif"><br></font></div><div dir="ltr"><font face="arial, sans-serif">For <span id="gmail-docs-internal-guid-bdc19c01-7fff-02bc-baea-8371cb09adb0" style=""><span style="color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;vertical-align:baseline">1.2.1</span><span style="color:rgb(0,0,0);background-color:transparent;font-weight:700;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;vertical-align:baseline"><span class="gmail-Apple-tab-span" style="text-wrap: nowrap;"> </span></span><span style="color:rgb(0,0,0);background-color:transparent;font-weight:700;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;vertical-align:baseline">3-letter ASCII Combinations : </span></span></font></div><div><font face="arial, sans-serif"><br>I am still under the impression that the 3-letter ISO3166 code is prohibited, primarily based on GAC Helsinki Communique : </font></div><div><font face="arial, sans-serif"><br></font></div><font face="arial, sans-serif"><i>20160630_GAC ICANN 56 Communique_FINAL [1].pdf
</i></font><div class="gmail-page" title="Page 9">
<div class="gmail-layoutArea">
<div class="gmail-column">
<p><font face="arial, sans-serif"><i>Use of 3-letter codes in the ISO-3166 list as gTLDs in future rounds
a. The GAC advises the ICANN Board to:
</i></font></p>
<ol style="list-style-type:lower-roman">
<li style="">
<p><font face="arial, sans-serif"><i>encourage the community to continue in depth analyses
and discussions on all aspects related to a potential use of
3-letter codes in the ISO-3166 list as gTLDs in future rounds,
in particular with regard to whether such a potential use is
considered to be in the public interest or not.
</i></font></p>
</li>
<li style="">
<p style=""><font face="arial, sans-serif" style=""><i>keep current protections in place for 3-letter codes in the
ISO-3166 list in place and not to lift these <b style="">unless future in-
depth discussions involving the GAC and the other ICANN
constituencies would lead to a consensus</b> that use of these
3-letter codes as TLDs would be in the public interest. </i></font></p>
</li>
</ol>
</div>
</div>
</div><div>The SubPro WT-5 report should have remained the same position, but please correct me if I am wrong or missing something. </div><div><br></div><div>Thank you very much ! </div><div><br></div><div>Best,</div><div><br></div><div>Ching </div><div><br></div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 22, 2023 at 2:43 PM Michael Karakash <<a href="mailto:michael.karakash@icann.org">michael.karakash@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 class="msg60167860161686539">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_60167860161686539WordSection1">
<p class="MsoNormal">Dear IRT Members,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We are pleased to share the proposed language of the AGB's <a href="https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/Jll2-6qcW7Y8-PT6lZ3q7W6ldx3C2YgNsrW6GLBSN6m4ZS4W105DGy64ThRgW5YKxHf25qFgQW1Ql6BW1sy4lGW4PY3tG36181vW91nN0t6HW9M0W3_cwQ_3cR1nkW8RkypX2pk_l7W3wlXnz6R7v_1W4SWp4Y80QxZXW8t7Jpx3NbKpcW7sHGMj8QjrXmW6bBRJb1G7VZ7V-dVKl3nRjKmW189dL02H5f72W3H7fmr8p2prZN4qR09pClmH2W6Yynj84tNgM9W2lfCMJ21D0b1VHVlHn4WsFcdW17r8s_5nChxcW7-SjVt5vTFhjW3t09kh3VzYp4N6kk1ZvkX3McW7M449V3TkPP6f6zlZnd04" target="_blank">
Reserved Names</a> section based on the Board-adopted recommendations in Topic 21 of the
<a href="https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/JjT4YGXpW50kH_H6lZ3m6W7LMkp214l24KW4ZtJJy1-mYxFW1QcpJM61YzJjV2Gc3Z4Qgn71VLkqZ59d6_ZfN1Gw5M4jTTc5W6N7kSd3jGLGxW7kYMx899kpnBW4mSxZm530Vb4W2VXcTl923ll-W79jrxF2-tvpXW32n9xV7kMhsLW4_FQqw4YSN0FVVrQf_7pW11vW7nm3wY17DzV9N2ycxqPJxb09W8pTGgb7w27MbW70ybMf3Zh4y7Vvg6f32k4hrmW8ZDmP91HQk67W4sPJK91VJQVGW3TrPfL8kB3wPV11Bt27Vj6c_W7WtrVd3y4v_WW5JjPTj48B8QsW8hhL3L8knPp0VjZ2lW8sh07QN8757r88fGwfN5M9vB4x1YbcW3XH7hx7lXFNdW2yw9FQ1_pKLFW83KNCn1l27xhf7rvCPH04" target="_blank">
Final Report</a>.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Additionally, the agenda and a PDF version of the document for Tuesday’s discussion are accessible
<a href="https://t.sidekickopen53.com/Ctc/DL+23284/cFFT304/Jl22-6qcW7lCdLW6lZ3lNW8FRg433fVMqlW3lrckB7_CV7nW1p2v8N5dmJrJW1rWwCb25MKb6W7xfmQZ1sN9R4W6tW3J73QsylhW5dfstq2ZWQ53N1Bj4krTXpymN6jcxKz8FQJvW2N7mm56BPgxXV9xf3v4MYKFWW5zcmjC7lWNr1W20tft-6lQ1HlW47_76z1SRwtYW1TTYyq7H9MBXN2XXXykfZDpmW3D5ym726bmWCW3F3JWs9h6F_QW22GlJf6zR6qPW6kDGvR2Gr_yYW2ylDq84yZy-JW35rdMF3pg04vW8Qw2mg93XNFRVq9RY47Bc91_d2tdCs04" target="_blank">here</a>.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">If you have any questions or concerns, please feel free to reach out.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Michael<u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
SubPro-IRT mailing list<br>
<a href="mailto:SubPro-IRT@icann.org" target="_blank">SubPro-IRT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/subpro-irt" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/subpro-irt</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.</div></blockquote></div><img src="https://t.sidekickopen53.com/Cto/DL+23284/cFFT304/R5R8b44n-N7sxJ772fJ6NW1V3lf51_kbDdW3F6K2t1XmJNkW1GdphK1YXSBVW3LFF0W3GLbtlW3GLy9020W67zn22X86K4W1" alt="" style="display:none!important" height="1" width="1"><div></div></div>