<html><head><meta http-equiv="content-type" content="text/html; charset=GB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; font-family: ΢ÈíÑźÚ; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><body>
<div><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="font-family: ΢ÈíÑźÚ; font-size: 10.5pt; line-height: 1.5; background-color: window;">we make the following comments to </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">"Recommendations for Managing IDN Variant Top-Level Domains" published by ICANN at https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-en:</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><o:p></o:p></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">1. In order to </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">¡°</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">avoid including variant TLDs in a manner that would create user vulnerabilities or a probability of confusion</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">¡±</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">, and to ensure the healthy and stable operation of the domain name system, we agree with ICANN recommendations: IDN variant TLDs {t1, t1v1, ¡} allocated to the same entity, same second level labels under IDN variant TLDs s1.{t1, t1v1, ¡} registered to the same entity, and Second-level variant labels under IDN variant TLDs {s1, s1v1, ¡}.{t1, t1v1, ¡} registered to the same entity.</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;color:rgb(216,216,216);font-size:10.5000pt;mso-font-kerning:1.0000pt;"><o:p></o:p></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">2. According to the premise that </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">¡°</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">Active IDN variant TLDs should be minimized¡±, we agree to strictly manage the IDN variant TLDs, and the IDN variant TLDs should be applied by each IDN registry based on actual conditions. </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><o:p></o:p></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-indent: 0pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">3. We recommend that t</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">he registr</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">y</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> of </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">IDN variant TLDs should</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">d</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">evelop</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">its own registration</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> and price</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> policy</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> </span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">for the second-level domain</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"> under IDN variant TLDs, under the principle that "Same second level labels under IDN variant TLDs s1.{t1, t1v1, ¡} registered to the same entity".</span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-indent: 0pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">In addition, the management of the IDN variant TLDs and its second level labels follows the management of the primary domain name. It is recommended to pay only the primary domain name management fees to ICANN. For example, the primary IDN TLD is t1, and the variant TLD is t1v1, then only pay ICANN the management fee for t1. In the case of Chinese IDN variant TLDs. Chinese includes Simplified Chinese and Traditional Chinese. Without considering the simplified and traditional form of second-level domain, registrants need to register "s.t1" and "s.t1v1" two domain names, and may pay 2 registration fees. In this case, it is likely that the registrant will only select one of the domain names to register. After all, another domain name will be reserved for the same registrant. This registration policy is not conducive to the common development of Simplified Chinese domain names and Traditional Chinese domain names.</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><o:p></o:p></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-indent: 0pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">4. We agree that "IDN variant TLDs {t1, t1v1, ¡} allocated to the same entity", but we disagree that "each variant label in a set should be a separate TLD application". For example, Simplified Chinese is simplified from Traditional Chinese. These two Chinese characters are corresponding; And Simplified Chinese and Traditional Chinese are distributed in different regions, they are coexisting and intersecting. The simplified and traditional form of a Chinese domain name is like the capitalization and lower case of an English domain name. It should not be a separate TLD application.</span><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><o:p></o:p></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">5. We recommend that the IDN Variant TLD application can apply Fast Track Requests. As long as IDN TLDs and their variant labels defined by the RZ-LGR, it is eligible for application. If the existing IDN TLD operates compliance with ICANN's operating standards for registries, and promises to comply with the basic principle of "Recommendations for managing IDN variant TLDs", the application complying with RZ-LGR shall get the approval and delegation.</span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;"><br></span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><span style="mso-spacerun:'yes';font-family:΢ÈíÑźÚ;font-size:10.5000pt;mso-font-kerning:1.0000pt;">Best Regards,</span></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-size: 10.5pt;"><br></p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-size: 10.5pt;">Lisa Liang</p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-size: 10.5pt;">KNET Co., Ltd.</p><p class="MsoNormal" style="margin: 0pt 0pt 0.0001pt; text-align: justify; font-family: Calibri; font-size: 10.5pt;"><br></p></div>
</body></html>