draft-ietf-dnsext-insensitive-05.txt | draft-ietf-dnsext-insensitive-06.txt | |||
---|---|---|---|---|
INTERNET-DRAFT Donald E. Eastlake 3rd | INTERNET-DRAFT Donald E. Eastlake 3rd | |||
Updates RFC 1034, 1035 Motorola Laboratories | Updates RFC 1034, 1035 Motorola Laboratories | |||
Expires July 2005 January 2005 | Expires January 2006 July 2005 | |||
Domain Name System (DNS) Case Insensitivity Clarification | Domain Name System (DNS) Case Insensitivity Clarification | |||
------ ---- ------ ----- ---- ------------- ------------- | ------ ---- ------ ----- ---- ------------- ------------- | |||
<draft-ietf-dnsext-insensitive-05.txt> | <draft-ietf-dnsext-insensitive-06.txt> | |||
Donald E. Eastlake 3rd | Donald E. Eastlake 3rd | |||
Status of This Document | Status of This Document | |||
By submitting this Internet-Draft, I certify that any applicable | By submitting this Internet-Draft, each author represents that any | |||
patent or other IPR claims of which I am aware have been disclosed, | applicable patent or other IPR claims of which he or she is aware | |||
or will be disclosed, and any of which I become aware will be | have been or will be disclosed, and any of which he or she becomes | |||
disclosed, in accordance with RFC 3668. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
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. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
Drafts. | Drafts. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
skipping to change at page 1, line 41 | skipping to change at page 1, line 41 | |||
material or to cite them other than a "work in progress." | material or to cite them other than a "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/1id-abstracts.html | http://www.ietf.org/1id-abstracts.html | |||
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 | |||
Copyright Notice | Copyright Notice | |||
Copyright (C) The Internet Society. All Rights Reserved. | Copyright (C) The Internet Society (2005). All Rights Reserved. | |||
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 updates RFCs 1034 and 1035. | of the rules. This clarification updates RFCs 1034 and 1035. | |||
INTERNET-DRAFT DNS Case Insensitivity | INTERNET-DRAFT DNS Case Insensitivity | |||
Acknowledgements | Acknowledgements | |||
skipping to change at page 2, line 35 | skipping to change at page 2, line 35 | |||
2.1 Escaping Unusual DNS Label Octets......................3 | 2.1 Escaping Unusual DNS Label Octets......................3 | |||
2.2 Example Labels with Escapes............................4 | 2.2 Example Labels with Escapes............................4 | |||
3. Name Lookup, Label Types, and CLASS.....................4 | 3. Name Lookup, Label Types, and CLASS.....................4 | |||
3.1 Original DNS Label Types...............................5 | 3.1 Original DNS Label Types...............................5 | |||
3.2 Extended Label Type Case Insensitivity Considerations..5 | 3.2 Extended Label Type Case Insensitivity Considerations..5 | |||
3.3 CLASS Case Insensitivity Considerations................5 | 3.3 CLASS 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 | |||
5. Internationalized Domain Names..........................7 | 5. Internationalized Domain Names..........................7 | |||
6. Security Considerations.................................7 | 6. Security Considerations.................................8 | |||
Full Copyright Notice and Disclaimer.......................9 | Copyright and Disclaimer...................................9 | |||
Normative References.......................................9 | Normative References.......................................9 | |||
Informative References....................................10 | Informative References....................................10 | |||
-02 to -03 Changes........................................10 | ||||
Changes Between Draft Version.............................11 | ||||
-02 to -03 Changes........................................11 | ||||
-03 to -04 Changes........................................11 | -03 to -04 Changes........................................11 | |||
-04 to -05 Changes........................................11 | -04 to -05 Changes........................................11 | |||
Author's Address..........................................11 | -05 to -06 Changes........................................12 | |||
Expiration and File Name..................................12 | ||||
Author's Address..........................................13 | ||||
Expiration and File Name..................................13 | ||||
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] that are treated in a | zero or more labels [STD 13][RFC 1591, 2606] that are treated in a | |||
case insensitive fashion. This document clarifies the meaning of | case insensitive fashion. This document clarifies the meaning of | |||
skipping to change at page 4, line 39 | skipping to change at page 4, line 39 | |||
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 5-octet label where the second | within a label. The second one show a 5-octet label where the second | |||
octet has all bits zero, the third is a backslash, and the fourth | octet has all bits zero, the third is a backslash, and the fourth | |||
octet has all bits one. | octet has all bits one. | |||
Donald\032E\.\032Eastlake\0323rd.example. | Donald\032E\.\032Eastlake\0323rd.example. | |||
and a\000\\\255z.example. | and a\000\\\255z.example. | |||
3. Name Lookup, Label Types, and CLASS | 3. Name Lookup, Label Types, and CLASS | |||
The design decision was made that comparisons on name lookup for all | The original DNS design decision was made that comparisons on name | |||
DNS queries should be case insensitive [STD 13]. That is to say, a | lookup for DNS queries should be case insensitive [STD 13]. That is | |||
lookup string octet with a value in the inclusive range of 0x41 to | to say, a lookup string octet with a value in the inclusive range of | |||
0x5A, the upper case ASCII letters, MUST match the identical value | 0x41 to 0x5A, the upper case ASCII letters, MUST match the identical | |||
and also match the corresponding value in the inclusive range 0x61 to | value and also match the corresponding value in the inclusive range | |||
0x7A, the lower case ASCII letters. And a lookup string octet with a | 0x61 to 0x7A, the lower case ASCII letters. And a lookup string octet | |||
lower case ASCII letter value MUST similarly match the identical | with a lower case ASCII letter value MUST similarly match the | |||
value and also match the corresponding value in the upper case ASCII | identical value and also match the corresponding value in the upper | |||
letter range. | case ASCII letter 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. The terms originally referred to the | invented after movable type. The terms originally referred to the | |||
two font trays for storing, in partitioned areas, the different | two font trays for storing, in partitioned areas, the different | |||
physical type elements. Before movable type, the nearest equivalent | physical type elements. Before movable type, the nearest equivalent | |||
INTERNET-DRAFT DNS Case Insensitivity | INTERNET-DRAFT DNS Case Insensitivity | |||
terms were "majuscule" and "minuscule".) | terms were "majuscule" and "minuscule".) | |||
skipping to change at page 5, line 23 | skipping to change at page 5, line 23 | |||
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. | |||
3.1 Original DNS Label Types | 3.1 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 (or | |||
which consist of an offset pointer to a name location elsewhere in | compression) labels which consist of an offset pointer to a name | |||
the wire encoding on a DNS message. (The ASCII label of length zero | location elsewhere in the wire encoding on a DNS message. (The ASCII | |||
is reserved for use as the name of the root node of the name tree.) | label of length zero is reserved for use as the name of the root node | |||
ASCII labels follow the ASCII case conventions described herein and, | of the name tree.) ASCII labels follow the ASCII case conventions | |||
as stated above, can actually contain arbitrary byte values. Indirect | described herein and, as stated above, can actually contain arbitrary | |||
labels are, in effect, replaced by the name to which they point which | byte values. Indirect labels are, in effect, replaced by the name to | |||
is then treated with the case insensitivity rules in this document. | which they point which is then treated with the case insensitivity | |||
rules in this document. | ||||
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].) | 2673] which is now Experimental [RFC 3363].) | |||
The ASCII case insensitivity conventions only apply to ASCII labels, | The ASCII case insensitivity conventions only apply to ASCII labels, | |||
that is to say, label type 0x0, whether appearing directly or invoked | that is to say, label type 0x0, whether appearing directly or invoked | |||
by indirect labels. | by indirect labels. | |||
3.3 CLASS Case Insensitivity Considerations | 3.3 CLASS Case Insensitivity Considerations | |||
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. With the | |||
original design of DNS, it was intended that a recursive DNS resolver | ||||
INTERNET-DRAFT DNS Case Insensitivity | INTERNET-DRAFT DNS Case Insensitivity | |||
be able to handle new CLASSes that were unknown at the time of its | ||||
implementation. This requires uniform handling of label case | ||||
insensitivity. Should it become desireable, for example, to allocate | ||||
a CLASS with "case sensitive ASCII labels" for example, it would be | ||||
necessary to allocate a new label type for these labels. | ||||
4. Case on Input and Output | 4. Case on Input and Output | |||
While ASCII label comparisons are case insensitive, [STD 13] says | While ASCII label comparisons are case insensitive, [STD 13] says | |||
case MUST be preserved on output, and preserved when convenient on | case MUST be preserved on output, and preserved when convenient on | |||
input. However, this means less than it would appear since the | input. However, this means less than it would appear since the | |||
preservation of case on output is NOT required when output is | preservation of case on output is NOT required when output is | |||
optimized by the use of indirect labels, as explained below. | optimized by the use of indirect labels, as explained below. | |||
4.1 DNS Output Case Preservation | 4.1 DNS Output Case Preservation | |||
skipping to change at page 6, line 35 | skipping to change at page 6, line 41 | |||
optimize output, indirect labels may be used to point to names | optimize output, indirect labels may be used to point to names | |||
elsewhere in the DNS answer. In determining whether the name to be | elsewhere in the DNS answer. In determining whether the name to be | |||
pointed to, for example the QNAME, is the "same" as the remainder of | pointed to, for example the QNAME, is the "same" as the remainder of | |||
the name being optimized, the case insensitive comparison specified | the name being optimized, the case insensitive comparison specified | |||
above is done. Thus such optimization may easily destroy the output | above is done. Thus such optimization may easily destroy the output | |||
preservation of case. This type of optimization is commonly called | preservation of case. This type of optimization is commonly called | |||
"name compression". | "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 data came from an ASCII Master File as defined in | |||
[STD 13] or a zone transfer. DNS Dynamic update and incremental zone | [STD 13] or a zone transfer. DNS Dynamic update and incremental zone | |||
transfers [RFC 1995] have been added as a source of DNS data [RFC | transfers [RFC 1995] have been added as a source of DNS data [RFC | |||
2136, 3007]. When a node in the DNS name tree is created by any of | 2136, 3007]. When a node in the DNS name tree is created by any of | |||
such inputs, no case conversion is done. Thus the case of ASCII | such inputs, no case conversion is done. Thus the case of ASCII | |||
labels is preserved if they are for nodes being created. However, | labels is preserved if they are for nodes being created. However, | |||
when a name label is input for a node that already exist in DNS data | when a name label is input for a node that already exist in DNS data | |||
being held, the situation is more complex. Implementations may retain | being held, the situation is more complex. Implementations are free | |||
the case first input for such a label or allow new input to override | to retain the case first loaded for such a label or allow new input | |||
the old case or even maintain separate copies preserving the input | to override the old case or even maintain separate copies preserving | |||
case. | ||||
For example, if data with owner name "foo.bar.example" is input and | INTERNET-DRAFT DNS Case Insensitivity | |||
the input case. | ||||
For example, if data with owner name "foo.bar.example" is loaded 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", might or might | of the label on the "bar.example" node, i.e. "bar", might or might | |||
not be changed to "BAR" or the actual input case could be preserved. | not be changed to "BAR" in the DNS stored data or the actual input | |||
Thus later retrieval of data stored under "xyz.bar.example" in this | case could be preserved. Thus later retrieval of data stored under | |||
case can easily return data with "xyz.BAR.example". The same | "xyz.bar.example" in this case can return all data with | |||
"xyz.BAR.example" or all data with "xyz.bar.example" or even, when | ||||
INTERNET-DRAFT DNS Case Insensitivity | more than one RR is being returned, a mixture of these two cases. | |||
This last case is unlikely because optimization of answer length | ||||
through indirect labels tends to cause only copy of the name tail | ||||
("bar.example" or "BAR.example") to be used for all returned RRs. | ||||
Note that none of this has any effect on the number of completeness | ||||
of the RR set returned, only on the case of the names in the RR set | ||||
returned. | ||||
considerations apply when inputting multiple data records with owner | The same considerations apply when inputting multiple data records | |||
names differing only in case. For example, if an "A" record is stored | with owner names differing only in case. For example, if an "A" | |||
as the first resourced record under owner name "xyz.BAR.example" and | record is the first resourced record stored under owner name | |||
then a second "A" record is stored under "XYZ.BAR.example", the | "xyz.BAR.example" and then a second "A" record is stored under | |||
second MAY be stored with the first (lower case initial label) name | "XYZ.BAR.example", the second MAY be stored with the first (lower | |||
or the second MAY override the first so that only an upper case | case initial label) name or the second MAY override the first so that | |||
initial label is retained or both capitalizations MAY be kept. | only an upper case initial label is retained or both capitalizations | |||
MAY be kept in the DNS stored data. In any case, a retrieval with | ||||
either capitalization will retrieve all RRs with either | ||||
capitalization. | ||||
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 | |||
unpredictable output capitalization. | unpredictable output capitalization. | |||
5. Internationalized Domain Names | 5. Internationalized Domain Names | |||
A scheme has been adopted for "internationalized domain names" and | A scheme has been adopted for "internationalized domain names" and | |||
"internationalized labels" as described in [RFC 3490, 3454, 3491, and | "internationalized labels" as described in [RFC 3490, 3454, 3491, and | |||
3492]. It makes most of [UNICODE] available through a separate | 3492]. It makes most of [UNICODE] available through a separate | |||
application level transformation from internationalized domain name | application level transformation from internationalized domain name | |||
to DNS domain name and from DNS domain name to internationalized | to DNS domain name and from DNS domain name to internationalized | |||
domain name. Any case insensitivity that internationalized domain | domain name. Any case insensitivity that internationalized domain | |||
names and labels have varies depending on the script and is handled | names and labels have varies depending on the script and is handled | |||
entirely as part of the transformation described in [RFC 3454] and | entirely as part of the transformation described in [RFC 3454] and | |||
[RFC 3491] which should be seen for further details. This is not a | [RFC 3491] which should be seen for further details. This is not a | |||
part of the DNS as standardized in STD 13. | part of the DNS as standardized in STD 13. | |||
INTERNET-DRAFT DNS Case Insensitivity | ||||
6. Security Considerations | 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. | |||
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 a case sensitive index into some 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 | or file system. Or it could be interpreted as binary data by some | |||
or authentication code system. These problems can usually be handled | integrity or authentication code system. These problems can usually | |||
by using a standardized or "canonical" form of the DNS ASCII type | be handled by using a standardized or "canonical" form of the DNS | |||
labels, that is, always mapping the ASCII letter value octets in | ASCII type labels, that is, always mapping the ASCII letter value | |||
ASCII labels to some specific pre-chosen case, either upper case or | octets in ASCII labels to some specific pre-chosen case, either upper | |||
lower case. An example of a canonical form for domain names (and also | case or lower case. An example of a canonical form for domain names | |||
a canonical ordering for them) appears in Section 8 of [RFC 2535]. | (and also a canonical ordering for them) appears in Section 6 of [RFC | |||
See also [RFC 3597]. | 4034]. See also [RFC 3597]. | |||
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 | |||
INTERNET-DRAFT DNS Case Insensitivity | ||||
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 | |||
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 | |||
Full Copyright Notice and Disclaimer | Copyright and Disclaimer | |||
Copyright (C) The Internet Society 2005. This document is subject to | Copyright (C) The Internet Society (2005). This document is subject | |||
the rights, licenses and restrictions contained in BCP 78 and except | to the rights, licenses and restrictions contained in BCP 78, and | |||
as set forth therein, the authors retain all their rights. | except as set forth therein, the authors retain all their rights. | |||
This document and the information contained herein are provided on an | This document and the information contained herein are provided on an | |||
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | |||
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET | OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET | |||
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, | ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, | |||
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE | INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE | |||
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | |||
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
Normative References | Normative References | |||
skipping to change at page 9, line 37 | skipping to change at page 9, line 37 | |||
[RFC 1995] - M. Ohta, "Incremental Zone Transfer in DNS", August | [RFC 1995] - M. Ohta, "Incremental Zone Transfer in DNS", August | |||
1996. | 1996. | |||
[RFC 2119] - S. Bradner, "Key words for use in RFCs to Indicate | [RFC 2119] - S. Bradner, "Key words for use in RFCs to Indicate | |||
Requirement Levels", March 1997. | Requirement Levels", March 1997. | |||
[RFC 2136] - P. Vixie, Ed., S. Thomson, Y. Rekhter, J. Bound, | [RFC 2136] - P. Vixie, Ed., S. Thomson, Y. Rekhter, J. Bound, | |||
"Dynamic Updates in the Domain Name System (DNS UPDATE)", April 1997. | "Dynamic Updates in the Domain Name System (DNS UPDATE)", April 1997. | |||
[RFC 2535] - D. Eastlake, "Domain Name System Security Extensions", | ||||
March 1999. | ||||
[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. | |||
[RFC 3597] - Andreas Gustafsson, "Handling of Unknown DNS RR Types", | [RFC 3597] - Andreas Gustafsson, "Handling of Unknown DNS RR Types", | |||
draft-ietf-dnsext-unknown-rrs-05.txt, March 2003. | draft-ietf-dnsext-unknown-rrs-05.txt, March 2003. | |||
[RFC 4034} - Arends, R., Austein, R., Larson, M., Massey, D., and S. | ||||
Rose, "Resource Records for the DNS Security Extensions", RFC 4034, | ||||
March 2005. | ||||
[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. | |||
INTERNET-DRAFT DNS Case Insensitivity | INTERNET-DRAFT DNS Case Insensitivity | |||
Informative References | Informative References | |||
skipping to change at page 10, line 33 | skipping to change at page 10, line 33 | |||
[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 3092] - D. Eastlake 3rd, C. Manros, E. Raymond, "Etymology of | [RFC 3092] - D. Eastlake 3rd, C. Manros, E. Raymond, "Etymology of | |||
Foo", 1 April 2001. | Foo", 1 April 2001. | |||
[RFC 3363] - Bush, R., Durand, A., Fink, B., Gudmundsson, O., and T. | ||||
Hain, "Representing Internet Protocol version 6 (IPv6) Addresses in | ||||
the Domain Name System (DNS)", RFC 3363, August 2002. | ||||
[RFC 3454] - P. Hoffman, M. Blanchet, "Preparation of | [RFC 3454] - P. Hoffman, M. Blanchet, "Preparation of | |||
Internationalized String ("stringprep")", December 2002. | Internationalized String ("stringprep")", December 2002. | |||
[RFC 3490] - P. Faltstrom, P. Hoffman, A. Costello, | [RFC 3490] - P. Faltstrom, P. Hoffman, A. Costello, | |||
"Internationalizing Domain Names in Applications (IDNA)", March 2003. | "Internationalizing Domain Names in Applications (IDNA)", March 2003. | |||
[RFC 3491] - P. Hoffman, M. Blanchet, "Nameprep: A Stringprep Profile | [RFC 3491] - P. Hoffman, M. Blanchet, "Nameprep: A Stringprep Profile | |||
for Internationalized Domain Names (IDN)", March 2003. | for Internationalized Domain Names (IDN)", March 2003. | |||
[RFC 3492] - A. Costello, "Punycode: A Bootstring encoding of Unicode | [RFC 3492] - A. Costello, "Punycode: A Bootstring encoding of Unicode | |||
for Internationalized Domain Names in Applications (IDNA)", March | for Internationalized Domain Names in Applications (IDNA)", March | |||
2003. | 2003. | |||
[UNICODE] - The Unicode Consortium, "The Unicode Standard", | [UNICODE] - The Unicode Consortium, "The Unicode Standard", | |||
<http://www.unicode.org/unicode/standard/standard.html>. | <http://www.unicode.org/unicode/standard/standard.html>. | |||
INTERNET-DRAFT DNS Case Insensitivity | ||||
Changes Between Draft Version | ||||
RFC Editor: The following summaries of changes between draft versions | ||||
are to be removed before publication. | ||||
-02 to -03 Changes | -02 to -03 Changes | |||
The following changes were made between draft version -02 and -03: | The following changes were made between draft version -02 and -03: | |||
1. Add internationalized domain name section and references. | 1. Add internationalized domain name section and references. | |||
INTERNET-DRAFT DNS Case Insensitivity | ||||
2. Change to indicate that later input of a label for an existing DNS | 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 | name tree node may or may not be normalized to the earlier input or | |||
override it or both may be preserved. | override it or both may be preserved. | |||
3. Numerous minor wording changes. | 3. Numerous minor wording changes. | |||
-03 to -04 Changes | -03 to -04 Changes | |||
The following changes were made between draft versions -03 and -04: | The following changes were made between draft versions -03 and -04: | |||
skipping to change at page 11, line 39 | skipping to change at page 12, line 5 | |||
The following changes were made between draft versions -04 and -05: | The following changes were made between draft versions -04 and -05: | |||
1. More clearly state that this draft updates RFCs 1034, 1035 [STD | 1. More clearly state that this draft updates RFCs 1034, 1035 [STD | |||
13]. | 13]. | |||
2. Add informative references to ISO 8859-1 and ISO 8859-2. | 2. Add informative references to ISO 8859-1 and ISO 8859-2. | |||
3. Fix hyphenation and capitalization nits. | 3. Fix hyphenation and capitalization nits. | |||
INTERNET-DRAFT DNS Case Insensitivity | ||||
-05 to -06 Changes | ||||
The following changes were made between draft version -05 and -06. | ||||
1. Add notation to the RFC Editor that the draft version change | ||||
summaries are to be removed before RFC publication. | ||||
2. Additional text explaining why labe case insensitivity is CLASS | ||||
independent. | ||||
3. Changes and additional text clarifying that the fact that | ||||
inconsistent case in data loaded into DNS may result in | ||||
unpredicatable or inconsistent case in DNS storage but has no effect | ||||
on the completeness of RR sets retrieved. | ||||
4. Add reference to [RFC 3363] and update reference to [RFC 2535] to | ||||
be to [RFC 4034]. | ||||
INTERNET-DRAFT DNS Case Insensitivity | ||||
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-786-7554 (w) | Telephone: +1 508-786-7554 (w) | |||
+1 508-634-2066 (h) | ||||
EMail: Donald.Eastlake@motorola.com | ||||
INTERNET-DRAFT DNS Case Insensitivity | EMail: Donald.Eastlake@motorola.com | |||
Expiration and File Name | Expiration and File Name | |||
This draft expires July 2005. | This draft expires January 2006. | |||
Its file name is draft-ietf-dnsext-insensitive-05.txt. | Its file name is draft-ietf-dnsext-insensitive-06.txt. | |||
End of changes. | ||||
This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |