idnits 2.17.1 draft-wicinski-dns-roadmap-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 31, 2016) is 2732 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 7719 (Obsoleted by RFC 8499) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Wicinski 3 Internet-Draft Salesforce 4 Intended status: Informational October 31, 2016 5 Expires: May 4, 2017 7 A Document Roadmap for the Doman Name System (DNS) Specifications 8 draft-wicinski-dns-roadmap-00 10 Abstract 12 This document contains a roadmap to the Requests for Comments (RFC) 13 documents relating to the Domain Name System (DNS). This roadmap 14 provides a brief summary of the documents defining DNS and the 15 various extensions. This serves as a guide and quick reference for 16 DNS Implementers, as well as others. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 4, 2017. 35 Copyright Notice 37 Copyright (c) 2016 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 54 1.2. DNS Terminology . . . . . . . . . . . . . . . . . . . . . 3 55 2. Core Functionality and Specifications . . . . . . . . . . . . 3 56 3. Implementation . . . . . . . . . . . . . . . . . . . . . . . 4 57 3.1. DNS Resource Record (RR) Types . . . . . . . . . . . . . 4 58 4. DNS Zones . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 4.1. Managing DNS Zone Data . . . . . . . . . . . . . . . . . 4 60 4.2. Updating DNS Zones . . . . . . . . . . . . . . . . . . . 4 61 4.3. Name Server Management . . . . . . . . . . . . . . . . . 4 62 5. DNS Security (DNSSEC) . . . . . . . . . . . . . . . . . . . . 4 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 67 8.2. Informative References . . . . . . . . . . . . . . . . . 7 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 70 1. Introduction 72 The Domain Name System (DNS) is a critical piece of communication for 73 Internet hosts. As DNS has evolved over the years, many distinct 74 documents have become part of the standard, updating older documents 75 either partially or completely. 77 This document is intended as an introduction to DNS, and also an 78 attempt to organize the work from over the years. It provides a 79 brief summary of the RFC documents that define DNS. This should be 80 useful to implementers and others on the relevance and significance 81 of the work that relate to DNS. 83 This roadmap includes a brief description of the contents of each 84 DNS-related RFC. In addition, a letter code after each RFC indicates 85 its category in the RFC document process. The explanations of these 86 codes are described in [RFC2026]. 88 S - Standards Truck (either Proposed Standard, Draft Standard or 89 Internet Standard) 91 E - Experimental 93 I - Informational 95 H - Historic 97 B - Best Current Practice 98 U - Unknown (or not formally defined) 100 The DNS consists of multiple portions which could be implemented. 101 These parts are (but are not restricted to): an Authorative Server 102 (which includes managing the storage of zone data) and a Caching 103 Server. 105 The roadmap is broken up into several sections. Section 2 decribes 106 the core functionality. Section 3 lists the RFCs which are required 107 to implement a DNS Server Section 3.1 lists the DNS Resource Record 108 (RR) Types nees Section 4 discusses managing DNS zone data and 109 updating DNS Zones Section 5 covers DNS Security (DNSSEC), how to 110 implmenet it. 112 Experimental extensions which are not yet standard track, as well as 113 documents which help to document behavior of the DNS but are not 114 required are in Section 6. Current Best Practices are described in 115 Section 7. 117 For the definition of DNS terms or phrases, please refer to the DNS 118 Terminology document [RFC7719] 120 1.1. Notational Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in [RFC2119]. 126 1.2. DNS Terminology 128 [RFC7719] I: "DNS Terminology" 130 Since the DNS has been defined in dozens of different RFC over 131 several decades, the terminology used by developers, implementors and 132 operators of the DNS protocol sometimes changed over time. This 133 document captured how terms were defined in the original standards, 134 and if they have different meanings today. 136 2. Core Functionality and Specifications 138 [RFC1034] U: "Domain Names - Concepts and Facilities" 140 [RFC1035] S: "Domain Names - Implementation and Specification" 142 [RFC2181] S: "Clarifications to the DNS Specification" 144 3. Implementation 146 [RFC2308] S: "Negative Caching of DNS Queries (DNS NCACHE)" 148 [RFC5001] S: "DNS Name Server Identifier (NSID) Option" 150 [RFC4343] S: "Domain Name System (DNS) Case Insensitivity 151 Clarification" 153 [RFC6604] S: "xNAME RCODE and Status Bits Clarification" 155 [RFC3597] S: "Handling of Unknown DNS Resource Record (RR) Types" 157 [RFC4592] S: "The Role of Wildcards in the Domain Name System" 159 [RFC1536] I: "Common DNS Implementation Errors and Suggested Fixes" 161 [RFC7766] S: "DNS Transport over TCP - Implementation Requirements" 163 3.1. DNS Resource Record (RR) Types 165 4. DNS Zones 167 4.1. Managing DNS Zone Data 169 4.2. Updating DNS Zones 171 4.3. Name Server Management 173 5. DNS Security (DNSSEC) 175 [RFC4033] S: "DNS Security Introduction and Requirements" 177 [RFC4034] S: "Resource Records for the DNS Security Extensions" 179 [RFC4035] S: "Protocol Modifications for the DNS Security Extensions" 181 [RFC3225] S: "Indicating Resolver Support of DNSSEC" 183 [RFC3226] S: "DNSSEC and IPv6 A6 aware server/resolver message size 184 requirements" 186 [RFC4470] S: "Minimally Covering NSEC Records and DNSSEC On-line 187 Signing" 189 [RFC4955] S: "DNS Security (DNSSEC) Experiments" 191 [RFC5155] S: "DNS Security (DNSSEC) Hashed Authenticated Denial of 192 Existence" 194 [RFC6840] S: "Clarifications and Implementation Notes for DNS 195 Security (DNSSEC)" 197 [RFC4956] E: "DNS Security (DNSSEC) Opt-In" 199 [RFC6841] I: "A Framework for DNSSEC Policies and DNSSEC Practice 200 Statements" 202 6. IANA Considerations 204 7. Security Considerations 206 8. References 208 8.1. Normative References 210 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 211 STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, 212 . 214 [RFC1035] Mockapetris, P., "Domain names - implementation and 215 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 216 November 1987, . 218 [RFC1536] Kumar, A., Postel, J., Neuman, C., Danzig, P., and S. 219 Miller, "Common DNS Implementation Errors and Suggested 220 Fixes", RFC 1536, DOI 10.17487/RFC1536, October 1993, 221 . 223 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 224 Requirement Levels", BCP 14, RFC 2119, 225 DOI 10.17487/RFC2119, March 1997, 226 . 228 [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS 229 Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997, 230 . 232 [RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS 233 NCACHE)", RFC 2308, DOI 10.17487/RFC2308, March 1998, 234 . 236 [RFC3225] Conrad, D., "Indicating Resolver Support of DNSSEC", 237 RFC 3225, DOI 10.17487/RFC3225, December 2001, 238 . 240 [RFC3226] Gudmundsson, O., "DNSSEC and IPv6 A6 aware server/resolver 241 message size requirements", RFC 3226, 242 DOI 10.17487/RFC3226, December 2001, 243 . 245 [RFC3597] Gustafsson, A., "Handling of Unknown DNS Resource Record 246 (RR) Types", RFC 3597, DOI 10.17487/RFC3597, September 247 2003, . 249 [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. 250 Rose, "DNS Security Introduction and Requirements", 251 RFC 4033, DOI 10.17487/RFC4033, March 2005, 252 . 254 [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. 255 Rose, "Resource Records for the DNS Security Extensions", 256 RFC 4034, DOI 10.17487/RFC4034, March 2005, 257 . 259 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 260 Rose, "Protocol Modifications for the DNS Security 261 Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005, 262 . 264 [RFC4343] Eastlake 3rd, D., "Domain Name System (DNS) Case 265 Insensitivity Clarification", RFC 4343, 266 DOI 10.17487/RFC4343, January 2006, 267 . 269 [RFC4470] Weiler, S. and J. Ihren, "Minimally Covering NSEC Records 270 and DNSSEC On-line Signing", RFC 4470, 271 DOI 10.17487/RFC4470, April 2006, 272 . 274 [RFC4592] Lewis, E., "The Role of Wildcards in the Domain Name 275 System", RFC 4592, DOI 10.17487/RFC4592, July 2006, 276 . 278 [RFC4955] Blacka, D., "DNS Security (DNSSEC) Experiments", RFC 4955, 279 DOI 10.17487/RFC4955, July 2007, 280 . 282 [RFC4956] Arends, R., Kosters, M., and D. Blacka, "DNS Security 283 (DNSSEC) Opt-In", RFC 4956, DOI 10.17487/RFC4956, July 284 2007, . 286 [RFC5001] Austein, R., "DNS Name Server Identifier (NSID) Option", 287 RFC 5001, DOI 10.17487/RFC5001, August 2007, 288 . 290 [RFC5155] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS 291 Security (DNSSEC) Hashed Authenticated Denial of 292 Existence", RFC 5155, DOI 10.17487/RFC5155, March 2008, 293 . 295 [RFC6604] Eastlake 3rd, D., "xNAME RCODE and Status Bits 296 Clarification", RFC 6604, DOI 10.17487/RFC6604, April 297 2012, . 299 [RFC6840] Weiler, S., Ed. and D. Blacka, Ed., "Clarifications and 300 Implementation Notes for DNS Security (DNSSEC)", RFC 6840, 301 DOI 10.17487/RFC6840, February 2013, 302 . 304 [RFC6841] Ljunggren, F., Eklund Lowinder, AM., and T. Okubo, "A 305 Framework for DNSSEC Policies and DNSSEC Practice 306 Statements", RFC 6841, DOI 10.17487/RFC6841, January 2013, 307 . 309 [RFC7766] Dickinson, J., Dickinson, S., Bellis, R., Mankin, A., and 310 D. Wessels, "DNS Transport over TCP - Implementation 311 Requirements", RFC 7766, DOI 10.17487/RFC7766, March 2016, 312 . 314 8.2. Informative References 316 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 317 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 318 . 320 [RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 321 Terminology", RFC 7719, DOI 10.17487/RFC7719, December 322 2015, . 324 Author's Address 326 Tim Wicinski 327 Salesforce 329 Email: tjw.ietf@gmail.com