< draft-ietf-dnsext-iana-dns-00.txt		draft-ietf-dnsext-iana-dns-01.txt >
	INTERNET-DRAFT Donald E. Eastlake 3rd		INTERNET-DRAFT Donald E. Eastlake 3rd
	Eric Brunner		Eric Brunner
	Bill Manning		Bill Manning
	Expires: June 2000 February 2000		Expires: December 2000 June 2000
	Domain Name System (DNS) IANA Considerations		Domain Name System (DNS) IANA Considerations
	------ ---- ------ ----- ---- --------------		------ ---- ------ ----- ---- --------------
			<draft-ietf-dnsext-iana-dns-01.txt>
	Status of This Document		Status of This Document
	Distribution of this draft <draft-ietf-dnsext-iana-dns-00.txt>, which		Distribution of this draft, which is intended to become a Best
	is intended to become a Best Current Practice, is unlimited. Comments		Current Practice, is unlimited. Comments should be sent to the DNS
	should be sent to the DNS Working Group mailing list		Working Group mailing list <namedroppers@internic.net> or to the
	<namedroppers@internic.net> or to the authors.		authors.
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six months
	months. Internet-Drafts may be updated, replaced, or obsoleted by		and may be updated, replaced, or obsoleted by other documents at any
	other documents at any time. It is not appropriate to use Internet-		time. It is inappropriate to use Internet- Drafts as reference
	Drafts as reference material or to cite them other than as a		material or to cite them other than as "work in progress."
	``working draft'' or ``work in progress.''
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Abstract		Abstract
	Internet Assigned Number Authority (IANA) parameter assignment		Internet Assigned Number Authority (IANA) parameter assignment
	skipping to change at page 2, line 17 ¶		skipping to change at page 2, line 17 ¶
	Status of This Document....................................1		Status of This Document....................................1
	Abstract...................................................1		Abstract...................................................1
	Table of Contents..........................................2		Table of Contents..........................................2
	1. Introduction............................................3		1. Introduction............................................3
	2. DNS Query/Response Headers..............................3		2. DNS Query/Response Headers..............................3
	2.1 One Spare Bit?.........................................4		2.1 One Spare Bit?.........................................4
	2.2 Opcode Assignment......................................4		2.2 Opcode Assignment......................................4
	2.3 RCODE Assignment.......................................5		2.3 RCODE Assignment.......................................5
	3. DNS Resource Records....................................5		3. DNS Resource Records....................................6
	3.1 RR TYPE IANA Considerations............................7		3.1 RR TYPE IANA Considerations............................7
	3.1.1 Special Note on the OPT RR...........................8		3.1.1 Special Note on the OPT RR...........................8
	3.2 RR CLASS IANA Considerations...........................8		3.2 RR CLASS IANA Considerations...........................8
	3.3 RR NAME Considerations.................................9		3.3 RR NAME Considerations.................................9
	4. Designated Expert......................................10		4. Security Considerations................................10
	5. Security Considerations................................10
	References................................................10
	Authors Addresses.........................................12		References................................................11
	Expiration and File Name..................................12
			Authors Addresses.........................................13
			Expiration and File Name..................................13
	1. Introduction		1. Introduction
	The Domain Name System (DNS) provides replicated distributed secure		The Domain Name System (DNS) provides replicated distributed secure
	hierarchical databases which hierarchically store "resource records"		hierarchical databases which hierarchically store "resource records"
	(RRs) under domain names.		(RRs) under domain names.
	This data is structured into CLASSes and zones which can be		This data is structured into CLASSes and zones which can be
	independently maintained. See [RFC 1034, 1035, 2136, 2181, 2535]		independently maintained. See [RFC 1034, 1035, 2136, 2181, 2535]
	familiarity with which is assumed.		familiarity with which is assumed.
	This document covers, either directly or by reference, general IANA		This document covers, either directly or by reference, general IANA
	parameter assignment considerations applying across DNS query and		parameter assignment considerations applying across DNS query and
	response headers and all RRs. There may be additional IANA		response headers and all RRs. There may be additional IANA
	considerations that apply to only a particular RR type or		considerations that apply to only a particular RR type or
	query/response opcode. See the specific RFC defining that RR type or		query/response opcode. See the specific RFC defining that RR type or
	query/response opcode for such considerations if they have been		query/response opcode for such considerations if they have been
	defined.		defined.
	IANA currently maintains a web page of DNS parameters at		IANA currently maintains a web page of DNS parameters. See
	<http://www.isi.edu/in-notes/iana/assignments/dns-parameters>.		<http://www.iana.org/numbers.htm>.
	"IETF Standards Action", "IETF Consensus", "Specification Required",		"IETF Standards Action", "IETF Consensus", "Specification Required",
	and "Private Use" are as defined in [RFC 2434].		and "Private Use" are as defined in [RFC 2434].
	2. DNS Query/Response Headers		2. DNS Query/Response Headers
	The header for DNS queries and responses contains field/bits in the		The header for DNS queries and responses contains field/bits in the
	following diagram taken from [RFC 2136, 2535]:		following diagram taken from [RFC 2136, 2535]:
	1 1 1 1 1 1		1 1 1 1 1 1
	skipping to change at page 5, line 10 ¶		skipping to change at page 5, line 10 ¶
	3 available for assignment		3 available for assignment
	4 Notify [RFC 1996]		4 Notify [RFC 1996]
	5 Update [RFC 2136]		5 Update [RFC 2136]
	6-15 available for assignment		6-15 available for assignment
	2.3 RCODE Assignment		2.3 RCODE Assignment
	It would appear from the DNS header above that only four bits of		It would appear from the DNS header above that only four bits of
	RCODE, or response/error code are available. However, RCODEs can		RCODE, or response/error code are available. However, RCODEs can
	appear not only at the top level of a DNS response but also inside		appear not only at the top level of a DNS response but also inside
	TSIG RRs [RFC XXX3] and OPT RRs [RFC 2671]. The OPT RR provides an		OPT RRs [RFC 2671], TSIG RRs [RFC 2845], and TKEY RRs [draft-ietf-
	eight bit extension resulting in a 12 bit RCODE field and the TSIG RR		dnsext-tkey-*.txt]. The OPT RR provides an eight bit extension
	has a 16 bit RCODE field.		resulting in a 12 bit RCODE field and the TSIG and TKEY RRs have a 16
			bit RCODE field.
	RCODE Name Description Reference		Error codes appearing in the DNS header and in these three RR types
			all refer to the same error code space with the single exception of
			error code 16 which has a different meaning in the OPT RR from its
			meaning in other contexts. See table below.
			RCODE Name Description Reference
	Decimal		Decimal
	Hexadecimal		Hexadecimal
	0 NoError No Error [RFC 1035]		0 NoError No Error [RFC 1035]
	1 FormErr Format Error [RFC 1035]		1 FormErr Format Error [RFC 1035]
	2 ServFail Server Failure [RFC 1035]		2 ServFail Server Failure [RFC 1035]
	3 NXDomain Non-Existent Domain [RFC 1035]		3 NXDomain Non-Existent Domain [RFC 1035]
	4 NotImp Not Implemented [RFC 1035]		4 NotImp Not Implemented [RFC 1035]
	5 Refused Query Refused [RFC 1035]		5 Refused Query Refused [RFC 1035]
	6 YXDomain Name Exists when it should not [RFC 2136]		6 YXDomain Name Exists when it should not [RFC 2136]
	7 YXRRSet RR Set Exists when it should not [RFC 2136]		7 YXRRSet RR Set Exists when it should not [RFC 2136]
	8 NXRRSet RR Set that should exist does not [RFC 2136]		8 NXRRSet RR Set that should exist does not [RFC 2136]
	9 NotAuth Server Not Authoritative for zone [RFC 2136]		9 NotAuth Server Not Authoritative for zone [RFC 2136]
	10 NotZone Name not contained in zone [RFC 2136]		10 NotZone Name not contained in zone [RFC 2136]
	11-15 available for assignment		11-15 available for assignment
	16 BADVERS Bad OPT Version [RFC 2671]		16 BADVERS Bad OPT Version [RFC 2671]
	16 BADSIG TSIG Signature Failure [RFC XXX3]		16 BADSIG TSIG Signature Failure [RFC 2845]
	17 BADKEY Key not recognized [RFC XXX3]		17 BADKEY Key not recognized [RFC 2845]
	18 BADTIME Signature out of time window [RFC XXX3]		18 BADTIME Signature out of time window [RFC 2845]
	19-3840 available for assignment		19 BADMODE Bad TKEY Mode [draft-ietf-dnsext-tkey-*.txt]
	0x0013-0x0F00		20 BADNAME Duplicate key name [draft-ietf-dnsext-tkey-*.txt]
	3841-4095 Private Use		21 BADALG Algorithm not supported [draft-ietf-dnsext-tkey-*.txt]
			22-3840 available for assignment
			0x0016-0x0F00
			3841-4095 Private Use
	0x0F01-0x0FFF		0x0F01-0x0FFF
	4096-65535 available for assignment		4096-65535 available for assignment
	0x1000-0xFFFF		0x1000-0xFFFF
	Since it is important that RCODEs be understood for interoperability,		Since it is important that RCODEs be understood for interoperability,
	assignment of new RCODE listed above as "available for assignment"		assignment of new RCODE listed above as "available for assignment"
	requires an IETF Consensus.		requires an IETF Consensus.
	3. DNS Resource Records		3. DNS Resource Records
	All RRs have the same top level format shown in the figure below		All RRs have the same top level format shown in the figure below
	taken from [RFC 1035]:		taken from [RFC 1035]:
	skipping to change at page 7, line 21 ¶		skipping to change at page 7, line 21 ¶
	used in queries. Meta-TYPEs designate transient data associated with		used in queries. Meta-TYPEs designate transient data associated with
	an particular DNS message and in some cases can also be used in		an particular DNS message and in some cases can also be used in
	queries. Thus far, data TYPEs have been assigned from 1 upwards plus		queries. Thus far, data TYPEs have been assigned from 1 upwards plus
	the block from 100 through 103 while Q and Meta Types have been		the block from 100 through 103 while Q and Meta Types have been
	assigned from 255 downwards (except for the OPT Meta-RR which is		assigned from 255 downwards (except for the OPT Meta-RR which is
	assigned TYPE 41). There have been DNS implementations which made		assigned TYPE 41). There have been DNS implementations which made
	caching decisions based on the top bit of the bottom byte of the RR		caching decisions based on the top bit of the bottom byte of the RR
	TYPE.		TYPE.
	There are currently three Meta-TYPEs assigned: OPT [RFC 2671], TSIG		There are currently three Meta-TYPEs assigned: OPT [RFC 2671], TSIG
	[RFC XXX3], and TKEY [work in progress].		[RFC 2845], and TKEY [draft-ietf-dnsext-tkey-*.txt].
	There are currently five QTYPEs assigned: * (all), MAILA, MAILB,		There are currently five QTYPEs assigned: * (all), MAILA, MAILB,
	AXFR, and IXFR.		AXFR, and IXFR.
	Considerations for the allocation of new RR TYPEs are as follows:		Considerations for the allocation of new RR TYPEs are as follows:
	Decimal		Decimal
	Hexadecimal		Hexadecimal
	0		0
	skipping to change at page 8, line 43 ¶		skipping to change at page 8, line 43 ¶
	0		0
	0x0000 - assignment requires an IETF Standards Action.		0x0000 - assignment requires an IETF Standards Action.
	1		1
	0x0001 - Internet (IN).		0x0001 - Internet (IN).
	2		2
	0x0002 - available for assignment by IETF Consensus as a data CLASS.		0x0002 - available for assignment by IETF Consensus as a data CLASS.
	3		3
	0x0003 - Chaos (CH) [Moon 81].		0x0003 - Chaos (CH) [Moon 1981].
	4		4
	0x0004 - Hesiod (HS) [Dyer 87].		0x0004 - Hesiod (HS) [Dyer 1987].
	5 - 127		5 - 127
	0x0005 - 0x007F - available for assignment by IETF Consensus as data		0x0005 - 0x007F - available for assignment by IETF Consensus as data
	CLASSes only.		CLASSes only.
	128 - 253		128 - 253
	0x0080 - 0x00FD - available for assignment by IETF Consensus as		0x0080 - 0x00FD - available for assignment by IETF Consensus as
	QCLASSes only.		QCLASSes only.
	254		254
	skipping to change at page 9, line 38 ¶		skipping to change at page 9, line 38 ¶
	3.3 RR NAME Considerations		3.3 RR NAME Considerations
	DNS NAMEs are sequences of labels [RFC 1035]. The last label in each		DNS NAMEs are sequences of labels [RFC 1035]. The last label in each
	NAME is "ROOT" which is the zero length label. By definition, the		NAME is "ROOT" which is the zero length label. By definition, the
	null or ROOT label can not be used for any other NAME purpose.		null or ROOT label can not be used for any other NAME purpose.
	At the present time, there are two categories of label types, data		At the present time, there are two categories of label types, data
	labels and compression labels. Compression labels are pointers to		labels and compression labels. Compression labels are pointers to
	data labels elsewhere within an RR or DNS message and are intended to		data labels elsewhere within an RR or DNS message and are intended to
	shorten the wire encoding of NAMEs. The two existing data label		shorten the wire encoding of NAMEs. The two existing data label
	types are frequently referred to as ASCII and Binary. ASCII labels		types are sometimes referred to as Text and Binary. Text labels can,
	can, in fact, include any octet value including zero octets but most		in fact, include any octet value including zero octets but most
	current uses involve only [US-ASCII] For retrieval ASCII labels are		current uses involve only [US-ASCII]. For retrieval, Text labels are
	defined to treat upper and lower case letters the same. Binary		defined to treat ASCII upper and lower case letter codes as matching.
	labels are bit sequences [RFC 2673].		Binary labels are bit sequences [RFC 2673].
	IANA considerations for label types are given in [RFC 2671].		IANA considerations for label types are given in [RFC 2671].
	NAMEs are local to a CLASS. The Hesiod [Dyer 87] and Chaos [Moon 81]		NAMEs are local to a CLASS. The Hesiod [Dyer 1987] and Chaos [Moon
	CLASSes are essentially for local use. The IN or Internet CLASS is		1981] CLASSes are essentially for local use. The IN or Internet
	thus the only DNS CLASS in global use on the Internet at this time.		CLASS is thus the only DNS CLASS in global use on the Internet at
			this time.
	A somewhat dated description of name allocation in the IN Class is		A somewhat dated description of name allocation in the IN Class is
	given in [RFC 1591]. Some information on reserved top level domain		given in [RFC 1591]. Some information on reserved top level domain
	names is in Best Current Practice 32 [RFC 2606].		names is in Best Current Practice 32 [RFC 2606].
	4. Designated Expert		4. Security Considerations
	To provide additional support to IANA in the DNS area, the IESG MAY
	appoint a designed expert.
	5. Security Considerations
	This document addresses IANA considerations in the allocation of		This document addresses IANA considerations in the allocation of
	general DNS parameters, not security. See [RFC 2535] for secure DNS		general DNS parameters, not security. See [RFC 2535] for secure DNS
	considerations.		considerations.
	References		References
	[Dyer 87] - Dyer, S., and F. Hsu, "Hesiod", Project Athena Technical		[Dyer 1987] - Dyer, S., and F. Hsu, "Hesiod", Project Athena
	Plan - Name Service, April 1987,		Technical Plan - Name Service, April 1987,
	[Moon 81] - D. Moon, "Chaosnet", A.I. Memo 628, Massachusetts		[Moon 1981] - D. Moon, "Chaosnet", A.I. Memo 628, Massachusetts
	Institute of Technology Artificial Intelligence Laboratory, June		Institute of Technology Artificial Intelligence Laboratory, June
	1981.		1981.
	[RFC 1034] - P. Mockapetris, "Domain Names - Concepts and		[RFC 1034] - P. Mockapetris, "Domain Names - Concepts and
	Facilities", STD 13, November 1987.		Facilities", STD 13, November 1987.
	[RFC 1035] - P. Mockapetris, "Domain Names - Implementation and		[RFC 1035] - P. Mockapetris, "Domain Names - Implementation and
	Specifications", STD 13, November 1987.		Specifications", STD 13, November 1987.
	[RFC 1591] - J. Postel, "Domain Name System Structure and		[RFC 1591] - J. Postel, "Domain Name System Structure and
	skipping to change at page 11, line 8 ¶		skipping to change at page 11, line 44 ¶
	[RFC 2535] - D. Eastlake, "Domain Name System Security Extensions",		[RFC 2535] - D. Eastlake, "Domain Name System Security Extensions",
	March 1999.		March 1999.
	[RFC 2606] - D. Eastlake, A. Panitz, "Reserved Top Level DNS Names",		[RFC 2606] - D. Eastlake, A. Panitz, "Reserved Top Level DNS Names",
	June 1999.		June 1999.
	[RFC 2671] - P. Vixie, "Extension mechanisms for DNS (EDNS0)", August		[RFC 2671] - P. Vixie, "Extension mechanisms for DNS (EDNS0)", August
	1999.		1999.
	[RFC 2672] - M. Crawford, " Non-Terminal DNS Name Redirection",		[RFC 2672] - M. Crawford, "Non-Terminal DNS Name Redirection", August
	August 1999.		1999.
	[RFC 2673] - M. Crawford, "Binary Labels in the Domain Name System",		[RFC 2673] - M. Crawford, "Binary Labels in the Domain Name System",
	August 1999.		August 1999.
	[RFC XXX3] - P. Vixie, O. Gudmundsson, D. Eastlake, B. Wellington,		[RFC 2845] - P. Vixie, O. Gudmundsson, D. Eastlake, B. Wellington,
	"Secret Key Transaction Signatures for DNS (TSIG)", xxx 2000 (draft-		"Secret Key Transaction Authentication for DNS (TSIG)", May 2000.
	ietf-dnsind-tsig-*.txt).
	[US-ASCII] - ANSI, "USA Standard Code for Information		[draft-ietf-dnsext-tkey-*.txt] - D. Eastlake, "Secret Key
	Interchange", X3.4, American National Standards Institute: New York,		Establishment for DNS (TKEY RR)", xxx 2000.
	1968.
			[US-ASCII] - ANSI, "USA Standard Code for Information Interchange",
			X3.4, American National Standards Institute: New York, 1968.
	Authors Addresses		Authors Addresses
	Donald E. Eastlake 3rd		Donald E. Eastlake 3rd
	Motorola		Motorola
	65 Shindegan Hill Road		140 Forest Avenue
	Carmel, NY 10512 USA		Hudson, MA 01749 USA
	Telephone: +1-914-276-2668 (h)		Telephone: +1-978-562-2827 (h)
	+1-508-261-5434 (w)		+1-508-261-5434 (w)
	email: dee3@torque.pothole.com		fax: +1-508-261-4447 (w)
			email: Donald.Eastlake@motorola.com
	Eric Brunner		Eric Brunner
	1415 Forest Avenue		Engage Technologies
	Portland, ME 04103 USA		100 Brickstone Square, 2nd Floor
			Andover, MA 01810
	Telephone: +1 207-797-0525		Telephone: +1-978-684-7796 (voice)
	email: brunner@world.std.com		+1-978-684-3636 (fax)
			email: brunner@engage.com
	Bill Manning		Bill Manning
	USC/ISI		USC/ISI
	4676 Admiralty Way, #1001		4676 Admiralty Way, #1001
	Marina del Rey, CA 90292 USA		Marina del Rey, CA 90292 USA
	Telephone: +1 310 822 1511		Telephone: +1 310 822 1511
	email: bmanning@isi.edu		email: bmanning@isi.edu
	Expiration and File Name		Expiration and File Name
	This draft expires August 2000.		This draft expires December 2000.
	Its file name is draft-ietf-dnsext-iana-dns-00.txt.		Its file name is draft-ietf-dnsext-iana-dns-02.txt.
End of changes. 31 change blocks.
	80 lines changed or deleted		88 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/