< draft-ietf-idnabis-mappings-03.txt		draft-ietf-idnabis-mappings-04.txt >
	IDNABIS P. Resnick		IDNABIS P. Resnick
	Internet-Draft Qualcomm Incorporated		Internet-Draft Qualcomm Incorporated
	Intended status: Standards Track P. Hoffman		Intended status: Standards Track P. Hoffman
	Expires: February 21, 2010 VPN Consortium		Expires: March 7, 2010 VPN Consortium
	August 20, 2009		September 3, 2009
	Mapping Characters in IDNA		Mapping Characters in IDNA
	draft-ietf-idnabis-mappings-03		draft-ietf-idnabis-mappings-04
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79. This document may contain material		provisions of BCP 78 and BCP 79. This document may contain material
	from IETF Documents or IETF Contributions published or made publicly		from IETF Documents or IETF Contributions published or made publicly
	available before November 10, 2008. The person(s) controlling the		available before November 10, 2008. The person(s) controlling the
	copyright in some of this material may not have granted the IETF		copyright in some of this material may not have granted the IETF
	Trust the right to allow modifications of such material outside the		Trust the right to allow modifications of such material outside the
	IETF Standards Process. Without obtaining an adequate license from		IETF Standards Process. Without obtaining an adequate license from
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on February 21, 2010.		This Internet-Draft will expire on March 7, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	Abstract		Abstract
	In the original version of the Internationalized Domain Names in		In the original version of the Internationalized Domain Names in
	Applications (IDNA) protocol, any Unicode code points taken from user		Applications (IDNA) protocol, any Unicode code points taken from user
	input were mapped into a set of Unicode code points that "make		input were mapped into a set of Unicode code points that "make
	sense", which were then encoded and passed to the domain name system		sense", which were then encoded and passed to the domain name system
	(DNS). The current version of IDNA presumes that the input to the		(DNS). The current version of IDNA presumes that the input to the
	protocol comes from a set of "permitted" code points, which it then		protocol comes from a set of "permitted" code points, which it then
	encodes and passes to the DNS, but does not specify what to do with		encodes and passes to the DNS, but does not specify what to do with
	the result of user input. This document describes the actions taken		the result of user input. This document describes the actions that
	by an implementation between user input and passing permitted code		can be taken by an implementation between user input and passing
	points to the new IDNA protocol.		permitted code points to the new IDNA protocol.
	1. Introduction		1. Introduction
	This document describes the operations that can be applied to user		This document describes the operations that can be applied to user
	input in order to get it into a form acceptable by the		input in order to get it into a form acceptable by the
	Internationalized Domain Names in Applications (IDNA) protocol		Internationalized Domain Names in Applications (IDNA) protocol
	[I-D.ietf-idnabis-protocol]. The document describes a general		[I-D.ietf-idnabis-protocol]. A general implementation procedure for
	implementation procedure for mapping in section 2.		mapping is given in section 2.
	It should be noted that this document does not specify the behavior		It should be noted that this document does not specify the behavior
	of a protocol that appears "on the wire". It describes an operation		of a protocol that appears "on the wire". It describes an operation
	that is to be applied to user input in order to prepare that user		that is to be applied to user input in order to prepare that user
	input for use in an "on the network" protocol. As unusual as this		input for use in an "on the network" protocol. As unusual as this
	may be for an IETF protocol document, it is a necessary operation to		may be for an IETF protocol document, it is a necessary operation to
	maintain interoperability.		maintain interoperability.
	2. The General Procedure		2. The General Procedure
	skipping to change at page 3, line 7 ¶		skipping to change at page 3, line 7 ¶
	mapping as described below, or can choose a different mapping. In		mapping as described below, or can choose a different mapping. In
	fact, an application might want to implement a full mapping that is		fact, an application might want to implement a full mapping that is
	substantially compatible with the original IDNA protocol instead of		substantially compatible with the original IDNA protocol instead of
	the algorithm given here.		the algorithm given here.
	The general algorithm that an application (or the input method		The general algorithm that an application (or the input method
	provided by an operating system) ought to use is relatively		provided by an operating system) ought to use is relatively
	straightforward:		straightforward:
	1. Upper case characters are mapped to their lower case equivalents		1. Upper case characters are mapped to their lower case equivalents
	by using the algorithm for mapping Unicode characters.		by using the algorithm for mapping case in Unicode characters.
	2. Full-width and half-width characters (those defined with		2. Full-width and half-width characters (those defined with
	Decomposition Types <wide> and <narrow>) are mapped to their		Decomposition Types <wide> and <narrow>) are mapped to their
	decomposition mappings as shown in the Unicode character		decomposition mappings as shown in the Unicode character
	database.		database.
	3. All characters are mapped using Unicode Normalization Form C		3. All characters are mapped using Unicode Normalization Form C
	(NFC).		(NFC).
	4. [I-D.ietf-idnabis-protocol] is specified such that the protocol		4. [I-D.ietf-idnabis-protocol] is specified such that the protocol
	skipping to change at page 4, line 8 ¶		skipping to change at page 4, line 8 ¶
	decomposition mappings, map any character whose		decomposition mappings, map any character whose
	"Decomposition_Type" (contained in the first part of of the sixth		"Decomposition_Type" (contained in the first part of of the sixth
	column) in <http://www.unicode.org/Public/UNIDATA/UnicodeData.txt>		column) in <http://www.unicode.org/Public/UNIDATA/UnicodeData.txt>
	is either "<wide>" or "<narrow>" to the "Decomposition_Mapping" of		is either "<wide>" or "<narrow>" to the "Decomposition_Mapping" of
	that character (contained in the second part of the sixth column)		that character (contained in the second part of the sixth column)
	in <http://www.unicode.org/Public/UNIDATA/UnicodeData.txt>.		in <http://www.unicode.org/Public/UNIDATA/UnicodeData.txt>.
	o The <http://www.unicode.org/Public/UNIDATA/UCD.html> web page has		o The <http://www.unicode.org/Public/UNIDATA/UCD.html> web page has
	useful descriptions of the contents of these files.		useful descriptions of the contents of these files.
	If this mappings in this document are applied to versions of Unicode		If the mappings in this document are applied to versions of Unicode
	later than Unicode 5.1, the later versions of the Unicode Standard		later than Unicode 5.1, the later versions of the Unicode Standard
	should be consulted.		should be consulted.
	These are a minimal set of mappings that an application should		These form a minimal set of mappings that an application should
	strongly consider doing. Of course, there are many others that might		strongly consider doing. Of course, there are many others that might
	be done.		be done.
	3. IANA Considerations		3. IANA Considerations
	This memo includes no request to IANA.		This memo includes no request to IANA.
	4. Security Considerations		4. Security Considerations
	This document suggests creating mappings that might cause confusion		This document suggests creating mappings that might cause confusion
	for some users while alleviating confusion in other users. Such		for some users while alleviating confusion in other users. Such
	confusion is not covered in any depth in this document (nor in the		confusion is not covered in any depth in this document (nor in the
	other IDNA-related documents).		other IDNA-related documents).
	5. Normative References		5. Acknowledgements
			This document is the product of the IDNAbis Working Group and
			contains contributions from many people in the Working Group.
			6. Normative References
	[I-D.ietf-idnabis-protocol]		[I-D.ietf-idnabis-protocol]
	Klensin, J., "Internationalized Domain Names in		Klensin, J., "Internationalized Domain Names in
	Applications (IDNA): Protocol",		Applications (IDNA): Protocol",
	draft-ietf-idnabis-protocol-14 (work in progress),		draft-ietf-idnabis-protocol-15 (work in progress),
	August 2009.		September 2009.
	[Unicode51]		[Unicode51]
	The Unicode Consortium, "The Unicode Standard, Version		The Unicode Consortium, "The Unicode Standard, Version
	5.1.0", 2008.		5.1.0", 2008.
	defined by: The Unicode Standard, Version 5.0, Boston, MA,		defined by: The Unicode Standard, Version 5.0, Boston, MA,
	Addison-Wesley, 2007, ISBN 0-321-48091-0, as amended by		Addison-Wesley, 2007, ISBN 0-321-48091-0, as amended by
	Unicode 5.1.0		Unicode 5.1.0
	(<http://www.unicode.org/versions/Unicode5.1.0/>).		(<http://www.unicode.org/versions/Unicode5.1.0/>).
End of changes. 10 change blocks.
	15 lines changed or deleted		20 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/