[Idngwg] Comment on Release for Registration one .COM Domain Name with a Single-Character Label: O.COM

Tue Jun 5 09:01:17 UTC 2018

Dear Edmon,

I will inquire further and get back.

Regards,
Sarmad

From: Idngwg [mailto:idngwg-bounces at icann.org] On Behalf Of Edmon
Sent: Tuesday, June 5, 2018 8:35 AM
To: 'JS Lascary' <jslascary at gmail.com>; 
comments-o-com-single-char-10may18 at icann.org
Cc: idngwg at icann.org
Subject: Re: [Idngwg] Comment on Release for Registration one .COM Domain Name 
with a Single-Character Label: O.COM

This is a very interesting observation.

I suppose you have already made the same observation to the public comment for 
the RSEP previously?

I wonder if Sarmad has any insight into why ICANN concluded that there were no 
security/stability issues?

https://www.icann.org/en/system/files/correspondence/atallah-to-kane-07dec17-en.pdf 
[icann.org] 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_atallah-2Dto-2Dkane-2D07dec17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=fyATwwSpAwK6munc_Z0Xqfqj4pz_6rWQM8tM2g_tLvQ&e=>

It seems to me that perhaps an RSTEP is in order here?

Edmon

From: Idngwg [mailto:idngwg-bounces at icann.org] On Behalf Of JS Lascary
Sent: Tuesday, June 5, 2018 10:24 AM
To: comments-o-com-single-char-10may18 at icann.org 
<mailto:comments-o-com-single-char-10may18 at icann.org>
Cc: idngwg at icann.org <mailto:idngwg at icann.org>
Subject: [Idngwg] Comment on Release for Registration one .COM Domain Name 
with a Single-Character Label: O.COM

It occurred to me that the Registry Service request from the registry 
operator, VeriSign, Inc. (hereinafter the 'Request') is in conflict with 
ICANN's Final Proposed Draft v. 4.0 of the IDN Guidelines  (hereinafter the 
'Guidelines') as published at the following uri 
<https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf 
[icann.org] 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_idn-2Dguidelines-2D10may18-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=rfv44neb7ET8TJy7Ncj7iyAN1ORW9t-Q6pNera2eZCc&e=> 
 >.

Specifically, section 2.5.3 of the Guidelines mentions that :

" TLD registries are encouraged to apply additional constraints on 
registrations that minimize Whole-Script Confusables as determined by Unicode 
Technical Report #36: Unicode Security Considerations 
(http://unicode.org/reports/tr36 [unicode.org] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__unicode.org_reports_tr36&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=4TMNg9naCBn77EwyR_ixZDUI5W7_9-Z6r3Z5-NmGqQo&e=> 
 ) and Unicode Technical Standard #39: Unicode Security Mechanisms 
(http://unicode.org/reports/tr39 [unicode.org] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__unicode.org_reports_tr39&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=Ye4ZDMEwK61eSxECmi7UhGTJJpppdfcKLHwHF_Hbxcc&e=> 
 ). "

In fact, the single character domain name proposed in the Request, o.com 
[o.com] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__o.com&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=8bUXidvqBVV9uCVW6OCtWXfcr1pVQopcH08tynMhbLk&e=> 
(Latin script), is Whole-Script Confusable with xn--0xa.com [xn--0xa.com] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__xn-2D-2D0xa.com&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=S_RiHncYc817gtcNMN0As7zScpDLZ8Ji-ajOisE_4yE&e=> 
(Greek Script) and xn--n1a.com [xn--n1a.com] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__xn-2D-2Dn1a.com&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=XLS880gxjgrvmqhpdiwXyA728yBmqnUoQEFTLDkgjJM&e=> 
(Cyrillic Script). At the time of this comment, the latter two are registered 
in the .com namespace and have been for over 14 years.

Given the above, I would welcome clarifications on the below points for the 
benefit of the entire ICANN community :

(i) What is each stakeholder's position on the matter. I note neither the 
Request nor ICANN's Review of the Request discuss the issue of Whole-Script 
Confusables. Moreover, there is no published policy on Whole-Script 
Confusables for the .com namespace at this time.

(ii) Assuming both the Guidelines and the Amendment to the .com Registry 
Agreement are adopted contemporaneously, will Verisign be required to update 
its .com IDN policy to reflect the Guidelines prior to proceeding with it's 
plan to release any single character domain name.

(iii) What are the "additional constraints on registrations that minimize 
Whole-Script Confusables" envisioned by Verisign.

(iv) In which scenario(s) can the domain name  proposed in the Request, o.com 
[o.com] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__o.com&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=9F-h7YEwVhlxXjDhCipE2CSdBDgneSQkPzxkbqmn3Hw&s=8bUXidvqBVV9uCVW6OCtWXfcr1pVQopcH08tynMhbLk&e=> 
(Latin script), be safely released in accordance with the Guidelines.

Many thanks,

Jean-Sebastien Lascary

cc idngwg at icann.org <mailto:idngwg at icann.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20180605/d31bb55f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5026 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20180605/d31bb55f/smime-0001.p7s>