Debian Codegraph @

rfc6927.html

raw
1 <pre>Independent Submission J. Levine
2 Request for Comments: 6927 Taughannock Networks
3 Category: Informational P. Hoffman
4 ISSN: 2070-1721 VPN Consortium
5 May 2013
6
7
8 <span class="h1">Variants in Second-Level Names Registered in Top-Level Domains</span>
9
10 Abstract
11
12 Internationalized Domain Names for Applications (IDNA) provides a
13 method to map a subset of names written in Unicode into the DNS.
14 Because of Unicode decisions, appearance, language and writing system
15 conventions, and historical reasons, it often has been asserted that
16 there is more than one way to write what competent readers and
17 writers think of as the same host name; these different ways of
18 writing are often called "variants". (The authors note that there
19 are many conflicting definitions for the term "variant" in the IDNA
20 community.) This document surveys the approaches that top-level
21 domains have taken to the registration and provisioning of domain
22 names that have variants. This document is not a product of the
23 IETF, does not propose any method to make variants work "correctly",
24 and is not an introduction to internationalization or IDNA.
25
26 Status of This Memo
27
28 This document is not an Internet Standards Track specification; it is
29 published for informational purposes.
30
31 This is a contribution to the RFC Series, independently of any other
32 RFC stream. The RFC Editor has chosen to publish this document at
33 its discretion and makes no statement about its value for
34 implementation or deployment. Documents approved for publication by
35 the RFC Editor are not a candidate for any level of Internet
36 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
37
38 Information about the current status of this document, any errata,
39 and how to provide feedback on it may be obtained at
40 <a href="http://www.rfc-editor.org/info/rfc6927">http://www.rfc-editor.org/info/rfc6927</a>.
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Levine &amp; Hoffman Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 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-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
73 <a href="#section-3">3</a>. Base Documents ..................................................<a href="#page-5">5</a>
74 <a href="#section-4">4</a>. Domain Practices of gTLDs .......................................<a href="#page-6">6</a>
75 <a href="#section-4.1">4.1</a>. AERO .......................................................<a href="#page-6">6</a>
76 <a href="#section-4.2">4.2</a>. ASIA .......................................................<a href="#page-6">6</a>
77 <a href="#section-4.3">4.3</a>. BIZ ........................................................<a href="#page-6">6</a>
78 <a href="#section-4.4">4.4</a>. CAT ........................................................<a href="#page-6">6</a>
79 <a href="#section-4.5">4.5</a>. COM ........................................................<a href="#page-7">7</a>
80 <a href="#section-4.6">4.6</a>. COOP .......................................................<a href="#page-7">7</a>
81 <a href="#section-4.7">4.7</a>. INFO .......................................................<a href="#page-7">7</a>
82 <a href="#section-4.8">4.8</a>. JOBS .......................................................<a href="#page-7">7</a>
83 <a href="#section-4.9">4.9</a>. MOBI .......................................................<a href="#page-7">7</a>
84 <a href="#section-4.10">4.10</a>. MUSEUM ....................................................<a href="#page-8">8</a>
85 <a href="#section-4.11">4.11</a>. NAME ......................................................<a href="#page-8">8</a>
86 <a href="#section-4.12">4.12</a>. NET .......................................................<a href="#page-8">8</a>
87 <a href="#section-4.13">4.13</a>. ORG .......................................................<a href="#page-8">8</a>
88 <a href="#section-4.14">4.14</a>. POST ......................................................<a href="#page-9">9</a>
89 <a href="#section-4.15">4.15</a>. PRO .......................................................<a href="#page-9">9</a>
90 <a href="#section-4.16">4.16</a>. TEL .......................................................<a href="#page-9">9</a>
91 <a href="#section-4.17">4.17</a>. TRAVEL ...................................................<a href="#page-10">10</a>
92 <a href="#section-4.18">4.18</a>. XXX ......................................................<a href="#page-10">10</a>
93 <a href="#section-5">5</a>. Domain Practices of ccTLDs .....................................<a href="#page-10">10</a>
94 <a href="#section-5.1">5.1</a>. BG ........................................................<a href="#page-10">10</a>
95 <a href="#section-5.2">5.2</a>. BR ........................................................<a href="#page-10">10</a>
96 <a href="#section-5.3">5.3</a>. CL ........................................................<a href="#page-10">10</a>
97 <a href="#section-5.4">5.4</a>. CN ........................................................<a href="#page-10">10</a>
98 <a href="#section-5.5">5.5</a>. ES ........................................................<a href="#page-11">11</a>
99 <a href="#section-5.6">5.6</a>. EU ........................................................<a href="#page-11">11</a>
100 <a href="#section-5.7">5.7</a>. GR ........................................................<a href="#page-11">11</a>
101 <a href="#section-5.8">5.8</a>. IL ........................................................<a href="#page-11">11</a>
102 <a href="#section-5.9">5.9</a>. IR ........................................................<a href="#page-11">11</a>
103 <a href="#section-5.10">5.10</a>. JP .......................................................<a href="#page-11">11</a>
104 <a href="#section-5.11">5.11</a>. KR .......................................................<a href="#page-12">12</a>
105
106
107
108 <span class="grey">Levine &amp; Hoffman Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
111
112
113 <a href="#section-5.12">5.12</a>. MY .......................................................<a href="#page-12">12</a>
114 <a href="#section-5.13">5.13</a>. NZ .......................................................<a href="#page-12">12</a>
115 <a href="#section-5.14">5.14</a>. PL .......................................................<a href="#page-12">12</a>
116 <a href="#section-5.15">5.15</a>. RS .......................................................<a href="#page-12">12</a>
117 <a href="#section-5.16">5.16</a>. RU .......................................................<a href="#page-12">12</a>
118 <a href="#section-5.17">5.17</a>. SA .......................................................<a href="#page-12">12</a>
119 <a href="#section-5.18">5.18</a>. SE .......................................................<a href="#page-13">13</a>
120 <a href="#section-5.19">5.19</a>. TW .......................................................<a href="#page-13">13</a>
121 <a href="#section-5.20">5.20</a>. UA .......................................................<a href="#page-13">13</a>
122 <a href="#section-5.21">5.21</a>. VE .......................................................<a href="#page-13">13</a>
123 <a href="#section-5.22">5.22</a>. XN--90A3AC ...............................................<a href="#page-13">13</a>
124 <a href="#section-5.23">5.23</a>. XN--MGBERP4A5D4AR ........................................<a href="#page-13">13</a>
125 <a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-13">13</a>
126 <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-14">14</a>
127 <a href="#section-8">8</a>. Informative References .........................................<a href="#page-14">14</a>
128
129 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
130
131 Internationalized Domain Names for Applications (IDNA) [<a href="./rfc5890" title="&quot;Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework&quot;">RFC5890</a>]
132 allows host names in the DNS [<a href="./rfc1035" title="&quot;Domain names - implementation and specification&quot;">RFC1035</a>] to contain characters from the
133 Unicode repertoire. Some Unicode characters are considered to be
134 "variants" of one another. Because of the 20th century reform of
135 Chinese writing, there is often more than one representation of what
136 Chinese speakers think of as the same character. Some languages
137 written in Latin characters with accents and diacritical marks, known
138 as decorated characters, allow the decorations to be omitted in some
139 situations; for example, French sometimes omits accents on capital
140 letters, depending on country and culture. Due to the difficulty of
141 representing decorated characters in ASCII systems, many users have
142 informally used undecorated characters in DNS host names, even when
143 they are not linguistically equivalent to the decorated versions.
144
145 There is no single agreed-on definition of "variant". In 2012, ICANN
146 said that variants "occur when a single conceptual character can be
147 identified with two or more different Unicode Code Points with
148 graphic representations that may be visually similar" (this
149 definition was previously available at
150 <a href="http://www.icann.org/en/resources/idn/variant-tlds">http://www.icann.org/en/resources/idn/variant-tlds</a>). ICANN's IDN
151 Variant Issues Project report [<a href="#ref-VIPREPORT" title="&quot;A Study of Issues Related to the Management of IDN Variant TLDs (Integrated Issues Report)&quot;">VIPREPORT</a>] says that "[t]here is today
152 no fully accepted definition for what may constitute a variant
153 relationship between top-level labels". <a href="./rfc3743">RFC 3743</a> [<a href="./rfc3743" title="&quot;Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean&quot;">RFC3743</a>] (an
154 Informational RFC, not the product of the IETF) says that the idea of
155 variants is "wherein one conceptual character can be identified with
156 several different Code Points in character sets for computer use".
157
158 The proper handing of variant names has been a topic of extensive
159 debate and research, with little consensus reached on how to handle
160 them or even what characters are variants of each other. Many people
161
162
163
164 <span class="grey">Levine &amp; Hoffman Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
167
168
169 would like variant names to behave "the same", for a diverse range of
170 meanings of "same". In some cases, it is a textual similarity, such
171 as variants having corresponding DNS records; in some, it is
172 functional similarity, such as variant names resolving to the same
173 web server; while in others, it is user experience similarity, such
174 as names resolving to web sites that, while not identical, are
175 perceived by human users as equivalent.
176
177 This document provides a snapshot of variant handling in the top-
178 level domains (TLDs) contracted by ICANN, so-called gTLDs (generic
179 TLDs) and sTLDs (sponsored TLDs), as of late 2012. We chose those
180 domains because ICANN requires each TLD to describe its IDN and
181 variant practices, and the TLD zone files are available for
182 inspection, to verify what actually goes into the zones. This
183 document also contains a small sampling of so-called ccTLDs (country
184 code TLDs, the TLDs that consist of two ASCII letters) for which we
185 could find information.
186
187 Since "variant" can mean vastly different things to different people,
188 there is also no agreement about when two zones are supposed to
189 "behave the same". Also, the gTLDs and sTLDs might have different
190 views of what variants are and are not required to report to ICANN
191 about their policies.
192
193 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
194
195 We use some terminology that has become generally agreed to when
196 discussing variant names, although we openly admit that such
197 agreement is not complete and the terminology continues to change.
198
199 Bundle: The IDN practices documents (see below) can identify sets of
200 code points that are considered variants of each other using
201 Language Variant Tables, defined in [<a href="./rfc3743" title="&quot;Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean&quot;">RFC3743</a>]. A set of names in
202 which the characters in each position are variants is known as a
203 bundle or, more technically, as an "IDL Package". The variant
204 rules vary among languages, and for the same language can vary
205 among TLDs. Many languages do not define variant characters and
206 hence do not have bundles.
207
208 Allocated: A name is allocated if sponsorship of that label in some
209 zone has been granted. This is similar to what many people refer
210 to as "registered".
211
212 Active: A name is active if it appears as an owner name in a zone.
213 Most allocated names are active, but some are not.
214
215
216
217
218
219
220 <span class="grey">Levine &amp; Hoffman Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
223
224
225 Blocked: Some names cannot be registered at all. For example, some
226 registries allow one name in a bundle to be registered and block
227 the rest.
228
229 Withheld: Some names can only be allocated under certain conditions.
230 For example, some registries permit only the registrant of one
231 name in a bundle to register or activate other names in the same
232 bundle.
233
234 Parallel NS: Multiple names in a bundle are provisioned in the TLD
235 with identical NS records, so they all are handled by the same
236 name servers.
237
238 DNAME aliasing: The DNAME [<a href="./rfc6672" title="&quot;DNAME Redirection in the DNS&quot;">RFC6672</a>] DNS record creates a shadow tree
239 of DNS records, roughly as though there were a CNAME in the shadow
240 tree pointing to each name in the target tree. DNAMEs have been
241 used both to provide resolution for several names in a bundle and
242 to provide resolution for every name under a TLD.
243
244 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Base Documents</span>
245
246 ICANN has published a variety of documents on variant management.
247 The most important are the "Guidelines for the Implementation of
248 Internationalized Domain Names" issued in Version 1.0 [<a href="#ref-G1" title="&quot;Guidelines for the Implementation of Internationalized Domain Names, Version 1.0&quot;">G1</a>] and
249 Version 3.0 [<a href="#ref-G3" title="&quot;Guidelines for the Implementation of Internationalized Domain Names, Version 3.0&quot;">G3</a>].
250
251 ICANN says that TLDs are supposed to register an IDN practices
252 document with IANA for each language and/or script in which the TLD
253 accepts IDN registrations, to be entered in the IANA Repository of
254 IDN Practices [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The practices document lists the Unicode
255 characters allowed in names in the language or script, which
256 characters are considered equivalent, and which of an equivalent
257 group is preferred. Some TLDs have been more diligent than others at
258 keeping the registry up to date. Also, some TLDs have tables for a
259 few languages and scripts, while others (notably .COM, .NET, and
260 .NAME) have a large set of tables, including some for languages and
261 scripts that are no longer spoken or used, such as Runic and Ogham.
262 The authors also note that many of the tables in the IANA registry
263 are clearly out of date, containing URLs of policy pages that no
264 longer exist and contact information for people who have left the
265 registry.
266
267 Some of the ICANN agreements with each TLD [<a href="#ref-ICANNAGREE" title="&quot;ICANN Registry Agreements&quot;">ICANNAGREE</a>] describe the
268 TLD's IDN practices, but most don't.
269
270
271
272
273
274
275
276 <span class="grey">Levine &amp; Hoffman Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
279
280
281 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Domain Practices of gTLDs</span>
282
283 This list covers most of the current set of gTLDs. In most cases,
284 the authors have also checked the zone files for the gTLD to verify
285 or augment the policy description.
286
287 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. AERO</span>
288
289 The .AERO TLD has no IDNs and no rules or practices for them.
290
291 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. ASIA</span>
292
293 The .ASIA domain accepts registrations in many Asian languages. They
294 have IANA tables for Japanese, Korean, and Chinese. The IANA tables
295 refer to their CJK IDN policies [<a href="#ref-ASIACJK" title="&quot;.ASIA CJK (Chinese Japanese Korean) IDN Policies&quot;">ASIACJK</a>], which say that applied-for
296 and preferred IDN variants are "active and included in the zone". No
297 IDN publication mechanism is described in the documentation, but
298 since the zone file contains no DNAMEs, they must be using parallel
299 NS for variants.
300
301 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. BIZ</span>
302
303 ICANN gave the registry (Neustar) non-specific permission to register
304 IDNs in a letter in 2004 [<a href="#ref-TWOMEY04A" title="&quot;Letter from Paul Twomey to Richard Tindal&quot;">TWOMEY04A</a>]. The IDN rules were apparently
305 discussed with ICANN but not defined; see Appendix 9 of the registry
306 agreement [<a href="#ref-ICANNBIZ9" title="">ICANNBIZ9</a>].
307
308 They have about a dozen IANA tables. No IDN publication mechanism is
309 described, but from inspection, it appears that variants are blocked.
310
311 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. CAT</span>
312
313 The IDN rules are described in <a href="#appendix-S">Appendix S</a>, Part VII.2 [<a href="#ref-ICANNCATS" title="">ICANNCATS</a>] of
314 the ICANN agreement. "Registry will take a very cautious approach in
315 its IDN offerings. IDNs will be bundled with the equivalent ASCII
316 domains". The only language is Catalan. No IDN publication
317 mechanism is described.
318
319 <a href="#appendix-S">Appendix S</a> includes "The list of non-ASCII-characters for Catalan
320 language and their ASCII equivalent for the purposes of the defined
321 service", which implicitly describes bundles. The bundles consist of
322 names with accented and unaccented vowels, U+00E7 ("c with cedilla")
323 and a plain c, and the Catalan "ela geminada" written as two l's
324 separated by a U+00B7 ("middle dot") and the three characters "l-l".
325
326
327
328
329
330
331
332 <span class="grey">Levine &amp; Hoffman Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
335
336
337 When a registrant registers an IDN, the registry also includes the
338 ASCII version. From inspection of the zone file, the ASCII version
339 is provisioned with NS, and the IDN is a DNAME alias of the ASCII
340 version.
341
342 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. COM</span>
343
344 ICANN and Verisign have extensive correspondence about IDNs and
345 variants, including letters to ICANN from Ben Turner [<a href="#ref-TURNER03" title="&quot;Letter from Ben Turner to Paul Twomey&quot;">TURNER03</a>] and
346 Russell Lewis [<a href="#ref-LEWIS03" title="&quot;Letter from Russell Lewis to Paul Twomey&quot;">LEWIS03</a>].
347
348 The IANA registry has tables for several dozen languages, including
349 archaic languages such as hieroglyphics and Aramaic. Verisign
350 publishes documents describing scripts and languages [<a href="#ref-VRSNLANG" title="&quot;Scripts and Languages&quot;">VRSNLANG</a>],
351 character variants [<a href="#ref-VRSNCHAR" title="&quot;Character Variants&quot;">VRSNCHAR</a>], registration rules [<a href="#ref-VRSNRULES" title="&quot;Registration Rules&quot;">VRSNRULES</a>], and
352 additional registration logic [<a href="#ref-VRSNADDL" title="&quot;Additional Logic&quot;">VRSNADDL</a>].
353
354 In Chinese, variants are blocked (see [<a href="#ref-VRSNADDL" title="&quot;Additional Logic&quot;">VRSNADDL</a>]). In other
355 languages, there is no bundling or blocking.
356
357 <span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. COOP</span>
358
359 The .COOP TLD has no IDNs and no rules or practices for them.
360
361 <span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. INFO</span>
362
363 The IANA registry has a table for German. The German table notes
364 that "the Eszet ... character used in the German script will be
365 mapped to a double 's' string (i.e. 'ss')". The domain also offers
366 names in Greek, Russian, Arabic, Korean, and other languages. The
367 list and IDN tables are on the registry's web site [<a href="#ref-INFOTABLES" title="&quot;Internationalized Domain Names&quot;">INFOTABLES</a>].
368
369 Afilias says (not in a published policy) that it does not allow
370 Korean characters with different widths and that there are no
371 variants in .INFO.
372
373 Appendix 9 of the registry agreement [<a href="#ref-ICANNINFO9" title="">ICANNINFO9</a>] refers to a 2003
374 letter from Paul Twomey [<a href="#ref-TWOMEY03" title="&quot;Letter from Paul Twomey to Ram Mohan&quot;">TWOMEY03</a>] that refers to blocking variants.
375
376 <span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. JOBS</span>
377
378 The .JOBS TLD has no IDNs and no rules or practices for them.
379
380 <span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>. MOBI</span>
381
382 The zone file has about 22,000 IDNs. Afilias says (not in a
383 published policy) that .MOBI supports Simplified Chinese only and
384 that the language table for this is the same as that used by .CN.
385
386
387
388 <span class="grey">Levine &amp; Hoffman Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
391
392
393 Variant characters are blocked from registration. The domain has no
394 tables at IANA. <a href="#appendix-S">Appendix S</a> of the registry agreement [<a href="#ref-ICANNMOBIS" title="">ICANNMOBIS</a>],
395 says that IDNs are provisioned according to [<a href="#ref-G1" title="&quot;Guidelines for the Implementation of Internationalized Domain Names, Version 1.0&quot;">G1</a>].
396
397 <span class="h3"><a class="selflink" id="section-4.10" href="#section-4.10">4.10</a>. MUSEUM</span>
398
399 The zone file has many IDNs, but spot checks find that many are lame
400 or dead. A 2004 letter from Paul Twomey [<a href="#ref-TWOMEY04" title="&quot;Letter from Paul Twomey to Cary Karp&quot;">TWOMEY04</a>] refers to [<a href="#ref-G1" title="&quot;Guidelines for the Implementation of Internationalized Domain Names, Version 1.0&quot;">G1</a>].
401
402 The registry has a detailed policy page [<a href="#ref-MUSEUMPOLICY">MUSEUMPOLICY</a>]. IDNs are
403 accepted in Latin and Hebrew scripts, with plans for Arabic, Chinese,
404 Japanese, Korean, Cyrillic, and Greek. They do no bundling or
405 blocking, but names that may be confusable due to visual similarity
406 are not allowed. These are apparently determined by manual
407 inspection, which is practical due to the very small size of the
408 domain.
409
410 <span class="h3"><a class="selflink" id="section-4.11" href="#section-4.11">4.11</a>. NAME</span>
411
412 The .NAME TLD is managed the same as .COM.
413
414 <span class="h3"><a class="selflink" id="section-4.12" href="#section-4.12">4.12</a>. NET</span>
415
416 The .NET TLD is managed the same as .COM.
417
418 <span class="h3"><a class="selflink" id="section-4.13" href="#section-4.13">4.13</a>. ORG</span>
419
420 A 2003 letter from Paul Twomey [<a href="#ref-TWOMEY03A" title="&quot;Letter from Paul Twomey to Edward Viltz&quot;">TWOMEY03A</a>] refers to [<a href="#ref-G1" title="&quot;Guidelines for the Implementation of Internationalized Domain Names, Version 1.0&quot;">G1</a>]. The
421 registry has a list of IDN languages [<a href="#ref-PIRIDN" title="&quot;Go Global&quot;">PIRIDN</a>], several written in
422 Latin script, plus Chinese and Korean. A Questions page [<a href="#ref-PIRFAQ" title="&quot;Internationalized Domain Name (IDN) Questions&quot;">PIRFAQ</a>]
423 states that Chinese names have been accepted since January 2010 and
424 Cyrillic names in seven languages since February 2011. The practices
425 for some, but not all, of the Latin languages are registered with
426 IANA.
427
428 A Chinese language policy form on the Public Interest Registry (PIR)
429 web site says that the ZH-CN and ZH-TW IDNs use the corresponding
430 ccTLD tables from IANA, and check boxes say that Variant Registration
431 Polices and Variant Management Policies are applicable but don't say
432 what those policies are.
433
434 Private correspondence [<a href="#ref-CHANDIWALA12">CHANDIWALA12</a>] describes not-yet-public rules
435 for variants in Chinese and Cyrillic in .ORG that restrict the number
436 of variants that a registration can have.
437
438 The Korean language policy form says that it uses the KRNIC table for
439 Korean from IANA and that there are no variants.
440
441
442
443
444 <span class="grey">Levine &amp; Hoffman Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
447
448
449 <span class="h3"><a class="selflink" id="section-4.14" href="#section-4.14">4.14</a>. POST</span>
450
451 The .POST TLD appears to have no registrations at all yet.
452
453 <span class="h3"><a class="selflink" id="section-4.15" href="#section-4.15">4.15</a>. PRO</span>
454
455 The .PRO TLD has no IDNs and no rules or practices for them.
456
457 <span class="h3"><a class="selflink" id="section-4.16" href="#section-4.16">4.16</a>. TEL</span>
458
459 The zone has many IDNs. It is probably operating according to a 2004
460 letter from Paul Twomey [<a href="#ref-TWOMEY04A" title="&quot;Letter from Paul Twomey to Richard Tindal&quot;">TWOMEY04A</a>] to Neustar, which did not mention
461 specific TLDs. Its policy page [<a href="#ref-TELPOLICY" title="&quot;.TEL Policies&quot;">TELPOLICY</a>] has links to IDN
462 practices for 17 languages, all but one of which are registered with
463 IANA. None of the Latin scripts do bundling or blocking. The
464 Japanese practices say that variants are blocked. The Chinese
465 practices document says:
466
467 Therefore, in addition to the blocking mechanism, bundling is also
468 implemented for the Chinese language IDNs. When registering a
469 Chinese language IDN (primary domain name) up to two additional
470 variant domain names will be automatically registered. The first
471 variant will consist entirely of simplified Chinese characters
472 that correspond to those comprising the primary domain name. The
473 second variant will consist exclusively of traditional Chinese
474 characters that correspond to those comprising the primary domain
475 name.
476
477 The primary domain name together with the requested variants
478 constitutes a bundle on which all operations are atomic. For
479 example, if the registrant adds a name server to the primary
480 domain name, all names in the bundle will be associated with that
481 new name server.
482
483 The zone has no DNAME records, so the second paragraph strongly
484 suggests parallel NS.
485
486 The .TEL TLD, intended as an online directory, does not allow
487 registrants to enter arbitrary Resource Records (RRs) in the zone.
488 Nearly all names have NS records pointing to Telnic's own name
489 servers. The A records all point to Telnic's own web server that
490 shows directory information. NAPTR records provide telephone numbers
491 of registrants if available. Users can only directly provision MX
492 records. Currently, there are 16 domains, none of which are IDNs,
493 that point to random other name servers and mostly appear to be
494 parked.
495
496
497
498
499
500 <span class="grey">Levine &amp; Hoffman Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
503
504
505 <span class="h3"><a class="selflink" id="section-4.17" href="#section-4.17">4.17</a>. TRAVEL</span>
506
507 The .TRAVEL TLD has no IDNs and no rules or practices for them.
508
509 <span class="h3"><a class="selflink" id="section-4.18" href="#section-4.18">4.18</a>. XXX</span>
510
511 The .XXX TLD has no IDNs and no rules or practices for them.
512
513 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Domain Practices of ccTLDs</span>
514
515 Some ccTLDs publish their IDN policies. This section is a non-
516 exhaustive sampling of some of those policies. Note that few ccTLDs
517 make their zone files available, so the authors could not validate
518 the policies by looking in the zone files.
519
520 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. BG</span>
521
522 The .BG TLD (for Bulgaria) publishes a policy page [<a href="#ref-BGPOLICY" title="&quot;Terms and Conditions for Domain Name Registration and Support in the .BG Zone and the Sub- Zones&quot;">BGPOLICY</a>]. It
523 has published an IDN table for the Bulgarian and Russian languages in
524 [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy does not mention variants.
525
526 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. BR</span>
527
528 The .BR TLD (for Brazil) publishes a policy page [<a href="#ref-BRPOLICY" title="&quot;Dominios .br&quot;">BRPOLICY</a>]. It has
529 published an IDN table for the Portuguese language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>].
530 Although the IDN table does not describe variants, the policy page
531 says that bundles consist of names that are the same disregarding
532 accents on vowels, cedillas on letter "c", and inserted or deleted
533 hyphens. Only the registrant of a name in a bundle can register
534 other names from the same bundle.
535
536 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. CL</span>
537
538 The .CL TLD (for Chile) publishes a policy page [<a href="#ref-CLPOLICY" title="&quot;Syntax Rules for Domain Names under .CL&quot;">CLPOLICY</a>]. It has
539 published an IDN table for the Latin script in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy
540 says that variants are not considered for registration.
541
542 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. CN</span>
543
544 The .CN TLD (for China) publishes its policy as [<a href="./rfc4713" title="&quot;Registration and Administration Recommendations for Chinese Domain Names&quot;">RFC4713</a>]. It has
545 published an IDN table for the Chinese language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The
546 policy says that variants are "added into the zone file", presumably
547 as NS records.
548
549
550
551
552
553
554
555
556 <span class="grey">Levine &amp; Hoffman Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
559
560
561 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. ES</span>
562
563 The .ES TLD (for Spain) publishes an IDN Area page [<a href="#ref-ESIDN" title="&quot;IDN area&quot;">ESIDN</a>]. It
564 allows ten accented vowels, U+00E7 ("c with cedilla"), U+00F1 ("n
565 with tilde"), and the Catalan "ela geminada" written as two l's
566 separated by a U+00B7 ("middle dot"). There are no published IDN
567 tables, and there appears to be no variant policy.
568
569 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. EU</span>
570
571 The .EU TLD (for Europe) publishes a policy page [<a href="#ref-EUPOLICY" title="&quot;.eu Domain Name Registration Terms and Conditions&quot;">EUPOLICY</a>]. It has
572 published IDN tables for three scripts in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. There appears
573 to be no variant policy.
574
575 <span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. GR</span>
576
577 The .GR TLD (for Greece) publishes a policy page [<a href="#ref-GRPOLICY" title="&quot;Regulation on Management and Assignment of [.gr] Domain Names&quot;">GRPOLICY</a>] and an
578 FAQ [<a href="#ref-GRFAQ" title="&quot;Frequently Asked Questions regarding [.gr] Domain Name registrations&quot;">GRFAQ</a>]. The policy says that all variants of a name under .GR
579 are assigned to the domain owner, with the zone pointing the NS
580 records of all the variants to the name server of the "main form" of
581 the registered name. The FAQ says that domain names in Greek
582 characters are inserted in the zone using their non-punctuated form
583 in Punycode and that the punctuated form is associated with the non-
584 punctuated with a DNAME record. It does not publish IDN tables in
585 [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>].
586
587 <span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. IL</span>
588
589 The .IL TLD (for Israel) publishes a policy page [<a href="#ref-ILPOLICY" title="&quot;Rules for the Allocation of Domain Names Under the Israel Country Code Top Level Domain (&quot;">ILPOLICY</a>]. It has
590 published an IDN table for the Hebrew language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. There
591 is no variant policy.
592
593 <span class="h3"><a class="selflink" id="section-5.9" href="#section-5.9">5.9</a>. IR</span>
594
595 The .IR TLD (for Iran) publishes a policy page [<a href="#ref-IRPOLICY" title="&quot;Internationalized Domain Names in .IR&quot;">IRPOLICY</a>]. It has
596 published an IDN table for the Persian language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The
597 IDN table says that it will block registration of variants. However,
598 the policy document says that no IDNs can be registered in .IR.
599
600 <span class="h3"><a class="selflink" id="section-5.10" href="#section-5.10">5.10</a>. JP</span>
601
602 The .JP TLD (for Japan) publishes a policy page [<a href="#ref-JPPOLICY" title="&quot;Technology bylaws regarding generic domain name registration JP&quot;">JPPOLICY</a>]. It has
603 published an IDN table for the Japanese language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. Each
604 code point in that table defines no variants, which means there are
605 no variants in registration or resolution.
606
607
608
609
610
611
612 <span class="grey">Levine &amp; Hoffman Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
615
616
617 <span class="h3"><a class="selflink" id="section-5.11" href="#section-5.11">5.11</a>. KR</span>
618
619 The .KR TLD (for South Korea) appears to only publish its policy as
620 an IDN table for the Korean language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy in
621 that table does not discuss variants.
622
623 <span class="h3"><a class="selflink" id="section-5.12" href="#section-5.12">5.12</a>. MY</span>
624
625 The .MY TLD (for Malaysia) appears to only publish its policy as an
626 IDN table for the Jawi language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]; however, IANA lists
627 that as a table for "Malay (macrolanguage)". The policy in that
628 table does not discuss variants.
629
630 <span class="h3"><a class="selflink" id="section-5.13" href="#section-5.13">5.13</a>. NZ</span>
631
632 The .NZ TLD (for New Zealand) publishes a policy page [<a href="#ref-NZPOLICY" title="&quot;Internationalised Domain Names (IDN)&quot;">NZPOLICY</a>]. It
633 has published IDN tables for the Latin script in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The
634 policy does not discuss variants.
635
636 <span class="h3"><a class="selflink" id="section-5.14" href="#section-5.14">5.14</a>. PL</span>
637
638 The .PL TLD (for Poland) publishes a policy page [<a href="#ref-PLPOLICY" title="&quot;Registering Internationalized Domain Names under .PL&quot;">PLPOLICY</a>]. It has
639 published IDN tables for numerous European languages in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>].
640 The policy says that it will block registration of "look-alike"
641 variants.
642
643 <span class="h3"><a class="selflink" id="section-5.15" href="#section-5.15">5.15</a>. RS</span>
644
645 The .RS TLD (for Serbia) publishes a policy page [<a href="#ref-RSPOLICY" title="&quot;General Terms And Conditions For Registration of .rs Domain Names&quot;">RSPOLICY</a>]. It has
646 published IDN tables for the Serbian language, and the Latin script,
647 in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy does not discuss variants.
648
649 <span class="h3"><a class="selflink" id="section-5.16" href="#section-5.16">5.16</a>. RU</span>
650
651 The .RU TLD (for Russia) appears to only publish its policy as an IDN
652 table for the Russian language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy in that
653 table does not discuss variants.
654
655 <span class="h3"><a class="selflink" id="section-5.17" href="#section-5.17">5.17</a>. SA</span>
656
657 The .SA TLD (for Saudi Arabia) publishes a policy page [<a href="#ref-SAPOLICY" title="&quot;Saudi Domain Name Registration Regulation&quot;">SAPOLICY</a>].
658 It has published an IDN table for the Arabic language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>].
659 The policy permits the registration of variants, but it is not clear
660 whether others can register names with variants if the owner of a
661 name has not registered them.
662
663
664
665
666
667
668 <span class="grey">Levine &amp; Hoffman Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
671
672
673 <span class="h3"><a class="selflink" id="section-5.18" href="#section-5.18">5.18</a>. SE</span>
674
675 The .SE TLD (for Sweden) publishes a policy page [<a href="#ref-SEPOLICY" title="&quot;Domain names (IDN)&quot;">SEPOLICY</a>]. It has
676 published IDN tables for the Swedish and Yiddish languages, and the
677 Latin script, in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy does not discuss variants.
678
679 <span class="h3"><a class="selflink" id="section-5.19" href="#section-5.19">5.19</a>. TW</span>
680
681 The .TW TLD (for Taiwan) appears to only publish its policy as an IDN
682 table for the Chinese language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy in that
683 table does not discuss variants.
684
685 <span class="h3"><a class="selflink" id="section-5.20" href="#section-5.20">5.20</a>. UA</span>
686
687 The .UA TLD (for Ukraine) publishes a policy page [<a href="#ref-UAPOLICY" title="&quot;Registration Schedule of IDN-domains&quot;">UAPOLICY</a>]. It has
688 published an IDN table for the Cyrillic script in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The
689 policy does not discuss variants.
690
691 <span class="h3"><a class="selflink" id="section-5.21" href="#section-5.21">5.21</a>. VE</span>
692
693 The .VE TLD (for Venezuela) appears to only publish its policy as an
694 IDN table for the Spanish language in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy in that
695 table does not discuss variants.
696
697 <span class="h3"><a class="selflink" id="section-5.22" href="#section-5.22">5.22</a>. XN--90A3AC</span>
698
699 The .XN--90A3AC TLD (for Serbia) (U+0441 U+0440 U+0431) publishes a
700 policy page [<a href="#ref-RSIDNPOLICY">RSIDNPOLICY</a>]. It has published IDN tables for the
701 Cyrillic script in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The policy does not discuss variants.
702
703 <span class="h3"><a class="selflink" id="section-5.23" href="#section-5.23">5.23</a>. XN--MGBERP4A5D4AR</span>
704
705 The .XN--MGBERP4A5D4AR TLD (for Saudi Arabia) (U+0627 U+0644 U+0633
706 U+0639 U+0648 U+062F U+064A U+0629) appears to only publish its
707 policy as an IDN table for the Arabic script in [<a href="#ref-IANAIDN" title="&quot;Repository of IDN Practices&quot;">IANAIDN</a>]. The
708 policy permits the registration of variants, but it is not clear
709 whether others can register names with variants if the owner of a
710 name has not registered them.
711
712 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
713
714 Many people contributed to this document, particularly Nacho Amadoz,
715 Marc Blanchet, Michelle Coon, Jordi Iparraguirre, Frederico A. C.
716 Neves, Vaggelis Segredakis, Doron Shikmoni, Andrew Sullivan, Dennis
717 Tan, and Joseph Yee.
718
719
720
721
722
723
724 <span class="grey">Levine &amp; Hoffman Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
727
728
729 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
730
731 There are many potential security considerations for various methods
732 of dealing with IDN variants. However, this document is only a
733 catalog of current variant policies and does not address whether they
734 are good or bad ideas from a security standpoint. The documents
735 cited in the Terminology section have a little discussion of security
736 considerations for IDN variants.
737
738 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Informative References</span>
739
740 [<a id="ref-ASIACJK">ASIACJK</a>] Dot.Asia Organisation, ".ASIA CJK (Chinese Japanese
741 Korean) IDN Policies", May 2011,
742 &lt;<a href="http://dot.asia/policies/DotAsia-CJK-IDN-Policies-COMPLETE--2011-05-04.pdf">http://dot.asia/policies/</a>
743 <a href="http://dot.asia/policies/DotAsia-CJK-IDN-Policies-COMPLETE--2011-05-04.pdf">DotAsia-CJK-IDN-Policies-COMPLETE--2011-05-04.pdf</a>&gt;.
744
745 [<a id="ref-BGPOLICY">BGPOLICY</a>] Register.BG, "Terms and Conditions for Domain Name
746 Registration and Support in the .BG Zone and the Sub-
747 Zones", August 2011, &lt;<a href="https://www.register.bg/user/static/rules/en/index.html">https://www.register.bg/user/</a>
748 <a href="https://www.register.bg/user/static/rules/en/index.html">static/rules/en/index.html</a>&gt;.
749
750 [<a id="ref-BRPOLICY">BRPOLICY</a>] Registro.br, "Dominios .br", September 2011,
751 &lt;<a href="http://registro.br/dominio/regras.html">http://registro.br/dominio/regras.html</a>&gt;.
752
753 [<a id="ref-CHANDIWALA12">CHANDIWALA12</a>]
754 Chandiwala, S., "Letter from Sadik Chandiwala to John
755 Levine", December 2012.
756
757 [<a id="ref-CLPOLICY">CLPOLICY</a>] NIC Chile, "Syntax Rules for Domain Names under .CL",
758 August 2005, &lt;<a href="http://www.nic.cl/CL-IDN-policy.html">http://www.nic.cl/CL-IDN-policy.html</a>&gt;.
759
760 [<a id="ref-ESIDN">ESIDN</a>] Red.es, "IDN area", &lt;<a href="http://www.dominios.es/dominios/en/todo-lo-que-necesitas-saber/valores-anadidos/area-idn">http://www.dominios.es/dominios/</a>
761 <a href="http://www.dominios.es/dominios/en/todo-lo-que-necesitas-saber/valores-anadidos/area-idn">en/todo-lo-que-necesitas-saber/valores-anadidos/</a>
762 <a href="http://www.dominios.es/dominios/en/todo-lo-que-necesitas-saber/valores-anadidos/area-idn">area-idn</a>&gt;.
763
764 [<a id="ref-EUPOLICY">EUPOLICY</a>] EURid, ".eu Domain Name Registration Terms and
765 Conditions", &lt;<a href="http://link.eurid.eu/trm-con">http://link.eurid.eu/trm-con</a>&gt;.
766
767 [<a id="ref-G1">G1</a>] ICANN, "Guidelines for the Implementation of
768 Internationalized Domain Names, Version 1.0",
769 &lt;<a href="http://www.icann.org/en/resources/idn/idn-guidelines-20jun03-en.htm">http://www.icann.org/en/resources/idn/</a>
770 <a href="http://www.icann.org/en/resources/idn/idn-guidelines-20jun03-en.htm">idn-guidelines-20jun03-en.htm</a>&gt;.
771
772 [<a id="ref-G3">G3</a>] ICANN, "Guidelines for the Implementation of
773 Internationalized Domain Names, Version 3.0",
774 &lt;<a href="http://www.icann.org/en/resources/idn/idn-guidelines-02sep11-en.htm">http://www.icann.org/en/resources/idn/</a>
775 <a href="http://www.icann.org/en/resources/idn/idn-guidelines-02sep11-en.htm">idn-guidelines-02sep11-en.htm</a>&gt;.
776
777
778
779
780 <span class="grey">Levine &amp; Hoffman Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
783
784
785 [<a id="ref-GRFAQ">GRFAQ</a>] Foundation for Research and Technology - Hellas,
786 "Frequently Asked Questions regarding [.gr] Domain Name
787 registrations",
788 &lt;<a href="https://grweb.ics.forth.gr/faq.jsp?lang=en">https://grweb.ics.forth.gr/faq.jsp?lang=en</a>&gt;.
789
790 [<a id="ref-GRPOLICY">GRPOLICY</a>] Foundation for Research and Technology - Hellas,
791 "Regulation on Management and Assignment of [.gr] Domain
792 Names", 2011, &lt;<a href="https://grweb.ics.forth.gr/tomcat_docs/AP592_012_2011_.pdf">https://grweb.ics.forth.gr/tomcat_docs/</a>
793 <a href="https://grweb.ics.forth.gr/tomcat_docs/AP592_012_2011_.pdf">AP592_012_2011_.pdf</a>&gt;.
794
795 [<a id="ref-IANAIDN">IANAIDN</a>] IANA, "Repository of IDN Practices",
796 &lt;<a href="http://www.iana.org/domains/idn-tables">http://www.iana.org/domains/idn-tables</a>&gt;.
797
798 [<a id="ref-ICANNAGREE">ICANNAGREE</a>] ICANN, "ICANN Registry Agreements",
799 &lt;<a href="http://www.icann.org/en/about/agreements/registries">http://www.icann.org/en/about/agreements/registries</a>&gt;.
800
801 [<a id="ref-ICANNBIZ9">ICANNBIZ9</a>] ICANN, "Appendix 9 of ICANN .BIZ Registry Agreement",
802 December 2006, &lt;<a href="http://www.icann.org/en/about/agreements/registries/biz/appendix-09-08dec06-en.htm">http://www.icann.org/en/about/</a>
803 <a href="http://www.icann.org/en/about/agreements/registries/biz/appendix-09-08dec06-en.htm">agreements/registries/biz/appendix-09-08dec06-en.htm</a>&gt;.
804
805 [<a id="ref-ICANNCATS">ICANNCATS</a>] ICANN, "Appendix S of ICANN .CAT Registry Agreement",
806 March 2006, &lt;<a href="http://www.icann.org/en/about/agreements/registries/cat/cat-appendixs-22mar06-en.htm">http://www.icann.org/en/about/agreements/</a>
807 <a href="http://www.icann.org/en/about/agreements/registries/cat/cat-appendixs-22mar06-en.htm">registries/cat/cat-appendixs-22mar06-en.htm</a>&gt;.
808
809 [<a id="ref-ICANNINFO9">ICANNINFO9</a>] ICANN, "Appendix 9 of ICANN .INFO Registry Agreement",
810 December 2006, &lt;<a href="http://www.icann.org/en/tlds/agreements/info/appendix-09-08dec06.htm">http://www.icann.org/en/tlds/agreements/</a>
811 <a href="http://www.icann.org/en/tlds/agreements/info/appendix-09-08dec06.htm">info/appendix-09-08dec06.htm</a>&gt;.
812
813 [<a id="ref-ICANNMOBIS">ICANNMOBIS</a>] ICANN, "Appendix S of ICANN .MOBI Registry Agreement",
814 November 2005,
815 &lt;<a href="http://www.icann.org/en/about/agreements/registries/mobi/mobi-appendixs-23nov05-en.htm">http://www.icann.org/en/about/agreements/</a>
816 <a href="http://www.icann.org/en/about/agreements/registries/mobi/mobi-appendixs-23nov05-en.htm">registries/mobi/mobi-appendixs-23nov05-en.htm</a>&gt;.
817
818 [<a id="ref-ILPOLICY">ILPOLICY</a>] Israel Internet Association (ISOC-IL), "Rules for the
819 Allocation of Domain Names Under the Israel Country Code
820 Top Level Domain ("IL ")", August 2010,
821 &lt;<a href="http://www.isoc.org.il/domains/il-domain-rules.html">http://www.isoc.org.il/domains/il-domain-rules.html</a>&gt;.
822
823 [<a id="ref-INFOTABLES">INFOTABLES</a>] Afilias, "Internationalized Domain Names",
824 &lt;<a href="http://info.info/information/internationalized-domain-names">http://info.info/information/</a>
825 <a href="http://info.info/information/internationalized-domain-names">internationalized-domain-names</a>&gt;.
826
827 [<a id="ref-IRPOLICY">IRPOLICY</a>] IPM/IRNIC, "Internationalized Domain Names in .IR",
828 &lt;<a href="http://www.nic.ir/Internationalized_Domain_Names">http://www.nic.ir/Internationalized_Domain_Names</a>&gt;.
829
830 [<a id="ref-JPPOLICY">JPPOLICY</a>] JPRS, "Technology bylaws regarding generic domain name
831 registration JP",
832 &lt;<a href="http://jprs.jp/doc/rule/saisoku-1-wideusejp.html">http://jprs.jp/doc/rule/saisoku-1-wideusejp.html</a>&gt;.
833
834
835
836 <span class="grey">Levine &amp; Hoffman Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
839
840
841 [<a id="ref-LEWIS03">LEWIS03</a>] Lewis, R., "Letter from Russell Lewis to Paul Twomey",
842 October 2003, &lt;<a href="http://www.icann.org/en/news/correspondence/lewis-to-twomey-13oct03-en.htm">http://www.icann.org/en/news/</a>
843 <a href="http://www.icann.org/en/news/correspondence/lewis-to-twomey-13oct03-en.htm">correspondence/lewis-to-twomey-13oct03-en.htm</a>&gt;.
844
845 [<a id="ref-MUSEUMPOLICY">MUSEUMPOLICY</a>]
846 MuseDoma, "Internationalized Domain Names (IDN) in
847 .museum - Policies and terms of use", January 2009,
848 &lt;<a href="http://about.museum/idn/idnpolicy.html">http://about.museum/idn/idnpolicy.html</a>&gt;.
849
850 [<a id="ref-NZPOLICY">NZPOLICY</a>] .nz Registry Services, "Internationalised Domain Names
851 (IDN)", &lt;<a href="http://nzrs.net.nz/dns/idn">http://nzrs.net.nz/dns/idn</a>&gt;.
852
853 [<a id="ref-PIRFAQ">PIRFAQ</a>] Public Interest Registry, "Internationalized Domain Name
854 (IDN) Questions", &lt;<a href="http://www.pir.org/why/global/idn">http://www.pir.org/why/global/idn</a>&gt;.
855
856 [<a id="ref-PIRIDN">PIRIDN</a>] Public Interest Registry, "Go Global",
857 &lt;<a href="http://www.pir.org/why/global">http://www.pir.org/why/global</a>&gt;.
858
859 [<a id="ref-PLPOLICY">PLPOLICY</a>] NASK (PL-TLD), "Registering Internationalized Domain
860 Names under .PL", July 2007,
861 &lt;<a href="http://www.dns.pl/IDN/idn-registration-policy.txt">http://www.dns.pl/IDN/idn-registration-policy.txt</a>&gt;.
862
863 [<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
864 specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
865
866 [<a id="ref-RFC3743">RFC3743</a>] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint
867 Engineering Team (JET) Guidelines for Internationalized
868 Domain Names (IDN) Registration and Administration for
869 Chinese, Japanese, and Korean", <a href="./rfc3743">RFC 3743</a>, April 2004.
870
871 [<a id="ref-RFC4713">RFC4713</a>] Lee, X., Mao, W., Chen, E., Hsu, N., and J. Klensin,
872 "Registration and Administration Recommendations for
873 Chinese Domain Names", <a href="./rfc4713">RFC 4713</a>, October 2006.
874
875 [<a id="ref-RFC5890">RFC5890</a>] Klensin, J., "Internationalized Domain Names for
876 Applications (IDNA): Definitions and Document
877 Framework", <a href="./rfc5890">RFC 5890</a>, August 2010.
878
879 [<a id="ref-RFC6672">RFC6672</a>] Rose, S. and W. Wijngaards, "DNAME Redirection in the
880 DNS", <a href="./rfc6672">RFC 6672</a>, June 2012.
881
882 [<a id="ref-RSIDNPOLICY">RSIDNPOLICY</a>]
883 RNIDS, "Internationalized Domain Names (IDN) in
884 xn--90a3ac ccTLD", October 2011, &lt;<a href="http://www.rnids.rs/data/DOKUMENTI/idn-srb-policy-termsofuse-v1.4-eng.pdf">http://www.rnids.rs/</a>
885 <a href="http://www.rnids.rs/data/DOKUMENTI/idn-srb-policy-termsofuse-v1.4-eng.pdf">data/DOKUMENTI/idn-srb-policy-termsofuse-v1.4-eng.pdf</a>&gt;.
886
887
888
889
890
891
892 <span class="grey">Levine &amp; Hoffman Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
895
896
897 [<a id="ref-RSPOLICY">RSPOLICY</a>] RNIDS, "General Terms And Conditions For Registration of
898 .rs Domain Names", June 2009, &lt;<a href="http://www.rnids.rs/data/DOKUMENTI/Opsti%20akti/list0029_en.pdf">http://www.rnids.rs/</a>
899 <a href="http://www.rnids.rs/data/DOKUMENTI/Opsti%20akti/list0029_en.pdf">data/DOKUMENTI/Opsti%20akti/list0029_en.pdf</a>&gt;.
900
901 [<a id="ref-SAPOLICY">SAPOLICY</a>] Saudi Network Information Center, "Saudi Domain Name
902 Registration Regulation", March 2011,
903 &lt;<a href="http://nic.sa/docs/Saudi_Domain_Name_Registration_Regulation_V3.0_EN.pdf">http://nic.sa/docs/</a>
904 <a href="http://nic.sa/docs/Saudi_Domain_Name_Registration_Regulation_V3.0_EN.pdf">Saudi_Domain_Name_Registration_Regulation_V3.0_EN.pdf</a>&gt;.
905
906 [<a id="ref-SEPOLICY">SEPOLICY</a>] .SE (The Internet Infrastructure Foundation), "Domain
907 names (IDN)",
908 &lt;<a href="https://www.iis.se/english/register/idn/">https://www.iis.se/english/register/idn/</a>&gt;.
909
910 [<a id="ref-TELPOLICY">TELPOLICY</a>] Telnic, ".TEL Policies",
911 &lt;<a href="http://www.telnic.org/policies.html">http://www.telnic.org/policies.html</a>&gt;.
912
913 [<a id="ref-TURNER03">TURNER03</a>] Turner, B., "Letter from Ben Turner to Paul Twomey",
914 November 2003, &lt;<a href="http://www.icann.org/en/news/correspondence/turner-to-twomey-17nov03-en.htm">http://www.icann.org/en/news/</a>
915 <a href="http://www.icann.org/en/news/correspondence/turner-to-twomey-17nov03-en.htm">correspondence/turner-to-twomey-17nov03-en.htm</a>&gt;.
916
917 [<a id="ref-TWOMEY03">TWOMEY03</a>] Twomey, P., "Letter from Paul Twomey to Ram Mohan",
918 August 2003, &lt;<a href="http://www.icann.org/en/news/correspondence/twomey-to-mohan-19aug03-en.htm">http://www.icann.org/en/news/</a>
919 <a href="http://www.icann.org/en/news/correspondence/twomey-to-mohan-19aug03-en.htm">correspondence/twomey-to-mohan-19aug03-en.htm</a>&gt;.
920
921 [<a id="ref-TWOMEY03A">TWOMEY03A</a>] Twomey, P., "Letter from Paul Twomey to Edward Viltz",
922 October 2003, &lt;<a href="http://www.icann.org/en/news/correspondence/twomey-to-viltz-21oct03-en.htm">http://www.icann.org/en/news/</a>
923 <a href="http://www.icann.org/en/news/correspondence/twomey-to-viltz-21oct03-en.htm">correspondence/twomey-to-viltz-21oct03-en.htm</a>&gt;.
924
925 [<a id="ref-TWOMEY04">TWOMEY04</a>] Twomey, P., "Letter from Paul Twomey to Cary Karp",
926 January 2004, &lt;<a href="http://www.icann.org/en/news/correspondence/twomey-to-karp-20jan04-en.htm">http://www.icann.org/en/news/</a>
927 <a href="http://www.icann.org/en/news/correspondence/twomey-to-karp-20jan04-en.htm">correspondence/twomey-to-karp-20jan04-en.htm</a>&gt;.
928
929 [<a id="ref-TWOMEY04A">TWOMEY04A</a>] Twomey, P., "Letter from Paul Twomey to Richard Tindal",
930 July 2004, &lt;<a href="http://www.icann.org/en/correspondence/twomey-to-tindal-29jul04.pdf">http://www.icann.org/en/correspondence/</a>
931 <a href="http://www.icann.org/en/correspondence/twomey-to-tindal-29jul04.pdf">twomey-to-tindal-29jul04.pdf</a>&gt;.
932
933 [<a id="ref-UAPOLICY">UAPOLICY</a>] UA ccTLD, "Registration Schedule of IDN-domains",
934 &lt;<a href="http://www.hostmaster.ua/idn/">http://www.hostmaster.ua/idn/</a>&gt;.
935
936 [<a id="ref-VIPREPORT">VIPREPORT</a>] ICANN, "A Study of Issues Related to the Management of
937 IDN Variant TLDs (Integrated Issues Report)",
938 &lt;<a href="http://www.icann.org/en/topics/idn/idn-vip-integrated-issues-final-clean-20feb12-en.pdf">http://www.icann.org/en/topics/idn/</a>
939 <a href="http://www.icann.org/en/topics/idn/idn-vip-integrated-issues-final-clean-20feb12-en.pdf">idn-vip-integrated-issues-final-clean-20feb12-en.pdf</a>&gt;.
940
941 [<a id="ref-VRSNADDL">VRSNADDL</a>] Verisign, "Additional Logic",
942 &lt;<a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/additional-logic/index.xhtml">http://www.verisigninc.com/en_US/products-and-services/</a>
943 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/additional-logic/index.xhtml">domain-name-services/domain-information-center/</a>
944 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/additional-logic/index.xhtml">idn-code-points/additional-logic/index.xhtml</a>&gt;.
945
946
947
948 <span class="grey">Levine &amp; Hoffman Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6927">RFC 6927</a> Variants in Second-Level Domain Names May 2013</span>
951
952
953 [<a id="ref-VRSNCHAR">VRSNCHAR</a>] Verisign, "Character Variants",
954 &lt;<a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/character-variants/index.xhtml">http://www.verisigninc.com/en_US/products-and-services/</a>
955 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/character-variants/index.xhtml">domain-name-services/domain-information-center/</a>
956 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/character-variants/index.xhtml">idn-resources/character-variants/index.xhtml</a>&gt;.
957
958 [<a id="ref-VRSNLANG">VRSNLANG</a>] Verisign, "Scripts and Languages",
959 &lt;<a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/scripts-languages/index.xhtml">http://www.verisigninc.com/en_US/products-and-services/</a>
960 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/scripts-languages/index.xhtml">domain-name-services/domain-information-center/</a>
961 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-resources/scripts-languages/index.xhtml">idn-resources/scripts-languages/index.xhtml</a>&gt;.
962
963 [<a id="ref-VRSNRULES">VRSNRULES</a>] Verisign, "Registration Rules",
964 &lt;<a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/registration-rules/index.xhtml">http://www.verisigninc.com/en_US/products-and-services/</a>
965 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/registration-rules/index.xhtml">domain-name-services/domain-information-center/</a>
966 <a href="http://www.verisigninc.com/en_US/products-and-services/domain-name-services/domain-information-center/idn-code-points/registration-rules/index.xhtml">idn-code-points/registration-rules/index.xhtml</a>&gt;.
967
968 Authors' Addresses
969
970 John Levine
971 Taughannock Networks
972
973 EMail: [email protected]
974
975
976 Paul Hoffman
977 VPN Consortium
978
979 EMail: [email protected]
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 Levine &amp; Hoffman Informational [Page 18]
1005 </pre>