[Latingp] New version of Proposal for inclusion Latin script letters in next version of MSR

Fri Jan 19 15:36:15 UTC 2018

Bill,

Some comments on your document:

Click sounds are uncommon in European languages (but they are common sounds in non-verbal communication), but velar stops are very common, e.g. "k" (https://en.wikipedia.org/wiki/Voiceless_velar_stop). Implossives are, however an example of sounds uncommon in European languages, e.g. https://en.wikipedia.org/wiki/Voiced_bilabial_implosive. For that U+0253 ("ɓ") is often used.

I think that you mean RFC 6912 (https://tools.ietf.org/html/rfc6912). I think it is incorrect, or not fully proper, to say that the RFC "DISALLOWs" anything. (There is an IDN property "DISALLOWED" meaning something else.) The RFC is an "Informational" RFC, which means that it is not a formal standard.

It is IAB of IETF that stands behind the RFC. There probably other decisions on the way to IP. IP has interpret things in their way to come to the conclusion that limits our working group.

You write that the RFC disallows "the use of punctuation marks in domain names". The IDNA standard, as specified in RFC 5892, almost all code points classified in Unicode as "punctution" is alread DISALLOWED. What you mean is that other code points, often being modifier letters in Unicode, but identical or resembling a punctuation should not be use, especially not in TLD names, according to RFC 6912.

It is not fully clear that "ǃ" (U+U01C3), being a homoglyph of "!" (U+0021) would create a larger security risk than allowing confusingly similar characters without variant control, e.g. "ĕ" (U+0115) and "ě" (U+0118).

Yours,
Mats

---
Mats Dufberg
DNS Specialist, IIS
Mobile: +46 73 065 3899
https://www.iis.se/en/

From: Latingp <latingp-bounces at icann.org> on behalf of Bill Jouris <bill.jouris at insidethestack.com>
Reply-To: Bill Jouris <bill.jouris at insidethestack.com>
Date: Friday 19 January 2018 at 01:11
To: Latin GP <latingp at icann.org>
Subject: Re: [Latingp] New version of Proposal for inclusion Latin script letters in next version of MSR

Hello all,

Earlier this week, I had been drafting a possible Appendix D for our final report, to discuss the overall issue of clicks and stops.  (And it is a VERY rough draft.  Note, for example, that the various RFCs and other documents are not yet identified.)

With this reply from the IP, it seems like the question may be better addressed in comments on MSR-3.  But I have attached what I had for those who may be interested.

Bill Jouris
Inside Products
bill.jouris at insidethestack.com
831-659-8360
925-855-9512 (direct)

From: Sarmad Hussain <sarmad.hussain at icann.org>
To: Mirjana Tasić <Mirjana.Tasic at rnids.rs>; Latin GP <latingp at icann.org>
Cc: "integrationpanel at icann.org" <integrationpanel at icann.org>
Sent: Wednesday, January 17, 2018 10:00 PM
Subject: Re: [Latingp] New version of Proposal for inclusion Latin script letters in next version of MSR

Dear Mirjana, Latin GP members,

Please find below the message from the Integration Panel.

Regards,
Sarmad

=========

The IP is pleased to acknowledge the input from the Chinese, Japanese and Latin GPs to the MSR-3 update of the Maximal Starting Repertoire. MSR-3 has just been released for public comment<https://www.icann.org/public-comments/msr-3-2018-01-17-en> and contains an updated listing of code points as well as the rationale for including or excluding particular code points. Based on the input received, the IP has extended the list of source sets for the Han ideographs with the net effect of adding three code points. The IP has added three Latin code points because new evidence provided invalidated the original rationale for their exclusion. An additional three Latin code points representing clicks were not included because the original rationale for their exclusion remains valid. For details see the overview document of MSR-3.

Integration Panel

1.      MSR-3 (HTML<https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-15jan18-en.html>, XML<https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-15jan18-en.xml>)
2.     MSR-3-Annotated-Hangul-Tables<https://www.icann.org/en/system/files/files/msr-3-hangul-15jan18-en.pdf> [PDF, 1.12 MB]
3.     MSR-3-Annotated-Han-Tables<https://www.icann.org/en/system/files/files/msr-3-han-15jan18-en.pdf> [PDF, 39 MB]
4.     MSR-3-Annotated-non-CJK-Tables<https://www.icann.org/en/system/files/files/msr-3-non-cjk-15jan18-en.pdf> [PDF, 2.16 MB]
5.     MSR-3-Overview and Rationale<https://www.icann.org/en/system/files/files/msr-3-overview-15jan18-en.pdf> [PDF, 1.1 MB]

From: Mirjana Tasić [mailto:Mirjana.Tasic at rnids.rs]
Sent: Tuesday, January 09, 2018 11:07 PM
To: Sarmad Hussain <sarmad.hussain at icann.org>
Cc: Latin GP <latingp at icann.org>
Subject: [Ext] New version of Proposal for inclusion Latin script letters in next version of MSR

Dear Sarmad,

After further investigation of Latin Repertoire, Latin GP has found one additional code point which is not included in our previous proposal for inclusion in the new version of MSR.

Please find enclosed the new version of our Proposal for inclusion Latin script letters in the next version of MSR.

Regards Mirjana

_______________________________________________
Latingp mailing list
Latingp at icann.org<mailto:Latingp at icann.org>
https://mm.icann.org/mailman/listinfo/latingp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180119/1b8e4cd9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 192 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180119/1b8e4cd9/image001-0001.png>