Network Working Group M. Blanchet
Internet-Draft Viagenie
Obsoletes: 2870 (if approved) L-J. Liman
Intended status: Best Current Practice Netnod
Expires: January 11, 2014 July 10, 2013

DNS Root Name Service Protocol and Deployment Requirements


The DNS Root Name service are a critical part of the Internet architecture. The protocol and deployment requirements expected to be implemented for the DNS root name services are defined in this document. Operational requirements are out of scope. This document obsoletes and reclassifies RFC2870 as Historic.

Status of This Memo

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

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 January 11, 2014.

Copyright Notice

Copyright (c) 2013 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 ( 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.

Table of Contents

1. Introduction

[RFC2870] discusses protocol and operational requirements for root name servers for Internet's domain name system(DNS) protocol [RFC1035]. Since its publication, both protocol and operational requirements have evolved. The concensus of the community is to separate the two sets of requirements into two documents. The operational requirements are defined in [RSSAC-001]. This document defines the protocol requirements and some deployment requirements.

The root servers are authoritative servers of the unique [RFC2826] root zone (".")[ROOTZONE], the zone, and the zone for the .arpa top-level domain[ARPAZONE]. This document describes the external interface of the root name servers from a protocol viewpoint of the service. It specifies basic requirements for the Internet that DNS clients meet when interacting with a root name service over the public Internet.

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in BCP 14, [RFC2119].

1.1. RFC 2870 as Historic

This document obsoletes and reclassifies [RFC2870] as Historic.

2. Protocol Requirements

This section describes the high-level protocol requirements. Operative details are not discussed and are left to the operators of the root name service.

The root name service:

3. Deployment Requirements

The root name service:

4. Security Considerations

This document does not specify a new protocol. However, the root name servers are a key component of the Internet architecture and play a key role into the overall security of the Internet[RFC2826]. Specific security considerations on the DNS protocols are discussed in their respective specifications. The security considerations on the operational side of the root name servers are discussed in [RSSAC-001].

5. IANA Considerations

This document has no action for IANA.

6. Acknowledgements

Some text was taken from [RFC2870]. Andrew Sullivan, Simon Perreault, Jean-Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe Abley, Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear, provided comments or text.

7. Informative References

, "
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS Specification", RFC 2181, July 1997.
[RFC2460] Deering, S.E. and R.M. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[RFC2826] Internet Architecture Board, "IAB Technical Comment on the Unique DNS Root", RFC 2826, May 2000.
[RFC2870] Bush, R., Karrenberg, D., Kosters, M. and R. Plzak, "Root Name Server Operational Requirements", BCP 40, RFC 2870, June 2000.
[RFC3172] Huston, G., "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")", BCP 52, RFC 3172, September 2001.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D. and S. Rose, "Protocol Modifications for the DNS Security Extensions", RFC 4035, March 2005.
[RSSAC-001] Abley, J., Damas, J., Larson, M., Liman, L-J., Manderson, T. and B. Verd, "Service Expectations of Root Servers", .
[ROOTZONE]Root Zone", .
[ARPAZONE] Internet Assigned Numbers Authority (IANA), , ".ARPA Zone Management", .

Authors' Addresses

Marc Blanchet Viagenie 246 Aberdeen Quebec, QC G1R 2E1 Canada EMail: URI:
Lars-Johan Liman Netnod Internet Exchange Box 30194 SE-104 25 Stockholm, Sweden EMail: URI: