draft-ietf-dnsext-5395bis-03.txt   rfc6195.txt 
INTERNET-DRAFT Donald Eastlake Internet Engineering Task Force (IETF) D. Eastlake 3rd
Obsoletes: 5395 Huawei Request for Comments: 6195 Huawei
BCP: 42 March 2011
Obsoletes: 5395
Updates: 1183, 3597 Updates: 1183, 3597
Intended status: Best Current Practice Category: Best Current Practice
Expires: July 15, 2011 January 16, 2011 ISSN: 2070-1721
Domain Name System (DNS) IANA Considerations Domain Name System (DNS) IANA Considerations
<draft-ietf-dnsext-5395bis-03.txt>
Abstract Abstract
This document specifies Internet Assigned Number Authority (IANA) This document specifies Internet Assigned Number Authority (IANA)
parameter assignment considerations are specified for the allocation parameter assignment considerations for the allocation of Domain Name
of Domain Name System (DNS) resource record types, CLASSes, operation System (DNS) resource record types, CLASSes, operation codes, error
codes, error codes, DNS protocol message header bits, and AFSDB codes, DNS protocol message header bits, and AFSDB resource record
resource record subtypes. subtypes.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This memo documents an Internet Best Current Practice.
provisions of BCP 78 and BCP 79.
Distribution of this draft is unlimited. It is intended to become the
new BCP 42 obsoleting RFC 5395. Comments should be sent to the DNS
Extensions Working Group mailing list <dnsext@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering This document is a product of the Internet Engineering Task Force
Task Force (IETF), its areas, and its working groups. Note that (IETF). It represents the consensus of the IETF community. It has
other groups may also distribute working documents as Internet- received public review and has been approved for publication by the
Drafts. Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Internet-Drafts are draft documents valid for a maximum of six months Information about the current status of this document, any errata,
and may be updated, replaced, or obsoleted by other documents at any and how to provide feedback on it may be obtained at
time. It is inappropriate to use Internet-Drafts as reference http://www.rfc-editor.org/info/rfc6195.
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at Copyright (c) 2011 IETF Trust and the persons identified as the
http://www.ietf.org/shadow.html document authors. All rights reserved.
INTERNET-DRAFT DNS IANA Considerations This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction............................................3 1. Introduction ....................................................2
1.1. Terminology...........................................3 1.1. Terminology ................................................3
2. DNS Query/Response Headers ......................................3
2. DNS Query/Response Headers..............................4 2.1. One Spare Bit? .............................................4
2.1. One Spare Bit?........................................4 2.2. OpCode Assignment ..........................................4
2.2. OpCode Assignment.....................................5 2.3. RCODE Assignment ...........................................4
2.3. RCODE Assignment......................................5 3. DNS Resource Records ............................................6
3.1. RRTYPE IANA Considerations .................................7
3. DNS Resource Records....................................7 3.1.1. DNS RRTYPE Allocation Policy ........................8
3.1. RRTYPE IANA Considerations............................8 3.1.2. DNS RRTYPE Expert Guidelines ........................9
3.1.1. DNS RRTYPE Allocation Policy........................9 3.1.3. Special Note on the OPT RR ..........................9
3.1.2. DNS RRTYPE Expert Guidelines.......................10 3.1.4. The AFSDB RR Subtype Field .........................10
3.1.3. Special Note on the OPT RR.........................10 3.2. RR CLASS IANA Considerations ..............................10
3.1.4. The AFSDB RR Subtype Field.........................10 3.3. Label Considerations ......................................12
3.2. RR CLASS IANA Considerations.........................11 3.3.1. Label Types ........................................12
3.3. Label Considerations.................................13 3.3.2. Label Contents and Use .............................12
3.3.1. Label Types........................................13 4. Security Considerations ........................................13
3.3.2. Label Contents and Use.............................13 5. IANA Considerations ............................................13
Appendix A. RRTYPE Allocation Template ............................14
4. Security Considerations................................14 Appendix B. Changes from RFC 5395 .................................15
5. IANA Considerations....................................14 Normative References ..............................................15
Informative References ............................................16
Annex A: RRTYPE Allocation Template.......................15
Annex B: Changes From RFC 5395............................16
INTERNET-DRAFT DNS IANA Considerations
1. Introduction 1. Introduction
The Domain Name System (DNS) provides replicated distributed secure The Domain Name System (DNS) provides replicated distributed secure
hierarchical databases that store "resource records" (RRs) under hierarchical databases that store "resource records" (RRs) under
domain names. DNS data is structured into CLASSes and zones that can domain names. DNS data is structured into CLASSes and zones that can
be independently maintained. See [RFC1034], [RFC1035], [RFC2136], be independently maintained. Familiarity with [RFC1034], [RFC1035],
[RFC2181], and [RFC4033], familiarity with which is assumed. [RFC2136], [RFC2181], and [RFC4033] is assumed.
This document provides, either directly or by reference, the general This document provides, either directly or by reference, the general
IANA parameter assignment considerations that apply across DNS query IANA parameter assignment considerations that apply across DNS query
and response headers and all RRs. There may be additional IANA and response headers and all RRs. There may be additional IANA
considerations that apply to only a particular RRTYPE or considerations that apply to only a particular RRTYPE or
query/response OpCode. See the specific RFC defining that RRTYPE or query/response OpCode. See the specific RFC defining that RRTYPE or
query/response OpCode for such considerations if they have been query/response OpCode for such considerations if they have been
defined, except for AFSDB RR considerations [RFC1183], which are defined, except for AFSDB RR considerations [RFC1183], which are
included herein. This RFC obsoletes [RFC5395]; however, the only included herein. This RFC obsoletes [RFC5395]; however, the only
significant change is the change to the public review mailing list to significant change is the change to the public review mailing list to
dnsext@ietf.org. dnsext@ietf.org.
IANA currently maintains a web page of DNS parameters available from IANA currently maintains a web page of DNS parameters available from
http://www.iana.org. http://www.iana.org.
1.1. Terminology 1.1. Terminology
"Standards Action", "IETF Review", "Specification Required", and "Standards Action", "IETF Review", "Specification Required", and
"Private Use" are as defined in [RFC5226]. "Private Use" are as defined in [RFC5226].
INTERNET-DRAFT DNS IANA Considerations 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 [RFC2136] and [RFC5395]: following diagram taken from [RFC2136] and [RFC5395]:
1 1 1 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ID | | ID |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|QR| OpCode |AA|TC|RD|RA| Z|AD|CD| RCODE | |QR| OpCode |AA|TC|RD|RA| Z|AD|CD| RCODE |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| QDCOUNT/ZOCOUNT | | QDCOUNT/ZOCOUNT |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ANCOUNT/PRCOUNT | | ANCOUNT/PRCOUNT |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| NSCOUNT/UPCOUNT | | NSCOUNT/UPCOUNT |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| ARCOUNT | | ARCOUNT |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
The ID field identifies the query and is echoed in the response so The ID field identifies the query and is echoed in the response so
they can be matched. they can be matched.
The QR bit indicates whether the header is for a query or a response. The QR bit indicates whether the header is for a query or a response.
The AA, TC, RD, RA, AD, and CD bits are each theoretically meaningful The AA, TC, RD, RA, AD, and CD bits are each theoretically meaningful
only in queries or only in responses, depending on the bit. However, only in queries or only in responses, depending on the bit. However,
some DNS implementations copy the query header as the initial value some DNS implementations copy the query header as the initial value
of the response header without clearing bits. Thus, any attempt to of the response header without clearing bits. Thus, any attempt to
use a "query" bit with a different meaning in a response or to define use a "query" bit with a different meaning in a response or to define
a query meaning for a "response" bit is dangerous, given existing a query meaning for a "response" bit is dangerous, given existing
implementation. Such meanings may only be assigned by an Standards implementation. Such meanings may only be assigned by a Standards
Action. Action.
The unsigned integer fields query count (QDCOUNT), answer count The unsigned integer fields query count (QDCOUNT), answer count
(ANCOUNT), authority count (NSCOUNT), and additional information (ANCOUNT), authority count (NSCOUNT), and additional information
count (ARCOUNT) express the number of records in each section for all count (ARCOUNT) express the number of records in each section for all
OpCodes except Update [RFC2136]. These fields have the same structure OpCodes except Update [RFC2136]. These fields have the same
and data type for Update but are instead the counts for the zone structure and data type for Update but are instead the counts for the
(ZOCOUNT), prerequisite (PRCOUNT), update (UPCOUNT), and additional zone (ZOCOUNT), prerequisite (PRCOUNT), update (UPCOUNT), and
information (ARCOUNT) sections. additional information (ARCOUNT) sections.
2.1. One Spare Bit? 2.1. One Spare Bit?
There have been ancient DNS implementations for which the Z bit being There have been ancient DNS implementations for which the Z bit being
on in a query meant that only a response from the primary server for on in a query meant that only a response from the primary server for
a zone is acceptable. It is believed that current DNS implementations a zone is acceptable. It is believed that current DNS
implementations ignore this bit.
INTERNET-DRAFT DNS IANA Considerations
ignore this bit.
Assigning a meaning to the Z bit requires a Standards Action. Assigning a meaning to the Z bit requires a Standards Action.
2.2. OpCode Assignment 2.2. OpCode Assignment
Currently DNS OpCodes are assigned as follows:
OpCode Name Reference
0 Query [RFC1035] Currently, DNS OpCodes are assigned as follows:
1 IQuery (Inverse Query, Obsolete) [RFC3425]
2 Status [RFC1035]
3 available for assignment
4 Notify [RFC1996]
5 Update [RFC2136]
6-15 available for assignment
New OpCode assignments require a Standards Action as modified by OpCode Name Reference
[RFC4020].
2.3. RCODE Assignment 0 Query [RFC1035]
1 IQuery (Inverse Query, Obsolete) [RFC3425]
2 Status [RFC1035]
3 available for assignment
4 Notify [RFC1996]
5 Update [RFC2136]
6-15 available for assignment
It would appear from the DNS header above that only four bits of New OpCode assignments require a Standards Action as modified by
RCODE, or response/error code, are available. However, RCODEs can [RFC4020].
appear not only at the top level of a DNS response but also inside
OPT RRs [RFC2671], TSIG RRs [RFC2845], and TKEY RRs [RFC2930]. The
OPT RR provides an 8-bit extension resulting in a 12-bit RCODE field,
and the TSIG and TKEY RRs have a 16-bit RCODE field.
Error codes appearing in the DNS header and in these three RR types 2.3. RCODE Assignment
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. This duplicate assignment was accidental.
See table below.
INTERNET-DRAFT DNS IANA Considerations It would appear from the DNS header above that only four bits of
RCODE, or response/error code, are available. However, RCODEs can
appear not only at the top level of a DNS response but also inside
OPT RRs [RFC2671], TSIG RRs [RFC2845], and TKEY RRs [RFC2930].
The OPT RR provides an 8-bit extension 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
Decimal types all refer to the same error code space with the single
Hexadecimal exception of error code 16, which has a different meaning in the
0 NoError No Error [RFC1035] OPT RR than in other contexts. This duplicate assignment was
1 FormErr Format Error [RFC1035] accidental. See table below.
2 ServFail Server Failure [RFC1035]
3 NXDomain Non-Existent Domain [RFC1035]
4 NotImp Not Implemented [RFC1035]
5 Refused Query Refused [RFC1035]
6 YXDomain Name Exists when it should not [RFC2136]
7 YXRRSet RR Set Exists when it should not [RFC2136]
8 NXRRSet RR Set that should exist does not [RFC2136]
9 NotAuth Server Not Authoritative for zone [RFC2136]
10 NotZone Name not contained in zone [RFC2136]
11 - 15 Available for assignment
16 BADVERS Bad OPT Version [RFC2671]
16 BADSIG TSIG Signature Failure [RFC2845]
17 BADKEY Key not recognized [RFC2845]
18 BADTIME Signature out of time window [RFC2845]
19 BADMODE Bad TKEY Mode [RFC2930]
20 BADNAME Duplicate key name [RFC2930]
21 BADALG Algorithm not supported [RFC2930]
22 BADTRUC Bad Truncation [RFC4635]
23 - 3,840
0x0017 - 0x0F00 Available for assignment
3,841 - 4,095 RCODE Name Description Reference
0x0F01 - 0x0FFF Private Use Decimal
Hexadecimal
0 NoError No Error [RFC1035]
1 FormErr Format Error [RFC1035]
2 ServFail Server Failure [RFC1035]
3 NXDomain Non-Existent Domain [RFC1035]
4 NotImp Not Implemented [RFC1035]
5 Refused Query Refused [RFC1035]
6 YXDomain Name Exists when it should not [RFC2136]
7 YXRRSet RR Set Exists when it should not [RFC2136]
8 NXRRSet RR Set that should exist does not [RFC2136]
9 NotAuth Server Not Authoritative for zone [RFC2136]
10 NotZone Name not contained in zone [RFC2136]
11 - 15 Available for assignment
16 BADVERS Bad OPT Version [RFC2671]
16 BADSIG TSIG Signature Failure [RFC2845]
17 BADKEY Key not recognized [RFC2845]
18 BADTIME Signature out of time window [RFC2845]
19 BADMODE Bad TKEY Mode [RFC2930]
20 BADNAME Duplicate key name [RFC2930]
21 BADALG Algorithm not supported [RFC2930]
22 BADTRUC Bad Truncation [RFC4635]
23 - 3,840
0x0017 - 0x0F00 Available for assignment
4,096 - 65,534 3,841 - 4,095
0x1000 - 0xFFFE Available for assignment 0x0F01 - 0x0FFF Private Use
65,535 4,096 - 65,534
0xFFFF Reserved, can only be allocated by a 0x1000 - 0xFFFE Available for assignment
Standards Action.
Since it is important that RCODEs be understood for interoperability, 65,535
assignment of new RCODE listed above as "available for assignment" 0xFFFF Reserved, can only be allocated by a
requires an IETF Review. Standards Action.
INTERNET-DRAFT DNS IANA Considerations Since it is important that RCODEs be understood for
interoperability, assignment of a new RCODE in the ranges listed
above as "Available for assignment" requires an IETF Review.
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 [RFC1035]. taken from [RFC1035].
1 1 1 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| | | |
/ / / /
/ NAME / / NAME /
/ / / /
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TYPE | | TYPE |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CLASS | | CLASS |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TTL | | TTL |
| | | |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| RDLENGTH | | RDLENGTH |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--| +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--|
/ RDATA / / RDATA /
/ / / /
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
NAME is an owner name, i.e., the name of the node to which this NAME is an owner name, i.e., the name of the node to which this
resource record pertains. NAMEs are specific to a CLASS as described resource record pertains. NAMEs are specific to a CLASS as described
in section 3.2. NAMEs consist of an ordered sequence of one or more in Section 3.2. NAMEs consist of an ordered sequence of one or more
labels, each of which has a label type [RFC1035] [RFC2671]. labels, each of which has a label type [RFC1035] [RFC2671].
TYPE is a 2-octet unsigned integer containing one of the RRTYPE TYPE is a 2-octet unsigned integer containing one of the RRTYPE
codes. See section 3.1. codes. See Section 3.1.
CLASS is a 2-octet unsigned integer containing one of the RR CLASS CLASS is a 2-octet unsigned integer containing one of the RR CLASS
codes. See section 3.2. codes. See Section 3.2.
TTL is a 4-octet (32-bit) unsigned integer that specifies, for data TTL is a 4-octet (32-bit) unsigned integer that specifies, for data
TYPEs, the number of seconds that the resource record may be cached TYPEs, the number of seconds that the resource record may be cached
before the source of the information should again be consulted. Zero before the source of the information should again be consulted. Zero
is interpreted to mean that the RR can only be used for the is interpreted to mean that the RR can only be used for the
transaction in progress. transaction in progress.
RDLENGTH is an unsigned 16-bit integer that specifies the length in RDLENGTH is an unsigned 16-bit integer that specifies the length in
octets of the RDATA field. octets of the RDATA field.
RDATA is a variable length string of octets that constitutes the RDATA is a variable-length string of octets that constitutes the
resource. The format of this information varies according to the TYPE resource. The format of this information varies according to the
and, in some cases, the CLASS of the resource record. TYPE and, in some cases, the CLASS of the resource record.
INTERNET-DRAFT DNS IANA Considerations
3.1. RRTYPE IANA Considerations 3.1. RRTYPE IANA Considerations
There are three subcategories of RRTYPE numbers: data TYPEs, QTYPEs, There are three subcategories of RRTYPE numbers: data TYPEs, QTYPEs,
and Meta-TYPEs. and Meta-TYPEs.
Data TYPEs are the means of storing data. QTYPES can only be used in Data TYPEs are the means of storing data. QTYPES can only be used in
queries. Meta-TYPEs designate transient data associated with a queries. Meta-TYPEs designate transient data associated with a
particular DNS message and, in some cases, can also be used in particular DNS message and, in some cases, can also be used in
queries. Thus far, data TYPEs have been assigned from 1 upward plus queries. Thus far, data TYPEs have been assigned from 1 upward,
the block from 100 through 103 and from 32,768 upward, while Q and plus the block from 100 through 103, and from 32,768 upward, while Q
Meta-TYPEs have been assigned from 255 downward except for the OPT and Meta-TYPEs have been assigned from 255 downward except for the
Meta-RR, which is assigned TYPE 41. There have been DNS OPT Meta-RR, which is assigned TYPE 41. There have been DNS
implementations that made caching decisions based on the top bit of implementations that made caching decisions based on the top bit of
the bottom byte of the RRTYPE. the bottom byte of the RRTYPE.
There are currently three Meta-TYPEs assigned: OPT [RFC2671], TSIG There are currently three Meta-TYPEs assigned: OPT [RFC2671], TSIG
[RFC2845], and TKEY [RFC2930]. There are currently five QTYPEs [RFC2845], and TKEY [RFC2930]. There are currently five QTYPEs
assigned: * (ALL), MAILA, MAILB, AXFR, and IXFR. assigned: * (ALL), MAILA, MAILB, AXFR, and IXFR.
RRTYPEs have mnemonics that must be completely disjoint from the RRTYPEs have mnemonics that must be completely disjoint from the
mnemonics used for CLASSes and that must match the following regular mnemonics used for CLASSes and that must match the following regular
expression: expression:
[A-Z][A-Z0-9\-]*[A-Z0-9] [A-Z][A-Z0-9\-]*[A-Z0-9]
Considerations for the allocation of new RRTYPEs are as follows: Considerations for the allocation of new RRTYPEs are as follows:
Decimal Decimal
Hexadecimal Hexadecimal
0 0
0x0000 - RRTYPE zero is used as a special indicator for the SIG (0) 0x0000 - RRTYPE zero is used as a special indicator for the SIG (0)
RR [RFC2931], [RFC4034] and in other circumstances, and it RR [RFC2931] [RFC4034] and in other circumstances, and it
must never be allocated for ordinary use. must never be allocated for ordinary use.
1 - 127 1 - 127
0x0001 - 0x007F - Remaining RRTYPEs in this range are assigned for 0x0001 - 0x007F - Remaining RRTYPEs in this range are assigned for
data TYPEs by the DNS RRTYPE Allocation Policy as specified data TYPEs by the DNS RRTYPE Allocation Policy as specified
in Section 3.1.1. in Section 3.1.1.
128 - 255 128 - 255
0x0080 - 0x00FF - Remaining RRTYPEs in this range are assigned for Q 0x0080 - 0x00FF - Remaining RRTYPEs in this range are assigned for Q
and Meta TYPEs by the DNS RRTYPE Allocation Policy as and Meta-TYPEs by the DNS RRTYPE Allocation Policy as
specified in Section 3.1.1. specified in Section 3.1.1.
256 - 61,439 256 - 61,439
0x0100 - 0xEFFF - Remaining RRTYPEs in this range are assigned for 0x0100 - 0xEFFF - Remaining RRTYPEs in this range are assigned for
data RRTYPEs by the DNS RRTYPE Allocation Policy as data RRTYPEs by the DNS RRTYPE Allocation Policy as
specified in Section 3.1.1. (32,768 and 32,769 (0x8000 and specified in Section 3.1.1. (32,768 and 32,769 (0x8000 and
0x8001) have been assigned.) 0x8001) have been assigned.)
INTERNET-DRAFT DNS IANA Considerations
61,440 - 65,279 61,440 - 65,279
0xF000 - 0xFEFF - Reserved for future use. IETF Review required to 0xF000 - 0xFEFF - Reserved for future use. IETF Review required to
define use. define use.
65,280 - 65,534 65,280 - 65,534
0xFF00 - 0xFFFE - Private Use. 0xFF00 - 0xFFFE - Private Use.
65,535 65,535
0xFFFF - Reserved, can only be assigned by a Standards Action. 0xFFFF - Reserved, can only be assigned by a Standards Action.
3.1.1. DNS RRTYPE Allocation Policy 3.1.1. DNS RRTYPE Allocation Policy
Parameter values specified in Section 3.1 above as assigned based on Parameter values specified in Section 3.1 above, as assigned based on
DNS RRTYPE Allocation Policy, are allocated by Expert Review if they DNS RRTYPE Allocation Policy, are allocated by Expert Review if they
meet the two requirements listed below. There will be a pool of a meet the two requirements listed below. There will be a pool of a
small number of Experts appointed by the IESG. Each application will small number of Experts appointed by the IESG. Each application will
be ruled on by an Expert selected by IANA. In any case where the be ruled on by an Expert selected by IANA. In any case where the
selected Expert is unavailable or states they have a conflict of selected Expert is unavailable or states they have a conflict of
interest, IANA may select another Expert from the pool. interest, IANA may select another Expert from the pool.
Some guidelines for the Experts are given in Section 3.1.2. RRTYPEs Some guidelines for the Experts are given in Section 3.1.2. RRTYPEs
that do not meet the requirements below may nonetheless be allocated that do not meet the requirements below may nonetheless be allocated
by a Standards Action as modified by [RFC4020]. by a Standards Action as modified by [RFC4020].
1. A complete template as specified in Appendix A has been posted for 1. A complete template as specified in Appendix A has been posted
three weeks to the dnsext@ietf.org mailing list before the Expert for three weeks to the dnsext@ietf.org mailing list before the
Review decision. Expert Review decision.
Note that partially completed or draft templates may be posted
directly by the applicant for comment and discussion, but the
formal posting to start the three week period is made by the
Expert.
2. The RR for which an RRTYPE code is being requested is either (a) a Note that partially completed or draft templates may be posted
data TYPE that can be handled as an Unknown RR as described in directly by the applicant for comment and discussion, but the
[RFC3597] or (b) a Meta-Type whose processing is optional, i.e., formal posting to start the three-week period is made by the
it is safe to simply discard RRs with that Meta-Type in queries or Expert.
responses.
Note that such RRs may include additional section processing, 2. The RR for which an RRTYPE code is being requested is either (a)
a data TYPE that can be handled as an Unknown RR as described in
[RFC3597] or (b) a Meta-TYPE whose processing is optional, i.e.,
it is safe to simply discard RRs with that Meta-TYPE in queries
or responses.
Note that such RRs may include additional section processing,
provided such processing is optional. provided such processing is optional.
After the applicant posts their formal application with their After the applicant posts their formal application with their
template as specified in Annex A, IANA appoints an Expert and the template as specified in Appendix A, IANA appoints an Expert and the
template is posted, with an indication that it is a formal template is posted, with an indication that it is a formal
application, to the dnsext@ietf.org mailing list. No less than three application, to the dnsext@ietf.org mailing list. No less than three
weeks and no more than six weeks after this posting to weeks and no more than six weeks after this posting to
dnsext@ietf.org, the selected Expert shall post a message, explicitly dnsext@ietf.org, the selected Expert shall post a message, explicitly
accepting or rejecting the application, to IANA, dnsext@ietf.org, and accepting or rejecting the application, to IANA, dnsext@ietf.org, and
the email address provided by the applicant. If the Expert does not the email address provided by the applicant. If the Expert does not
INTERNET-DRAFT DNS IANA Considerations
post such a message, the application shall be considered rejected but post such a message, the application shall be considered rejected but
may be re-submitted to IANA. IANA should report non-responsive may be resubmitted to IANA. IANA should report non-responsive
Experts to the IESG. Experts to the IESG.
IANA shall maintain a public archive of approved templates. IANA shall maintain a public archive of approved templates.
3.1.2. DNS RRTYPE Expert Guidelines 3.1.2. DNS RRTYPE Expert Guidelines
The selected DNS RRTYPE Expert is required to monitor discussion of The selected DNS RRTYPE Expert is required to monitor discussion of
the proposed RRTYPE, which may occur on the dnsext@ietf.org mailing the proposed RRTYPE, which may occur on the dnsext@ietf.org mailing
list, and may consult with other technical experts as necessary. The list, and may consult with other technical experts as necessary. The
Expert should normally reject any RRTYPE allocation request that Expert should normally reject any RRTYPE allocation request that
meets one or more of the following criterion: meets one or more of the following criteria:
1. Was documented in a manner that was not sufficiently clear to
evaluate or implement.
2. The proposed RRTYPE or RRTYPEs affect DNS processing and do not
meet the criteria in point 2 of Section 3.1.1 above.
3. The documentation of the proposed RRTYPE or RRTYPEs is incomplete. 1. Was documented in a manner that was not sufficiently clear to
(Additional documentation can be provided during the public evaluate or implement.
comment period or by the Expert.)
4. Application use as documented makes incorrect assumptions about 2. The proposed RRTYPE or RRTYPEs affect DNS processing and do not
DNS protocol behavior, such as wild cards, CNAME, DNAME, etc. meet the criteria in point 2 of Section 3.1.1 above.
5. An excessive number of RRTYPE values is being requested when the 3. The documentation of the proposed RRTYPE or RRTYPEs is
purpose could be met with a smaller number or with Private Use incomplete. (Additional documentation can be provided during the
values. public comment period or by the Expert.)
3.1.3. Special Note on the OPT RR 4. Application use as documented makes incorrect assumptions about
DNS protocol behavior, such as wild cards, CNAME, DNAME, etc.
The OPT (OPTion) RR (RRTYPE 41) and its IANA Considerations are 5. An excessive number of RRTYPE values is being requested when the
specified in [RFC2671]. Its primary purpose is to extend the purpose could be met with a smaller number or with Private Use
effective field size of various DNS fields including RCODE, label values.
type, OpCode, flag bits, and RDATA size. In particular, for resolvers
and servers that recognize it, it extends the RCODE field from 4 to
12 bits.
3.1.4. The AFSDB RR Subtype Field 3.1.3. Special Note on the OPT RR
The AFSDB RR [RFC1183] is a CLASS-insensitive RR that has the same The OPT (OPTion) RR (RRTYPE 41) and its IANA considerations are
RDATA field structure as the MX RR [RFC1035], but the 16-bit unsigned specified in [RFC2671]. Its primary purpose is to extend the
effective field size of various DNS fields including RCODE, label
type, OpCode, flag bits, and RDATA size. In particular, for
resolvers and servers that recognize it, it extends the RCODE field
from 4 to 12 bits.
INTERNET-DRAFT DNS IANA Considerations 3.1.4. The AFSDB RR Subtype Field
integer field at the beginning of the RDATA is interpreted as a The AFSDB RR [RFC1183] is a CLASS-insensitive RR that has the same
subtype as follows: RDATA field structure as the MX RR [RFC1035], but the 16-bit
unsigned integer field at the beginning of the RDATA is interpreted
as a subtype as follows:
Decimal Decimal
Hexadecimal Hexadecimal
0 0
0x0000 - Reserved; allocation requires a Standards Action. 0x0000 - Reserved; allocation requires a Standards Action.
1 1
0x0001 - Andrews File Service v3.0 Location Service [RFC1183]. 0x0001 - Andrews File Service v3.0 Location Service [RFC1183].
skipping to change at page 11, line 31 skipping to change at page 10, line 33
3 - 65,279 3 - 65,279
0x0003 - 0xFEFF - Allocation by IETF Review. 0x0003 - 0xFEFF - Allocation by IETF Review.
65,280 - 65,534 65,280 - 65,534
0xFF00 - 0xFFFE - Private Use. 0xFF00 - 0xFFFE - Private Use.
65,535 65,535
0xFFFF - Reserved; allocation requires a Standards Action. 0xFFFF - Reserved; allocation requires a Standards Action.
3.2. RR CLASS IANA Considerations 3.2. RR CLASS IANA Considerations
There are currently two subcategories of DNS CLASSes: normal, data- There are currently two subcategories of DNS CLASSes: normal, data-
containing classes and QCLASSes that are only meaningful in queries containing classes and QCLASSes that are only meaningful in queries
or updates. or updates.
DNS CLASSes have been little used but constitute another dimension of DNS CLASSes have been little used but constitute another dimension of
the DNS distributed database. In particular, there is no necessary the DNS distributed database. In particular, there is no necessary
relationship between the name space or root servers for one data relationship between the name space or root servers for one data
CLASS and those for another data CLASS. The same DNS NAME can have CLASS and those for another data CLASS. The same DNS NAME can have
completely different meanings in different CLASSes. The label types completely different meanings in different CLASSes. The label types
are the same, and the null label is usable only as root in every are the same, and the null label is usable only as root in every
CLASS. As global networking and DNS have evolved, the IN, or CLASS. As global networking and DNS have evolved, the IN, or
Internet, CLASS has dominated DNS use. Internet, CLASS has dominated DNS use.
As yet there has not be a requirement for "meta-CLASSes". That would As yet, there has not been a requirement for "meta-CLASSes". That
be a CLASS to designate transient data associated with a particular would be a CLASS to designate transient data associated with a
DNS message, which might be usable in queries. However, it is particular DNS message, which might be usable in queries. However,
possible that there might be a future requirement for one or more it is possible that there might be a future requirement for one or
"meta-CLASSes". more "meta-CLASSes".
CLASSes have mnemonics that must be completely disjoint from the CLASSes have mnemonics that must be completely disjoint from the
mnemonics used for RRTYPEs and that must match the following regular mnemonics used for RRTYPEs and that must match the following regular
expression: expression:
INTERNET-DRAFT DNS IANA Considerations
[A-Z][A-Z0-9\-]*[A-Z0-9] [A-Z][A-Z0-9\-]*[A-Z0-9]
The current CLASS assignments and considerations for future The current CLASS assignments and considerations for future
assignments are as follows: assignments are as follows:
Decimal Decimal
Hexadecimal Hexadecimal
0 0
0x0000 - Reserved; assignment requires a Standards Action. 0x0000 - Reserved; assignment requires a Standards Action.
skipping to change at page 12, line 32 skipping to change at page 11, line 34
0x0002 - Available for assignment by IETF Review as a data CLASS. 0x0002 - Available for assignment by IETF Review as a data CLASS.
3 3
0x0003 - Chaos (CH) [Moon1981]. 0x0003 - Chaos (CH) [Moon1981].
4 4
0x0004 - Hesiod (HS) [Dyer1987]. 0x0004 - Hesiod (HS) [Dyer1987].
5 - 127 5 - 127
0x0005 - 0x007F - Available for assignment by IETF Review for data 0x0005 - 0x007F - Available for assignment by IETF Review for data
CLASSes only. CLASSes only.
128 - 253 128 - 253
0x0080 - 0x00FD - Available for assignment by IETF Review for 0x0080 - 0x00FD - Available for assignment by IETF Review for
QCLASSes and meta-CLASSes only. QCLASSes and meta-CLASSes only.
254 254
0x00FE - QCLASS NONE [RFC2136]. 0x00FE - QCLASS NONE [RFC2136].
255 255
0x00FF - QCLASS * (ANY) [RFC1035]. 0x00FF - QCLASS * (ANY) [RFC1035].
256 - 32,767 256 - 32,767
0x0100 - 0x7FFF - Assigned by IETF Review. 0x0100 - 0x7FFF - Assigned by IETF Review.
32,768 - 57,343 32,768 - 57,343
0x8000 - 0xDFFF - Assigned for data CLASSes only, based on 0x8000 - 0xDFFF - Assigned for data CLASSes only, based on
Specification Required as defined in [RFC5226]. Specification Required as defined in [RFC5226].
57,344 - 65,279 57,344 - 65,279
0xE000 - 0xFEFF - Assigned for QCLASSes and meta-CLASSes only, based 0xE000 - 0xFEFF - Assigned for QCLASSes and meta-CLASSes only, based
on Specification Required as defined in [RFC5226]. on Specification Required as defined in [RFC5226].
65,280 - 65,534 65,280 - 65,534
0xFF00 - 0xFFFE - Private Use. 0xFF00 - 0xFFFE - Private Use.
INTERNET-DRAFT DNS IANA Considerations
65,535 65,535
0xFFFF - Reserved; can only be assigned by a Standards Action. 0xFFFF - Reserved; can only be assigned by a Standards Action.
3.3. Label Considerations 3.3. Label Considerations
DNS NAMEs are sequences of labels [RFC1035]. DNS NAMEs are sequences of labels [RFC1035].
3.3.1. Label Types 3.3.1. Label Types
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. shorten the wire encoding of NAMEs.
The two existing data label types are sometimes referred to as Text The two existing data label types are sometimes referred to as Text
and Binary. Text labels can, in fact, include any octet value and Binary. Text labels can, in fact, include any octet value
including zero-value octets, but many current uses involve only [US- including zero-value octets, but many current uses involve only
ASCII]. For retrieval, Text labels are defined to treat ASCII upper [US-ASCII]. For retrieval, Text labels are defined to treat ASCII
and lower case letter codes as matching [RFC4343]. Binary labels are upper and lower case letter codes as matching [RFC4343]. Binary
bit sequences [RFC2673]. The Binary label type is Experimental labels are bit sequences [RFC2673]. The Binary label type is
[RFC3363]. Experimental [RFC3363].
IANA considerations for label types are given in [RFC2671]. IANA considerations for label types are given in [RFC2671].
3.3.2. Label Contents and Use 3.3.2. Label Contents and Use
The last label in each NAME is "ROOT", which is the zero-length The last label in each NAME is "ROOT", which is the zero-length
label. By definition, the null or ROOT label cannot be used for any label. By definition, the null or ROOT label cannot be used for any
other NAME purpose. other NAME purpose.
NAMEs are local to a CLASS. The Hesiod [Dyer1987] and Chaos NAMEs are local to a CLASS. The Hesiod [Dyer1987] and Chaos
[Moon1981] CLASSes are for essentially local use. The IN, or [Moon1981] CLASSes are for essentially local use. The IN, or
Internet, CLASS is thus the only DNS CLASS in global use on the Internet, CLASS is thus the only DNS CLASS in global use on the
Internet at this time. Internet at this time.
A somewhat out-of-date description of name allocation in the IN Class A somewhat out-of-date description of name allocation in the IN Class
is given in [RFC1591]. Some information on reserved top-level domain is given in [RFC1591]. Some information on reserved top-level domain
names is in BCP 32 [RFC2606]. names is in BCP 32 [RFC2606].
INTERNET-DRAFT DNS IANA Considerations 4. Security Considerations
4. 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 [RFC4033], [RFC4034], and general DNS parameters, not security. See [RFC4033], [RFC4034], and
[RFC4035] for secure DNS considerations. [RFC4035] for secure DNS considerations.
5. IANA Considerations 5. IANA Considerations
This document consists entirely of DNS IANA Considerations. This document consists entirely of DNS IANA Considerations.
IANA shall establish a process for accepting Annex A templates, IANA has established a process for accepting Appendix A templates and
selecting an Expert from those appointed to review such template form selecting an Expert from those appointed to review such template form
applications, and archive and make available all approved RRTYPE applications. IANA archives and makes available all approved RRTYPE
allocation templates. It is the duty of the applicant to post the allocation templates. It is the duty of the applicant to post the
formal application template to the dns-rrtype-applications@ietf.org formal application template to the dns-rrtype-applications@ietf.org
mailing list which IANA will monitor. The dnsext@ietf.org mailing mailing list, which IANA will monitor. The dnsext@ietf.org mailing
list is for community discussion and comment. See Section 3.1 and list is for community discussion and comment. See Section 3.1 and
Annex A for more details. Appendix A for more details.
INTERNET-DRAFT DNS IANA Considerations
Annex A: RRTYPE Allocation Template Appendix A. RRTYPE Allocation Template
DNS RRTYPE PARAMETER ALLOCATION TEMPLATE DNS RRTYPE PARAMETER ALLOCATION TEMPLATE
When ready for formal consideration, this template is to be submitted When ready for formal consideration, this template is to be submitted
to IANA for processing by emailing the template to dns-rrtype- to IANA for processing by emailing the template to
applications@ietf.org. dns-rrtype-applications@ietf.org.
A. Submission Date: A. Submission Date:
B. Submission Type: B. Submission Type:
[ ] New RRTYPE [ ] New RRTYPE
[ ] Modification to existing RRTYPE [ ] Modification to existing RRTYPE
C. Contact Information for submitter (will be publicly posted): C. Contact Information for submitter (will be publicly posted):
Name: Name:
Email Address: Email Address:
International telephone number: International telephone number:
Other contact handles: Other contact handles:
D. Motivation for the new RRTYPE application? D. Motivation for the new RRTYPE application.
Please keep this part at a high level to inform the Expert and Please keep this part at a high level to inform the Expert and
reviewers about uses of the RRTYPE. Remember most reviewers will reviewers about uses of the RRTYPE. Most reviewers will be DNS
be DNS experts that may have limited knowledge of your application experts that may have limited knowledge of your application space.
space.
E. Description of the proposed RR type. E. Description of the proposed RR type.
This description can be provided in-line in the template, as an This description can be provided in-line in the template, as an
attachment or with a publicly available URL. attachment, or with a publicly available URL.
F. What existing RRTYPE or RRTYPEs come closest to filling that need F. What existing RRTYPE or RRTYPEs come closest to filling that need
and why are they unsatisfactory? and why are they unsatisfactory?
G. What mnemonic is requested for the new RRTYPE (optional)? G. What mnemonic is requested for the new RRTYPE (optional)?
Note: this can be left blank and the mnemonic decided after the Note: this can be left blank and the mnemonic decided after the
template is accepted. template is accepted.
H. Does the requested RRTYPE make use of any existing IANA Registry H. Does the requested RRTYPE make use of any existing IANA registry
or require the creation of a new IANA sub-registry in DNS or require the creation of a new IANA sub-registry in DNS
Parameters? Parameters? If so, please indicate which registry is to be used
If so, please indicate which registry is to be used or created. If or created. If a new sub-registry is needed, specify the
a new sub-registry is needed, specify the allocation policy for it allocation policy for it and its initial contents. Also include
and its initial contents. Also include what the modification what the modification procedures will be.
procedures will be.
I. Does the proposal require/expect any changes in DNS I. Does the proposal require/expect any changes in DNS
servers/resolvers that prevent the new type from being processed servers/resolvers that prevent the new type from being processed
as an unknown RRTYPE (see [RFC3597])? as an unknown RRTYPE (see [RFC3597])?
J. Comments: J. Comments:
INTERNET-DRAFT DNS IANA Considerations Appendix B. Changes From RFC 5395
Annex B: Changes From RFC 5395
Replace "namedroppers@ops.ietf.org" with "dnsext@ietf.org". Replaced "namedroppers@ops.ietf.org" with "dnsext@ietf.org".
Drop description of changes from RFC 2929 to RFC 5395 since those Dropped description of changes from RFC 2929 to RFC 5395 since those
changes have already happened and we don't need to do them again. changes have already happened, and we don't need to do them again.
Updates to boilerplate text. Updated the boilerplate text.
Fix Section 5 to say that it is the duty of the applicant, not the Fixed Section 5 to say that it is the duty of the applicant, not the
expert, to post the application to dns-rrtype-applications@ietf.org. expert, to post the application to dns-rrtype-applications@ietf.org.
Change the regular expression for RRTYPE and CLASS names so as to Changed the regular expression for RRTYPE and CLASS names so as to
prohibit trailing hypen ("-") and require a minimum length of 2 prohibit trailing hyphen ("-") and require a minimum length of 2
characters. characters.
A number of minor editorial and typos fixes. Made a number of minor editorial and typos fixes.
INTERNET-DRAFT DNS IANA Considerations
Normative References Normative References
[RFC1034] - Mockapetris, P., "Domain names - concepts and [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
facilities", STD 13, RFC 1034, November 1987. STD 13, RFC 1034, November 1987.
[RFC1035] - Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[RFC1996] - Vixie, P., "A Mechanism for Prompt Notification of Zone [RFC1035] Mockapetris, P., "Domain names - implementation and
Changes (DNS NOTIFY)", RFC 1996, August 1996. specification", STD 13, RFC 1035, November 1987.
[RFC2136] - Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. Bound, [RFC1996] Vixie, P., "A Mechanism for Prompt Notification of Zone
"Dynamic Updates in the Domain Name System (DNS UPDATE)", RFC 2136, Changes (DNS NOTIFY)", RFC 1996, August 1996.
April 1997.
[RFC2181] - Elz, R. and R. Bush, "Clarifications to the DNS [RFC2136] Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. Bound,
Specification", RFC 2181, July 1997. "Dynamic Updates in the Domain Name System (DNS UPDATE)",
RFC 2136, April 1997.
[RFC2671] - Vixie, P., "Extension Mechanisms for DNS (EDNS0)", RFC [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
2671, August 1999. Specification", RFC 2181, July 1997.
[RFC2845] - Vixie, P., Gudmundsson, O., Eastlake 3rd, D., and B. [RFC2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)", RFC
Wellington, "Secret Key Transaction Authentication for DNS (TSIG)", 2671, August 1999.
RFC 2845, May 2000.
[RFC2930] - Eastlake 3rd, D., "Secret Key Establishment for DNS (TKEY [RFC2845] Vixie, P., Gudmundsson, O., Eastlake 3rd, D., and B.
RR)", RFC 2930, September 2000. Wellington, "Secret Key Transaction Authentication for DNS
(TSIG)", RFC 2845, May 2000.
[RFC3425] - Lawrence, D., "Obsoleting IQUERY", RFC 3425, November [RFC2930] Eastlake 3rd, D., "Secret Key Establishment for DNS (TKEY
2002. RR)", RFC 2930, September 2000.
[RFC3597] - Gustafsson, A., "Handling of Unknown DNS Resource Record [RFC3425] Lawrence, D., "Obsoleting IQUERY", RFC 3425, November
(RR) Types", RFC 3597, September 2003. 2002.
[RFC4020] - Kompella, K. and A. Zinin, "Early IANA Allocation of [RFC3597] Gustafsson, A., "Handling of Unknown DNS Resource Record
Standards Track Code Points", BCP 100, RFC 4020, February 2005. (RR) Types", RFC 3597, September 2003.
[RFC4033] - Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4020] Kompella, K. and A. Zinin, "Early IANA Allocation of
Rose, "DNS Security Introduction and Requirements", RFC 4033, March Standards Track Code Points", BCP 100, RFC 4020, February
2005. 2005.
[RFC4034] - Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions", RFC 4034, Rose, "DNS Security Introduction and Requirements", RFC
March 2005. 4033, March 2005.
[RFC4035] - Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security Extensions", RFC Rose, "Resource Records for the DNS Security Extensions",
4035, March 2005. RFC 4034, March 2005.
INTERNET-DRAFT DNS IANA Considerations [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, March 2005.
[RFC4635] - Eastlake 3rd, D., "HMAC SHA (Hashed Message [RFC4635] Eastlake 3rd, D., "HMAC SHA (Hashed Message Authentication
Authentication Code, Secure Hash Algorithm) TSIG Algorithm Code, Secure Hash Algorithm) TSIG Algorithm Identifiers",
Identifiers", RFC 4635, August 2006. RFC 4635, August 2006.
[RFC5226] - Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[US-ASCII] - ANSI, "USA Standard Code for Information Interchange", [US-ASCII] ANSI, "USA Standard Code for Information Interchange",
X3.4, American National Standards Institute: New York, 1968. X3.4, American National Standards Institute: New York,
1968.
Informative References Informative References
[Dyer1987] - Dyer, S., and F. Hsu, "Hesiod", Project Athena Technical [Dyer1987] Dyer, S., and F. Hsu, "Hesiod", Project Athena Technical
Plan - Name Service, April 1987. Plan - Name Service, April 1987.
[Moon1981] - Moon, D., "Chaosnet", A.I. Memo 628, Massachusetts
Institute of Technology Artificial Intelligence Laboratory, June
1981.
[RFC1183] - Everhart, C., Mamakos, L., Ullmann, R., and P. [Moon1981] Moon, D., "Chaosnet", A.I. Memo 628, Massachusetts
Mockapetris, "New DNS RR Definitions", RFC 1183, October 1990. Institute of Technology Artificial Intelligence
Laboratory, June 1981.
[RFC1591] - Postel, J., "Domain Name System Structure and [RFC1183] Everhart, C., Mamakos, L., Ullmann, R., and P.
Delegation", RFC 1591, March 1994. Mockapetris, "New DNS RR Definitions", RFC 1183, October
1990.
[RFC2606] - Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS [RFC1591] Postel, J., "Domain Name System Structure and Delegation",
Names", BCP 32, RFC 2606, June 1999. RFC 1591, March 1994.
[RFC2673] - Crawford, M., "Binary Labels in the Domain Name System", [RFC2606] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
RFC 2673, August 1999. Names", BCP 32, RFC 2606, June 1999.
[RFC2931] - Eastlake 3rd, E., "DNS Request and Transaction Signatures [RFC2673] Crawford, M., "Binary Labels in the Domain Name System",
( SIG(0)s )", RFC 2931, September 2000. RFC 2673, August 1999.
[RFC3363] - Bush, R., Durand, A., Fink, B., Gudmundsson, O., and T. [RFC2931] Eastlake 3rd, D., "DNS Request and Transaction Signatures
Hain, "Representing Internet Protocol version 6 (IPv6) Addresses in ( SIG(0)s )", RFC 2931, September 2000.
the Domain Name System (DNS)", RFC 3363, August 2002.
[RFC4343] - Eastlake, D., "Domain Name System (DNS) Case [RFC3363] Bush, R., Durand, A., Fink, B., Gudmundsson, O., and T.
Insensitivity Clarification", RFC 4343, December 2005. Hain, "Representing Internet Protocol version 6 (IPv6)
Addresses in the Domain Name System (DNS)", RFC 3363,
August 2002.
[RFC5395] - Eastlake 3rd, D., "Domain Name System (DNS) IANA [RFC4343] Eastlake 3rd, D., "Domain Name System (DNS) Case
Considerations", BCP 42, RFC 5395, November 2008. Insensitivity Clarification", RFC 4343, January 2006.
INTERNET-DRAFT DNS IANA Considerations [RFC5395] Eastlake 3rd, D., "Domain Name System (DNS) IANA
Considerations", BCP 42, RFC 5395, November 2008.
Author's Address Author's Address
Donald Eastlake Donald E. Eastlake 3rd
Huawei Huawei Technologies
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Telephone: +1-508-333-2270 Phone: +1-508-333-2270
email: d3e3e3@gmail.com EMail: d3e3e3@gmail.com
Copyright and IPR Provisions
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License. The definitive version of an IETF
Document is that published by, or under the auspices of, the IETF.
Versions of IETF Documents that are published by third parties,
including those that are translated into other languages, should not
be considered to be definitive versions of IETF Documents. The
definitive version of these Legal Provisions is that published by, or
under the auspices of, the IETF. Versions of these Legal Provisions
that are published by third parties, including those that are
translated into other languages, should not be considered to be
definitive versions of these Legal Provisions. For the avoidance of
doubt, each Contributor to the IETF Standards Process licenses each
Contribution that he or she makes as part of the IETF Standards
Process to the IETF Trust pursuant to the provisions of RFC 5378. No
language to the contrary, or terms, conditions or rights that differ
from or are inconsistent with the rights and licenses granted under
RFC 5378, shall have any effect and shall be null and void, whether
published or posted by such Contributor, or included with or in such
Contribution.
 End of changes. 142 change blocks. 
396 lines changed or deleted 365 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/