<div><span class="Apple-style-span" style="font-family: Garamond; "><h1 style="font-size: 18pt; "><br></h1><div style="margin-top: 0px; margin-bottom: 0px; "><br><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
</p><hr><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "></p><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
to reduce the opportunities for attacks via the encoding system.</blockquote>=><div style="margin-top: 0px; margin-bottom: 0px; ">[Reword]</div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; ">
<b>Rationale.</b> I don't know what "the encoding system" means here, so I can't even suggest any replacement text.<blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
<br></blockquote><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
The information given in this section is provided to make the rules, tables, and protocol easier to understand. It is not normative. </blockquote><div style="margin-top: 0px; margin-bottom: 0px; ">=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
This document is not normative. The information given in this document is provided to make IDNA2008 easier to understand, and provide background information for why changes were made from IDNA2003.</blockquote><div style="margin-top: 0px; margin-bottom: 0px; ">
[AND move to the end of Section 1.1]</div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><b>Rationale.</b> Make it clear that not just that section is not normative.</div>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Characters that are placed in the "PROTOCOL-VALID" category are never removed from it unless the code points themselves are removed from Unicode (such removal would be inconsistent with the Unicode stability principles (see [Unicode51], Appendix F) and hence should never occur).</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; ">=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Characters that are placed in the "PROTOCOL-VALID" category are expected to never be removed from it or reclassified. While theoretically characters could be removed from Unicode, such removal would be inconsistent with the Unicode stability principles (see [Unicode51], Appendix F) and hence should never occur.</blockquote>
<b><div style="margin-top: 0px; margin-bottom: 0px; "><br></div>Rationale. </b>Use the same language for PROTOCOL-VALID as for DISALLOWED ("expected to never"), since "never" alone is a promise that can't be kept. Reword the Unicode issue for clarity.<div style="margin-top: 0px; margin-bottom: 0px; ">
<br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Only the former are fully tested at lookup time.</blockquote>=><br><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Only the former require full testing at lookup time.</blockquote><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><b>Rationale. </b>Wording as spec (see other note).</div>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Some characters are sufficiently problematic for use in IDNs that they should be excluded for both registration and lookup (i.e., IDNA- conforming applications performing name lookup should verify that these characters are absent; if they are present, the label strings should be rejected rather than converted to A-labels and looked up.</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; ">=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Some characters are inappropriate for use in IDNs and are thus excluded for both registration and lookup (i.e., IDNA- conforming applications performing name lookup should verify that these characters are absent; if they are present, the label strings should be rejected rather than converted to A-labels and looked up. Some of these characters are problematic for use in IDNs (such as the FRACTION SLASH character), while some of them (such as the HEART symbol) simply fall outside the conventions for typical identifiers (basically letters and numbers).</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><b>Rationale. </b>For only an miniscule fraction of the characters that were in unmapped in IDNA2003 and illegal in IDNA2008 is there any evidence of being "problematic". Also the "should be" language is more appropriate for a proposal, not describing the current spec. The above wording makes clear the main reason for this break in compatibility, while noting the problematic nature of some characters. Also supplies some concrete examples (we could use more of that!).</div>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; ">Note that this is in line with text further down, where it does have a breakdown into two categories "some because they are actively dangerous in URI, IRI, or similar contexts and others because there is no evidence that they are important enough to..."</div>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
If a character is classified as "DISALLOWED" in error and the error is sufficiently problematic, the only recourse would be either to introduce a new code point into Unicode and classify it as "PROTOCOL-VALID" or for the IETF to accept the considerable costs of an incompatible change and replace the relevant RFC with one containing appropriate exceptions.</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; ">=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
If a character is classified as "DISALLOWED" when it should not have been, there are two possible recourses:<br>(a) Replace the relevant RFC with one containing appropriate exceptions, accepting a change that many people feel to have considerable costs.<br>
(b) Propose a new character in Unicode that would be identical (except for its behavior in IDNA), which would be extremely unlikely to be accepted, since it would violate Unicode and ISO policies on duplicate encoding.<br>
<br><br></blockquote><b>Rationale.</b> Reflect reality. There is no particular consensus that changing DISALLOWED to PVALID would in fact have such costs. However, because some people do feel that is to be the case, we can certainly reflect that opinion here. We also don't want to hold out false hope that Unicode/ISO would do a duplicate encoding just for the purpose of IDNA.<br>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; ">
<br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
For example, it is generally believed that labels containing characters from more than one script are a bad practice although there may be some important exceptions to that principle.</blockquote><div style="margin-top: 0px; margin-bottom: 0px; ">
=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
For example, labels containing characters from more than one script are problematic where those characters can cause problems of visual confusion, such as using a Cyrillic character for "a" -- which looks exactly like a Latin "a" -- in the midst of an otherwise Latin label. In other cases, mixing scripts may be perfectly acceptable, such as using Latin letters in the midst of Chinese characters.<br>
<br></blockquote><b>Rationale. </b>Use concrete examples of problems.<br><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Other issues in domain name identification and processing arise because IDNA2003 specified that several other characters be treated ...<br>[[anchor16: Above text is a substitute for an earlier (pre -01) version and is hoped to be more clear. Comments and improvements welcome.]]</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; "><span style="font-family: Times; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><font size="2">=></font></span></pre>
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><font size="2">[Remove]</font></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span class="Apple-style-span" style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><font size="2"><span class="Apple-style-span" style="font-weight: bold; ">Rationale. </span>Unless at least one example of a concrete problem can be provided, this needs to be removed. What is wrong with changing the Regex for recognizing a URL from using [.] as the label delimiter to using [.。｡﹒．] (that is, [\x{002E}\x{FF0E}\x{FE52} \x{3002}\x{FF61}])?</font></span></pre>
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; "><hr></span></pre></span></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Highly Localized Preprocessing.</blockquote><div style="margin-top: 0px; margin-bottom: 0px; "><span style="font-family: Times; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; ">=><br>[Remove this section and reword neighboring text. ]</span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span class="Apple-style-span" style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><b>Rationale.</b> Major security issue (see notes on protocol).</span></pre>
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; "><hr></span></pre></span></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
Anyone looking up a label in a DNS zone is required to <br>...<br>o Avoid validating other contextual rules about characters, including mixed-script label prohibitions, although such rules may be used to influence presentation decisions in the user interface. </blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; "><span style="font-family: Times; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; ">=><br>
[Remove last clause. Add editorial note that this needs to be reviewed against final text in protocol.]</span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><b>Rationale. </b>The protocol does not, and should not, <span class="Apple-style-span" style="font-weight: bold; ">*require*</span> someone <span class="Apple-style-span" style="font-weight: bold; "><span class="Apple-style-span" style="font-style: italic; ">not to validate</span></span> that a purported U-Label is actually a U-Label!! Secondly, this and any other place in the document that reiterates what protocol requires needs to be marked to be verified before publication for accuracy, so that items like this don't mistakenly get through.</span></pre>
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span style="font-family: Garamond; white-space: normal; "><br></span></pre><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; "><hr></span></pre></span></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
characters are permanently excluded</blockquote><div style="margin-top: 0px; margin-bottom: 0px; "><span style="font-family: Times; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; ">
<span style="font-family: Garamond; white-space: normal; ">=></span></pre></span></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
characters are excluded<br><br></blockquote><b>Rationale. </b>In accordance with "expected" language elsewhere. We need only say "excluded".<br><div style="margin-top: 0px; margin-bottom: 0px; "><br></div>
<div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
For example, an essential element of the ASCII case- mapping functions is that uppercase(character) must be equal to uppercase(lowercase(character)). That requirement may not be satisfied with IDNs. For example, there are some characters in scripts that use case distinction that do not have counterparts in one case or the other.</blockquote>
<div style="margin-top: 0px; margin-bottom: 0px; ">=></div><div style="margin-top: 0px; margin-bottom: 0px; ">[Delete]</div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; ">
<b>Rationale. </b>While the roundtripping under case operations of ASCII of characters is a feature, it is not an "essential" feature of ASCII. Moreover, even in ASCII, strings do not roundtrip: "McGowan" doesn't roundtrip, for example. And neither of these points are relevant to the argument at hand, they just weaken it.</div>
<div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; "><hr></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
For example, putative labels that contain unassigned code points will now be rejected, while IDNA2003 permitted them (something that is now recognized as a considerable source of risk)</blockquote><div style="margin-top: 0px; margin-bottom: 0px; ">
=></div><blockquote class="webkit-indent-blockquote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-width: initial; border-color: initial; padding-top: 10px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-color: rgb(221, 221, 221); border-right-color: rgb(221, 221, 221); border-bottom-color: rgb(221, 221, 221); border-left-color: rgb(221, 221, 221); border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; ">
For example, putative labels that contain unassigned code points will now be rejected, while IDNA2003 permitted them (something many feel to be a considerable source of risk)</blockquote><div style="margin-top: 0px; margin-bottom: 0px; ">
<br></div><b>Rationale.</b> It isn't so recognized. There is no example of any case where it is a risk, since a label containing unassigned characters was always rejected in registration in IDNA2003, and therefore couldn't be matched. Note that IDNA2008 also does not require lookup to completely verify that putative U-Labels are actual U-Labels.<br>
</div><div><br></div></div></span></div><div><br></div><br clear="all">Mark<br>