[Idngwg] call today - 2 Feb. 2017

Thu Feb 2 09:26:08 UTC 2017

Thanks Edmon.

The changes have been incorporated in the attached document.  We will use
this version for our call today.

Regards,

Sarmad

From: Edmon Chung [mailto:edmon at registry.asia] 
Sent: Thursday, February 02, 2017 2:02 PM
To: Sarmad Hussain <sarmad.hussain at icann.org>; idngwg at icann.org
Subject: [Ext] RE: [Idngwg] Summary of meeting on 26 Jan. 2017

Hi Everyone,

please find a rough draft for 4th part (with minor edits to part 1) as
discussed from last meeting:

======================================================

2.7       Similarity and Confusability of Labels

...

Commingling of cross-script code points in a single IDN label
(recommendation 5, version 3) 

All code points in a single label must be taken from the same script as
determined by the Unicode Standard Annex #24: Script Names
http://www.unicode.org/reports/tr24[unicode.org]
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unicode.org_reports
_tr24&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPca
wI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=vs67oSzdoKg1I8yXSeEulH7Yxcufd2VTpR6oqGOVaIM
&s=ztaPF-opuZl1GG3Qr6GxanJ3or_kOwASxeQsoWC6ca4&e=> . Exceptions to this
guideline are permissible for languages with established orthographies and
conventions that require the commingled use of multiple scripts. 

....

Harmonization of variant rules across same-script IDN tables

...

Cross-script homoglyph labels

...

Limitations of IDN tables and policies

In the case of any exceptions made allowing mixing of scripts, visually
confusable characters from different scripts will not be allowed to co-exist
in a single set of permissible code points unless a corresponding policy and
character table is clearly defined.  TLD registries should also consider
policies for visually confusable characters within a same script.
Nevertheless, it is important to understand that not all visual confusing
similarity issues can be addressed by IDN tables, LGRs and policies.  Other
policies such as dispute resolution policies may be necessary to mitigate
against abusive registrations exploiting visually similar characters.  For
example, even for Latin LDH repertoire, whereas the digit "0" and letter
"O", or the capital letter "I", small letter "l" and digit "1", may be
considered visually confusable characters the mitigation policy for abuse is
often addressed by dispute resolution policies, leveraging other bodies of
knowledge (e.g. Trademark Law) to evaluate whether similarities between
names causes confusion and abuse.

======================================================

Also, my apologies, I will not be able to join the call today.

Edmon

From: idngwg-bounces at icann.org <mailto:idngwg-bounces at icann.org>
[mailto:idngwg-bounces at icann.org] On Behalf Of Sarmad Hussain
Sent: Wednesday, 1 February 2017 01:28 AM
To: idngwg at icann.org <mailto:idngwg at icann.org> 
Subject: [Idngwg] Summary of meeting on 26 Jan. 2017

Dear All, 

Please find attached the summary of the meeting of the WG on 26 Jan.  Please
let me know if there are any changes or suggestions.

The meeting has the following AIs:

S. No.

Action Items 

Owner

1

Draft the additional fourth part of the recommendation by splitting the
first recommendation on comingling cross-script code points on addressing
similarity cases

EC

2 

>From 20170119 -  Update recommendation on grandfathering current
registrations based on the discussion

KF

The next meeting is scheduled for Thursday 2 Feb. 2017 11am UTC. We will
continue following a weekly meeting schedule.

The attached notes of the meeting and the recording of the meeting are
available at the IDNGWG wiki page at
https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commun
ity.icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di
splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u
3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-
mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKByc
MzrAZTgn8xXAy86zJg9CEjjI&e=> . 

Regards,
Sarmad 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20170202/e953e2cd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IDN Guidelines 4.0 20170202.pdf
Type: application/pdf
Size: 530009 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20170202/e953e2cd/IDNGuidelines4.020170202-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IDN Guidelines 4.0 20170202.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 42697 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20170202/e953e2cd/IDNGuidelines4.020170202-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5046 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20170202/e953e2cd/smime-0001.p7s>