<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:CenturyGothic;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:19940409;
mso-list-template-ids:160834260;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:973486266;
mso-list-type:hybrid;
mso-list-template-ids:-866885578 -349252040 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.75in;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:3.25in;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.75in;
text-indent:-9.0pt;}
@list l2
{mso-list-id:1993483259;
mso-list-template-ids:641789290;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hello —during today’s meeting some of you referred to the DNS stability review process as the function to determine whether an applied-for string if deemed fit for the root zone. I also observed that we might
want to focus on the very limited function of the RZ-LGR, and to deal with contention sets and other evaluation procedures later on.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">To that end, I looked at the old applicant guide book and searched for the DNS stability: string requirements (2.2.1.3.2). Basically, string requirements is broken down into three parts: Part I (technical
requirements for all labels, Part II (requirements for IDNs), and Part III (policy requirements for gTLDs).
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The RZ-LGR, I believe, is meant to “replace” or “automate” Parts I and II of the string requirements review process (a copy of the text is down below for your reference). In addition to those functions, also
helps with the calculation of variant labels, so that the applicants don’t have to come up with IDN variant rules of their own.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The difference between the prior AGB and the RZ-LGR (if adopted), are
</span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:.25in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt">that the latter starts with a smaller universe of “valid” letters. Before RZ-LGR, virtually all protocol valid code points were available to be used
in a TLD string (with exception of course of hyphen and digits). The RZ-LGR starts with a smaller repertoire than IDNA2008 (i.e. Maximal Starting Repertoire) which is further limited by each script generation panel. The result of each generation panel’s work
is merged into the RZ-LGR. So, one applicant might challenge the RZ-LGR’s results because it did not accept one letter, or a combination or some script rule. This should be okay to challenge, but the process by which the applicant finds resolution would be
through the established LGR procedure (i.e. make the case for inclusion of a new letter or rule) to maintain the stability of the RZ-LGR.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:.25in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt">the RZ-LGR is designed to calculate the variant labels. The prior DNS stability review process did not do that; applicants were asked to provide these
self-identified variant labels.</span><o:p></o:p></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I hope this helps the discussion.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dennis</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p><b><i><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Part I -- Technical Requirements for all Labels (Strings)
</span></i></b><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">– The technical requirements for top-level domain labels follow.
</span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo2">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.1 The ASCII label (i.e., the label as transmitted on the wire) must be valid as specified in technical standards
<i>Domain Names: Implementation and Specification </i>(RFC 1035), and <i>Clarifications to the DNS Specification
</i>(RFC 2181) and any updates thereto. This includes the following: </span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<p style="margin-left:.75in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.1.1 The label must have no more than 63 characters.
</span><o:p></o:p></p>
<p style="margin-left:.75in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.1.2 Upper and lower case characters are treated as identical.
</span><o:p></o:p></p>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo2">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.2 The ASCII label must be a valid host name, as specified in the technical standards
<i>DOD Internet Host Table Specification </i>(RFC 952), <i>Requirements for Internet Hosts — Application and Support
</i>(RFC 1123), and <i>Application Techniques for Checking and Transformation of Names (RFC 3696), Internationalized Domain Names in Applications (IDNA)(RFCs 5890-5894), and any updates thereto.
</i>This includes the following: </span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<p style="margin-left:.25in;text-indent:.5in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.2.1 The ASCII label must consist entirely of letters (alphabetic characters a-z), or
</span><o:p></o:p></p>
<p style="margin-left:.25in;text-indent:.5in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">1.2.2 The label must be a valid IDNA A-label (further restricted as described in Part II below).
</span><o:p></o:p></p>
<p><b><i><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">Part II -- Requirements for Internationalized Domain Names
</span></i></b><o:p></o:p></p>
<p><i><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">– </span></i><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">These requirements apply only to prospective top-level domains that contain non-ASCII characters. Applicants
for these internationalized top-level domain labels are expected to be familiar with the Internet Engineering Task Force (IETF) IDNA standards, Unicode standards, and the terminology associated with Internationalized Domain Names.
</span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1 The label must be an A-label as defined in IDNA, converted from (and convertible to) a U-label that is consistent with the definition in IDNA, and further restricted by the following, non-exhaustive,
list of limitations: </span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1.1 Must be a valid A-label according to IDNA.
</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1.2 The derived property value of all codepoints used in the U-label, as defined by IDNA, must be PVALID or CONTEXT (accompanied
</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1.3 The general category of all codepoints, as defined by IDNA, must be one of (Ll, Lo, Lm, Mn, Mc).
</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1.4 The U-label must be fully compliant with Normalization Form C, as described in
<i>Unicode Standard Annex #15: Unicode Normalization Forms. </i>See also examples in
<span style="color:blue">http://unicode.org/faq/normalization.html</span>. </span>
<o:p></o:p></p>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.1.5 The U-label must consist entirely of characters with the same directional property, or fulfill the requirements of the Bidi rule per RFC 5893.
</span><o:p></o:p></p>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.2 The label must meet the relevant criteria of the ICANN
<i>Guidelines for the Implementation of Internationalised Domain Names</i>. See <span style="color:blue">
http://www.icann.org/en/topics/idn/implementation-guidelines.htm</span>. This includes the following, non- exhaustive, list of limitations:
</span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.2.1 All code points in a single label must be taken from the same script as determined by the Unicode Standard Annex #24: Unicode Script Property (See
<span style="color:blue">http://www.unicode.org/reports/tr24/</span>). </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"CenturyGothic",serif">2.2.2 Exceptions to 2.2.1 are permissible for languages with established orthographies and conventions that require the commingled use of multiple scripts. However,
even with this exception, 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 are clearly defined.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>