RFC 3197 on Applicability Statement - DNS MIB Extensions
RFC Editor <rfc-ed@ISI.EDU> Tue, 27 November 2001 23:42 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29682; Tue, 27 Nov 2001 18:42:57 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA19476 for ietf-123-outbound.10@ietf.org; Tue, 27 Nov 2001 18:35:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA19447 for <all-ietf@loki.ietf.org>; Tue, 27 Nov 2001 18:27:59 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29398 for <all-ietf@ietf.org>; Tue, 27 Nov 2001 18:27:54 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id fARNRvH01788; Tue, 27 Nov 2001 15:27:57 -0800 (PST)
Message-Id: <200111272327.fARNRvH01788@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3197 on Applicability Statement - DNS MIB Extensions
Cc: rfc-ed@ISI.EDU, namedroppers@nic.ddn.mil.cnri.reston.va
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 27 Nov 2001 15:27:56 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3197 Title: Applicability Statement for DNS MIB Extensions Author(s): R. Austein Status: Informational Date: November 2001 Mailbox: sra@hactrn.net Pages: 5 Characters: 8610 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-dnsmib-historical-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3197.txt 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 document is a product of the DNS Extensions Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.