draft-iab-2870bis-03.txt   rfc7720.txt 
Network Working Group M. Blanchet Internet Engineering Task Force (IETF) M. Blanchet
Internet-Draft Viagenie Request for Comments: 7720 Viagenie
Obsoletes: 2870 (if approved) L-J. Liman BCP: 40 L-J. Liman
Intended status: Best Current Practice Netnod Obsoletes: 2870 Netnod
Expires: March 27, 2016 September 24, 2015 Category: Best Current Practice December 2015
ISSN: 2070-1721
DNS Root Name Service Protocol and Deployment Requirements DNS Root Name Service Protocol and Deployment Requirements
draft-iab-2870bis-03.txt
Abstract Abstract
The DNS Root Name service is a critical part of the Internet The DNS root name service is a critical part of the Internet
architecture. The protocol and deployment requirements expected to architecture. The protocol and deployment requirements for the DNS
be implemented for the DNS root name service are defined in this root name service are defined in this document. Operational
document. Operational requirements are out of scope. requirements are out of scope.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This memo documents an Internet Best Current Practice.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
This Internet-Draft will expire on March 27, 2016. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7720.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. RFC 2870 as Historic . . . . . . . . . . . . . . . . . . 2 1.1. Relationship to RFC 2870 . . . . . . . . . . . . . . . . 2
2. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 2 2. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 3
3. Deployment Requirements . . . . . . . . . . . . . . . . . . . 3 3. Deployment Requirements . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. Informative References . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Informative References . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
[RFC2870] discusses protocol and operational requirements for root [RFC2870] discusses protocol and operational requirements for root
name servers for Internet's domain name system(DNS) protocol name servers for the Internet's domain name system (DNS) protocol
[RFC1035]. Since its publication, both protocol and operational [RFC1035]. Since its publication, both protocol and operational
requirements have evolved. It makes more sense now to separate the requirements have evolved. It makes more sense now to separate the
two sets of requirements into two separate documents. The two sets of requirements into two separate documents. This document
operational requirements are defined in [RSSAC-001]. This document only defines the protocol requirements and some deployment
defines the protocol requirements and some deployment requirements. requirements. The operational requirements that were defined in RFC
2870 have been removed. Operational requirements are now defined by
the Root Server System Advisory Committee of ICANN and are documented
in [RSSAC-001].
The root servers are authoritative servers of the unique [RFC2826] The root servers are authoritative servers of the unique [RFC2826]
root zone (".")[ROOTZONE]. They currently also serve the root- root zone (".") [ROOTZONE]. They currently also serve the root-
servers.net zone. Some also serve the zone for the .arpa top-level servers.net zone. Some also serve the zone for the .arpa top-level
domain[ARPAZONE]. This document describes the external interface of domain [ARPAZONE] [RFC3172]. This document describes the external
the root name servers from a protocol viewpoint of the service. It interface of the root name servers from a protocol viewpoint of the
specifies basic requirements for the Internet that DNS clients meet service. It specifies basic requirements for the Internet that DNS
when interacting with a root name service over the public Internet. clients meet when interacting with a root name service over the
public Internet.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in BCP 14, [RFC2119]. document, are to be interpreted as described in BCP 14, [RFC2119].
1.1. RFC 2870 as Historic 1.1. Relationship to RFC 2870
This document obsoletes and reclassifies [RFC2870] as Historic. This document obsoletes [RFC2870].
This document and [RSSAC-001] together functionally replace This document and [RSSAC-001] together functionally replace
[RFC2870]. [RFC2870].
2. Protocol Requirements 2. Protocol Requirements
This section describes the minimum high-level protocol requirements. This section describes the minimum high-level protocol requirements.
Operative details are documented in [RSSAC-001] and implementation is Operative details are documented in [RSSAC-001].
left to the operators of the root name service.
The root name service: The root name service:
MUST implement core DNS [RFC1035] and clarifications to the DNS o MUST implement core DNS [RFC1035] and clarifications to the DNS
[RFC2181]. [RFC2181].
MUST support IPv4[RFC0791] and IPv6[RFC2460] transport of DNS o MUST support IPv4 [RFC791] and IPv6 [RFC2460] transport of DNS
queries and responses. queries and responses.
MUST support UDP[RFC0768] and TCP[RFC0793] transport of DNS o MUST support UDP [RFC768] and TCP [RFC793] transport of DNS
queries and responses. queries and responses.
MUST generate checksums when sending UDP datagrams and MUST verify o MUST generate checksums when sending UDP datagrams and MUST verify
checksums when receiving UDP datagrams containing a non-zero checksums when receiving UDP datagrams containing a non-zero
checksum. checksum.
MUST implement DNSSEC[RFC4035], as an authoritative name service. o MUST implement DNSSEC [RFC4035] as an authoritative name service.
MUST implement EDNS(0)[RFC6891]. o MUST implement extension mechanisms for DNS (EDNS(0)) [RFC6891].
3. Deployment Requirements 3. Deployment Requirements
The root name service: The root name service:
MUST answer queries from any entity conforming to [RFC1122] with a o MUST answer queries from any entity conforming to [RFC1122] with a
valid IP address. valid IP address.
MUST serve the unique [RFC2826] root zone[ROOTZONE]. o MUST serve the unique [RFC2826] root zone [ROOTZONE].
4. Security Considerations 4. Security Considerations
This document does not specify a new protocol. However, the root This document does not specify a new protocol. However, the root
name service is a key component of the Internet architecture and play name service is a key component of the Internet architecture and play
a key role into the overall security of the Internet[RFC2826]. a key role into the overall security of the Internet [RFC2826].
Specific security considerations on the DNS protocols are discussed Specific security considerations on the DNS protocols are discussed
in their respective specifications. The security considerations on in their respective specifications. The security considerations on
the operational side of the root name servers are discussed in the operational side of the root name servers are discussed in
[RSSAC-001]. [RSSAC-001].
5. IANA Considerations 5. Informative References
This document has no action for IANA.
6. Acknowledgements
Some text was taken from [RFC2870]. The editors of this document [ARPAZONE] IANA, ".ARPA Zone Management",
would like to sincerely thank the following individuals for valuable <http://www.iana.org/domains/arpa>.
contributions to the text: Andrew Sullivan, Simon Perreault, Jean-
Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe Abley,
Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear, Bill
Manning, David Conrad, Paul Hoffman, Terry Manderson, Jari Arkko,
Mark Andrews.
7. Informative References [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC0768, August 1980,
<http://www.rfc-editor.org/info/rfc768>.
[ARPAZONE] [RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791,
Internet Assigned Numbers Authority (IANA), , ".ARPA Zone DOI 10.17487/RFC0791, September 1981,
Management", <http://www.iana.org/domains/arpa>. <http://www.rfc-editor.org/info/rfc791>.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC793] Postel, J., "Transmission Control Protocol", STD 7,
DOI 10.17487/RFC0768, August 1980, RFC 793, DOI 10.17487/RFC0793, September 1981,
<http://www.rfc-editor.org/info/rfc768>. <http://www.rfc-editor.org/info/rfc793>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC1035] Mockapetris, P., "Domain names - implementation and
DOI 10.17487/RFC0791, September 1981, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
<http://www.rfc-editor.org/info/rfc791>. November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
RFC 793, DOI 10.17487/RFC0793, September 1981, Communication Layers", STD 3, RFC 1122,
<http://www.rfc-editor.org/info/rfc793>. DOI 10.17487/RFC1122, October 1989,
<http://www.rfc-editor.org/info/rfc1122>.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, Requirement Levels", BCP 14, RFC 2119,
November 1987, <http://www.rfc-editor.org/info/rfc1035>. DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Communication Layers", STD 3, RFC 1122, Specification", RFC 2181, DOI 10.17487/RFC2181, July
DOI 10.17487/RFC1122, October 1989, 1997, <http://www.rfc-editor.org/info/rfc2181>.
<http://www.rfc-editor.org/info/rfc1122>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
Requirement Levels", BCP 14, RFC 2119, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
DOI 10.17487/RFC2119, March 1997, December 1998, <http://www.rfc-editor.org/info/rfc2460>.
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS [RFC2826] Internet Architecture Board, "IAB Technical Comment on
Specification", RFC 2181, DOI 10.17487/RFC2181, July 1997, the Unique DNS Root", RFC 2826, DOI 10.17487/RFC2826, May
<http://www.rfc-editor.org/info/rfc2181>. 2000, <http://www.rfc-editor.org/info/rfc2826>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak,
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, "Root Name Server Operational Requirements", BCP 40,
December 1998, <http://www.rfc-editor.org/info/rfc2460>. RFC 2870, DOI 10.17487/RFC2870, June 2000,
<http://www.rfc-editor.org/info/rfc2870>.
[RFC2826] Internet Architecture Board, "IAB Technical Comment on the [RFC3172] Huston, G., Ed., "Management Guidelines & Operational
Unique DNS Root", RFC 2826, DOI 10.17487/RFC2826, May Requirements for the Address and Routing Parameter Area
2000, <http://www.rfc-editor.org/info/rfc2826>. Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172,
September 2001, <http://www.rfc-editor.org/info/rfc3172>.
[RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Name Server Operational Requirements", BCP 40, RFC 2870, Rose, "Protocol Modifications for the DNS Security
DOI 10.17487/RFC2870, June 2000, Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005,
<http://www.rfc-editor.org/info/rfc2870>. <http://www.rfc-editor.org/info/rfc4035>.
[RFC3172] Huston, G., Ed., "Management Guidelines & Operational [RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
Requirements for the Address and Routing Parameter Area for DNS (EDNS(0))", STD 75, RFC 6891,
Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172, DOI 10.17487/RFC6891, April 2013,
September 2001, <http://www.rfc-editor.org/info/rfc3172>. <http://www.rfc-editor.org/info/rfc6891>.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. [ROOTZONE] "Root Zone", <ftp://rs.internic.net/domain/root.zone>.
Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, DOI 10.17487/RFC4035, March 2005,
<http://www.rfc-editor.org/info/rfc4035>.
[RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms [RSSAC-001] Root Server System Advisory Committee (RSSAC), "Service
for DNS (EDNS(0))", STD 75, RFC 6891, Expectations of Root Servers", November 2014,
DOI 10.17487/RFC6891, April 2013, <https://www.icann.org/en/system/files/files/
<http://www.rfc-editor.org/info/rfc6891>. rssac-001-root-service-expectations-04dec15-en.pdf>.
[ROOTZONE] Acknowledgements
"Root Zone", <ftp://rs.internic.net/domain/root.zone>.
[RSSAC-001] Some text was taken from [RFC2870]. The editors of this document
Root Server System Advisory Committee (RSSAC), , "Service would like to sincerely thank the following individuals for valuable
Expectations of Root Servers", November 2014, contributions to the text: Andrew Sullivan, Simon Perreault,
<https://www.icann.org/en/system/files/files/rssac-001- Jean-Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe
draft-20nov14-en.pdf>. Abley, Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear,
Bill Manning, David Conrad, Paul Hoffman, Terry Manderson, Jari
Arkko, and Mark Andrews.
Authors' Addresses Authors' Addresses
Marc Blanchet Marc Blanchet
Viagenie Viagenie
246 Aberdeen 246 Aberdeen
Quebec, QC G1R 2E1 Quebec, QC G1R 2E1
Canada Canada
Email: Marc.Blanchet@viagenie.ca Email: Marc.Blanchet@viagenie.ca
 End of changes. 43 change blocks. 
118 lines changed or deleted 110 lines changed or added

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