idnits 2.17.1 draft-jet-idnabis-cjk-localmapping-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 2, 2009) is 5528 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-07) exists of draft-ietf-idnabis-bidi-03 == Outdated reference: A later version (-13) exists of draft-ietf-idnabis-defs-06 == Outdated reference: A later version (-18) exists of draft-ietf-idnabis-protocol-09 == Outdated reference: A later version (-17) exists of draft-ietf-idnabis-rationale-06 ** Downref: Normative reference to an Informational draft: draft-ietf-idnabis-rationale (ref. 'I-D.ietf-idnabis-rationale') == Outdated reference: A later version (-09) exists of draft-ietf-idnabis-tables-05 ** Obsolete normative reference: RFC 3490 (Obsoleted by RFC 5890, RFC 5891) ** Obsolete normative reference: RFC 3491 (Obsoleted by RFC 5891) -- Possible downref: Non-RFC (?) normative reference: ref. 'UAX15' -- Possible downref: Non-RFC (?) normative reference: ref. 'Unicode' Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. YONEYA 3 Internet-Draft JPRS 4 Intended status: BCP X. LEE 5 Expires: September 3, 2009 CNNIC 6 YJ. Suh 7 NIDA 8 E. Chen 9 TWNIC 10 March 2, 2009 12 CJK local mapping in IDNA2008 13 draft-jet-idnabis-cjk-localmapping-00 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. This document may contain material 19 from IETF Documents or IETF Contributions published or made publicly 20 available before November 10, 2008. The person(s) controlling the 21 copyright in some of this material may not have granted the IETF 22 Trust the right to allow modifications of such material outside the 23 IETF Standards Process. Without obtaining an adequate license from 24 the person(s) controlling the copyright in such materials, this 25 document may not be modified outside the IETF Standards Process, and 26 derivative works of it may not be created outside the IETF Standards 27 Process, except to format it for publication as an RFC or to 28 translate it into languages other than English. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on September 3, 2009. 48 Copyright Notice 49 Copyright (c) 2009 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents in effect on the date of 54 publication of this document (http://trustee.ietf.org/license-info). 55 Please review these documents carefully, as they describe your rights 56 and restrictions with respect to this document. 58 Abstract 60 Development of IDNA2008 is now in final stage. It will cause 61 incompatibilities for Chinese, Japanese and Korean (CJK) scripts and 62 languages. To avoid incompatibilities with IDNA2008 and current IDNA 63 (IDNA2003), definition of specific local mapping (pre process of IDNA 64 to be performed to IDN candidate string) for CJK is recommended. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 1.1. Positioning of this document . . . . . . . . . . . . . . . 4 70 1.2. Why CJK? . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 3. List of incompatibilities of CJK between IDNA2008 and 73 IDNA2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 3.1. Label separators . . . . . . . . . . . . . . . . . . . . . 5 75 3.2. Compatibility characters . . . . . . . . . . . . . . . . . 6 76 3.3. Exceptions . . . . . . . . . . . . . . . . . . . . . . . . 6 77 4. Solutions for incompatibilities . . . . . . . . . . . . . . . . 7 78 4.1. Label saparators . . . . . . . . . . . . . . . . . . . . . 7 79 4.2. Compatibility characters . . . . . . . . . . . . . . . . . 7 80 4.3. Exceptions . . . . . . . . . . . . . . . . . . . . . . . . 7 81 5. Guideline to keep compatibility in registration protocol . . . 7 82 6. Guideline to keep compatibility in domain name lookup 83 protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 84 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 85 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 86 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 87 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 88 10.1. Normative References . . . . . . . . . . . . . . . . . . . 8 89 10.2. Informative References . . . . . . . . . . . . . . . . . . 9 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 92 1. Introduction 94 1.1. Positioning of this document 96 IDNA protocol is going to be revised by IDNA2008 97 ([I-D.ietf-idnabis-rationale] [I-D.ietf-idnabis-defs] 98 [I-D.ietf-idnabis-protocol] [I-D.ietf-idnabis-tables] 99 [I-D.ietf-idnabis-bidi]) which is in the final stage includes 100 incompatibilities with IDNA2003 ([RFC3490] [RFC3491] [RFC3492]) in 101 some cases. Due to those incompatibilities, name resolution of 102 existing registered IDNs are possible to fail. To avoid such 103 incompatibilities, IDNA2008 recommends to perform local mapping 104 before registration and domain name lookup of IDNA processing, but it 105 does not mention any specific method. This document defines local 106 mapping for IDNA2008 regarding CJK to avoid incompatibilites between 107 IDNA2008 and IDNA2003. 109 1.2. Why CJK? 111 CJK shares some scripts such as Han and punctations. Therefore, it 112 is useful to have common local mapping definition in areas and / or 113 languages that share scripts. Furthermore, ccTLDs in CJK area are 114 initiative of IDN because they have been actively working for IDN 115 development and deployment since IDNA2003 start up, had published JET 116 Guideline together, and accumulated and shared their experiences and 117 knowledge of IDN registration and operation. Definition developed by 118 such ccTLDs depending on their experiences is useful for community. 120 2. Terminology 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 CJK 128 The term "CJK" stands for "Chinese, Japanese and Korean". 130 CJK IDN 132 The term "CJK IDN" stands for "Chinese IDN" or "Japanese IDN" or 133 "Korean IDN". 135 CJK scripts 136 +---------------------------------------+---------------+-+-+-+ 137 | Script Name | Code(Range) |C|J|K| 138 +---------------------------------------+---------------+-+-+-+ 139 |CJK Symbols and Punctuation | U+3000-U+3007 |Y|Y| | 140 |Hiragana | U+3040-U+309F | |Y| | 141 |Katakana | U+30A0-U+30FF | |Y| | 142 |CJK Unified Ideographs Extension A | U+3400-U+4DFF |Y| | | 143 |CJK Unified Ideographs | U+4E00-U+9FFF |Y|Y| | 144 |Hangul Syllables | U+AC00-U+D7A3 | | |Y| 145 |CJK Compatibility Ideographs | U+F900-U+FAFF |Y| | | 146 |Halfwidth and Fullwidth Forms | U+FF00-U+FFEF |Y|Y| | 147 |CJK Unified Ideographs Extension A |U+20000-U+2A6D6|Y| | | 148 |CJK Compatibility Ideographs Supplement|U+2F800-U+2FA1F|Y| | | 149 +---------------------------------------+---------------+-+-+-+ 151 Chinese IDN 153 The term "Chinese IDN" stands for "IDN consists from CJK scripts 154 marked with 'Y' in 'C' column and LDH". Permitted characters in 155 Chinese IDN are listed in [IANA-IDN-Language-zh-CN] and 156 [IANA-IDN-Language-zh-TW]. 158 Japanese IDN 160 The term "Japanese IDN" stands for "IDN consists from CJK scripts 161 marked with 'Y' in 'J' column and LDH". Permitted characters in 162 Japanese IDN are listed in [IANA-IDN-Language-ja-JP]. 164 Korean IDN 166 The term "Korean IDN" stands for "IDN consists from CJK scripts 167 marked with 'Y' in 'K' column and LDH". Permitted characters in 168 Korean IDN are listed in [IANA-IDN-Language-ko-KR]. 170 Other terms defined in [I-D.ietf-idnabis-defs] are used. 172 3. List of incompatibilities of CJK between IDNA2008 and IDNA2003 174 3.1. Label separators 176 Following characters are defined as label separator in IDNA2003, but 177 not defined in IDNA2008. 179 +---------------------------------------+---------------+-+-+-+ 180 | Script Name | Code |C|J|K| 181 +---------------------------------------+---------------+-+-+-+ 182 |IDEOGRAPHIC FULL STOP | U+3002 |Y|Y| | 183 |HALFWIDTH IDEOGRAPHIC FULL STOP | U+FF61 |Y|Y| | 184 |FULLWIDTH FULL STOP | U+FF0E |Y|Y| | 185 +---------------------------------------+---------------+-+-+-+ 187 CJK IDN which includes those characters are valid in IDNA2003 but 188 invalid in IDNA2008. 190 3.2. Compatibility characters 192 Compatibility characters that are mapped to canonical (valid) 193 characters by Unicode Normalization Form KC (NFKC) [Unicode] [UAX15] 194 in IDNA2003 are invalid in IDNA2008. 196 +---------------------------------------+---------------+-+-+-+ 197 | Script Name | Code(Range) |C|J|K| 198 +---------------------------------------+---------------+-+-+-+ 199 |FULLWIDTH DIGITS | U+FF10-U+FF19 |Y|Y| | 200 |FULLWIDTH LATIN CAPITAL LETTERS | U+FF21-U+FF3A |Y|Y| | 201 |FULLWIDTH LATIN SMALL LETTERS | U+FF41-U+FF5A |Y|Y| | 202 |HALFWIDTH KATAKANA LETTERS | U+FF65-U+FF9F | |Y| | 203 +---------------------------------------+---------------+-+-+-+ 205 CJK IDN which includes those characters are valid in IDNA2003 but 206 invalid in IDNA2008. 208 3.3. Exceptions 210 Some of mark characters of quasi-Han or quasi-Kana are exceptions in 211 IDNA2008 that have position and / or adjacent character property 212 limitations are valid in IDNA2003. 214 +---------------------------------------+---------------+-+-+-+ 215 | Script Name | Code |C|J|K| 216 +---------------------------------------+---------------+-+-+-+ 217 |IDEOGRAPHIC ITERATION MARK | U+3006 | |Y| | 218 |KATAKANA MIDDLEDOT | U+30FB | |Y| | 219 +---------------------------------------+---------------+-+-+-+ 221 CJK IDN which includes those characters are valid in IDNA2003 but 222 happen to be invalid in IDNA2008. 224 4. Solutions for incompatibilities 226 4.1. Label saparators 228 If characters listed in section Section 3.1 is included in CJK IDN 229 candidate string, those characters were mapped to FULL STOP (U+002E) 230 in local mapping processing. 232 4.2. Compatibility characters 234 If characters listed in section Section 3.2 is included in CJK IDN 235 candidate string, those characters were mapped to canonical 236 characters by NFKC in local mapping processing. 238 4.3. Exceptions 240 If characters listed in section Section 3.3 is included in CJK IDN 241 candidate string, those characters were treated as PROTOCOL VALID 242 instead of CONTEXTO. [NOTE: this is not local mapping, but requires 243 property change of those characters] 245 5. Guideline to keep compatibility in registration protocol 247 Registries who treat CJK IDN must implement solutions described in 248 section Section 4. 250 6. Guideline to keep compatibility in domain name lookup protocol 252 Application softwares which treat CJK IDN must implement solutions 253 described in section Section 4. Local mappings or corresponding pre- 254 processing must be performed on user interface (input/output) 255 processing, such as: 257 - User typing or pasting in input area 258 - String extraction from free context in contents area 259 - Displaing on dialogue and / or address bar 261 Note that those strings are used for domain name lookup. 263 7. IANA Considerations 265 None. 267 8. Security Considerations 269 None. 271 9. Acknowledgements 273 Many suggestions and advices were given from JET members, especially 274 Yao Jiankang, ... 276 10. References 278 10.1. Normative References 280 [I-D.ietf-idnabis-bidi] 281 Alvestrand, H. and C. Karp, "An updated IDNA criterion for 282 right-to-left scripts", draft-ietf-idnabis-bidi-03 (work 283 in progress), November 2008. 285 [I-D.ietf-idnabis-defs] 286 Klensin, J., "Internationalized Domain Names for 287 Applications (IDNA): Definitions and Document Framework", 288 draft-ietf-idnabis-defs-06 (work in progress), 289 February 2009. 291 [I-D.ietf-idnabis-protocol] 292 Klensin, J., "Internationalized Domain Names in 293 Applications (IDNA): Protocol", 294 draft-ietf-idnabis-protocol-09 (work in progress), 295 February 2009. 297 [I-D.ietf-idnabis-rationale] 298 Klensin, J., "Internationalized Domain Names for 299 Applications (IDNA): Background, Explanation, and 300 Rationale", draft-ietf-idnabis-rationale-06 (work in 301 progress), December 2008. 303 [I-D.ietf-idnabis-tables] 304 Faltstrom, P., "The Unicode code points and IDNA", 305 draft-ietf-idnabis-tables-05 (work in progress), 306 December 2008. 308 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 309 Requirement Levels", BCP 14, RFC 2119, March 1997. 311 [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, 312 "Internationalizing Domain Names in Applications (IDNA)", 313 RFC 3490, March 2003. 315 [RFC3491] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep 316 Profile for Internationalized Domain Names (IDN)", 317 RFC 3491, March 2003. 319 [RFC3492] Costello, A., "Punycode: A Bootstring encoding of Unicode 320 for Internationalized Domain Names in Applications 321 (IDNA)", RFC 3492, March 2003. 323 [UAX15] The Unicode Consortium, "Unicode Normalization Forms", 324 Unicode Standard Annex 325 #15, http://www.unicode.org/reports/tr15/, 2008. 327 [Unicode] The Unicode Consortium, "The Unicode Standard, Version 328 5.0", Boston, MA, USA: Addiso-Wesley. ISBN 0-321-48091-0, 329 2007. 331 10.2. Informative References 333 [IANA-IDN-Language-ja-JP] 334 JPRS, ".JP Japanese", IANA IDN language tables, http:// 335 www.iana.org/domains/idn-tables/tables/jp_ja-jp_1.2.html, 336 August 2005. 338 [IANA-IDN-Language-ko-KR] 339 KRNIC, ".KR Korean", IANA IDN language tables, http:// 340 www.iana.org/domains/idn-tables/tables/kr_ko-kr_1.0.html, 341 March 2004. 343 [IANA-IDN-Language-zh-CN] 344 CNNIC, ".CN Chinese", IANA IDN language tables, http:// 345 www.iana.org/domains/idn-tables/tables/cn_zh-cn_4.0.html, 346 March 2005. 348 [IANA-IDN-Language-zh-TW] 349 TWNIC, ".TW Chinese", IANA IDN language tables, http:// 350 www.iana.org/domains/idn-tables/tables/tw_zh-tw_4.0.html, 351 March 2005. 353 Authors' Addresses 355 Yoshiro YONEYA 356 JPRS 357 Chiyoda First Bldg. East 13F 358 3-8-1 Nishi-Kanda 359 Chiyoda-ku, Tokyo 101-0065 360 Japan 362 Phone: +81 3 5215 8451 363 Email: yone@jprs.co.jp 365 Xiaodong LEE 366 CNNIC 367 No.4 South 4th Street, Zhongguancun 368 Beijing 100080 369 Peoples Republic of China 371 Phone: +86 10 58813020 372 Email: lee@cnnic.cn 374 YungJin Suh 375 NIDA 376 11F, 398, Seocho-no 377 Deocho-gu, Seoul 137-857 378 South Korea 380 Phone: +82 2 2186 4562 381 Email: yjsuh@nida.or.kr 383 Erin Chen 384 TWNIC 385 4F-2, No.9 Sec. 2, Roosevelt Rd. 386 Taipei 100 387 Taiwan 389 Phone: +886 2 23411313#502 390 Email: erin@twnic.net.tw