DNS Root Name Service Protocol and Deployment Requirements
draft-iab-2870bis-02

The information below is for an old version of the document
Document Type Active Internet-Draft
Last updated 2015-03-12 (latest revision 2015-02-14)
Replaces draft-blanchet-iab-2870bis
Stream IETF
Intended RFC status Best Current Practice
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Jari Arkko
Send notices to jari.arkko@piuha.net, housley@vigilsec.com, marc.blanchet@viagenie.ca, liman@netnod.se
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                        M. Blanchet
Internet-Draft                                                  Viagenie
Obsoletes: 2870 (if approved)                                 L-J. Liman
Intended status: Best Current Practice                            Netnod
Expires: August 18, 2015                               February 14, 2015

       DNS Root Name Service Protocol and Deployment Requirements
                        draft-iab-2870bis-02.txt

Abstract

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

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 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 August 18, 2015.

Copyright Notice

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

Blanchet & Liman         Expires August 18, 2015                [Page 1]
Internet-Draft       Root Name Service Requirements        February 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  RFC 2870 as Historic  . . . . . . . . . . . . . . . . . .   2
   2.  Protocol Requirements . . . . . . . . . . . . . . . . . . . .   2
   3.  Deployment Requirements . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

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.  It makes more sense now to separate the
   two sets of requirements into two separate 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].  They currently also serve the root-
   servers.net zone.  Some also serve 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.

   This document and [RSSAC-001] together functionally replace
   [RFC2870].

2.  Protocol Requirements

   This section describes the minimum high-level protocol requirements.
   Operative details are documented in [RSSAC-001] and implementation is
   left to the operators of the root name service.

   The root name service:

Blanchet & Liman         Expires August 18, 2015                [Page 2]
Internet-Draft       Root Name Service Requirements        February 2015

      MUST implement core DNS [RFC1035] and clarifications to the DNS
      [RFC2181].

      MUST support IPv4[RFC0791] and IPv6[RFC2460] transport of DNS
      queries and responses.

      MUST support UDP[RFC0768] and TCP[RFC0793] transport of DNS
Show full document text