RFC 3197: Applicability Statement for DNS MIB Extensions
In plain English — editorial summary, not part of the RFC
This document explains why, after more than six years as proposed standards, the DNS Server and Resolver MIB extensions were never deployed, and recommends retiring these MIB extensions by moving them to Historical status. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3197
- Published
- November 2001
- Authors
- R. Austein
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1612DNS Resolver MIB ExtensionsCurrent
May 1994
- RFC 1611DNS Server MIB ExtensionsCurrent
May 1994
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 3090DNS Security Extension Clarification on Zone StatusObsoleted
March 2001
- RFC 2845Secret Key Transaction Authentication for DNS (TSIG)Obsoleted
May 2000
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 2667IP Tunnel MIBObsoleted
August 1999
- RFC 2606Reserved Top Level DNS NamesUpdated
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?