| Network Working Group | Y. YONEYA |
| Internet-Draft | JPRS |
| Intended status: Informational | T. Nemoto |
| Expires: February 07, 2014 | Keio University |
| August 06, 2013 |
Mapping characters for PRECIS classes
draft-ietf-precis-mappings-03
The framework for preparation and comparison of internationalized strings ("PRECIS") defines several classes of strings for preparation and comparison. In the framework, case mapping is defined because many protocols handle case-sensitive or case-insensitive string comparison and therefore preparation of the string is mandatory. As described in the mapping for Internationalized Domain Names in Applications (IDNA) and the PRECIS problem statement, mappings for internationalized strings are not limited to case, but also width mapping and mapping of delimiters and other specials can be taken into consideration. This document provides guidelines for authors of protocol profiles of the PRECIS framework and describes several mappings that can be applied between receiving user input and passing permitted code points to internationalized protocols. The mappings described here are expected to be applied as Additional mapping in the PRECIS framework.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 07, 2014.
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
In many cases, user input of internationalized strings is generated through the use of an input method editor ("IME") or through copy-and-paste from free text. Usually users do not care about the case and/or width of input characters because they appear to be visually identical. Further, users rarely switch IME state to input special characters such as protocol elements. For Internationalized Domain Names ("IDNs"), the IDNA Mapping specification [RFC5895] describes methods for handling these issues. For PRECIS strings, case mapping and width mapping are defined in the PRECIS framework specification [I-D.ietf-precis-framework], but delimiter mapping, special mapping, and language dependent mapping are not defined. Handling of mappings other than case and width is also important to increase chance of strings match as users expect. This document provides guidelines for authors of protocol profiles of the PRECIS framework and describes mappings that can be applied between receiving user input and passing permitted code points to internationalized protocols. The mappings described in this document are expected to be applied as Additional mapping in the PRECIS framework.
The PRECIS framework defines several protocol-independent mappings. The additional mappings defined in this document are protocol-dependent, i.e., they depend on the rules for a particular application protocol.
Some application protocols define delimiters for use in such protocols, but the delimiters are different for each protocols. Therefore, the delimiter mapping table should be based on a well-defined mapping table for each protocol.
Delimiter mapping is supposed to map delimiter characters that have compatible characters to canonical characters. For example, '@' in mail address or ':' and '/' in URI has width compatible character. And '+', '-', '<' and '>' may be such character. Another example is the FULL STOP character (U+002E) which is a delimiter in the visual presentation of domain names. Some IMEs generate semantic or width compatible character of FULL STOP such as IDEOGRAPHIC FULL STOP (U+3002) when a user types FULL STOP on the keyboard. Such FULL STOP compatible characters need to be mapped to the FULL STOP before passing the string to the protocol.
Aside from delimiter characters, certain protocols have characters which need to be mapped in ways that are different from the rules specified in the PRECIS framework (e.g., mapping non-ASCII space characters to ASCII space). In this document, these mappings are called "special mappings". They are different for each protocol. Therefore, the special mapping table should be based on a well-defined mapping table for each protocol. Examples of special mapping are the following; [RFC3748], SASLprep [RFC4013], IMAP4 ACL [RFC4314] and LDAPprep [RFC4518] define the rule that some codepoints for non-ASCII space are mapped to SPACE (U+0020).
As examples, EAP
Local case mapping is case folding that depends on language and context. For example, the mapping of LATIN CAPITAL LETTER I (U+0049) depends on the language context of the user: if the language is Turkish (or one of several other languages), the character should be mapped into LATIN SMALL LETTER DOTLESS I (U+0131) as this character's lower case equivalent.
To solve such problems for PRECIS framework, this document defines characters that need local case mapping based on the Specialcasing.txt [Specialcasing] file in section 3.13 of The Unicode Standard [Unicode]. Local case mapping targets only characters that get two different results to perform just casefolding that is defined in the Casefolding.txt [Casefolding] and perform special casefolding that is defined in the Specialcasing.txt then casefolding, because PRECIS framework have casefolding.
There are two types casefoldings defined as Unconditional Mappings and Conditional Mappings in the Specialcasing.txt file. Conditional mappings have Language-Insensitive Mappings that target characters whose full case mappings do not depend on language, but do depend on context. Language-Sensitive Mappings that these are characters whose full case mappings depend on language and perhaps also context.
Of these mappings, characters with Unconditional Mappings or with Language-Insensitive Mappings in Conditional Mappings target are mapped into same codepoint(s) with just casefolding or special casefolding then casefolding. But characters with Language-Sensitive Mappings in Conditional Mappings targets are mapped into different codepoints. Therefore this document defines characters that are a part of characters of Lithuanian(lt), Turkish(tr) and Azerbaijanian(az) that Language-Sensitive Mappings targets as targets for local case mapping.
The following are the methods to calculate codepoints that local case mapping targets. Here Casefolding() means casefolding described in the Casefolding.txt file [Casefolding] and Specialcasing() means specialcasing described in the Specialcasing.txt file [Specialcasing].
If Casefolding(Specialcasing(cp)) != Casefolding(cp)
Then cp is a target
Else cp is not a target;
Application developers should calculate codepoints that local case mapping targets by using the latest Casefolding.txt and Specialcasing.txt. Appendix B "Code points list for local case mapping" lists codepoints in Unicode 6.2 calculated by this method.
The mappings described in this document are expected to be applied as Additional mapping in the PRECIS framework. Basically, the mappings described in this document describes could be applied in any order. However, this section specifies a particular order to minimize the effect of codepoint changes introduced by the mappings. This mapping order is very general and was designed to be acceptable to the widest user community.
As well as Mapping Characters for IDNA2008 [RFC5895], this document suggests creating mappings that might cause confusion for some users while alleviating confusion in other users. Such confusion is not covered in any depth in this document.
This document has no actions for the IANA.
Martin Dürst suggested a need for the case folding about the mapping (map final sigma to sigma, German sz to ss,.).
Joe Hildebrand, John Klensin, Marc Blanchet, Pete Resnick and Peter Saint-Andre, et al. gave important suggestion for this document during at WG meeting.
This table is the mapping type list for each protocol. Values marked "o" indicate that the protocol use the type of mapping. Values marked "-" indicate that the protocol doesn't use the type of mapping.
+----------------------+-------------+-----------+------+---------+
| \ Type of mapping | Width | Delimiter | Case | Special |
| RFC \ | (NFKC) | | | |
+----------------------+-------------+-----------+------+---------+
| 3490 | - | o | - | - |
| 3491 | o | - | o | - |
| 3722 | o | - | o | - |
| 3748 | o | - | - | o |
| 4013 | o | - | - | o |
| 4314 | o | - | - | o |
| 4518 | o | - | o | o |
| 6120 | - | - | o | - |
+----------------------+-------------+-----------+------+---------+
Followings are a list of characters that need Local case mapping. Format:
<Language>; <Codepoint>; <Lowercase>; <Comments>
<Language> means the alpha-2 codes in [ISO.3166-1].