Mapping characters for precis classes
draft-yoneya-precis-mappings-03
Document | Type |
Replaced Internet-Draft
(individual in app area)
Expired & archived
|
|
---|---|---|---|
Authors | Yoshiro Yoneya , Takahiro Nemoto | ||
Last updated | 2015-10-14 (Latest revision 2012-10-04) | ||
Replaced by | draft-ietf-precis-mappings | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-precis-mappings | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Pete Resnick | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Preparation and comparison of internationalized strings ("precis") framework [I-D.ietf-precis-framework] is defining several classes of strings for preparation and comparison. In the document, case mapping is defined because many of protocols handle case sensitive or case insensitive string comparison and therefore preparation of string is mandatory. As described in IDNA mapping [RFC5895] and precis problem statement [I-D.ietf-precis-problem-statement], mappings in internationalized strings are not limited to case, but also width, delimiters and/or other specials are taken into consideration. This document is a guideline for authors of protocol profiles of precis framework and describes the mappings that must be considered between receiving user input and passing permitted code points to internationalized protocols.
Authors
Yoshiro Yoneya
Takahiro Nemoto
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)