| Network Working Group | T. Wicinski |
| Internet-Draft | Salesforce |
| Intended status: Informational | October 31, 2016 |
| Expires: May 4, 2017 |
A Document Roadmap for the Doman Name System (DNS) Specifications
draft-wicinski-dns-roadmap-00
This document contains a roadmap to the Requests for Comments (RFC) documents relating to the Domain Name System (DNS). This roadmap provides a brief summary of the documents defining DNS and the various extensions. This serves as a guide and quick reference for DNS Implementers, as well as others.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on May 4, 2017.
Copyright (c) 2016 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 Simplified BSD License.
The Domain Name System (DNS) is a critical piece of communication for Internet hosts. As DNS has evolved over the years, many distinct documents have become part of the standard, updating older documents either partially or completely.
This document is intended as an introduction to DNS, and also an attempt to organize the work from over the years. It provides a brief summary of the RFC documents that define DNS. This should be useful to implementers and others on the relevance and significance of the work that relate to DNS.
This roadmap includes a brief description of the contents of each DNS-related RFC. In addition, a letter code after each RFC indicates its category in the RFC document process. The explanations of these codes are described in [RFC2026].
S - Standards Truck (either Proposed Standard, Draft Standard or Internet Standard)
E - Experimental
I - Informational
H - Historic
B - Best Current Practice
U - Unknown (or not formally defined)
The DNS consists of multiple portions which could be implemented. These parts are (but are not restricted to): an Authorative Server (which includes managing the storage of zone data) and a Caching Server.
The roadmap is broken up into several sections. Section 2 decribes the core functionality. Section 3 lists the RFCs which are required to implement a DNS Server Section 3.1 lists the DNS Resource Record (RR) Types nees Section 4 discusses managing DNS zone data and updating DNS Zones Section 5 covers DNS Security (DNSSEC), how to implmenet it.
Experimental extensions which are not yet standard track, as well as documents which help to document behavior of the DNS but are not required are in Section 6. Current Best Practices are described in Section 7.
For the definition of DNS terms or phrases, please refer to the DNS Terminology document [RFC7719]
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].
[RFC7719] I: “DNS Terminology”
Since the DNS has been defined in dozens of different RFC over several decades, the terminology used by developers, implementors and operators of the DNS protocol sometimes changed over time. This document captured how terms were defined in the original standards, and if they have different meanings today.
[RFC1034] U: “Domain Names - Concepts and Facilities”
[RFC1035] S: “Domain Names - Implementation and Specification”
[RFC2181] S: “Clarifications to the DNS Specification”
[RFC2308] S: “Negative Caching of DNS Queries (DNS NCACHE)”
[RFC5001] S: “DNS Name Server Identifier (NSID) Option”
[RFC4343] S: “Domain Name System (DNS) Case Insensitivity Clarification”
[RFC6604] S: “xNAME RCODE and Status Bits Clarification”
[RFC3597] S: “Handling of Unknown DNS Resource Record (RR) Types”
[RFC4592] S: “The Role of Wildcards in the Domain Name System”
[RFC1536] I: “Common DNS Implementation Errors and Suggested Fixes”
[RFC7766] S: “DNS Transport over TCP - Implementation Requirements”
[RFC4033] S: “DNS Security Introduction and Requirements”
[RFC4034] S: “Resource Records for the DNS Security Extensions”
[RFC4035] S: “Protocol Modifications for the DNS Security Extensions”
[RFC3225] S: “Indicating Resolver Support of DNSSEC”
[RFC3226] S: “DNSSEC and IPv6 A6 aware server/resolver message size requirements”
[RFC4470] S: “Minimally Covering NSEC Records and DNSSEC On-line Signing”
[RFC4955] S: “DNS Security (DNSSEC) Experiments”
[RFC5155] S: “DNS Security (DNSSEC) Hashed Authenticated Denial of Existence”
[RFC6840] S: “Clarifications and Implementation Notes for DNS Security (DNSSEC)”
[RFC4956] E: “DNS Security (DNSSEC) Opt-In”
[RFC6841] I: “A Framework for DNSSEC Policies and DNSSEC Practice Statements”
| [RFC2026] | Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996. |
| [RFC7719] | Hoffman, P., Sullivan, A. and K. Fujiwara, "DNS Terminology", RFC 7719, DOI 10.17487/RFC7719, December 2015. |