draft-josefsson-dns-url.txt		rfc4501.txt
	Network Working Group S. Josefsson		Network Working Group S. Josefsson
	Internet-Draft SJD		Request for Comments: 4501 SJD
	Expires: February 2, 2006 August 2005		Category: Standards Track May 2006
	Domain Name System Uniform Resource Identifiers		Domain Name System Uniform Resource Identifiers
	draft-josefsson-dns-url-14
	Status of this Memo
	By submitting this Internet-Draft, each author represents that any		Status of This Memo
	applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-
	Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on February 2, 2006.		This document specifies an Internet standards track protocol for the
			Internet community, and requests discussion and suggestions for
			improvements. Please refer to the current edition of the "Internet
			Official Protocol Standards" (STD 1) for the standardization state
			and status of this protocol. Distribution of this memo is unlimited.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document defines Uniform Resource Identifiers for Domain Name		This document defines Uniform Resource Identifiers for Domain Name
	System resources.		System resources.
	See <http://josefsson.org/dns-url/> for more information.
	Table of Contents		Table of Contents
	1. Introduction and Background . . . . . . . . . . . . . . . . . 3		1. Introduction and Background . . . . . . . . . . . . . . . . . 2
	2. Usage Model . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Usage Model . . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. DNS URI Registration . . . . . . . . . . . . . . . . . . . . . 5		3. DNS URI Registration . . . . . . . . . . . . . . . . . . . . . 3
	4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 9		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	8. Copying Conditions . . . . . . . . . . . . . . . . . . . . . . 10		8. Copying Conditions . . . . . . . . . . . . . . . . . . . . . . 8
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 10		9.1. Normative References . . . . . . . . . . . . . . . . . . 8
	9.2. Informative References . . . . . . . . . . . . . . . . . . 10		9.2. Informative References . . . . . . . . . . . . . . . . . 8
	Appendix A. Revision Changes . . . . . . . . . . . . . . . . . . 11
	A.1. Changes since -06 . . . . . . . . . . . . . . . . . . . . 11
	A.2. Changes since -07 . . . . . . . . . . . . . . . . . . . . 11
	A.3. Changes since -08 . . . . . . . . . . . . . . . . . . . . 12
	A.4. Changes since -09 . . . . . . . . . . . . . . . . . . . . 12
	A.5. Changes since -10 . . . . . . . . . . . . . . . . . . . . 12
	A.6. Changes since -11 . . . . . . . . . . . . . . . . . . . . 12
	A.7. Changes since -12 . . . . . . . . . . . . . . . . . . . . 12
	A.8. Changes since -13 . . . . . . . . . . . . . . . . . . . . 12
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
	Intellectual Property and Copyright Statements . . . . . . . . . . 14
	1. Introduction and Background		1. Introduction and Background
	The Domain Name System (DNS) [1] [2] is a widely deployed system		The Domain Name System (DNS) [1] [2] is a widely deployed system
	used, among other things, to translate host names into IP addresses.		used, among other things, to translate host names into IP addresses.
	Several protocols use Uniform Resource Identifiers (URIs) to refer to		Several protocols use Uniform Resource Identifiers (URIs) to refer to
	data. By defining a URI scheme for DNS data, the gap between these		data. By defining a URI scheme for DNS data, the gap between these
	two worlds is bridged. The DNS URI scheme defined here can be used		two worlds is bridged. The DNS URI scheme defined here can be used
	to reference any data stored in the DNS.		to reference any data stored in the DNS.
	skipping to change at page 7, line 32		skipping to change at page 5, line 32
	this URI scheme places no restrictions.		this URI scheme places no restrictions.
	Intended usage: Whenever it is useful for DNS resources to be		Intended usage: Whenever it is useful for DNS resources to be
	referenced by protocol-independent identifiers. Often, this occurs		referenced by protocol-independent identifiers. Often, this occurs
	when the data is more important than the access method. Since		when the data is more important than the access method. Since
	software in general has coped without this so far, it is not		software in general has coped without this so far, it is not
	anticipated to be implemented widely, nor migrated to by existing		anticipated to be implemented widely, nor migrated to by existing
	systems, but specific solutions (especially security-related) may		systems, but specific solutions (especially security-related) may
	find this appropriate.		find this appropriate.
	Applications and/or protocols that use this scheme include Security-		Applications and/or protocols that use this scheme include
	related software, DNS administration tools, and network programming		Security-related software, DNS administration tools, and network
	packages.		programming packages.
	Interoperability considerations: The data referenced by this URI		Interoperability considerations: The data referenced by this URI
	scheme might be transferred by protocols that are not URI aware (such		scheme might be transferred by protocols that are not URI aware (such
	as the DNS protocol). This is not anticipated to have any serious		as the DNS protocol). This is not anticipated to have any serious
	interoperability impact.		interoperability impact.
	Interoperability problems may occur if one entity understands a new		Interoperability problems may occur if one entity understands a new
	DNS class/type mnemonic that another entity does not. This is an		DNS class/type mnemonic that another entity does not. This is an
	interoperability problem for DNS software in general, although it is		interoperability problem for DNS software in general, although it is
	not a major practical problem for current DNS deployments, as the DNS		not a major practical problem for current DNS deployments, as the DNS
	skipping to change at page 10, line 23		skipping to change at page 8, line 23
	modify, and distribute it in any way that does not diminish the		modify, and distribute it in any way that does not diminish the
	rights of anyone else to use, modify, and distribute it, provided		rights of anyone else to use, modify, and distribute it, provided
	that redistributed derivative works do not contain misleading author		that redistributed derivative works do not contain misleading author
	or version information. Derivative works need not be licensed under		or version information. Derivative works need not be licensed under
	similar terms.		similar terms.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[1] Mockapetris, P., "Domain names - concepts and facilities",		[1] Mockapetris, P., "Domain names - concepts and facilities", STD
	STD 13, RFC 1034, November 1987.		13, RFC 1034, November 1987.
	[2] Mockapetris, P., "Domain names - implementation and		[2] Mockapetris, P., "Domain names - implementation and
	specification", STD 13, RFC 1035, November 1987.		specification", STD 13, RFC 1035, November 1987.
	[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[4] Crocker, D. and P. Overell, "Augmented BNF for Syntax		[4] Crocker, D. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", RFC 4234, October 2005.		Specifications: ABNF", RFC 4234, October 2005.
	[5] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[5] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986,		Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986,
	January 2005.		January 2005.
	9.2. Informative References		9.2. Informative References
	[6] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9,		[6] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC
	RFC 959, October 1985.		959, October 1985.
	[7] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet		[7] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet
	Mail Extensions (MIME) Part Four: Registration Procedures",		Mail Extensions (MIME) Part Four: Registration Procedures", BCP
	BCP 13, RFC 2048, November 1996.		13, RFC 2048, November 1996.
	[8] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer,		[8] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer, "OpenPGP
	"OpenPGP Message Format", RFC 2440, November 1998.		Message Format", RFC 2440, November 1998.
	[9] Eastlake, D. and O. Gudmundsson, "Storing Certificates in the		[9] Eastlake 3rd, D. and O. Gudmundsson, "Storing Certificates in
	Domain Name System (DNS)", RFC 2538, March 1999.		the Domain Name System (DNS)", RFC 2538, March 1999.
	[10] Crawford, M., "Binary Labels in the Domain Name System",		[10] Crawford, M., "Binary Labels in the Domain Name System", RFC
	RFC 2673, August 1999.		2673, August 1999.
	[11] Petke, R. and I. King, "Registration Procedures for URL Scheme		[11] Petke, R. and I. King, "Registration Procedures for URL Scheme
	Names", BCP 35, RFC 2717, November 1999.		Names", BCP 35, RFC 2717, November 1999.
	[12] Connolly, D. and L. Masinter, "The 'text/html' Media Type",		[12] Connolly, D. and L. Masinter, "The 'text/html' Media Type", RFC
	RFC 2854, June 2000.		2854, June 2000.
	[13] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852,		[13] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852,
	July 2004.		July 2004.
	[14] Faltstrom, P., Hoffman, P., and A. Costello,		[14] Faltstrom, P., Hoffman, P., and A. Costello, "Internationalizing
	"Internationalizing Domain Names in Applications (IDNA)",		Domain Names in Applications (IDNA)", RFC 3490, March 2003.
	RFC 3490, March 2003.
	[15] Josefsson, S., "Domain Name System Media Types", RFC 4027,		[15] Josefsson, S., "Domain Name System Media Types", RFC 4027, April
	April 2005.		2005.
	[16] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,		[16] Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,
	"DNS Security Introduction and Requirements", RFC 4033,		"DNS Security Introduction and Requirements", RFC 4033, March
	March 2005.		2005.
	Appendix A. Revision Changes
	Note to RFC editor: Remove this appendix before publication.
	A.1. Changes since -06
	The MIME registration templates for text/dns and application/dns was
	removed, and will be defined in separate documents.
	Improved discussion related to which mnemonics that must be
	supported. The interoperability problem that provoked the
	clarification is also mentioned.
	Security consideration improvements.
	A.2. Changes since -07
	Author/Change Controller changed to author of this document, not
	IESG. Terminology section collapsed into introduction. The second
	paragraph of the introduction rewritten and gives explicit examples.
	Intended usage and applications fields fixed. Moved this revision
	tracking information to an appendix. Mention IDN in charset section.
	All previous thanks to suggestions by Larry Masinter.
	A.3. Changes since -08
	Modifications derived from Last-Call comments: Made more clear that
	DNS URIs does not imply use of the DNS protocol, but the issue is not
	stressed because of the apparent inflamatory state of affairs. Added
	informative references to HTML and FTP. Clarified that dnsname can
	be empty. Clarified that first dnsqueryelement "win" in case of
	ambiguity. Clarified security consideration with respect to unknown
	dnsqueryelements. Use "authority" instead of "server". Say "IANA
	registered" instead of "standard". Interoperability note about
	binary DNS labels. Typos.
	A.4. Changes since -09
	Use legal texts from RFC 3667. Update UTF-8 reference to RFC 3629.
	Simplified introduction. Discuss relative and absolute dnsname's.
	Clarify that empty dnsname correspond to the root. Change so that
	dns:foo?TYPE=A;TYPE=TXT is invalid, instead of meaning TYPE=A. The
	underspecified extension mechanism was dropped; now only TYPE= and
	CLASS= are permitted. Remove background discussion of why the
	dnsname field is made a IDN unaware domain name slot. Use standard
	DNS escaping (i.e, "\." for ".") instead of broken approach that
	violated the URI specification. Improve examples. Add security
	considerations.
	A.5. Changes since -10
	Add section "Usage Model". Move acknowledgements, as per rfc2223bis.
	Add permissive copying condition. Updates to align with RFC 3986.
	A.6. Changes since -11
	Fix typos. IESG feedback: Move RFC2119 reference to normative
	section. Replace OCSP example with X.509 CRL Distribution Point
	extension. Fix ABNF not to use "...".
	A.7. Changes since -12		Author's Address
	Reference MIME and RFC 4027. IESG feedback: Do not mention OpenPGP/		Simon Josefsson
	X.509 as illustrative examples in the introduction section.		SJD
	A.8. Changes since -13		EMail: simon@josefsson.org
	Fix typos. Incorporate RFC Editor fixes.		Full Copyright Statement
	Author's Address		Copyright (C) The Internet Society (2006).
	Simon Josefsson		This document is subject to the rights, licenses and restrictions
	SJD		contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
	Email: simon@josefsson.org		This document and the information contained herein are provided on an
			"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
			OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
			ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
			INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
			INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
			WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property Statement		Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 14, line 29		skipping to change at page 10, line 45
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity		Acknowledgement
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.
	Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 28 change blocks.
	163 lines changed or deleted		61 lines changed or added
This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/