Network Working Group | M. Blanchet |
Internet-Draft | Viagenie |
Obsoletes: 2870 (if approved) | L-J. Liman |
Intended status: Best Current Practice | Netnod |
Expires: December 13, 2013 | June 11, 2013 |
DNS Root Name Service Protocol and Deployment Requirements
draft-blanchet-iab-2870bis-00.txt
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.
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 December 13, 2013.
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 (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.
[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 root-servers.net 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].
This document obsoletes and reclassifies [RFC2870] as Historic.
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:
The root name service:
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].
This document has no action for IANA.
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.