Browse Prior Art Database

Root Name Server Operational Requirements (RFC2870)

IP.com Disclosure Number: IPCOM000003471D
Original Publication Date: 2000-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 8 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Bush: AUTHOR [+4]

Abstract

As the internet becomes increasingly critical to the world's social and economic infrastructure, attention has rightly focused on the correct, safe, reliable, and secure operation of the internet infrastructure itself. The root domain name servers are seen as a crucial part of that technical infrastructure. The primary focus of this document is to provide guidelines for operation of the root name servers. Other major zone server operators (gTLDs, ccTLDs, major zones) may also find it useful. These guidelines are intended to meet the perceived societal needs without overly prescribing technical details.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group R. Bush

Request for Comments: 2870 Verio

Obsoletes: 2010 D. Karrenberg

BCP: 40 RIPE NCC

Category: Best Current Practice M. Kosters

Network Solutions

R. Plzak

SAIC

June 2000

Root Name Server Operational Requirements

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

As the internet becomes increasingly critical to the world's social

and economic infrastructure, attention has rightly focused on the

correct, safe, reliable, and secure operation of the internet

infrastructure itself. The root domain name servers are seen as a

crucial part of that technical infrastructure. The primary focus of

this document is to provide guidelines for operation of the root name

servers. Other major zone server operators (gTLDs, ccTLDs, major

zones) may also find it useful. These guidelines are intended to

meet the perceived societal needs without overly prescribing

technical details.

1. Background

The resolution of domain names on the internet is critically

dependent on the proper, safe, and secure operation of the root

domain name servers. Currently, these dozen or so servers are

provided and operated by a very competent and trusted group of

volunteers. This document does not propose to change that, but

merely to provide formal guidelines so that the community understands

how and why this is done.

1.1 The Internet Corporation for Assigned Names and Numbers (ICANN)

has become responsible for the operation of the root servers.

The ICANN has appointed a Root Server System Advisory Committee

(RSSAC) to give technical and operational advice to the ICANN

board. The ICANN and the RSSAC look to the IETF to provide

engineering standards.

1.2 The root servers serve the root, aka ".", zone. Although today

some of the root servers also serve some TLDs (top level domains)

such as gTLDs (COM, NET, ORG, etc.), infrastructural TLDs such as

INT and IN-ADDR.ARPA, and some ccTLDs (country code TLDs, e.g. SE

for Sweden), this is likely to change (see 2.5).

1.3 The root servers are neither involved with nor dependent upon the

'whois' data.

1.4 The domain name system has proven to be sufficiently robust that

we are confident that the, presumably te...