< draft-klensin-idna-5892upd-unicode70-01.txt		draft-klensin-idna-5892upd-unicode70-02.txt >
	Network Working Group J. Klensin		Network Working Group J. Klensin
	Internet-Draft		Internet-Draft
	Updates: 5892, 5894 (if approved) P. Faltstrom		Updates: 5892, 5894 (if approved) P. Faltstrom
	Intended status: Standards Track Netnod		Intended status: Standards Track Netnod
	Expires: June 10, 2015 December 7, 2014		Expires: June 10, 2015 December 7, 2014
	IDNA Update for Unicode 7.0.0		IDNA Update for Unicode 7.0.0
	draft-klensin-idna-5892upd-unicode70-01.txt		draft-klensin-idna-5892upd-unicode70-02.txt
	Abstract		Abstract
	The current version of the IDNA specifications anticipated that each		The current version of the IDNA specifications anticipated that each
	new version of Unicode would be reviewed to verify that no changes		new version of Unicode would be reviewed to verify that no changes
	had been introduced that required adjustments to the set of rules		had been introduced that required adjustments to the set of rules
	and, in particular, whether new exceptions or backward compatibility		and, in particular, whether new exceptions or backward compatibility
	adjustments were needed. That review was conducted for Unicode 7.0.0		adjustments were needed. That review was conducted for Unicode 7.0.0
	and identified a potentially problematic new code point. This		and identified a potentially problematic new code point. This
	specification discusses that code point and associated issues and		specification discusses that code point and associated issues and
	skipping to change at page 2, line 32 ¶		skipping to change at page 2, line 32 ¶
	3.1. Disallow This New Code Point . . . . . . . . . . . . . . 9		3.1. Disallow This New Code Point . . . . . . . . . . . . . . 9
	3.2. Disallow the combining sequences for these characters . . 10		3.2. Disallow the combining sequences for these characters . . 10
	3.3. Do Nothing Other Than Warn . . . . . . . . . . . . . . . 11		3.3. Do Nothing Other Than Warn . . . . . . . . . . . . . . . 11
	3.4. Normalization Form IETF (or DNS) . . . . . . . . . . . . 11		3.4. Normalization Form IETF (or DNS) . . . . . . . . . . . . 11
	4. Editorial clarification to RFC 5892 . . . . . . . . . . . . . 11		4. Editorial clarification to RFC 5892 . . . . . . . . . . . . . 11
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 12		7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	8.1. Normative References . . . . . . . . . . . . . . . . . . 13		8.1. Normative References . . . . . . . . . . . . . . . . . . 13
	8.2. Informative References . . . . . . . . . . . . . . . . . 14		8.2. Informative References . . . . . . . . . . . . . . . . . 15
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
	A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 15		A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 15
			A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
	1. Introduction		1. Introduction
	The current version of the IDNA specifications, known as "IDNA2008"		The current version of the IDNA specifications, known as "IDNA2008"
	[RFC5890], anticipated that each new version of Unicode would be		[RFC5890], anticipated that each new version of Unicode would be
	reviewed to verify that no changes had been introduced that required		reviewed to verify that no changes had been introduced that required
	adjustments to IDNA's rules and, in particular, whether new		adjustments to IDNA's rules and, in particular, whether new
	exceptions or backward compatibility adjustments were needed. When		exceptions or backward compatibility adjustments were needed. When
	that review was carefully conducted for Unicode 7.0.0 [Unicode7],		that review was carefully conducted for Unicode 7.0.0 [Unicode7],
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	point is that there are several other Arabic-script code points that		point is that there are several other Arabic-script code points that
	behave in the same way for similar language-specific reasons.		behave in the same way for similar language-specific reasons.
	In particular, at least three other grapheme clusters that have been		In particular, at least three other grapheme clusters that have been
	present for many version of Unicode can be seen as involving issues		present for many version of Unicode can be seen as involving issues
	similar to those for the newly-added ARABIC LETTER BEH WITH HAMZA		similar to those for the newly-added ARABIC LETTER BEH WITH HAMZA
	ABOVE. ARABIC LETTER HAH WITH HAMZA ABOVE (U+0681) and ARABIC LETTER		ABOVE. ARABIC LETTER HAH WITH HAMZA ABOVE (U+0681) and ARABIC LETTER
	REH WITH HAMZA ABOVE (U+076C) do not have decomposition forms and are		REH WITH HAMZA ABOVE (U+076C) do not have decomposition forms and are
	preferred over combining sequences using HAMZA ABOVE (U+0654)		preferred over combining sequences using HAMZA ABOVE (U+0654)
	[Unicode62-Hamza]. By contrast, ARABIC LETTER ALEF WITH HAMZA ABOVE		[Unicode62-Hamza]. By contrast, ARABIC LETTER ALEF WITH HAMZA ABOVE
	(U+0623) decomposes into \u'0627'\u'0653' and ARABIC LETTER YEH WITH		(U+0623) decomposes into \u'0627'\u'0654' and ARABIC LETTER YEH WITH
	HAMZA ABOVE (U+0626) decomposes into \u'064A'\u'0654' so the		HAMZA ABOVE (U+0626) decomposes into \u'064A'\u'0654' so the
	precomposed character and combining sequences compare equal when both		precomposed character and combining sequences compare equal when both
	are normalized, as this specification prefers.		are normalized, as this specification prefers.
	There are other variations in which a precomposed character involving		There are other variations in which a precomposed character involving
	HAMZA ABOVE has a decomposition to a combining sequence that can form		HAMZA ABOVE has a decomposition to a combining sequence that can form
	it. For example, ARABIC LETTER U WITH HAMZA ABOVE (U+0677) has a		it. For example, ARABIC LETTER U WITH HAMZA ABOVE (U+0677) has a
	compatibility (???) decomposition into the combining sequence		compatibility (???) decomposition into the combining sequence
	\u'06C7'\u'0674'.		\u'06C7'\u'0674'.
	skipping to change at page 12, line 28 ¶		skipping to change at page 12, line 28 ¶
	5. Acknowledgements		5. Acknowledgements
	The Unicode 7.0.0 changes were extensively discussed within the IAB's		The Unicode 7.0.0 changes were extensively discussed within the IAB's
	Internationalization Program. The authors are grateful for the		Internationalization Program. The authors are grateful for the
	discussions and feedback there, especially from Andrew Sullivan and		discussions and feedback there, especially from Andrew Sullivan and
	David Thaler. Additional information was requested and received from		David Thaler. Additional information was requested and received from
	Mark Davis and Ken Whistler and while they probably do not agree with		Mark Davis and Ken Whistler and while they probably do not agree with
	the necessity of excluding this code point or taking even more		the necessity of excluding this code point or taking even more
	drastic action as their responsibility is to look at the Unicode		drastic action as their responsibility is to look at the Unicode
	Consortium requirements for stability, the decision would not have		Consortium requirements for stability, the decision would not have
	been possible without their input. Several experts and reviewers who		been possible without their input. Thanks to Bill McQuillan for
			reading the document carefully enough to identify and report a
			confusing typographical error. Several experts and reviewers who
	prefer to remain anonymous also provided helpful input and comments		prefer to remain anonymous also provided helpful input and comments
	on preliminary versions of this document.		on preliminary versions of this document.
	6. IANA Considerations		6. IANA Considerations
	When the IANA registry and tables are updated to reflect Unicode		When the IANA registry and tables are updated to reflect Unicode
	7.0.0, changes should be made according to the decisions the IETF		7.0.0, changes should be made according to the decisions the IETF
	makes about Section 3.		makes about Section 3.
	7. Security Considerations		7. Security Considerations
	skipping to change at page 15, line 32 ¶		skipping to change at page 15, line 38 ¶
	RFC Editor: Please remove this appendix before publication.		RFC Editor: Please remove this appendix before publication.
	A.1. Changes from version -00 to -01		A.1. Changes from version -00 to -01
	o Version 01 of this document is an extensive rewrite and		o Version 01 of this document is an extensive rewrite and
	reorganization, reflecting discussions with UTC members and adding		reorganization, reflecting discussions with UTC members and adding
	three more options for discussion to the original proposal to		three more options for discussion to the original proposal to
	simply disallow the new code point.		simply disallow the new code point.
			A.2. Changes from version -01 to -02
			Corrected a typographical error in which Hamza Above was incorrectly
			listed with the wrong code point.
	Authors' Addresses		Authors' Addresses
	John C Klensin		John C Klensin
	1770 Massachusetts Ave, Ste 322		1770 Massachusetts Ave, Ste 322
	Cambridge, MA 02140		Cambridge, MA 02140
	USA		USA
	Phone: +1 617 245 1457		Phone: +1 617 245 1457
	Email: john-ietf@jck.com		Email: john-ietf@jck.com
	Patrik Faltstrom		Patrik Faltstrom
	Netnod		Netnod
	Franzengatan 5		Franzengatan 5
	Stockholm 112 51		Stockholm 112 51
	Sweden		Sweden
	Phone: +46 70 6059051		Phone: +46 70 6059051
	Email: paf@netnod.se		Email: paf@netnod.se
End of changes. 7 change blocks.
	5 lines changed or deleted		12 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/