< draft-klensin-idna-5892upd-unicode70-02.txt		draft-klensin-idna-5892upd-unicode70-03.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: July 10, 2015 January 6, 2015
	IDNA Update for Unicode 7.0.0		IDNA Update for Unicode 7.0.0
	draft-klensin-idna-5892upd-unicode70-02.txt		draft-klensin-idna-5892upd-unicode70-03.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
	updates RFC 5982 accordingly. It also applies an editorial		updates RFC 5892 accordingly. It also applies an editorial
	clarification that was the subject of an earlier erratum. In		clarification that was the subject of an earlier erratum. In
	addition, the discussion of the specific issue updates RFC 5894.		addition, the discussion of the specific issue updates RFC 5894.
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 June 10, 2015.		This Internet-Draft will expire on July 10, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	skipping to change at page 2, line 36 ¶		skipping to change at page 2, line 36 ¶
	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 . . . . . . . . . . . . . . . . . 15		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		A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 15
			A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 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 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. Thanks to Bill McQuillan for		been possible without their input. Thanks to Bill McQuillan and Ted
	reading the document carefully enough to identify and report a		Hardie for reading versions of the document carefully enough to
	confusing typographical error. Several experts and reviewers who		identify and report some confusing typographical errors. Several
	prefer to remain anonymous also provided helpful input and comments		experts and reviewers who prefer to remain anonymous also provided
	on preliminary versions of this document.		helpful input and comments 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
	[[CREF1: NOTE IN DRAFT: This section is unchanged in version -01 of		[[CREF1: NOTE IN DRAFT: This section is unchanged in version -01 of
	skipping to change at page 15, line 43 ¶		skipping to change at page 15, line 43 ¶
	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		A.2. Changes from version -01 to -02
	Corrected a typographical error in which Hamza Above was incorrectly		Corrected a typographical error in which Hamza Above was incorrectly
	listed with the wrong code point.		listed with the wrong code point.
	Authors' Addresses		A.3. Changes from version -02 to -03
			Corrected a typographical error in the Abstract in which RFC 5892 was
			incorrectly shown as 5982.
			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. 10 change blocks.
	11 lines changed or deleted		17 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/