idnits 2.17.1 draft-blanchet-iab-2870bis-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC2870, but the abstract doesn't seem to directly say this. It does mention RFC2870 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (June 11, 2013) is 3971 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 793 (Obsoleted by RFC 9293) -- Obsolete informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) -- Obsolete informational reference (is this intentional?): RFC 2870 (Obsoleted by RFC 7720) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Blanchet 3 Internet-Draft Viagenie 4 Obsoletes: 2870 (if approved) L-J. Liman 5 Intended status: Best Current Practice Netnod 6 Expires: December 13, 2013 June 11, 2013 8 DNS Root Name Service Protocol and Deployment Requirements 9 draft-blanchet-iab-2870bis-00.txt 11 Abstract 13 The DNS Root Name service are a critical part of the Internet 14 architecture. The protocol and deployment requirements expected to 15 be implemented for the DNS root name services are defined in this 16 document. Operational requirements are out of scope. This document 17 obsoletes and reclassifies RFC2870 as Historic. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on December 13, 2013. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. RFC 2870 as Historic . . . . . . . . . . . . . . . . . . 2 55 2. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 3 56 3. Deployment Requirements . . . . . . . . . . . . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Informative References . . . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 63 1. Introduction 65 [RFC2870] discusses protocol and operational requirements for root 66 name servers for Internet's domain name system(DNS) protocol 67 [RFC1035]. Since its publication, both protocol and operational 68 requirements have evolved. The concensus of the community is to 69 separate the two sets of requirements into two documents. The 70 operational requirements are defined in [RSSAC-001]. This document 71 defines the protocol requirements and some deployment requirements. 73 The root servers are authoritative servers of the unique [RFC2826] 74 root zone (".")[ROOTZONE], the root-servers.net zone, and the zone 75 for the .arpa top-level domain[ARPAZONE]. This document describes 76 the external interface of the root name servers from a protocol 77 viewpoint of the service. It specifies basic requirements for the 78 Internet that DNS clients meet when interacting with a root name 79 service over the public Internet. 81 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 82 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this 83 document, are to be interpreted as described in BCP 14, [RFC2119]. 85 1.1. RFC 2870 as Historic 87 This document obsoletes and reclassifies [RFC2870] as Historic. 89 2. Protocol Requirements 91 This section describes the high-level protocol requirements. 92 Operative details are not discussed and are left to the operators of 93 the root name service. 95 The root name service: 97 MUST implement [RFC1035] and [RFC2181]. 99 MUST support IPv4[RFC0791] and IPv6[RFC2460] transport of DNS 100 queries and responses. 102 MUST support UDP[RFC0768] and TCP[RFC0793] transport of DNS 103 queries and responses. 105 MUST generate checksums when sending UDP datagrams and MUST verify 106 checksums when receiving UDP datagrams containing a non-zero 107 checksum. 109 MUST implement DNSSEC[RFC4035], as an authoritative name service 110 serving signed zones accodingly. 112 3. Deployment Requirements 114 The root name service: 116 MUST answer queries from any Internet host 118 MUST serve the unique [RFC2826] root zone[ROOTZONE], the root- 119 servers.net zone, and the zone for the .arpa top-level domain 120 [ARPAZONE],[RFC3172]. 122 4. Security Considerations 124 This document does not specify a new protocol. However, the root 125 name servers are a key component of the Internet architecture and 126 play a key role into the overall security of the Internet[RFC2826]. 127 Specific security considerations on the DNS protocols are discussed 128 in their respective specifications. The security considerations on 129 the operational side of the root name servers are discussed in 130 [RSSAC-001]. 132 5. IANA Considerations 134 This document has no action for IANA. 136 6. Acknowledgements 138 Some text was taken from [RFC2870]. Andrew Sullivan, Simon 139 Perreault, Jean-Philippe Dionne, Dave Thaler, Russ Housley, Alissa 140 Cooper, Joe Abley, Joao Damas, Daniel Karrenberg, Jacques Latour, 141 Eliot Lear, provided comments or text. 143 7. Informative References 145 [ARPAZONE] 146 Internet Assigned Numbers Authority (IANA), ., ".ARPA Zone 147 Management", , . 149 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 150 August 1980. 152 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 153 1981. 155 [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 156 793, September 1981. 158 [RFC1035] Mockapetris, P., "Domain names - implementation and 159 specification", STD 13, RFC 1035, November 1987. 161 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 162 Requirement Levels", BCP 14, RFC 2119, March 1997. 164 [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS 165 Specification", RFC 2181, July 1997. 167 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 168 (IPv6) Specification", RFC 2460, December 1998. 170 [RFC2826] Internet Architecture Board, "IAB Technical Comment on the 171 Unique DNS Root", RFC 2826, May 2000. 173 [RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root 174 Name Server Operational Requirements", BCP 40, RFC 2870, 175 June 2000. 177 [RFC3172] Huston, G., "Management Guidelines & Operational 178 Requirements for the Address and Routing Parameter Area 179 Domain ("arpa")", BCP 52, RFC 3172, September 2001. 181 [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. 182 Rose, "Protocol Modifications for the DNS Security 183 Extensions", RFC 4035, March 2005. 185 [ROOTZONE] 186 , "Root Zone", , . 188 [RSSAC-001] 189 Abley, J., Damas, J., Larson, M., Liman, L-J., Manderson, 190 T., and B. Verd, "Service Expectations of Root Servers", , 191 . 193 Authors' Addresses 195 Marc Blanchet 196 Viagenie 197 246 Aberdeen 198 Quebec, QC G1R 2E1 199 Canada 201 Email: Marc.Blanchet@viagenie.ca 202 URI: http://viagenie.ca 204 Lars-Johan Liman 205 Netnod Internet Exchange 206 Box 30194 207 SE-104 25 Stockholm 208 Sweden 210 Email: liman@netnod.se 211 URI: http://www.netnod.se/