draft-ietf-dnsext-insensitive-02.txt		draft-ietf-dnsext-insensitive-03.txt
	INTERNET-DRAFT Donald E. Eastlake 3rd		INTERNET-DRAFT Donald E. Eastlake 3rd
	Clarifies STD0013 Motorola Laboratories		Clarifies STD0013 Motorola Laboratories
	Expires August 2003 February 2003		Expires September 2003 April 2003
	Domain Name System (DNS) Case Insensitivity Clarification		Domain Name System (DNS) Case Insensitivity Clarification
	------ ---- ------ ----- ---- ------------- -------------		------ ---- ------ ----- ---- ------------- -------------
	<draft-ietf-dnsext-insensitive-02.txt>		<draft-ietf-dnsext-insensitive-03.txt>
	Donald E. Eastlake 3rd		Donald E. Eastlake 3rd
	Status of This Document		Status of This Document
	Distribution of this document is unlimited. Comments should be sent		Distribution of this document is unlimited. Comments should be sent
	to the DNSEXT working group at namedroppers@ops.ietf.org.		to the DNSEXT working group at namedroppers@ops.ietf.org.
	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 RFC 2026. Internet-Drafts are		all provisions of Section 10 of RFC 2026. Internet-Drafts are
	skipping to change at page 1, line 42		skipping to change at page 2, line 5
	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
	Domain Name System (DNS) names are "case insensitive". This document		Domain Name System (DNS) names are "case insensitive". This document
	explains exactly what that means and provides a clear specification		explains exactly what that means and provides a clear specification
	of the rules. This clarification should not have any interoperability		of the rules. This clarification should not have any interoperability
	consequences.		consequences.
	Copyright (C) 2003 The Internet Society. All Rights Reserved.
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	Acknowledgements		Acknowledgements
	The contributions to this document of Rob Austein, Olafur		The contributions to this document of Rob Austein, Olafur
	Gudmundsson, Daniel J. Anderson, Alan Barrett, Dana, Andrew Main, and		Gudmundsson, Daniel J. Anderson, Alan Barrett, Marc Blanchet, Dana,
	Scott Seligman are gratefully acknowledged.		Andreas Gustafsson, Andrew Main, and Scott Seligman are gratefully
			acknowledged.
	Table of Contents		Table of Contents
	Status of This Document....................................1		Status of This Document....................................1
	Abstract...................................................1		Abstract...................................................1
	Acknowledgements...........................................2		Acknowledgements...........................................2
	Table of Contents..........................................2		Table of Contents..........................................2
	1. Introduction............................................3		1. Introduction............................................3
	skipping to change at page 2, line 34		skipping to change at page 2, line 35
	2.2 Example Labels with Escapes............................4		2.2 Example Labels with Escapes............................4
	2.3 Name Lookup Case Insensitivity.........................4		2.3 Name Lookup Case Insensitivity.........................4
	2.4 Original DNS Label Types...............................5		2.4 Original DNS Label Types...............................5
	3. Additional DNS Case Insensitivity Considerations........5		3. Additional DNS Case Insensitivity Considerations........5
	3.1 CLASS Case Insensitivity Considerations................5		3.1 CLASS Case Insensitivity Considerations................5
	3.2 Extended Label Type Case Insensitivity Considerations..5		3.2 Extended Label Type Case Insensitivity Considerations..5
	4. Case on Input and Output................................6		4. Case on Input and Output................................6
	4.1 DNS Output Case Preservation...........................6		4.1 DNS Output Case Preservation...........................6
	4.2 DNS Input Case Preservation............................6		4.2 DNS Input Case Preservation............................6
	4.3 Wildcard Matching......................................7		4.3 Wildcard Matching......................................7
	5. Security Considerations.................................7		5. Internationalized Domain Names..........................7
			6. Security Considerations.................................7
	Normative References.......................................9		Normative References.......................................9
	Informative References.....................................9		Informative References.....................................9
			-02 to -03 Changes........................................10
	Author's Address..........................................10		Author's Address..........................................10
	Expiration and File Name..................................10		Expiration and File Name..................................10
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	1. Introduction		1. Introduction
	The Domain Name System (DNS) is the global hierarchical replicated		The Domain Name System (DNS) is the global hierarchical replicated
	distributed database system for Internet addressing, mail proxy, and		distributed database system for Internet addressing, mail proxy, and
	other information. Each node in the DNS tree has a name consisting of		other information. Each node in the DNS tree has a name consisting of
	zero or more labels [STD 13][RFC 1591, 2606] which have been		zero or more labels [STD 13][RFC 1591, 2606] that are treated in a
	specified as being treated in a case insensitive fashion. This		case insensitive fashion. This document clarifies the meaning of
	document clarifies the meaning of "case insensitive" for this		"case insensitive" for the DNS.
	application.
	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 [RFC 2119].		document are to be interpreted as described in [RFC 2119].
	2. Case Insensitivity of DNS Labels		2. Case Insensitivity of DNS Labels
	DNS was specified in the era of [ASCII]. DNS names were expected to		DNS was specified in the era of [ASCII]. DNS names were expected to
	look like most host names or Internet email address right halves (the		look like most host names or Internet email address right halves (the
	part after the at-sign ("@")) or be numeric as in the in-addr.arpa		part after the at-sign, "@") or be numeric as in the in-addr.arpa
	part of the DNS name space. For example,		part of the DNS name space. For example,
	foo.example.net.		foo.example.net.
	aol.com.		aol.com.
	www.gnu.ai.mit.edu.		www.gnu.ai.mit.edu.
	or 69.2.0.192.in-addr.arpa.		or 69.2.0.192.in-addr.arpa.
	Case varied alternatives to the above would be DNS names like		Case varied alternatives to the above would be DNS names like
	Foo.ExamplE.net.		Foo.ExamplE.net.
	AOL.COM.		AOL.COM.
	WWW.gnu.AI.mit.EDU.		WWW.gnu.AI.mit.EDU.
	or 69.2.0.192.in-ADDR.ARPA.		or 69.2.0.192.in-ADDR.ARPA.
	The individual octets of which DNS names consist are not limited to		The individual octets of which DNS names consist are not limited to
	valid ASCII character codes. They are defined as 8-bit bytes and all		valid ASCII character codes. They are as 8-bit bytes and all values
	values are allowed. Most applications, however, interprete them		are allowed. Many applications, however, interprete them as ASCII
	as ASCII characters.		characters.
	2.1 Escaping Unusual DNS Label Octets		2.1 Escaping Unusual DNS Label Octets
	An escape is needed for all octet values outside of the inclusive		In Master Files [STD 13] and other human readable and writable ASCII
	range of 0x21 ("!") to 0x7E ("~"). That is to say, all octet values in		contexts, an escape is needed for the byte value for period (0x2E,
	the two inclusive ranges 0x00 to 0x20 and 0x7F to 0xFF.		".") and all octet values outside of the inclusive range of 0x21 ("!")
			to 0x7E ("~"). That is to say, 0x2E and all octet values in the two
			inclusive ranges 0x00 to 0x20 and 0x7F to 0xFF.
	One typographic convention for octets that do not correspond to an		One typographic convention for octets that do not correspond to an
	ASCII printing graphic is to show them as a back-slash followed by the
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	value of the octet as an unsigned integer represented by exactly three		ASCII printing graphic is to use a back-slash followed by the value of
	decimal digits. The same convention can be used for printing ASCII		the octet as an unsigned integer represented by exactly three decimal
	characters. This includes the back-slash character used in this		digits.
	convention itself and the special label separator period (".") which
	can be expressed as \092 and \046 respectively.		The same convention can be used for printing ASCII characters so that
			they will be treated as a normal label character. This includes the
			back-slash character used in this convention itself and the special
			label separator period (".") which can be expressed as \092 and \046
			respectively. It is advisable to avoid using a backslash to quote an
			immediately following non-printing ASCII character code to avoid
			implementation difficulties.
	A back-slash followed by only one or two decimal digits is		A back-slash followed by only one or two decimal digits is
	undefined. A back-slash followed by four decimal digits produces two		undefined. A back-slash followed by four decimal digits produces two
	octets, the first octet having the value of the first three digits		octets, the first octet having the value of the first three digits
	considered as a decimal number and the second octet being the		considered as a decimal number and the second octet being the
	character code for the fourth decimal digit.		character code for the fourth decimal digit.
	Octets, other than those corresponding to the ASCII digits 0 through
	9, can also be protected from recognition, so that they will be
	treated as a normal label character, by a second convention:
	preceding them with a back-slash. This is the most commonly used
	technique for protecting back slash ("\") and period ("."). However,
	it is advisable to avoid using this on other than printing ASCII
	characters to avoid implementation difficulties.
	2.2 Example Labels with Escapes		2.2 Example Labels with Escapes
	The first example below shows embedded spaces and a period (".")		The first example below shows embedded spaces and a period (".")
	within a label. The second one show a 4 octet label where the second		within a label. The second one show a 5 octet label where the second
	octet has all bits zero and the third octet has all bits one.		octet has all bits zero, the third is a backslahs,
			and the fourth octet has all bits one.
	Donald\032E\.\032Eastlake\0323rd.example.		Donald\032E\.\032Eastlake\0323rd.example.
	or a\000\255z.example.		and a\000\\\255z.example.
	2.3 Name Lookup Case Insensitivity		2.3 Name Lookup Case Insensitivity
	The design decision was made that comparisons on name lookup for DNS		The design decision was made that comparisons on name lookup for DNS
	queries should be case insensitive [STD 13]. That is to say, a lookup		queries should be case insensitive [STD 13]. That is to say, a lookup
	string octet with a value in the inclusive range of 0x41 to 0x5A, the		string octet with a value in the inclusive range of 0x41 to 0x5A, the
	upper case ASCII letters, MUST match the identical value and also		upper case ASCII letters, MUST match the identical value and also
	match the corresponding value in the inclusive range 0x61 to 0x7A,		match the corresponding value in the inclusive range 0x61 to 0x7A,
	the lower case ASCII letters. And a lookup string octet with a lower		the lower case ASCII letters. And a lookup string octet with a lower
	case ASCII letter value MUST similarly match the identical value and		case ASCII letter value MUST similarly match the identical value and
	also match the corresponding value in the upper case ASCII letter		also match the corresponding value in the upper case ASCII letter
	range.		range.
	(Historical Note: the terms "upper case" and "lower case" were		(Historical Note: the terms "upper case" and "lower case" were
	invented after movable type became wide spread for printing. The		invented after movable type. The terms originally referred to the
	terms originally referred to the two font trays for storing, in		two font trays for storing, in partitioned areas, the different
	partitioned areas, the different physical type elements. Before		physical type elements. Before movable type, the nearest equivalent
	movable type, the nearest equivalent terms were "majuscule" and		terms were "majuscule" and "minuscule".)
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	"minuscule".)
	One way to implement this rule would be, when comparing octets, to		One way to implement this rule would be, when comparing octets, to
	subtract 0x20 from all octets in the inclusive range 0x61 to 0x7A		subtract 0x20 from all octets in the inclusive range 0x61 to 0x7A
	before the comparison. Such an operation is commonly known as "case		before the comparison. Such an operation is commonly known as "case
	folding" but implementation via case folding is not required. Note		folding" but implementation via case folding is not required. Note
	that the DNS case insensitivity does NOT correspond to the case		that the DNS case insensitivity does NOT correspond to the case
	folding specified in iso-8859-1 or iso-8859-2. For example, the		folding specified in iso-8859-1 or iso-8859-2. For example, the
	octets 0xDD (\221) and 0xFD (\253) do NOT match although in other		octets 0xDD (\221) and 0xFD (\253) do NOT match although in other
	contexts where they are interpreted as the upper and lower case		contexts, where they are interpreted as the upper and lower case
	version of "Y" with an acute accent, they might.		version of "Y" with an acute accent, they might.
	2.4 Original DNS Label Types		2.4 Original DNS Label Types
	DNS labels in wire encoded names have a type associated with them.		DNS labels in wire encoded names have a type associated with them.
	The original DNS standard [RFC 1035] had only two types. ASCII		The original DNS standard [RFC 1035] had only two types. ASCII
	labels, with a length of from zero to 63 octets and indirect labels		labels, with a length of from zero to 63 octets and indirect labels
	which consist of an offset pointer to a name location elsewhere in		which consist of an offset pointer to a name location elsewhere in
	the wire encoding on a DNS message. (The ASCII label of length zero		the wire encoding on a DNS message. (The ASCII label of length zero
	is reserved for use as the name of the root node of the name tree.)		is reserved for use as the name of the root node of the name tree.)
	skipping to change at page 6, line 4		skipping to change at page 5, line 47
	As described in [STD 13] and [RFC 2929], DNS has an additional axis		As described in [STD 13] and [RFC 2929], DNS has an additional axis
	for data location called CLASS. The only CLASS in global use at this		for data location called CLASS. The only CLASS in global use at this
	time is the "IN" or Internet CLASS.		time is the "IN" or Internet CLASS.
	The handling of DNS label case is not CLASS dependent.		The handling of DNS label case is not CLASS dependent.
	3.2 Extended Label Type Case Insensitivity Considerations		3.2 Extended Label Type Case Insensitivity Considerations
	DNS was extended by [RFC 2671] to have additional label type numbers		DNS was extended by [RFC 2671] to have additional label type numbers
	available. (The only such type defined so far is the BINARY type [RFC		available. (The only such type defined so far is the BINARY type [RFC
			2673].)
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	2673].)
	The ASCII case insensitivity conventions, or case folding, only apply		The ASCII case insensitivity conventions, or case folding, only apply
	to ASCII labels, that is to say, label type 0x0, whether appearing		to ASCII labels, that is to say, label type 0x0, whether appearing
	directly or invoked by indirect labels.		directly or invoked by indirect labels.
	4. Case on Input and Output		4. Case on Input and Output
	While ASCII label comparisons are case insensitive, case MUST be		While ASCII label comparisons are case insensitive, case MUST be
	preserved on output, except when output is optimized by the use of		preserved on output, except when output is optimized by the use of
	indirect labels, and preserved when possible on input.		indirect labels, and preserved when convenient on input.
	4.1 DNS Output Case Preservation		4.1 DNS Output Case Preservation
	[STD 13] views the DNS namespace as a node tree. ASCII output is as		[STD 13] views the DNS namespace as a node tree. ASCII output is as
	if a name was marshalled by taking the label on the node whose name		if a name was marshalled by taking the label on the node whose name
	is to be output, converting it to a typographically encoded ASCII		is to be output, converting it to a typographically encoded ASCII
	string, walking up the tree outputting each label encountered, and		string, walking up the tree outputting each label encountered, and
	preceding all labels but the first with a period ("."). Wire output		preceding all labels but the first with a period ("."). Wire output
	follows the same sequence but each label is wire encoded and no		follows the same sequence but each label is wire encoded and no
	periods inserted. No "case conversion" or "case folding" is done		periods inserted. No "case conversion" or "case folding" is done
	skipping to change at page 6, line 42		skipping to change at page 6, line 40
	comparison specified above is done. Thus such optimization MAY		comparison specified above is done. Thus such optimization MAY
	destroy the output preservation of case. This type of optimization is		destroy the output preservation of case. This type of optimization is
	commonly called "name compression".		commonly called "name compression".
	4.2 DNS Input Case Preservation		4.2 DNS Input Case Preservation
	Originally, DNS input came from an ASCII Master File as defined in		Originally, DNS input came from an ASCII Master File as defined in
	[STD 13]. DNS Dynamic update has been added as a source of DNS data		[STD 13]. DNS Dynamic update has been added as a source of DNS data
	[RFC 2136, 3007]. When a node in the DNS name tree is created by such		[RFC 2136, 3007]. When a node in the DNS name tree is created by such
	input, no case conversion is done and the case of ASCII labels is		input, no case conversion is done and the case of ASCII labels is
	preserved if they are for nodes being created. However, no change is		preserved if they are for nodes being created. However, when a name
	made in the name label on nodes that already exist in the DNS data		label is input for a node that already exist in DNS data being
	being augmented or updated. It is quite common for higher level nodes		augmented or updated, the situation is more complex. Implemenations
	to already exist.		may retain the case first input for such a label or allow new input
			to override the old case or maintain separate copies preserving the
			input case.
	For example, if data with owner name "foo.bar.example" is input and		For example, if data with owner name "foo.bar.example" is input and
	then later data with owner name "xyz.BAR.example" is input, the name		then later data with owner name "xyz.BAR.example" is input, the name
	of the label on the "bar.example" node, i.e. "bar", is not changed to		of the label on the "bar.example" node, i.e. "bar", might or might
	"BAR". Thus later retrieval of data stored under "xyz.bar.example" in		not be changed to "BAR" or the actual input case could be preserved.
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	this case can easily result is obtaining data with "xyz.BAR.example".		Thus later retrieval of data stored under "xyz.bar.example" in this
	The same considerations apply when inputting multiple data records		case can easily result is obtaining data with "xyz.BAR.example". The
	with owner names differing only in case. From the example above, if		same considerations apply when inputting multiple data records with
	an "A" record is stored under owner name "xyz.BAR.example" and then a		owner names differing only in case. From the example above, if an "A"
	second "A" record under "XYZ.BAR.example", the second will be stored		record is stored under owner name "xyz.BAR.example" and then a second
	at the node with the first (lower case initial label) name.		"A" record under "XYZ.BAR.example", the second MAY be stored with the
			first (lower case initial label) name.
	Note that the order of insertion into a server database of the DNS		Note that the order of insertion into a server database of the DNS
	name tree nodes that appear in a Master File is not defined so that		name tree nodes that appear in a Master File is not defined so that
	the results of inconsistent capitalization in a Master File are		the results of inconsistent capitalization in a Master File are
	unpredicatable output capitalization.		unpredicatable output capitalization.
	4.3 Wildcard Matching		4.3 Wildcard Matching
	There is one additional instance of note, which reflects the general		There is one additional instance of note, which reflects the general
	rules that output case reflects input case unless there is		rules that output case reflects input case unless there is
	conflicting capitalization in the DNS database or the output case is		conflicting capitalization in the DNS database or the output case is
	hidden by name compression. This is when a query matches a wildcard		hidden by name compression. This is when a query matches a wildcard
	in the DNS database at a server. In that case, the answer SHOULD		in the DNS database at a server. In that case, the answer SHOULD
	reflect the input case of the label or labels that matched the		reflect the input case of the label or labels that matched the
	wildcard unless they are replaced by an indirect label which MAY		wildcard unless they are replaced by an indirect label which MAY
	point to a name with different capitalization.		point to a name with different capitalization.
	5. Security Considerations		5. Internationalized Domain Names
			A scheme has been adopted for "internationalized domain names" and
			"internationalized labels" as described in [RFC 3490, 3454, 3491, and
			3492]. It makes most of [UNICODE] available through a separate
			application level transformation from internationalized domain name
			to DNS domain name and from DNS domain name to internationalized
			domain name. Any case insensitivity that internationalized domain
			names and labels have varies depending on the script and is handled
			entirely as part of the transformation described in [RFC 3454] and
			[RFC 3491] which should be seen for further details. This is not a
			part of the DNS as standardized in STD 13.
			6. Security Considerations
	The equivalence of certain DNS label types with case differences, as		The equivalence of certain DNS label types with case differences, as
	clarified in this document, can lead to security problems. For		clarified in this document, can lead to security problems. For
	example, a user could be confused by believing two domain names		example, a user could be confused by believing two domain names
	differing only in case were actually different names.		differing only in case were actually different names.
			INTERNET-DRAFT DNS Case Insensitivity
	Furthermore, a domain name may be used in contexts other than the		Furthermore, a domain name may be used in contexts other than the
	DNS. It could be used as an index into some case sensitive data base		DNS. It could be used as a case sensitive index into some data base
	system. Or it could be interpreted as binary data by some integrity		system. Or it could be interpreted as binary data by some integrity
	or authentication code system. These problems can usually be handled		or authentication code system. These problems can usually be handled
	by using a standardized or "canonical" form of the DNS ASCII type		by using a standardized or "canonical" form of the DNS ASCII type
	labels, that is, always map the ASCII letter value octets in ASCII		labels, that is, always map the ASCII letter value octets in ASCII
	labels to some specific pre-chosen case, either upper case or lower		labels to some specific pre-chosen case, either upper case or lower
	case. An example of a canonical form for domain names (and also a		case. An example of a canonical form for domain names (and also a
	canonical ordering for them) appears in Section 8 of [RFC 2535]. See		canonical ordering for them) appears in Section 8 of [RFC 2535]. See
	also [UNKRR].		also [UNKRR].
	Finally, a non-DNS name may be stored into DNS with the false		Finally, a non-DNS name may be stored into DNS with the false
	expectation that case will always be preserved. For example, although		expectation that case will always be preserved. For example, although
	this would be quite rare, on a system with case sensitive email		this would be quite rare, on a system with case sensitive email
	address local parts, an attempt to store two "RP" records that		address local parts, an attempt to store two "RP" records that
	differed only in case would probably produce unexpected results that		differed only in case would probably produce unexpected results that
	INTERNET-DRAFT DNS Case Insensitivity
	might have security implications. That is because the entire email		might have security implications. That is because the entire email
	address, including the possibly case sensitive local or left hand		address, including the possibly case sensitive local or left hand
	part, is encoded into a DNS name in a readable fashion where the case		part, is encoded into a DNS name in a readable fashion where the case
	of some letters might be changed on output as described above.		of some letters might be changed on output as described above.
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
	Normative References		Normative References
	[ASCII] - ANSI, "USA Standard Code for Information Interchange",		[ASCII] - ANSI, "USA Standard Code for Information Interchange",
	skipping to change at page 9, line 33		skipping to change at page 9, line 33
	[RFC 3007] - B. Wellington, "Secure Domain Name System (DNS) Dynamic		[RFC 3007] - B. Wellington, "Secure Domain Name System (DNS) Dynamic
	Update", November 2000.		Update", November 2000.
	[STD 13]		[STD 13]
	- P. Mockapetris, "Domain names - concepts and facilities", RFC		- P. Mockapetris, "Domain names - concepts and facilities", RFC
	1034, November 1987.		1034, November 1987.
	- P. Mockapetris, "Domain names - implementation and		- P. Mockapetris, "Domain names - implementation and
	specification", RFC 1035, November 1987.		specification", RFC 1035, November 1987.
	[UNKRR] - Andreas Gustafsson, "Handling of Unknown DNS RR Types",		[UNKRR] - Andreas Gustafsson, "Handling of Unknown DNS RR Types",
	draft-ietf-dnsext-unknown-rrs-04.txt, September 2002.		draft-ietf-dnsext-unknown-rrs-05.txt, March 2003.
	Informative References		Informative References
	[RFC 1591] - J. Postel, "Domain Name System Structure and		[RFC 1591] - J. Postel, "Domain Name System Structure and
	Delegation", March 1994.		Delegation", March 1994.
	[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 2929] - D. Eastlake, E. Brunner-Williams, B. Manning, "Domain		[RFC 2929] - D. Eastlake, E. Brunner-Williams, B. Manning, "Domain
	Name System (DNS) IANA Considerations", September 2000.		Name System (DNS) IANA Considerations", September 2000.
	[RFC 2671] - P. Vixie, "Extension mechanisms for DNS (EDNS0)", August		[RFC 2671] - P. Vixie, "Extension mechanisms for DNS (EDNS0)", 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 3454] - P. Hoffman, M. Blanchet, "Preparation of
			Internationalized String ("stringprep")", December 2002.
	INTERNET-DRAFT DNS Case Insensitivity		INTERNET-DRAFT DNS Case Insensitivity
			[RFC 3490] - P. Faltstrom, P. Hoffman, A. Costello,
			"Internationalizing Domain Names in Applications (IDNA)", March 2003.
			[RFC 3491] - P. Hoffman, M. Blanchet, "Nameprep: A Stringprep Profile
			for Internationalized Domain Names (IDN)", March 2003.
			[RFC 3492] - A. Costello, "Punycode: A Bootstring encoding of Unicode
			for Internationalized Domain Names in Applications (IDNA)", March
			2003.
			[UNICODE] - The Unicode Consortium, "The Unicode Standard",
			<http://www.unicode.org/unicode/standard/standard.html>.
			-02 to -03 Changes
			The following changes were made between draft version -02 and -03:
			1. Add internationalized domain name section and references.
			2. Change to indicate that later input of a label for an existing DNS
			name tree node may or may not be normalized to the earlier input or
			override it or both may be preserved.
			3. Numerous minor wording changes.
	Author's Address		Author's Address
	Donald E. Eastlake 3rd		Donald E. Eastlake 3rd
	Motorola Laboratories		Motorola Laboratories
	155 Beaver Street		155 Beaver Street
	Milford, MA 01757 USA		Milford, MA 01757 USA
	Telephone: +1 508-851-8280 (w)		Telephone: +1 508-851-8280 (w)
	+1 508-634-2066 (h)		+1 508-634-2066 (h)
	EMail: Donald.Eastlake@motorola.com		EMail: Donald.Eastlake@motorola.com
	Expiration and File Name		Expiration and File Name
	This draft expires August 2003.		This draft expires September 2003.
	Its file name is draft-ietf-dnsext-insensitive-02.txt.		Its file name is draft-ietf-dnsext-insensitive-03.txt.
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/