Domain Name System (DNS) IANA Considerations
draft-ietf-dnsext-rfc6195bis-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (dnsext WG)
|
|
Last updated |
|
2012-07-02
|
|
Replaces |
|
draft-eastlake-dnsext-6195bis
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
INTERNET-DRAFT Donald Eastlake
Obsoletes: 6195 Huawei
Updates: 1183, 2845, 2930, 3597
Intended status: Best Current Practice
Expires: January 1, 2013 July 2, 2012
Domain Name System (DNS) IANA Considerations
<draft-ietf-dnsext-rfc6195bis-03.txt>
Abstract
This document specifies Internet Assigned Number Authority (IANA)
parameter assignment considerations for the allocation of Domain Name
System (DNS) resource record types, CLASSes, operation codes, error
codes, DNS protocol message header bits, and AFSDB resource record
subtypes. It obsoletes RFC 6195 and updates RFCs 1183, 2845, 2930,
and 3597.
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Distribution of this draft is unlimited. It is intended to become the
new BCP 42 obsoleting RFC 6195. Comments should be sent to the DNS
Extensions Working Group mailing list <dnsext@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
D. Eastlake 3rd [Page 1]
INTERNET-DRAFT DNS IANA Considerations
Table of Contents
1. Introduction............................................3
1.1 Terminology............................................3
1.2 Acknowledgement........................................3
2. DNS Query/Response Headers..............................4
2.1 One Spare Bit?.........................................5
2.2 OpCode Assignment......................................5
2.3 RCODE Assignment.......................................5
3. DNS Resource Records....................................8
3.1 RRTYPE IANA Considerations.............................9
3.1.1 DNS RRTYPE Allocation Policy........................10
3.1.2 DNS RRTYPE Expert Guidelines........................11
3.1.3 Special Note on the OPT RR..........................11
3.1.4 The AFSDB RR Subtype Field..........................12
3.2 RR CLASS IANA Considerations..........................12
3.3. Label Considerations.................................14
3.3.1 Label Types.........................................14
3.3.2 Label Contents and Use..............................14
4. Security Considerations................................16
5. IANA Considerations....................................16
Appendix A: RRTYPE Allocation Template....................17
Appendix B: Changes From RFC 6195.........................18
Normative References......................................19
Informative References....................................20
D. Eastlake 3rd [Page 2]
INTERNET-DRAFT DNS IANA Considerations
1. Introduction
The Domain Name System (DNS) provides replicated distributed secure
hierarchical databases that store "resource records" (RRs) under
domain names. DNS data is structured into CLASSes and zones that can
be independently maintained. Familiarity with [RFC1034], [RFC1035],
[RFC2136], [RFC2181], and [RFC4033] is assumed.
This document provides, either directly or by reference, the general
IANA parameter assignment considerations that apply across DNS query
and response headers and all RRs. There may be additional IANA
considerations that apply to only a particular RRTYPE or
query/response OpCode. See the specific RFC defining that RRTYPE or
query/response OpCode for such considerations if they have been
defined, except for AFSDB RR considerations [RFC1183], which are
included herein. This RFC obsoletes [RFC6195]; however, the only
significant changes are those to the RRTYPE IANA allocation process,
aimed at streamlining it and clarifying the expected behavior of the
parties involved, and the closing of the AFSDB sub-type registry.
Show full document text