Debian Codegraph @

rfc5242.html

raw
1 <pre>Network Working Group J. Klensin
2 Request for Comments: 5242
3 Category: Informational H. Alvestrand
4 Google
5 1 April 2008
6
7
8 A Generalized Unified Character Code: Western European and CJK Sections
9
10 Status of This Memo
11
12 This memo provides information for the Internet community. It does
13 not specify an Internet standard of any kind. Distribution of this
14 memo is unlimited.
15
16 IESG Note
17
18 This is not an IETF document. Readers should be aware of <a href="./rfc4690">RFC 4690</a>,
19 "Review and Recommendations for Internationalized Domain Names
20 (IDNs)", and its references.
21
22 This document is not a candidate for any level of Internet Standard.
23 The IETF disclaims any knowledge of the fitness of this document for
24 any purpose, and in particular notes that it has not had IETF review
25 for such things as security, congestion control, or inappropriate
26 interaction with deployed protocols. The RFC Editor has chosen to
27 publish this document at its discretion. Readers of this document
28 should exercise caution in evaluating its value for implementation
29 and deployment.
30
31 Abstract
32
33 Many issues have been identified with the use of general-purpose
34 character sets for internationalized domain names and similar
35 purposes. This memo describes a fully unified coded character set
36 for scripts based on Latin, Greek, Cyrillic, and Chinese (CJK)
37 characters. It is not a complete specification of that character
38 set.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Klensin &amp; Alvestrand Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-1.2">1.2</a>. Discussion . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
62 <a href="#section-2">2</a>. Types of Characters . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
63 <a href="#section-2.1">2.1</a>. Base Character . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-2.2">2.2</a>. Nonspacing Marks . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
65 <a href="#section-2.3">2.3</a>. Case Indicators . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
66 <a href="#section-2.4">2.4</a>. Joining Indicators . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
67 <a href="#section-2.5">2.5</a>. Character-Matrix Positioning Indicators . . . . . . . . . <a href="#page-5">5</a>
68 <a href="#section-2.6">2.6</a>. Position Shaping Controls . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
69 <a href="#section-2.7">2.7</a>. Repetition Indicators . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
70 <a href="#section-2.8">2.8</a>. Control Characters . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
71 <a href="#section-3">3</a>. Code Assigment Groupings . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
72 <a href="#section-4">4</a>. Canonical Form . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
73 <a href="#section-5">5</a>. Examples of Graphic Element Codes . . . . . . . . . . . . . . <a href="#page-8">8</a>
74 <a href="#section-6">6</a>. Composite Characters and Unicode Equivalences . . . . . . . . <a href="#page-10">10</a>
75 <a href="#section-7">7</a>. Ideographic Characters . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
76 <a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
77 <a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
78 <a href="#section-10">10</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
79 <a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
80 <a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
81 <a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Klensin &amp; Alvestrand Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 Many issues have been identified with the use of general-purpose
116 character sets for internationalized domain names and similar
117 purposes. This memo specifies a fully unified coded character set
118 for scripts based on Latin, Greek, Cyrillic, and Chinese characters.
119
120 There are four important principles in this work:
121
122 1. If it looks alike, it is alike. The number of base characters
123 and marks should be minimized. Glyphs are more important than
124 character abstractions.
125
126 2. If it is the same thing, it is the same thing. Two symbols that
127 have the same semantic meaning in all contexts should be encoded
128 in a way that allows their identity to be discovered by removing
129 modifiers, rather than having to resort to external equivalence
130 tables.
131
132 3. For simplicity, when a character form can be evaluated on the
133 basis of either serif or sanserif fonts, the sanserif font is
134 always preferred.
135
136 4. The use of combining characters and modifiers is preferred to
137 adding more base characters.
138
139 Based on these principles, it becomes obvious that:
140
141 o Ligatures, digraphs, and final forms are constructed with special
142 modifiers so that relationships to basic forms are obvious.
143
144 o Symbols consisting of multiple marks are always constructed from
145 combining characters and positional modifiers; thus, the "i"
146 character is constructed from the vertical line symbol followed by
147 a combining dot above. Similarly "f" is composed of a centered
148 vertical line, a right hook in the top position, and an
149 appropriately-positioned composing hyphen.
150
151 This document draws strongly from the design and terminology of
152 Unicode [<a href="#ref-Unicode" title="&quot;The Unicode Standard, Version 5.0&quot;">Unicode</a>] but represents a radically different approach.
153
154 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
155
156 All special-use terms in this document, including descriptions of
157 behaviors and related relationships, are used with their common-sense
158 meanings.
159
160
161
162
163
164 <span class="grey">Klensin &amp; Alvestrand Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
167
168
169 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Discussion</span>
170
171 Questions to, and contributions for, this coding system should be
172 addressed to the mailing list
173 [email protected].
174
175 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Types of Characters</span>
176
177 This document defines several types of characters. Note that these
178 definitions are not the same as the Unicode definitions for similar
179 or identical terms.
180
181 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Base Character</span>
182
183 Any character that is used as an atomic shape, rather than being
184 assembled from such a character in combination with combining
185 (overstriking) marks, symbols, or specially-designed base characters.
186 When used alone, base characters always take up space. For example,
187 a, c, l,...
188
189 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Nonspacing Marks</span>
190
191 Marks, symbols, and character components that are used to form
192 characters when used in combination with base characters. They do
193 not occupy separate character positions when displayed.
194
195 For example, the special combining symbols LeftUpperHook and
196 RightLowerHook, described in <a href="#section-5">Section 5</a>, are nonspacing marks.
197
198 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Case Indicators</span>
199
200 In scripts with case, only the lower-case characters are base
201 characters. Upper-case forms are represented by using the UC
202 modifier. So the traditional "A" character is represented by
203 "a&lt;UC&gt;". Note that this means that case-independent comparisons are
204 made simply by ignoring the &lt;UC&gt; modifiers rather than by complicated
205 mapping operations.
206
207 The initial set of case modifiers consists exclusively of:
208
209 UC Upper-case, code value 1 (hexadecimal)
210
211 The code values two through four are reserved for the impending
212 encoding of scripts with more than two cases; five is reserved for
213 expansion in case a script with more than four cases is identified.
214
215
216
217
218
219
220 <span class="grey">Klensin &amp; Alvestrand Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
223
224
225 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Joining Indicators</span>
226
227 Zero-width joiners are used to build characters, not only to separate
228 or join words. As compared to Unicode, a richer set of joiners is
229 used to distinguish between the inter-word and ligature-forming
230 (including half-character forming) cases. Unicode ZWJ and ZWNJ are
231 supplemented by ZWCJ, OJ, and ONJ. ZWCJ is used to modify a spacing
232 basic character into a nonspacing role. For example, there is no "w"
233 character, but only "u&lt;ZWCJ&gt;u". Upper-case "W" is coded as
234 u&lt;ZWCJ&gt;u&lt;UC&gt; -- the CWCJ binds more tightly than the UC modifier.
235
236 The initial set of joining indicators consists exclusively of:
237
238 ZWCJ Character joiner (also known as "ligature joiner"), code value
239 6 (hexadecimal).
240
241 OJ Overlay joiner (permits use of a subsequent character that would
242 normally be spacing as nonspacing), code value 7 (hexadecimal).
243
244 ONJ Overlay non-joiner (turns a nonspacing mark into a standalone
245 character), code value 8 (hexadecimal). This joiner should not be
246 necessary, and is normally prohibited by the "shortest string"
247 rule. But there may be unanticipated cases.
248
249 ZWJ Zero-width joiner for words or word-like constructions, code
250 value 9 (hexadecimal).
251
252 ZWNJ Zero-width non-joiner for words or word-like constructions,
253 code value A (hexadecimal).
254
255 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Character-Matrix Positioning Indicators</span>
256
257 Many characters are defined by constructed glyphs using nonspacing
258 marks. For example, the characters "b" and "d" are coded as
259 o&lt;VerticalLine&gt;&lt;PositionLeft&gt; and o&lt;VerticalLine&gt;&lt;PositionRight&gt;,
260 respectively. The Catalan ligature that has caused some difficulties
261 in Internationalizing Domain Names in Applications (IDNA) [<a href="./rfc3490" title="&quot;Internationalizing Domain Names in Applications (IDNA)&quot;">RFC3490</a>]
262 is coded as l&lt;ZWCJ&gt;&lt;.&gt;&lt;PositionVMiddle&gt;&lt;ZWCJ&gt;l
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Klensin &amp; Alvestrand Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
279
280
281 The initial table of positioning indicators is:
282
283 +-------------------+-----------+
284 | Name | Hex value |
285 +-------------------+-----------+
286 | PositionLeft | 20 |
287 | PositionCenter | 21 |
288 | PositionRight | 22 |
289 | PositionTop | 30 |
290 | PositionVMiddle | 31 |
291 | PositionBottom | 32 |
292 | PositionDescender | 33 |
293 +-------------------+-----------+
294
295 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Position Shaping Controls</span>
296
297 These controls designate character form changes for initial or final-
298 form characters. Where the distinction is important, medial-form
299 characters are the default when no qualification occurs. As with
300 case comparisons, comparisons are performed by ignoring these control
301 functions.
302
303 +-------------+-----------+
304 | Name | Hex value |
305 +-------------+-----------+
306 | InitialForm | 71 |
307 | FinalForm | 72 |
308 +-------------+-----------+
309
310 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Repetition Indicators</span>
311
312 For compactness of coding, two repetition indicators are introduced
313 for double (Repeat2) and triple (Repeat3) characters that may be
314 treated as ligatures or special cases. Two consecutive uses of a
315 character compare equal to the character followed by &lt;Repeat2&gt;. The
316 interpretation of u&lt;ZWCJ&gt;u&lt;Repeat3&gt; is left as an exercise for the
317 reader.
318
319 The initial table of repetition indicators is:
320
321 +---------+-----------+
322 | Name | Hex value |
323 +---------+-----------+
324 | Repeat2 | 50 |
325 | Repeat3 | 51 |
326 | Repeat1 | 52 |
327 +---------+-----------+
328
329
330
331
332 <span class="grey">Klensin &amp; Alvestrand Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
335
336
337 For larger repeats, these repeats can be combined; the sequence
338 &lt;Repeat2&gt;&lt;Repeat3&gt; represents six repeats, while the
339 &lt;Repeat3&gt;&lt;Repeat2&gt; represents five repeats. Following the "shortest
340 string" principle (see <a href="#section-4">Section 4</a>), Repeat1 must not ever appear
341 except in combination with Repeat2 and/or Repeat3. The generation of
342 other numbers is left as an exercise for the reader.
343
344 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Control Characters</span>
345
346 Because it is intended primarily for domain names, this specification
347 has no provision for control or spacing characters.
348
349 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Code Assigment Groupings</span>
350
351 Following the reasoning used in Unicode [<a href="#ref-Unicode" title="&quot;The Unicode Standard, Version 5.0&quot;">Unicode</a>], every character
352 occupies exactly 23 bits (conventionally stored as three octets, with
353 the leading bit always zero). This value is chosen because both 3
354 and 23 are prime numbers, unlike 42.
355
356 The code point value zero is permanently reserved and will not be
357 used unless it is necessary to expand the code space.
358
359 Code values between 1 and 255 (decimal) are reserved for the special
360 character formation codes described in <a href="#section-2.3">Section 2.3</a> through
361 <a href="#section-2.7">Section 2.7</a>.
362
363 Code values between 256 and 511 (decimal) are reserved for character
364 formation marks for non-ideographic characters. Most, but not all,
365 of these are nonspacing (combining) characters.
366
367 Code values between 512 and 1023 are reserved on general principles
368 and in case it is necessary to invent new rules and make them
369 retroactive.
370
371 Code values of 1024 and above are to be allocated for characters,
372 glyphs, and other character elements.
373
374 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Canonical Form</span>
375
376 When glyphs are constructed using the mechanisms described here,
377 there is a single canonical form for representing any given glyph.
378 There are no exceptions to that form, and any sequence of characters
379 and qualifiers that is not consistent with the form is invalid. If
380 there are two possible ways to represent a given character, the
381 shorter one (in octet count) is the only permitted form. If there
382 are two possible ways that are of the same length, the only permitted
383 form is the one that has the smaller value when the numeric values of
384 all of the octets in each are summed.
385
386
387
388 <span class="grey">Klensin &amp; Alvestrand Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
391
392
393 The ordering rules are as follows:
394
395 1. A base character or composite character (see below) must come
396 first.
397
398 2. The base character may be followed by ZWCJ or OJ, but not both,
399 followed by a base or nonspacing character or mark.
400
401 3. If ZWCJ appears, the next character must be a base character or
402 nonspacing mark.
403
404 4. If OJ appears, the next character must be a base character, since
405 the function of OJ is to make a spacing base character into a
406 nonspacing (overlay) character.
407
408 5. That character can be followed by positional qualifiers that
409 apply to it. Vertical positional qualifiers precede horizontal
410 positional qualifiers.
411
412 6. That sequence of characters may be followed by a case qualifier.
413
414 7. That entire sequence of characters forms a composite character.
415 When the composite character is non-trivial, the rules may be
416 applied to it recursively. If grouping is needed to distinguish
417 between one composite character and the next, ZWNCJ may be used
418 at the beginning of a composite character to identify a group
419 boundary.
420
421 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples of Graphic Element Codes</span>
422
423 The initial lists of positioning and combining controls appear above.
424 This section shows codes for some base characters. Names in upper
425 case are the Unicode names for the characters. These are followed,
426 for information, by the Unicode code point designations. The code
427 point list is informative, not normative, and may not be complete
428 (especially since additional matching code points may be added to
429 Unicode over time). Note that several Unicode characters that are
430 considered different by Unicode are assigned the same code sequence
431 in the system specified here.
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Klensin &amp; Alvestrand Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
447
448
449 +------------------------+-------+----------------------------------+
450 | Name | Hex | Comment |
451 | | value | |
452 +------------------------+-------+----------------------------------+
453 | FULL STOP (U+002E) | 110 | Used as both base character (in |
454 | | | bottom center position) and as |
455 | | | movable dot with OJ and |
456 | | | positional qualifiers. |
457 | HYPHEN-MINUS (U+002D) | 108 | Used as a spacing base character |
458 | | | (in horizontally and vertically |
459 | | | centered position) and as a |
460 | | | movable half-width horizontal |
461 | | | line with OJ and positional |
462 | | | qualifiers. In the context of |
463 | | | this specification, should be |
464 | | | known as Half Horizontal Line. |
465 | LOW LINE (U+005F) | 109 | Used as a spacing base character |
466 | | | (in bottom position) and as a |
467 | | | movable full-width horizontal |
468 | | | line with OJ and positional |
469 | | | qualifiers. In the context of |
470 | | | this specification, should be |
471 | | | known as Horizontal Line. |
472 | VERTICAL LINE (U+007C) | 102 | As with the horizontal lines, |
473 | | | normally a spacing base |
474 | | | character (in the middle |
475 | | | position between left and |
476 | | | right), but can be used as a |
477 | | | right to left movable |
478 | | | full-height vertical line with |
479 | | | OJ and/or positional qualifiers. |
480 | HalfHeightVerticalLine | 105 | Similar to VERTICAL LINE, but |
481 | | | only half height. |
482 | SOLIDUS (U+002F) | 103 | Used only for character |
483 | | | formation; forward slash |
484 | REVERSE SOLIDUS | 104 | Used only for character |
485 | (U+005C) | | formation; reverse slash |
486 | RightUpperHook | 131 | Used only for character |
487 | | | formation; nonspacing mark. |
488 | LeftUpperHook | 132 | Used only for character |
489 | | | formation; nonspacing mark. |
490 | LeftLowerHook | 133 | Used only for character |
491 | | | formation; nonspacing mark. |
492 | RightLowerHook | 134 | Used only for character |
493 | | | formation; nonspacing mark. |
494 | HalfHeightHoop | 140 | Used only for character |
495 | | | formation; nonspacing mark. |
496
497
498
499
500 <span class="grey">Klensin &amp; Alvestrand Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
503
504
505 | HalfHeightInvertedHoop | 141 | Used only for character |
506 | | | formation; nonspacing mark. |
507 | DIGIT ZERO (U+0030) | 400 | |
508 | DIGIT ONE (U+0031) | 401 | |
509 | DIGIT TWO (U+0032) | 402 | |
510 | DIGIT NINE (U+0039) | 409 | |
511 | LATIN SMALL LETTER A | 40A | |
512 | (U+0061) | | |
513 | LATIN SMALL LETTER O | 418 | Unify with Greek Omicron |
514 | (U+006F, U+03BF) | | |
515 | LATIN SMALL LETTER C | 40C | Unifying C with Cyrillic ES |
516 | (U+0063, U+0441) | | |
517 | GREEK SMALL LETTER | 491 | |
518 | SIGMA (U+03C3) | | |
519 +------------------------+-------+----------------------------------+
520
521 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Composite Characters and Unicode Equivalences</span>
522
523 This section provides examples of characters that are derived from or
524 based on others, known as "composite characters".
525
526 +------------------+--------------+---------------------------------+
527 | Name | Hex value | Comment |
528 +------------------+--------------+---------------------------------+
529 | LATIN SMALL | 418 007 102 | |
530 | LETTER B | 020 | |
531 | (U+0062) | | |
532 | LATIN SMALL | 418 007 102 | |
533 | LETTER D | 022 | |
534 | (U+0064) | | |
535 | LATIN SMALL | 40C 007 108 | |
536 | LETTER E | 031 | |
537 | (U+0065) | | |
538 | LATIN SMALL | 40A 006 40C | |
539 | LETTER AE | 007 108 031 | |
540 | (U+00E6) | | |
541 | LATIN SMALL | 102 131 030 | Note that 007 is not needed |
542 | LETTER F | 007 108 | before 131 because hooks are |
543 | (U+0066) | | exclusively nonspacing |
544 | | | (combining). |
545 | LATIN SMALL | 102 020 141 | |
546 | LETTER H | 021 032 | |
547 | (U+0068) | | |
548 | LATIN SMALL | 105 007 110 | |
549 | LETTER I | 021 030 | |
550 | (U+0069) | | |
551
552
553
554
555
556 <span class="grey">Klensin &amp; Alvestrand Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
559
560
561 | LATIN SMALL | 105 020 141 | |
562 | LETTER N | 021 032 | |
563 | (U+006E) | | |
564 | LATIN SMALL | 418 007 102 | Unified P, Greek Rho, Cyrillic |
565 | LETTER P | 033 020 033 | ER |
566 | (U+0070, U+03C1, | | |
567 | U+0440) | | |
568 | LATIN CAPITAL | 40A 001 | |
569 | LETTER A | | |
570 | (U+0041) | | |
571 | LATIN CAPITAL | 418 007 102 | |
572 | LETTER B | 020 001 | |
573 | (U+0042) | | |
574 | LATIN CAPITAL | 40C 001 | |
575 | LETTER C | | |
576 | (U+0043) | | |
577 | LATIN CAPITAL | 418 007 102 | |
578 | LETTER D | 022 001 | |
579 | (U+0044) | | |
580 | GREEK SMALL | 491 072 | |
581 | LETTER FINAL | | |
582 | SIGMA (U+03C2) | | |
583 +------------------+--------------+---------------------------------+
584
585 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Ideographic Characters</span>
586
587 Because of the traditional model of forming characters using selected
588 radicals and strokes in combination, Han-derived ("CJK") characters
589 are even more naturally represented, with less ambiguity, in the
590 system specified here than European ones. The mechanisms used in
591 this specification and represented in the tables (see <a href="#section-8">Section 8</a>) are
592 similar to those described as "Radicals" and "Strokes" in <a href="#section-5.1">Section 5.1</a>
593 and in <a href="#section-5.2">Section 5.2</a> ("Ideographic Description Characters") of The
594 Unicode Standard [<a href="#ref-Unicode" title="&quot;The Unicode Standard, Version 5.0&quot;">Unicode</a>]. Of course, following the same principles
595 outlined above for European characters, only radicals, stroke, and
596 description controls would be treated as base characters; no distinct
597 compound precomposed ideographic characters are registered.
598
599 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
600
601 IANA is requested to keep the actual registry of characters and code
602 tables. The registry entries consist of a character name (preferably
603 matching the Unicode character name when one is available), the code
604 sequence used to represent the character and optional descriptive
605 information. The characters and codes identified in <a href="#section-2">Section 2</a>,
606 <a href="#section-5">Section 5</a>, and <a href="#section-6">Section 6</a> above should be used to initialize the
607 table. Since the coding system is user-extensible, registrations
608 should be accepted for new characters as long as they don't look like
609
610
611
612 <span class="grey">Klensin &amp; Alvestrand Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
615
616
617 old ones. A designated expert with a background in calligraphy or
618 abstract art, and considerable experience in evaluating claims about
619 the count of angels on heads of pins, should be selected to advise
620 IANA on "looks like".
621
622 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
623
624 The representation of characters in this format should be a
625 significant boon for security. It eliminates many possibilities of
626 phishing attacks, since Principle 1 prevents the existence of two
627 characters that look alike but are different.
628
629 By detaching the encoding of characters for domain names from the
630 encoding of characters for other purposes, it also guarantees that
631 reasonable-looking names will have been encoded by competent
632 entities, thereby providing a significant degree of safety by
633 obscurity.
634
635 Because of the method by which upper-case forms are encoded and
636 because similarity is sometimes in the mind of the beholder, this
637 specification will not completely eliminate opportunities for visual
638 confusion. For example, because the lower-case characters are quite
639 different, LATIN CAPITAL LETTER A and GREEK CAPITAL LETTER ALPHA will
640 never compare equal, even though they look alike.
641
642 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span>
643
644 The authors would like to acknowledge the many contributions of
645 J.F.C. Morphin for pointing out the inadequacies of trying to address
646 the challenges of internationalization within the context of existing
647 engineering principles. His comments and related ones, in
648 combination with issues encountered in trying to internationalize
649 domain names based on Unicode, have contributed greatly to the frame
650 of mind underlying large parts of the proposal documented here. The
651 theoretical framework for this coding system is based, in part, on
652 Unicode and its collection of names and sample glyphs but represents
653 a very different approach to the coding system itself.
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Klensin &amp; Alvestrand Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
671
672
673 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
674
675 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
676
677 [<a id="ref-Unicode">Unicode</a>] The Unicode Consortium, "The Unicode Standard, Version
678 5.0", 2007.
679 Boston, MA, USA: Addison-Wesley. ISBN 0-321-48091-0
680
681 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
682
683 [<a id="ref-RFC3490">RFC3490</a>] Faltstrom, P., Hoffman, P., and A. Costello,
684 "Internationalizing Domain Names in Applications (IDNA)",
685 <a href="./rfc3490">RFC 3490</a>, March 2003.
686
687 Authors' Addresses
688
689 John C Klensin
690 1770 Massachusetts Ave, #322
691 Cambridge, MA 02140
692 USA
693
694 Phone: +1 617 491 5735
695 EMail: [email protected]
696
697
698 Harald Tveit Alvestrand
699 Google
700 Beddingen 10
701 Trondheim, 7014
702 Norway
703
704 EMail: [email protected]
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Klensin &amp; Alvestrand Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5242">RFC 5242</a> Unified CCS April 2008</span>
727
728
729 Full Copyright Statement
730
731 Copyright (C) The IETF Trust (2008).
732
733 This document is subject to the rights, licenses and restrictions
734 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and at <a href="http://www.rfc-editor.org/copyright.html">http://www.rfc-editor.org/copyright.html</a>,
735 and except as set forth therein, the authors retain all their rights.
736
737 This document and the information contained herein are provided on an
738 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
739 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
740 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
741 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
742 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
743 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
744
745 Intellectual Property
746
747 The IETF takes no position regarding the validity or scope of any
748 Intellectual Property Rights or other rights that might be claimed to
749 pertain to the implementation or use of the technology described in
750 this document or the extent to which any license under such rights
751 might or might not be available; nor does it represent that it has
752 made any independent effort to identify any such rights. Information
753 on the procedures with respect to rights in RFC documents can be
754 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
755
756 Copies of IPR disclosures made to the IETF Secretariat and any
757 assurances of licenses to be made available, or the result of an
758 attempt made to obtain a general license or permission for the use of
759 such proprietary rights by implementers or users of this
760 specification can be obtained from the IETF on-line IPR repository at
761 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
762
763 The IETF invites any interested party to bring to its attention any
764 copyrights, patents or patent applications, or other proprietary
765 rights that may cover technology that may be required to implement
766 this standard. Please address the information to the IETF at
767 [email protected].
768
769
770
771
772
773
774
775
776
777
778
779
780 Klensin &amp; Alvestrand Informational [Page 14]
781 </pre>