| 1 |
<pre>Internet Architecture Board (IAB) A. Sullivan |
| 2 |
Request for Comments: 6912 Dyn, Inc. |
| 3 |
Category: Informational D. Thaler |
| 4 |
ISSN: 2070-1721 Microsoft |
| 5 |
J. Klensin |
| 6 |
|
| 7 |
O. Kolkman |
| 8 |
NLnet Labs |
| 9 |
April 2013 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">Principles for Unicode Code Point Inclusion in Labels in the DNS</span> |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
Internationalized Domain Names in Applications (IDNA) makes available |
| 17 |
to DNS zone administrators a very wide range of Unicode code points. |
| 18 |
Most operators of zones should probably not permit registration of |
| 19 |
U-labels using the entire range. This is especially true of zones |
| 20 |
that accept registrations across organizational boundaries, such as |
| 21 |
top-level domains and, most importantly, the root. It is |
| 22 |
unfortunately not possible to generate algorithms to determine |
| 23 |
whether permitting a code point presents a low risk. This memo |
| 24 |
presents a set of principles that can be used to guide the decision |
| 25 |
of whether a Unicode code point may be wisely included in the |
| 26 |
repertoire of permissible code points in a U-label in a zone. |
| 27 |
|
| 28 |
Status of This Memo |
| 29 |
|
| 30 |
This document is not an Internet Standards Track specification; it is |
| 31 |
published for informational purposes. |
| 32 |
|
| 33 |
This document is a product of the Internet Architecture Board (IAB) |
| 34 |
and represents information that the IAB has deemed valuable to |
| 35 |
provide for permanent record. It represents the consensus of the |
| 36 |
Internet Architecture Board (IAB). Documents approved for |
| 37 |
publication by the IAB are not a candidate for any level of Internet |
| 38 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 39 |
|
| 40 |
Information about the current status of this document, any errata, |
| 41 |
and how to provide feedback on it may be obtained at |
| 42 |
<a href="http://www.rfc-editor.org/info/rfc6912">http://www.rfc-editor.org/info/rfc6912</a>. |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Sullivan, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2013 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. |
| 68 |
|
| 69 |
Table of Contents |
| 70 |
|
| 71 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 72 |
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 73 |
<a href="#section-2">2</a>. Background . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 74 |
<a href="#section-2.1">2.1</a>. More-Restrictive Rules Going Up the DNS Tree . . . . . . <a href="#page-6">6</a> |
| 75 |
<a href="#section-3">3</a>. Principles Applicable to All Zones . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 76 |
<a href="#section-3.1">3.1</a>. Longevity Principle . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 77 |
<a href="#section-3.2">3.2</a>. Least Astonishment Principle . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 78 |
<a href="#section-3.3">3.3</a>. Contextual Safety Principle . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 79 |
<a href="#section-4">4</a>. Principles Applicable to All Public Zones . . . . . . . . . . <a href="#page-7">7</a> |
| 80 |
<a href="#section-4.1">4.1</a>. Conservatism Principle . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 81 |
<a href="#section-4.2">4.2</a>. Inclusion Principle . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 82 |
<a href="#section-4.3">4.3</a>. Simplicity Principle . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 83 |
<a href="#section-4.4">4.4</a>. Predictability Principle . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 84 |
<a href="#section-4.5">4.5</a>. Stability Principle . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 85 |
<a href="#section-5">5</a>. Principle Specific to the Root Zone . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 86 |
<a href="#section-5.1">5.1</a>. Letter Principle . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 87 |
<a href="#section-6">6</a>. Confusion and Context . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 88 |
<a href="#section-7">7</a>. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 89 |
<a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 90 |
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 91 |
<a href="#section-10">10</a>. IAB Members at the Time of Approval . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 92 |
<a href="#section-11">11</a>. Informative References . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Sullivan, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
Operators of a DNS zone need to set policies around what Unicode code |
| 116 |
points are allowed in labels in that zone. Typically there are a |
| 117 |
number of important goals to consider when constructing such |
| 118 |
policies. These include, for instance, avoiding possible visual |
| 119 |
confusability between two labels, avoiding possible confusion between |
| 120 |
Fully Qualified Domain Names (FQDNs) and IP address literals, |
| 121 |
accessibility to the disabled (see "Web Content Accessibility |
| 122 |
Guidelines (WCAG) 2.0" [<a href="#ref-WCAG20" title=""Web Content Accessibility Guidelines (WCAG) 2.0"">WCAG20</a>] for some discussion in a web |
| 123 |
context), and other usability issues. |
| 124 |
|
| 125 |
This document provides a set of principles that zone operators can |
| 126 |
use to construct their code point policies in order to improve |
| 127 |
usability and clarity and thereby reduce confusion. |
| 128 |
|
| 129 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span> |
| 130 |
|
| 131 |
This document uses the following terms. |
| 132 |
|
| 133 |
A-label: an LDH label that starts with "xn--" and meets all the |
| 134 |
IDNA requirements, with additional restrictions as explained in |
| 135 |
<a href="#section-2.3.2.1">Section 2.3.2.1</a> of the IDNA Definitions document [<a href="./rfc5890" title=""Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"">RFC5890</a>]. |
| 136 |
|
| 137 |
Character: a member of a set of elements used for the |
| 138 |
organization, control, or representation of data. See <a href="#section-2">Section 2</a> |
| 139 |
of the Internationalization Terminology document [<a href="./rfc6365" title=""Terminology Used in Internationalization in the IETF"">RFC6365</a>] for |
| 140 |
more details. |
| 141 |
|
| 142 |
Language: a way that humans communicate. The use of language |
| 143 |
occurs in many forms, the most common of which are speech, |
| 144 |
writing, and signing. See <a href="./rfc6365#section-2">Section 2 of RFC 6365</a> for more details. |
| 145 |
|
| 146 |
LDH label: a string consisting of ASCII letters, digits, and the |
| 147 |
hyphen, with additional restrictions as explained in <a href="./rfc5890#section-2.3.1">Section 2.3.1 |
| 148 |
of RFC 5890</a>. |
| 149 |
|
| 150 |
Public zone: in this document, a DNS zone that accepts |
| 151 |
registration requests from organizations outside the zone |
| 152 |
administrator's own organization. (Whether the zone performs |
| 153 |
delegation is a separate question. What is important is the |
| 154 |
diversity of the registration-requesting community.) Note that |
| 155 |
under this definition, the root zone is a public zone, though one |
| 156 |
that has a unique function in the DNS. |
| 157 |
|
| 158 |
Rendering: the display of a string of text. See Section 5 of <a href="./rfc6365">RFC</a> |
| 159 |
<a href="./rfc6365">6365</a> for more details. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Sullivan, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 167 |
|
| 168 |
|
| 169 |
Script: a set of graphic characters used for the written form of |
| 170 |
one or more languages. See <a href="./rfc6365#section-2">Section 2 of RFC 6365</a> for more |
| 171 |
details. |
| 172 |
|
| 173 |
U-label: a string of Unicode characters that meets all the IDNA |
| 174 |
requirements and includes at least one non-ASCII character, with |
| 175 |
additional restrictions as explained in Section 2.3.2.1 of <a href="./rfc5890">RFC</a> |
| 176 |
<a href="./rfc5890">5890</a>. |
| 177 |
|
| 178 |
Writing system: a set of rules for using one or more scripts to |
| 179 |
write a particular language. See <a href="./rfc6365#section-2">Section 2 of RFC 6365</a> for more |
| 180 |
details. |
| 181 |
|
| 182 |
This memo does not propose a protocol standard, and the use of words |
| 183 |
such as "should" follow the ordinary English meaning, and not that |
| 184 |
laid out in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 185 |
|
| 186 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background</span> |
| 187 |
|
| 188 |
In recent communications [<a href="#ref-IABCOMM1" title=""IAB Statement: 'The interpretation of rules in the ICANN gTLD Applicant Guidebook'"">IABCOMM1</a>] [<a href="#ref-IABCOMM2" title=""Response to ICANN questions concerning 'The interpretation of rules in the ICANN gTLD Applicant Guidebook'"">IABCOMM2</a>], the IAB has |
| 189 |
emphasized the importance of conservatism in allocating labels |
| 190 |
conforming to IDNA2008 [<a href="./rfc5890" title=""Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"">RFC5890</a>] [<a href="./rfc5891" title=""Internationalized Domain Names in Applications (IDNA): Protocol"">RFC5891</a>] [<a href="./rfc5892" title=""The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)"">RFC5892</a>] [<a href="./rfc5893" title=""Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)"">RFC5893</a>] |
| 191 |
[<a href="./rfc5894" title=""Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale"">RFC5894</a>] [<a href="./rfc5895" title=""Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008"">RFC5895</a>] in DNS zones, and especially in the root zone. |
| 192 |
Traditional LDH labels in the root zone used only alphabetic |
| 193 |
characters (i.e., ASCII a-z, which under the DNS also match A-Z). |
| 194 |
Matters are more complicated with U-labels, however. The IAB |
| 195 |
communications recommended that U-labels permit only code points with |
| 196 |
a General_Category (gc) of Ll (Lowercase_Letter), Lo (Other_Letter), |
| 197 |
or Lm (Modifier_Letter), but noted that for practical considerations |
| 198 |
other code points might be permitted on a case-by-case basis. |
| 199 |
|
| 200 |
The IAB recommendations do, however, leave some issues open that need |
| 201 |
to be addressed. It is not clear that all code points permitted |
| 202 |
under IDNA2008 that have a General_Category of Lo or Lm are |
| 203 |
appropriate for a zone such as the root zone. To take but one |
| 204 |
example, the code point U+02BC (MODIFIER LETTER APOSTROPHE) has a |
| 205 |
General_Category of Lm. In practically every rendering (and we are |
| 206 |
unaware of an exception), U+02BC is indistinguishable from U+2019 |
| 207 |
(RIGHT SINGLE QUOTATION MARK), which has a General_Category of Pf |
| 208 |
(Final_Punctuation). U+02BC will also be read by large numbers of |
| 209 |
people as being the same character as U+0027 (APOSTROPHE), which has |
| 210 |
a General_Category of Po (Other_Punctuation), and some computer |
| 211 |
systems may treat U+02BC as U+0027. U+02BC is PROTOCOL VALID |
| 212 |
(PVALID) under IDNA2008 (see the IDNA Code Points document |
| 213 |
[<a href="./rfc5892" title=""The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)"">RFC5892</a>]), whereas both other code points are DISALLOWED. So, to |
| 214 |
begin with, it is plain that not every code point with a |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Sullivan, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 223 |
|
| 224 |
|
| 225 |
General_Category of Ll, Lo, or Lm is consistent with the type of |
| 226 |
conservatism principle discussed in <a href="#section-4.1">Section 4.1</a> below or the previous |
| 227 |
IAB recommendations. |
| 228 |
|
| 229 |
To make matters worse, some languages are dependent on code points |
| 230 |
with General_Category Mc (Spacing_Mark) or General_Category Mn |
| 231 |
(Nonspacing_Mark). This dependency is particularly common in Indic |
| 232 |
languages, though not exclusive to them. (At the risk of vastly |
| 233 |
oversimplifying, the overarching issue is mostly the interaction of |
| 234 |
complex writing systems and the way Unicode works.) To restrict |
| 235 |
users of those languages to only code points with General_Category of |
| 236 |
Ll, Lo, or Lm would be extremely limiting. While DNS labels are not |
| 237 |
words, or sentences, or phrases (as noted in the next steps for IDN |
| 238 |
[<a href="./rfc4690" title=""Review and Recommendations for Internationalized Domain Names (IDNs)"">RFC4690</a>]), they are intended to support useful mnemonics. Mnemonics |
| 239 |
that diverge wildly from the usual conventions are poor ones, because |
| 240 |
in not following the usual conventions they are not easy to remember. |
| 241 |
Also, wide divergence from usual conventions, if not well-justified |
| 242 |
(and especially in a shared namespace like the root), invites |
| 243 |
political controversy. |
| 244 |
|
| 245 |
Many of the issues above turn out to be relevant to all public zones. |
| 246 |
Moreover, the overall issue of developing a policy for code point |
| 247 |
permission is common to all zones that accept A-labels or U-labels |
| 248 |
for registration. As <a href="#section-4.3">Section 4.3</a> of the IDNA Protocol document |
| 249 |
[<a href="./rfc5891" title=""Internationalized Domain Names in Applications (IDNA): Protocol"">RFC5891</a>] says, every registry at every level of the DNS is "expected |
| 250 |
to establish policies about label registrations". |
| 251 |
|
| 252 |
For reasons of sound management, it is not desirable to decide |
| 253 |
whether to permit a given code point only when an application |
| 254 |
containing that code point is pending. That approach reduces |
| 255 |
predictability and is bound to appear subject to special pleas. It |
| 256 |
is better instead to produce the rules governing acceptance of code |
| 257 |
points in advance. |
| 258 |
|
| 259 |
As is evident from the foregoing discussion about the Letter and Mark |
| 260 |
categories, it is simply not possible to make code point decisions |
| 261 |
algorithmically. If it were possible to develop such an algorithm, |
| 262 |
it would already exist: the DNS is hardly unique in needing to impose |
| 263 |
restrictions on code points while accommodating many different |
| 264 |
linguistic communities. Nevertheless, new guidelines can be made by |
| 265 |
starting from overarching principles. These guidelines act more as |
| 266 |
meta-rules, leading to the establishment of other rules about the |
| 267 |
inclusion and exclusion of particular code points in labels in a |
| 268 |
given zone, always based on the list of code points permitted by |
| 269 |
IDNA. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Sullivan, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. More-Restrictive Rules Going Up the DNS Tree</span> |
| 282 |
|
| 283 |
A set of principles derived from the above ideas follows in Sections |
| 284 |
3 through 5 below. Such principles fall into three categories. Some |
| 285 |
principles apply to every DNS zone. Some additional principles apply |
| 286 |
to all public zones, including the root zone. Finally, other |
| 287 |
principles apply only to the root zone. This means that zones higher |
| 288 |
in the DNS tree tend to have more restrictive rules (since additional |
| 289 |
principles apply), and zones lower in the DNS tree tend to have less |
| 290 |
restrictive rules, since they are used within a more narrow context. |
| 291 |
In general, the relevant context for a principle is that of the zone, |
| 292 |
not that of a given subset of the user community; for the root zone, |
| 293 |
for example, the context is "the entire Internet population". |
| 294 |
|
| 295 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Principles Applicable to All Zones</span> |
| 296 |
|
| 297 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Longevity Principle</span> |
| 298 |
|
| 299 |
Unicode properties of a code point ought to be stable across the |
| 300 |
versions of Unicode that users of the zone are likely to have |
| 301 |
installed. Because it is possible for the properties of a code point |
| 302 |
to change between Unicode versions, a good way to predict such |
| 303 |
stability is to ensure that a code point has in fact been stable for |
| 304 |
multiple successive versions of Unicode. This principle is related |
| 305 |
to the Stability Principle in <a href="#section-4.5">Section 4.5</a>. |
| 306 |
|
| 307 |
The more diverse the community using the zone, the greater the |
| 308 |
importance of following this principle. The policy for a leaf zone |
| 309 |
in the DNS might only require stability across two Unicode versions, |
| 310 |
whereas a more public zone might require stability across four or |
| 311 |
more releases before the code point's properties are considered long- |
| 312 |
lived and stable. |
| 313 |
|
| 314 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Least Astonishment Principle</span> |
| 315 |
|
| 316 |
Every zone administrator should be sensitive to the likely use of a |
| 317 |
code point to be permitted, particularly taking into account the |
| 318 |
population likely to use the zone. Zone administrators should |
| 319 |
especially consider whether a candidate code point could present |
| 320 |
difficulty if the code point is encountered outside the usual |
| 321 |
linguistic circumstances. By the same token, the failure to support |
| 322 |
a code point that is normal in some linguistic circumstances could be |
| 323 |
very surprising for users likely to encounter the names in that |
| 324 |
circumstance. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Sullivan, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Contextual Safety Principle</span> |
| 338 |
|
| 339 |
Every zone administrator should be sensitive to ways in which a code |
| 340 |
point that is permitted could be used in support of malicious |
| 341 |
activity. This is not a completely new problem: the digit 1 and the |
| 342 |
lowercase letter l are, for instance, easily confused in many |
| 343 |
contexts. The very large repertoire of code points in Unicode (even |
| 344 |
just the subset permitted for IDNs) makes the problem somewhat worse, |
| 345 |
just because of the scale. |
| 346 |
|
| 347 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Principles Applicable to All Public Zones</span> |
| 348 |
|
| 349 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Conservatism Principle</span> |
| 350 |
|
| 351 |
Public zones are, by definition, zones that are shared by different |
| 352 |
groups of people. Therefore, any decision to permit a code point in |
| 353 |
a public zone (including the root) should be as conservative as |
| 354 |
practicable. Doubts should always be resolved in favor of rejecting |
| 355 |
a code point for inclusion rather than in favor of including it, in |
| 356 |
order to minimize risk. |
| 357 |
|
| 358 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Inclusion Principle</span> |
| 359 |
|
| 360 |
Just as IDNA2008 starts from the principle that the Unicode range is |
| 361 |
excluded, and then adds code points according to derived properties |
| 362 |
of the code points, so a public zone should only permit inclusion of |
| 363 |
a code point if it is known to be "safe" in terms of usability and |
| 364 |
confusability within the context of that zone. The default treatment |
| 365 |
of a code point should be that it is excluded. |
| 366 |
|
| 367 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Simplicity Principle</span> |
| 368 |
|
| 369 |
The rules for determining whether a code point is to be included |
| 370 |
should be simple enough that they are readily understood by someone |
| 371 |
with a moderate background in the DNS and Unicode issues. This |
| 372 |
principle does not mean that a completely naive person needs to be |
| 373 |
able to understand the rationale for including a code point, but it |
| 374 |
does mean that if the reason for inclusion of a very peculiar code |
| 375 |
point, even a safe one, is too difficult to understand, the code |
| 376 |
point would not be permitted. |
| 377 |
|
| 378 |
The meaning of "simple" or "readily understood" is context-dependent. |
| 379 |
For instance, the root zone has to serve everyone in the world; for |
| 380 |
practical purposes, this means that the reasons for including a code |
| 381 |
point need to be comprehensible even to people who cannot use the |
| 382 |
script where the code point is found. In a zone that permits a |
| 383 |
constrained subset of Unicode characters (for instance, only those |
| 384 |
needed to write a single alphabetic language) and that supports a |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Sullivan, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 391 |
|
| 392 |
|
| 393 |
clearly delineated linguistic community (for instance, the speakers |
| 394 |
of a single language with well-understood written conventions), more |
| 395 |
complicated rules might be acceptable. Compare this principle with |
| 396 |
the Least Astonishment Principle in <a href="#section-3.2">Section 3.2</a>. |
| 397 |
|
| 398 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Predictability Principle</span> |
| 399 |
|
| 400 |
The rules for determining whether a code point is to be included |
| 401 |
should be predictable enough that those with the requisite |
| 402 |
understanding of DNS, IDNA, and Unicode will usually reach the same |
| 403 |
conclusion. This is not a requirement for algorithmic treatment of |
| 404 |
code points; as previously noted, that is not possible. Rather, it |
| 405 |
is to say that the consistent application of professional judgment is |
| 406 |
likely to yield the same results; combined with the principle in |
| 407 |
<a href="#section-4.1">Section 4.1</a>, when results are not predictable, the anomalous code |
| 408 |
point would not be permitted. |
| 409 |
|
| 410 |
Just as in <a href="#section-4.3">Section 4.3</a>, this principle tends to cause more |
| 411 |
restriction the more diverse the community using the zone; it is most |
| 412 |
restrictive for the root zone. This is because what is predictable |
| 413 |
within a given language community is possibly very surprising across |
| 414 |
languages. |
| 415 |
|
| 416 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Stability Principle</span> |
| 417 |
|
| 418 |
Once a code point is permitted, it is at least very hard to stop |
| 419 |
permitting that code point. In public zones (including the root), |
| 420 |
the list of code points to be permitted should change very slowly, if |
| 421 |
at all, and usually only in the direction of permitting an addition |
| 422 |
as time and experience indicate that inclusion of such a code point |
| 423 |
is both safe and consistent with these principles. |
| 424 |
|
| 425 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Principle Specific to the Root Zone</span> |
| 426 |
|
| 427 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Letter Principle</span> |
| 428 |
|
| 429 |
"Requirements for Internet Hosts - Application and Support" [<a href="./rfc1123" title=""Requirements for Internet Hosts - Application and Support"">RFC1123</a>] |
| 430 |
notes that top-level labels "will be alphabetic". In the absence of |
| 431 |
widespread agreement about the force of that note, prudence suggests |
| 432 |
that U-labels in the root zone should exclude code points that are |
| 433 |
not normally used to write words, or that are in some cases normally |
| 434 |
used for purposes other than writing words. This is not the same as |
| 435 |
using Unicode's General_Category to include only letters. It is a |
| 436 |
restriction that expands the possible class of included code points |
| 437 |
beyond the Unicode letters, but only expands so far as to include the |
| 438 |
things that are normally used to create words. Under this principle, |
| 439 |
code points with (for example) General_Category Mn (Nonspacing_Mark) |
| 440 |
might be included -- but only those that are used to write words and |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Sullivan, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 447 |
|
| 448 |
|
| 449 |
not (for instance) musical symbols. In addition, such marks should |
| 450 |
only be used within a label in ways that they would be used when |
| 451 |
making a word: combinations that would be nonsense when used in a |
| 452 |
word should also be rejected when tried in DNS labels. This |
| 453 |
principle should be applied as narrowly as possible; as the next |
| 454 |
steps for IDN document [<a href="./rfc4690" title=""Review and Recommendations for Internationalized Domain Names (IDNs)"">RFC4690</a>] says, "While DNS labels may |
| 455 |
conveniently be used to express words in many circumstances, the goal |
| 456 |
is not to express words (or sentences or phrases), but to permit the |
| 457 |
creation of unambiguous labels with good mnemonic value". |
| 458 |
|
| 459 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Confusion and Context</span> |
| 460 |
|
| 461 |
While many discussions of confusion have focused on characters, e.g., |
| 462 |
whether two characters are confusable with each other (and under what |
| 463 |
circumstances), a focus on characters alone could lead to the |
| 464 |
prohibition of very large numbers of labels, including many that |
| 465 |
present little risk. Instead, the focus should be on whether one |
| 466 |
label is confusable with another. For example, if a label contains |
| 467 |
several characters that are distinct to a particular script, and all |
| 468 |
of its characters are from that script, it is inherently not |
| 469 |
confusable with a label from any other script no matter what other |
| 470 |
characters might appear in it. Another label that lacks those |
| 471 |
distinguishing characters might be a problem. The notion extends |
| 472 |
from labels to domain names, in the sense that distinguishing |
| 473 |
characters used in a higher-level label may set expectations with |
| 474 |
respect to the characters in the lower-level labels. This |
| 475 |
expectation might be regarded as a benefit, but it is also a problem, |
| 476 |
since there is no technical way to require consistent policies in |
| 477 |
delegated namespaces. |
| 478 |
|
| 479 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Conclusion</span> |
| 480 |
|
| 481 |
The principles outlined in this document can be applied when |
| 482 |
considering any range of Unicode code points for possible inclusion |
| 483 |
in a DNS zone. It is worth observing that doing anything (especially |
| 484 |
in light of <a href="#section-4.5">Section 4.5</a>) implicitly disadvantages communities with a |
| 485 |
writing system not yet well understood and not represented in the |
| 486 |
technical and policy communities involved in the discussion. That |
| 487 |
disadvantage is to be guarded against as much as practical, but is |
| 488 |
effectively impossible to prevent (while still taking action) in |
| 489 |
light of imperfect human knowledge. |
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Sullivan, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 506 |
|
| 507 |
The principles outlined in this memo are intended to improve |
| 508 |
usability and clarity and thereby reduce confusion among different |
| 509 |
labels. While these principles may contribute to reduction of risk, |
| 510 |
they are not sufficient to provide a comprehensive |
| 511 |
internationalization policy for zone management. |
| 512 |
|
| 513 |
Additional discussion of security considerations can be found in the |
| 514 |
Unicode Security Considerations [<a href="#ref-UTR36" title=""Unicode Security Considerations"">UTR36</a>]. |
| 515 |
|
| 516 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span> |
| 517 |
|
| 518 |
The authors thank the participants in the IAB Internationalization |
| 519 |
program for the discussion of the ideas in this memo, particularly |
| 520 |
Marc Blanchet. In addition, Stephane Bortzmeyer, Paul Hoffman, |
| 521 |
Daniel Kalchev, Panagiotis Papaspiliopoulos, and Vaggelis Segredakis |
| 522 |
made specific comments. |
| 523 |
|
| 524 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IAB Members at the Time of Approval</span> |
| 525 |
|
| 526 |
Bernard Aboba |
| 527 |
Jari Arkko |
| 528 |
Marc Blanchet |
| 529 |
Ross Callon |
| 530 |
Alissa Cooper |
| 531 |
Spencer Dawkins |
| 532 |
Joel Halpern |
| 533 |
Russ Housley |
| 534 |
David Kessens |
| 535 |
Danny McPherson |
| 536 |
Jon Peterson |
| 537 |
Dave Thaler |
| 538 |
Hannes Tschofenig |
| 539 |
|
| 540 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Informative References</span> |
| 541 |
|
| 542 |
[<a id="ref-IABCOMM1">IABCOMM1</a>] Internet Architecture Board, "IAB Statement: 'The |
| 543 |
interpretation of rules in the ICANN gTLD Applicant |
| 544 |
Guidebook'", February 2012, <<a href="http://www.iab.org/documents/correspondence-reports-documents/201/">http://www.iab.org/</a> |
| 545 |
<a href="http://www.iab.org/documents/correspondence-reports-documents/201/">documents/correspondence-reports-documents/201/</a>>. |
| 546 |
|
| 547 |
[<a id="ref-IABCOMM2">IABCOMM2</a>] Internet Architecture Board, "Response to ICANN questions |
| 548 |
concerning 'The interpretation of rules in the ICANN gTLD |
| 549 |
Applicant Guidebook'", March 2012, <<a href="http://www.iab.org/documents/correspondence-reports-documents/201/">http://www.iab.org/</a> |
| 550 |
<a href="http://www.iab.org/documents/correspondence-reports-documents/201/">documents/correspondence-reports-documents/201/</a>>. |
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Sullivan, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 559 |
|
| 560 |
|
| 561 |
[<a id="ref-RFC1123">RFC1123</a>] Braden, R., "Requirements for Internet Hosts - Application |
| 562 |
and Support", STD 3, <a href="./rfc1123">RFC 1123</a>, October 1989. |
| 563 |
|
| 564 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 565 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 566 |
|
| 567 |
[<a id="ref-RFC4690">RFC4690</a>] Klensin, J., Faltstrom, P., Karp, C., and IAB, "Review and |
| 568 |
Recommendations for Internationalized Domain Names |
| 569 |
(IDNs)", <a href="./rfc4690">RFC 4690</a>, September 2006. |
| 570 |
|
| 571 |
[<a id="ref-RFC5890">RFC5890</a>] Klensin, J., "Internationalized Domain Names for |
| 572 |
Applications (IDNA): Definitions and Document Framework", |
| 573 |
<a href="./rfc5890">RFC 5890</a>, August 2010. |
| 574 |
|
| 575 |
[<a id="ref-RFC5891">RFC5891</a>] Klensin, J., "Internationalized Domain Names in |
| 576 |
Applications (IDNA): Protocol", <a href="./rfc5891">RFC 5891</a>, August 2010. |
| 577 |
|
| 578 |
[<a id="ref-RFC5892">RFC5892</a>] Faltstrom, P., "The Unicode Code Points and |
| 579 |
Internationalized Domain Names for Applications (IDNA)", |
| 580 |
<a href="./rfc5892">RFC 5892</a>, August 2010. |
| 581 |
|
| 582 |
[<a id="ref-RFC5893">RFC5893</a>] Alvestrand, H. and C. Karp, "Right-to-Left Scripts for |
| 583 |
Internationalized Domain Names for Applications (IDNA)", |
| 584 |
<a href="./rfc5893">RFC 5893</a>, August 2010. |
| 585 |
|
| 586 |
[<a id="ref-RFC5894">RFC5894</a>] Klensin, J., "Internationalized Domain Names for |
| 587 |
Applications (IDNA): Background, Explanation, and |
| 588 |
Rationale", <a href="./rfc5894">RFC 5894</a>, August 2010. |
| 589 |
|
| 590 |
[<a id="ref-RFC5895">RFC5895</a>] Resnick, P. and P. Hoffman, "Mapping Characters for |
| 591 |
Internationalized Domain Names in Applications (IDNA) |
| 592 |
2008", <a href="./rfc5895">RFC 5895</a>, September 2010. |
| 593 |
|
| 594 |
[<a id="ref-RFC6365">RFC6365</a>] Hoffman, P. and J. Klensin, "Terminology Used in |
| 595 |
Internationalization in the IETF", <a href="https://www.rfc-editor.org/bcp/bcp166">BCP 166</a>, <a href="./rfc6365">RFC 6365</a>, |
| 596 |
September 2011. |
| 597 |
|
| 598 |
[<a id="ref-UTR36">UTR36</a>] Davis, M. and M. Suignard, "Unicode Security |
| 599 |
Considerations", Unicode Technical Report #36, July 2012. |
| 600 |
|
| 601 |
[<a id="ref-WCAG20">WCAG20</a>] W3C, "Web Content Accessibility Guidelines (WCAG) 2.0", |
| 602 |
W3C Recommendation, December 2008, |
| 603 |
<<a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/">http://www.w3.org/TR/2008/REC-WCAG20-20081211/</a>>. |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Sullivan, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6912">RFC 6912</a> DNS Zone Code Point Principles April 2013</span> |
| 615 |
|
| 616 |
|
| 617 |
Authors' Addresses |
| 618 |
|
| 619 |
Andrew Sullivan |
| 620 |
Dyn, Inc. |
| 621 |
150 Dow St |
| 622 |
Manchester, NH 03101 |
| 623 |
USA |
| 624 |
|
| 625 |
EMail: [email protected] |
| 626 |
|
| 627 |
|
| 628 |
Dave Thaler |
| 629 |
Microsoft |
| 630 |
One Microsoft Way |
| 631 |
Redmond, WA 98052 |
| 632 |
USA |
| 633 |
|
| 634 |
EMail: [email protected] |
| 635 |
|
| 636 |
|
| 637 |
John C Klensin |
| 638 |
1770 Massachusetts Ave, Ste 322 |
| 639 |
Cambridge, MA 02140 |
| 640 |
USA |
| 641 |
|
| 642 |
Phone: +1 617 491 5735 |
| 643 |
EMail: [email protected] |
| 644 |
|
| 645 |
|
| 646 |
Olaf Kolkman |
| 647 |
NLnet Labs |
| 648 |
Science Park 400 |
| 649 |
Amsterdam 1098 XH |
| 650 |
The Netherlands |
| 651 |
|
| 652 |
EMail: [email protected] |
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
Sullivan, et al. Informational [Page 12] |
| 669 |
</pre> |