< draft-ietf-dnsop-alt-tld-04.txt		draft-ietf-dnsop-alt-tld-05.txt >
	dnsop W. Kumari		dnsop W. Kumari
	Internet-Draft Google		Internet-Draft Google
	Intended status: Informational A. Sullivan		Intended status: Informational A. Sullivan
	Expires: September 22, 2016 Dyn		Expires: March 16, 2017 Dyn
	March 21, 2016		September 12, 2016
	The ALT Special Use Top Level Domain		The ALT Special Use Top Level Domain
	draft-ietf-dnsop-alt-tld-04		draft-ietf-dnsop-alt-tld-05
	Abstract		Abstract
	This document reserves a string (ALT) to be used as a TLD label in		This document reserves a string (ALT) to be used as a TLD label in
	non-DNS contexts or for names that have no meaning in a global		non-DNS contexts or for names that have no meaning in a global
	context. It also provides advice and guidance to developers		context. It also provides advice and guidance to developers
	developing alternate namespaces.		developing alternate namespaces.
	[ Ed note: This document lives in GitHub at:		[ Ed note: This document lives in GitHub at:
	https://github.com/wkumari/draft-wkumari-dnsop-alt-tld . Issues and		https://github.com/wkumari/draft-wkumari-dnsop-alt-tld . Issues and
	pull requests happily accepted. ]		pull requests happily accepted. ]
			[ Question for Working Group. It has been proposed that the string
			.ALT should be replaced with something else e.g. .NOT-DNS. As naming
			discussions in the IETF are always short, simple, and not
			controversial, we figured we should open these for discussion now.
			We would appreciate clear feedback on preference and rationale. ]
	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 September 22, 2016.		This Internet-Draft will expire on March 16, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 2		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2		1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. The ALT namespace . . . . . . . . . . . . . . . . . . . . . . 4		3. The ALT namespace . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Choice of the ALT Name . . . . . . . . . . . . . . . . . 5		3.1. Choice of the ALT Name . . . . . . . . . . . . . . . . . 5
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	4.1. Domain Name Reservation Considerations . . . . . . . . . 6		4.1. Domain Name Reservation Considerations . . . . . . . . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 7		5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
	7. Normative References . . . . . . . . . . . . . . . . . . . . 8		7. Normative References . . . . . . . . . . . . . . . . . . . . 8
	Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 8		Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	Many protocols and systems need to name entities. Names that look		Many protocols and systems need to name entities. Names that look
	like DNS names (a series of labels separated with dots) have become		like DNS names (a series of labels separated with dots) have become
	common, even in systems that are not part of the global DNS		common, even in systems that are not part of the global DNS
	administered by IANA.		administered by IANA.
	This document provides a solution that may be more appropriate than		This document provides a solution that may, in many cases, be more
	[RFC6761] in many cases.		appropriate than [RFC6761].
	This document reserves the label "ALT" (short for "Alternate") as a		This document reserves the label "ALT" (short for "Alternate") as a
	Special Use Domain ([RFC6761]). This label is intended to be used as		Special Use Domain ([RFC6761]). This label is intended to be used as
	the final label to signify that the name is not rooted in the DNS,		the final (rightmost) label to signify that the name is not rooted in
	and that normal registration and lookup rules do not apply.		the DNS, and that normal registration and lookup rules do not apply.
	1.1. Requirements notation		1.1. Requirements notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	1.2. Terminology		1.2. Terminology
	This document assumes familiarity with DNS terms and concepts.		This document assumes familiarity with DNS terms and concepts.
	skipping to change at page 8, line 33 ¶		skipping to change at page 8, line 46 ¶
	<http://www.rfc-editor.org/info/rfc6303>.		<http://www.rfc-editor.org/info/rfc6303>.
	[RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names",		[RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names",
	RFC 6761, DOI 10.17487/RFC6761, February 2013,		RFC 6761, DOI 10.17487/RFC6761, February 2013,
	<http://www.rfc-editor.org/info/rfc6761>.		<http://www.rfc-editor.org/info/rfc6761>.
	Appendix A. Changes / Author Notes.		Appendix A. Changes / Author Notes.
	[RFC Editor: Please remove this section before publication ]		[RFC Editor: Please remove this section before publication ]
			From -04 to -05:
			o Version bump - we are waiting in the queue for progress on SUN,
			bumping this to keep it alive.
	From -03 to -04:		From -03 to -04:
	o 3 changes - the day, the month and the year (a bump to keep		o 3 changes - the day, the month and the year (a bump to keep
	alive).		alive).
	From -02 to -03:		From -02 to -03:
	o Incorporate suggestions from Stephane and Paul Hoffman.		o Incorporate suggestions from Stephane and Paul Hoffman.
	From -01 to -02:		From -01 to -02:
End of changes. 9 change blocks.
	11 lines changed or deleted		22 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/