Protocol Action: DNS Server MIB Extensions to Historic Standard

The IESG <> Thu, 11 October 2001 22:16 UTC

Received: from (loki []) by (8.9.1a/8.9.1a) with ESMTP id SAA27125; Thu, 11 Oct 2001 18:16:43 -0400 (EDT)
Received: (from adm@localhost) by (8.9.1b+Sun/8.9.1) id SAA07324 for; Thu, 11 Oct 2001 18:05:01 -0400 (EDT)
Received: from ( []) by (8.9.1b+Sun/8.9.1) with ESMTP id RAA07172 for <>; Thu, 11 Oct 2001 17:42:07 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost []) by (8.9.1a/8.9.1a) with ESMTP id RAA26244; Thu, 11 Oct 2001 17:42:04 -0400 (EDT)
Message-Id: <>
To: IETF-Announce:;
Cc: RFC Editor <>
Cc: Internet Architecture Board <>
From: The IESG <>
Subject: Protocol Action: DNS Server MIB Extensions to Historic Standard
Date: Thu, 11 Oct 2001 17:42:04 -0400

The IESG has approved reclassifying the following RFCs as Historic

RFC1611 DNS Server MIB Extensions
RFC1612 DNS Resolver MIB Extensions

In the same action, the IESG approved publication of Applicability
Statement for DNS MIB Extensions <draft-ietf-dnsext-dnsmib-historical-00.txt>
as an Informational RFC.

This document is the product of the DNS Extensions Working Group.

The contact persons are Erik Nordmark and Thomas Narten.

Technical Summary
   The document states the reasons for moving RFC 1611 and RFC 1612 to

   More than six years after the DNS Server and Resolver MIB extensions
   became proposed standards, there still has not been any significant
   deployment of these MIB extensions.  This note examines the reasons
   why these MIB extensions were never deployed, and recommends retiring
   these MIB extensions by moving them to Historical status.

Working Group Summary

   There was consensus in the working group to reclassify the DNS MIB
   documents.  Interested parties where encouraged to form a design team
   to produce more usable MIBs for DNS and bring them to the DNSEXT WG
   when they are ready for review.

Protocol Quality

   This document has been reviewed for the IESG by Erik Nordmark.

Note to RFC Editor:

Please replace the Security Considerations section in
draft-ietf-dnsext-dnsmib-historical-00.txt with the following text:

   Re-classifying an existing MIB document from Proposed Std
   to Historic does not have any negative impact on security for
   the Internet.