RFC 2870: Root Name Server Operational Requirements
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7720.
Current document in this lineage: RFC 7720 — DNS Root Name Service Protocol and Deployment Requirements
In plain English — editorial summary, not part of the RFC
The primary focus of this document is to provide guidelines for operation of the root name servers. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2870
- Published
- June 2000
- Authors
- R. Bush; D. Karrenberg; M. Kosters; R. Plzak
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2010 (1996)
- RFC 2870 (2000)
- RFC 7720 (2015) ✓
Read the full history of DNS Root Name Service Protocol and Deployment Requirements →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 2726PGP Authentication for RIPE Database UpdatesCurrent
December 1999
- RFC 2725Routing Policy System SecurityUpdated
December 1999
- RFC 3053IPv6 Tunnel BrokerCurrent
January 2001
- RFC 3084COPS Usage for Policy Provisioning (COPS-PR)Current
March 2001
- RFC 2621RADIUS Accounting Server MIBObsoleted
June 1999
- RFC 2620RADIUS Accounting Client MIBObsoleted
June 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?