< draft-ietf-dnsop-alt-tld-12.txt		draft-ietf-dnsop-alt-tld-13.txt >
	dnsop W. Kumari		dnsop W. Kumari
	Internet-Draft Google		Internet-Draft Google
	Intended status: Informational A. Sullivan		Intended status: Informational A. Sullivan
	Expires: February 24, 2020 Oracle		Expires: 23 December 2021 Oracle
	August 23, 2019		21 June 2021
	The ALT Special Use Top Level Domain		The ALT Special Use Top Level Domain
	draft-ietf-dnsop-alt-tld-12		draft-ietf-dnsop-alt-tld-13
	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. It also provides advice and guidance to developers		non-DNS contexts. It also provides advice and guidance to developers
	developing alternative namespaces.		developing alternative namespaces.
	[Ed note: Text inside square brackets ([]) is additional background		[Ed note: Text inside square brackets ([]) is additional background
	information, answers to frequently asked questions, general musings,		information, answers to frequently asked questions, general musings,
	etc. They will be removed before publication. This document is		etc. They will be removed before publication. This document is
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 February 24, 2020.		This Internet-Draft will expire on 23 December 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2021 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/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		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 . . . . . . . . . . . . . . . . . . 2
	1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		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 . . . . . . . . . . . . . . . . . 4		3.1. Choice of the ALT Name . . . . . . . . . . . . . . . . . 4
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	skipping to change at page 3, line 12 ¶		skipping to change at page 3, line 12 ¶
	"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.
	Please see [RFC1034] for background and concepts, and [RFC7719] for		Please see [RFC1034] for background and concepts, and [RFC7719] for
	terminology. Readers are also expected to be familiar with the		terminology. Readers are also expected to be familiar with the
	discussions in [RFC8244]		discussions in [RFC8244]
	o DNS name: Domain names that are intended to be used with DNS		* DNS name: Domain names that are intended to be used with DNS
	resolution, either in the global DNS or in some other context		resolution, either in the global DNS or in some other context
	o DNS context: The namespace anchored at the globally-unique DNS		* DNS context: The namespace anchored at the globally-unique DNS
	root. This is the namespace or context that "normal" DNS uses.		root. This is the namespace or context that "normal" DNS uses.
	o non-DNS context: Any other (alternative) namespace.		* non-DNS context: Any other (alternative) namespace.
	o pseudo-TLD: A label that appears in a fully-qualified domain name		* pseudo-TLD: A label that appears in a fully-qualified domain name
	in the position of a TLD, but which is not registered in the		in the position of a TLD, but which is not registered in the
	global DNS. This term is not intended to be pejorative.		global DNS. This term is not intended to be pejorative.
	o TLD: The last visible label in either a fully-qualified domain		* TLD: The last visible label in either a fully-qualified domain
	name or a name that is qualified relative to the root. See the		name or a name that is qualified relative to the root. See the
	discussion in Section 2.		discussion in Section 2.
	2. Background		2. Background
	The success of the DNS makes it a natural starting point for systems		The success of the DNS makes it a natural starting point for systems
	that need to name entities in a non-DNS context.		that need to name entities in a non-DNS context.
	In many cases, these systems build a DNS-style tree parallel to, but		In many cases, these systems build a DNS-style tree parallel to, but
	separate from, the global DNS. They often use a pseudo-TLD to cause		separate from, the global DNS. They often use a pseudo-TLD to cause
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 8 ¶
	While these are not DNS names, in order for this technique to be		While these are not DNS names, in order for this technique to be
	effective the names need to continue to follow both the DNS format		effective the names need to continue to follow both the DNS format
	and conventions (a prime consideration for alternative name formats		and conventions (a prime consideration for alternative name formats
	is that they can be entered in places that normally take DNS context		is that they can be entered in places that normally take DNS context
	names); this rules out using suffixes that do not follow the usual		names); this rules out using suffixes that do not follow the usual
	letter, digit, and hyphen label convention.		letter, digit, and hyphen label convention.
	A short label was deemed desirable for a number of reasons,		A short label was deemed desirable for a number of reasons,
	including:		including:
	o this is a switch to other resolution contexts, some which may have		* this is a switch to other resolution contexts, some which may have
	long labels (for example derived from public keys).		long labels (for example derived from public keys).
	o some queries will undoubtedly leak into the DNS. As many of these		* some queries will undoubtedly leak into the DNS. As many of these
	alternate resolution systems are specifically designed for		alternate resolution systems are specifically designed for
	privacy, limiting how far they leak is desirable.		privacy, limiting how far they leak is desirable.
	o as there are not protocol police, the label needs to be attractive		* as there are not protocol police, the label needs to be attractive
	to implementors of alternate resolution contexts so that they are		to implementors of alternate resolution contexts so that they are
	willing to use this.		willing to use this.
	4. IANA Considerations		4. IANA Considerations
	The IANA is requested to add the ALT string to the "Special-Use		The IANA is requested to add the ALT string to the "Special-Use
	Domain Name" registry ([RFC6761], and reference this document.		Domain Name" registry ([RFC6761], and reference this document.
	4.1. Domain Name Reservation Considerations		4.1. Domain Name Reservation Considerations
	skipping to change at page 8, line 13 ¶		skipping to change at page 8, line 13 ¶
	2015, <https://www.rfc-editor.org/info/rfc7686>.		2015, <https://www.rfc-editor.org/info/rfc7686>.
	[RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS		[RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
	Terminology", RFC 7719, DOI 10.17487/RFC7719, December		Terminology", RFC 7719, DOI 10.17487/RFC7719, December
	2015, <https://www.rfc-editor.org/info/rfc7719>.		2015, <https://www.rfc-editor.org/info/rfc7719>.
	8.2. Informative References		8.2. Informative References
	[Dingledine2004]		[Dingledine2004]
	Dingledine, R., Mathewson, N., and P. Syverson, "Tor: The		Dingledine, R., Mathewson, N., and P. Syverson, "Tor: The
	Second-Generation Onion Router", , 8 2004,		Second-Generation Onion Router", , August 2004,
	<<https://svn.torproject.org/svn/projects/design-paper/		<<https://svn.torproject.org/svn/projects/design-paper/
	tor-design.html>>.		tor-design.html>>.
	[RFC8198] Fujiwara, K., Kato, A., and W. Kumari, "Aggressive Use of		[RFC8198] Fujiwara, K., Kato, A., and W. Kumari, "Aggressive Use of
	DNSSEC-Validated Cache", RFC 8198, DOI 10.17487/RFC8198,		DNSSEC-Validated Cache", RFC 8198, DOI 10.17487/RFC8198,
	July 2017, <https://www.rfc-editor.org/info/rfc8198>.		July 2017, <https://www.rfc-editor.org/info/rfc8198>.
	[RFC8244] Lemon, T., Droms, R., and W. Kumari, "Special-Use Domain		[RFC8244] Lemon, T., Droms, R., and W. Kumari, "Special-Use Domain
	Names Problem Statement", RFC 8244, DOI 10.17487/RFC8244,		Names Problem Statement", RFC 8244, DOI 10.17487/RFC8244,
	October 2017, <https://www.rfc-editor.org/info/rfc8244>.		October 2017, <https://www.rfc-editor.org/info/rfc8244>.
	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 -12 to -13:
			* Just bumping versions to prevent expiration.
	From -08 to -12:		From -08 to -12:
	o Just bumping versions to prevent expiration.		* Just bumping versions to prevent expiration.
	o Updated references (aggressive-nsec is now RFC 8198, draft-ietf-		* Updated references (aggressive-nsec is now RFC 8198, draft-ietf-
	dnsop-sutld-ps is now 8244).		dnsop-sutld-ps is now 8244).
	From -07 to -08:		From -07 to -08:
	o Made it clear that this is only for non-DNS.		* Made it clear that this is only for non-DNS.
	o As per Interim consensus, removed the "add this to local zones"		* As per Interim consensus, removed the "add this to local zones"
	text.		text.
	o Added a Privacy Considerations section		* Added a Privacy Considerations section
	o Grammar fix -- "alternative" is more correct than "alternate",		* Grammar fix -- "alternative" is more correct than "alternate",
	replaced.		replaced.
	From -06 to -07:		From -06 to -07:
	o Rolled up the GItHub releases in to a full release.		* Rolled up the GItHub releases in to a full release.
	From -07.2 to -07.3 (GitHub point release):		From -07.2 to -07.3 (GitHub point release):
	Removed 'sandbox' at Stephane's suggestion - https://www.ietf.org/		Removed 'sandbox' at Stephane's suggestion - https://www.ietf.org/
	mail-archive/web/dnsop/current/msg18495.html		mail-archive/web/dnsop/current/msg18495.html
	Suggested (in 4.1 bullet 3) that DNS libraries ignore these -- Bob		Suggested (in 4.1 bullet 3) that DNS libraries ignore these -- Bob
	Harold - https://mailarchive.ietf.org/arch/msg/dnsop/		Harold - https://mailarchive.ietf.org/arch/msg/dnsop/
	a_ruPf8osSzi_hCzCqOxYLXhYoA		a_ruPf8osSzi_hCzCqOxYLXhYoA
	Added some pointers to the SUTLD document.		Added some pointers to the SUTLD document.
	From -07.1 to -07.2 (Github point release):		From -07.1 to -07.2 (Github point release):
	o Reverted the <TBD> string (at request of chairs).		* Reverted the <TBD> string (at request of chairs).
	o Added an editors note explaining the above.		* Added an editors note explaining the above.
	o Removed some more background, editorializing, etc.		* Removed some more background, editorializing, etc.
	From -06 to -07.1 (https://github.com/wkumari/draft-wkumari-dnsop-		From -06 to -07.1 (https://github.com/wkumari/draft-wkumari-dnsop-
	alt-tld/tree/7988fcf06100f7a17f21e6993b781690b5774472):		alt-tld/tree/7988fcf06100f7a17f21e6993b781690b5774472):
	o Replaced ALT with <TBD> at the suggestions of George.		* Replaced ALT with <TBD> at the suggestions of George.
	From -05 to -06:		From -05 to -06:
	o Removed a large amount of background - we now have the (adopted)		* Removed a large amount of background - we now have the (adopted)
	tldr document for that.		tldr document for that.
	o Made it clear that pseudo-TLD is not intended to be pejorative.		* Made it clear that pseudo-TLD is not intended to be pejorative.
	o Tried to make it cleat that this is something people can choose to		* Tried to make it cleat that this is something people can choose to
	use - or not.		use - or not.
	From -04 to -05:		From -04 to -05:
	o Version bump - we are waiting in the queue for progress on SUN,		* Version bump - we are waiting in the queue for progress on SUN,
	bumping this to keep it alive.		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		* 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.		* Incorporate suggestions from Stephane and Paul Hoffman.
	From -01 to -02:		From -01 to -02:
	o Merged a bunch of changes from Paul Hoffman. Thanks for sending a		* Merged a bunch of changes from Paul Hoffman. Thanks for sending a
	git pull.		git pull.
	From -00 to 01:		From -00 to 01:
	o Removed the "delegated to new style AS112 servers" text -this was		* Removed the "delegated to new style AS112 servers" text -this was
	legacy from the omnicient AS112 days. (Joe Abley)		legacy from the omnicient AS112 days. (Joe Abley)
	o Removed the "Advice to implemntors" section. This used to		* Removed the "Advice to implemntors" section. This used to
	recommend that people used a subdomain of a domain in the DNS. It		recommend that people used a subdomain of a domain in the DNS. It
	was pointed out that this breaks things badly if the domain		was pointed out that this breaks things badly if the domain
	expires.		expires.
	o Added text about why we don't want to adminster a registry for		* Added text about why we don't want to adminster a registry for
	ALT.		ALT.
	From Individual-06 to DNSOP-00		From Individual-06 to DNSOP-00
	o Nothing changed, simply renamed draft-wkumari-dnsop-alt-tld to		* Nothing changed, simply renamed draft-wkumari-dnsop-alt-tld to
	draft-ietf-dnsop-alt-tld		draft-ietf-dnsop-alt-tld
	From -05 to -06		From -05 to -06
	o Incorporated comments from a number of people, including a number		* Incorporated comments from a number of people, including a number
	of suggestion heard at the IETF meeting in Dallas, and the DNSOP		of suggestion heard at the IETF meeting in Dallas, and the DNSOP
	Interim meeting in May, 2015.		Interim meeting in May, 2015.
	o Removed the "Let's have an (optional) IANA registry for people to		* Removed the "Let's have an (optional) IANA registry for people to
	(opportinistically) register their string, if they want that		(opportinistically) register their string, if they want that
	option" stuff. It was, um, optional....		option" stuff. It was, um, optional....
	From -04 to -05		From -04 to -05
	o Went through and made sure that I'd captured the feedback		* Went through and made sure that I'd captured the feedback
	received.		received.
	o Comments from Ed Lewis.		* Comments from Ed Lewis.
	o Filled in the "Domain Name Reservation Considerations" section of		* Filled in the "Domain Name Reservation Considerations" section of
	RFC6761.		RFC6761.
	o Removed examples from .Onion.		* Removed examples from .Onion.
	From -03 to -04		From -03 to -04
			* Incorporated some comments from Paul Hoffman
	o Incorporated some comments from Paul Hoffman
	From -02 to -03		From -02 to -03
	o After discussions with chairs, made this much more generic (not
			* After discussions with chairs, made this much more generic (not
	purely non-DNS), and some cleanup.		purely non-DNS), and some cleanup.
	From -01 to -02		From -01 to -02
	o Removed some fluffy wording, tightened up the language some.		* Removed some fluffy wording, tightened up the language some.
	From -00 to -01.		From -00 to -01.
	o Fixed the abstract.		* Fixed the abstract.
	o Recommended that folk root their non-DNS namespace under a DNS		* Recommended that folk root their non-DNS namespace under a DNS
	namespace that they control (Joe Abley)		namespace that they control (Joe Abley)
	Authors' Addresses		Authors' Addresses
	Warren Kumari		Warren Kumari
	Google		Google
	1600 Amphitheatre Parkway		1600 Amphitheatre Parkway
	Mountain View, CA 94043		Mountain View, CA, 94043
	US		United States of America
	Email: warren@kumari.net		Email: warren@kumari.net
	Andrew Sullivan		Andrew Sullivan
	Oracle		Oracle
	150 Dow Street		150 Dow Street
	Manchester, NH 03101		Manchester, NH, 03101
	US		United States of America
	Email: asullivan@dyn.com		Email: asullivan@dyn.com
End of changes. 50 change blocks.
	60 lines changed or deleted		63 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/