< draft-faltstrom-unicode11-03.txt		draft-faltstrom-unicode11-04.txt >
	Network Working Group P. Faltstrom		Network Working Group P. Faltstrom
	Internet-Draft Netnod		Internet-Draft Netnod
	Intended status: Informational October 02, 2018		Intended status: Informational October 07, 2018
	Expires: April 5, 2019		Expires: April 10, 2019
	IDNA2008 and Unicode 11.0.0		IDNA2008 and Unicode 11.0.0
	draft-faltstrom-unicode11-03		draft-faltstrom-unicode11-04
	Abstract		Abstract
	This document describes changes between Unicode 6.3.0 and Unicode		This document describes changes between Unicode 6.3.0 and Unicode
	11.0.0 in the context of IDNA2008. It further suggests for the IETF		11.0.0 in the context of IDNA2008. It further suggests for the IETF
	a path forward regarding ensuring IDNA2008 follows the evolution of		a path forward regarding ensuring IDNA2008 follows the evolution of
	the Unicode Standard.		the Unicode Standard.
	In a few cases changes have been made in the Unicode Standard related		In a few cases changes have been made in the Unicode Standard related
	to the algorithm IDNA2008 specifies. IDNA2008 do give the ability to		to the algorithm IDNA2008 specifies. IDNA2008 do give the ability to
	add exceptions for backward compatibility to the algorithm but the		add exceptions for backward compatibility to the algorithm but the
	conclusions provided in this document suggests no such changes.		conclusions provided in this document suggests no such changes.
			Thus this document requests that IANA update the tables to Unicode
			11.
			In addition, all registries should continue the practice of
			calculating a repertoire using conservatism and inclusion principles.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on April 5, 2019.		This Internet-Draft will expire on April 10, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Keywords for Requirement Levels . . . . . . . . . . . . . . . 3		2. Keywords for Requirement Levels . . . . . . . . . . . . . . . 4
	3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. IDNA2008 Documents . . . . . . . . . . . . . . . . . . . 3		3.1. IDNA2008 Documents . . . . . . . . . . . . . . . . . . . 4
	3.2. Deployment . . . . . . . . . . . . . . . . . . . . . . . 5		3.2. Deployment . . . . . . . . . . . . . . . . . . . . . . . 5
	4. Notable changes between Unicode 6.3.0 and 11.0.0 . . . . . . 6		4. Notable changes between Unicode 6.3.0 and 11.0.0 . . . . . . 6
	4.1. Changes to Unicode 7.0.0 . . . . . . . . . . . . . . . . 6		4.1. Changes to Unicode 7.0.0 . . . . . . . . . . . . . . . . 6
	4.2. Changes between Unicode 7.0.0 and 10.0.0 . . . . . . . . 6		4.2. Changes between Unicode 7.0.0 and 10.0.0 . . . . . . . . 7
	4.3. Changes to Unicode 11.0.0 . . . . . . . . . . . . . . . . 6		4.3. Changes to Unicode 11.0.0 . . . . . . . . . . . . . . . . 7
	5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 8		5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 8
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 8		7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	9.1. Normative References . . . . . . . . . . . . . . . . . . 9		9.1. Normative References . . . . . . . . . . . . . . . . . . 9
	9.2. Non-normative references . . . . . . . . . . . . . . . . 10		9.2. Non-normative references . . . . . . . . . . . . . . . . 10
	Appendix A. Changes from Unicode 6.3.0 to Unicode 7.0.0 . . . . 12		Appendix A. Changes from Unicode 6.3.0 to Unicode 7.0.0 . . . . 12
	Appendix B. Changes from Unicode 7.0.0 to Unicode 8.0.0 . . . . 15		Appendix B. Changes from Unicode 7.0.0 to Unicode 8.0.0 . . . . 15
	Appendix C. Changes from Unicode 8.0.0 to Unicode 9.0.0 . . . . 16		Appendix C. Changes from Unicode 8.0.0 to Unicode 9.0.0 . . . . 16
	Appendix D. Changes from Unicode 9.0.0 to Unicode 10.0.0 . . . . 17		Appendix D. Changes from Unicode 9.0.0 to Unicode 10.0.0 . . . . 17
	Appendix E. Changes from Unicode 10.0.0 to Unicode 11.0.0 . . . 18		Appendix E. Changes from Unicode 10.0.0 to Unicode 11.0.0 . . . 18
	Appendix F. Code points in Unicode Character Database (UCD)		Appendix F. Code points in Unicode Character Database (UCD)
	format for Unicode 11.0.0 . . . . . . . . . . . . . 20		format for Unicode 11.0.0 . . . . . . . . . . . . . 20
	skipping to change at page 2, line 45 ¶		skipping to change at page 3, line 7 ¶
	1. Introduction		1. Introduction
	The current version of Internationalized Domain Names for		The current version of Internationalized Domain Names for
	Applications (IDNA) was largely completed in 2008, known within the		Applications (IDNA) was largely completed in 2008, known within the
	series and elsewhere as "IDNA2008" and is specified in a series of		series and elsewhere as "IDNA2008" and is specified in a series of
	documents (see Section Section 3.1). The standard include an		documents (see Section Section 3.1). The standard include an
	algorithm by which a derived property value is calculated based on		algorithm by which a derived property value is calculated based on
	the properties defined in the Unicode Standard.		the properties defined in the Unicode Standard.
	When the Unicode Standard is updated code points are assigned that		When the Unicode Standard is updated code points are assigned and
	earlier was not and property values changes for already assigned code		property values might be changed for already assigned code points.
	points.
	Assigning code points might create problems if the newly assigned		Assigning code points might create problems if the newly assigned
	code points are compositions of code points so that it either changes		code points are compositions of code points so that it either changes
	or would have changed the normalization functions. This because it		or would have changed the normalization functions. This because it
	changes the matching algorithms used which in turn might create		changes the matching algorithms used which in turn might create
	problems looking up already stored strings in for example DNS.		problems looking up already stored strings in for example DNS.
	Changing properties to already assigned code points might create		Changing properties for already assigned code points might create
	problems if the change do result in the derived property value		problems if the change do result in the derived property value
	changes. This might make an earlier allowed code point (derived		changes. This might make an earlier allowed code point (derived
	property value PVALID) not be allowed anymore (derived property value		property value PVALID) not be allowed anymore (derived property value
	DISALLOWED). Or the other way around, a code point that was not		DISALLOWED). Or the other way around, a code point that was not
	allowed (and because of that blocked in some situations) suddenly end		allowed (and because of that blocked in some situations) suddenly end
	up being allowed.		up being allowed.
	Historically the IETF has accepted all implications of changes in the		Historically the IETF has accepted all implications of changes in the
	Unicode Standard even though the changes have resulted in problematic		Unicode Standard even though the changes have resulted in problematic
	changes in the derived property value. The primary reason for that		changes in the derived property value. The primary reason for that
	skipping to change at page 8, line 23 ¶		skipping to change at page 8, line 32 ¶
	To increase overall harmonization in the use of internationalized		To increase overall harmonization in the use of internationalized
	domain names, the author recommends that the derived property values		domain names, the author recommends that the derived property values
	MUST be calculated according to the IDNA2008 specification for		MUST be calculated according to the IDNA2008 specification for
	Unicode Version 11.0.0 [Unicode-11.0.0].		Unicode Version 11.0.0 [Unicode-11.0.0].
	All registries (and others) SHOULD calculate a repertoire, for		All registries (and others) SHOULD calculate a repertoire, for
	example as explained in draft-freytag-troublesome-characters		example as explained in draft-freytag-troublesome-characters
	[I-D.freytag-troublesome-characters] and draft-klensin-idna-		[I-D.freytag-troublesome-characters] and draft-klensin-idna-
	rfc5891bis [I-D.klensin-idna-rfc5891bis] using the conservatism and		rfc5891bis [I-D.klensin-idna-rfc5891bis] using the conservatism and
	inclusive principles as laid out in SAC-084 [SAC-084].		inclusion principles as laid out in SAC-084 [SAC-084].
	6. IANA Considerations		6. IANA Considerations
	IANA is requested to update the registry of derived property values		IANA is requested to update the registry of derived property values
	after validation with the Appointed Expert that the derived property		after validation with the Appointed Expert that the derived property
	values are calculated correctly.		values are calculated correctly.
	7. Security Considerations		7. Security Considerations
	This document makes recommendations regarding the use of the IDNA2008		This document makes recommendations regarding the use of the IDNA2008
	skipping to change at page 8, line 45 ¶		skipping to change at page 9, line 7 ¶
	current Unicode version. It also recommends that registries (and		current Unicode version. It also recommends that registries (and
	others dealing with Internationalized Domain Names) explicitly select		others dealing with Internationalized Domain Names) explicitly select
	appropriate subsets of characters with the derived value of PVALID.		appropriate subsets of characters with the derived value of PVALID.
	Not following these recommendations can lead to various security		Not following these recommendations can lead to various security
	issues. Specifically, allowing confusable characters may lead to		issues. Specifically, allowing confusable characters may lead to
	various phishing attacks.		various phishing attacks.
	8. Acknowledgements		8. Acknowledgements
	Thanks to Martin Durst, Asmus Freytag, Ted Hardie, John Klensin,		Thanks to Martin Durst, Asmus Freytag, Ted Hardie, John Klensin, Erik
	Michel Suignard, Andrew Sullivan and Suzanne Woolf for input to this		Nordmark, Michel Suignard, Andrew Sullivan and Suzanne Woolf for
	document.		input to this document.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[IAB] Internet Architecture Board, "IAB Statement on Identifiers		[IAB] Internet Architecture Board, "IAB Statement on Identifiers
	and Unicode 7.0.0", IAB Statement on Identifiers and		and Unicode 7.0.0", IAB Statement on Identifiers and
	Unicode 7.0.0		Unicode 7.0.0
	https://www.iab.org/documents/correspondence-reports-		https://www.iab.org/documents/correspondence-reports-
	documents/2015-2/iab-statement-on-identifiers-and-unicode-		documents/2015-2/iab-statement-on-identifiers-and-unicode-
End of changes. 11 change blocks.
	18 lines changed or deleted		23 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/