<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2/8/2019 8:10 PM, John Levine wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20190209041033.42007200E09690@ary.qy">
<pre class="moz-quote-pre" wrap="">In article <a class="moz-txt-link-rfc2396E" href="mailto:370933817.844561549679203331.JavaMail.root@mx2.datainfosys.com"><370933817.844561549679203331.JavaMail.root@mx2.datainfosys.com></a> you write:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">-=-=-=-=-=-
Dear All,
ICANN announced the release of the Recommendations for Managing Internationalized Domain Name (IDN) Variant Top-Level Domains (TLDs) as a collection of six documents.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Keep in mind that this is just about what (if any) variants to allow as TLDs. It's not very
relevant to the variants of registered names within contracted domains.
For example, TLDs can't contain digits, but registered names can.
</pre>
</blockquote>
<p><font face="Candara">The focus on "variants" is a bit misleading
here. The Root Zone LGR effort covers <b>repertoire selection</b>
and <b>required context rules</b> as well as the <b>definition
of variants</b>. This will be even more apparent when the next
batch of scripts gets added.</font></p>
<p>Now, the Root Zone has some specific restrictions, particularly
the "letter principle" which restricts the allowable repertoire to
"letters" and therefore excludes digits and hyphen for ASCII (or
their analogues for other scripts - even if PVALID).</p>
<p>However, the various script LGRs for the Root Zone constitute an
excellent starting point and reference for any LGR for other
public zones in the same script. Relaxing the restrictions to
allow digits, for example, would constitute a rather minor effort
compared to the work that went into researching and refining the
repertoire, each involving teams up to thirty linguists and
technical experts depending on the script, sometimes working over
several years.</p>
<p>In some case, the respective panel analyzed the requirements of
almost 200 different languages to arrive at a repertoire that
maximizes the coverage for meaningful mnemonics while excluding
unused, unfamilar and other risky, yet unneeded characters.</p>
<p>Just because they are not "turn-key" for some other zone is a
poor reason to disregard their value as reference and starting
points.</p>
<p>A./</p>
<p>PS: any public zone supporting more than one script would be
well-advised to study and implement the cross-script variants
defined in the RZ-LGR.<br>
</p>
</body>
</html>