SNMPv1 and SNMPv2c to HISTORIC
"C. M. Heard" <heard@pobox.com> Fri, 18 January 2002 20:30 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25964 for ietf-outbound.10@ietf.org; Fri, 18 Jan 2002 15:30:02 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25703 for ietf-mainout; Fri, 18 Jan 2002 15:20:08 -0500 (EST)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25698 for <ietf@ietf.org>; Fri, 18 Jan 2002 15:20:02 -0500 (EST)
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA28694 for <ietf@ietf.org>; Fri, 18 Jan 2002 12:20:04 -0800 (envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Fri, 18 Jan 2002 12:20:04 -0800
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
Subject: SNMPv1 and SNMPv2c to HISTORIC
Message-ID: <Pine.LNX.4.10.10201181213490.25103-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf@ietf.org
Precedence: bulk
X-Loop: ietf@ietf.org
Folks who scan only the titles of last call announcements might want to note that the the actions proposed below will not only elevate SNMPv3 to Standard but will also reclassify SNMPv1 and SNMPv2c as Historic. //cmh ---------- Forwarded message ---------- Date: Thu, 17 Jan 2002 09:51:52 -0500 From: The IESG <iesg-secretary@ietf.org> Reply-To: iesg@ietf.org To: IETF-Announce: ; Cc: snmpv3@lists.tislabs.com Subject: Last Call: An Architecture for Describing SNMP Management Frameworks to Standard The IESG has received a request from the SNMP Version 3 Working Group to consider publication of the following Internet-Drafts as Standards: o An Architecture for Describing SNMP Management Frameworks <draft-ietf-snmpv3-arch-v2-02.txt> as a Standard. o Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) <draft-ietf-snmpv3-mpd-v2-02.txt> o SNMP Applications <draft-ietf-snmpv3-appl-v3-01.txt> o User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) <draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt> o View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) <draft-ietf-snmpv3-vacm-v2-01.txt> These are editorial updates to RFCs 2571-2575 respectfully. As part of this action, RFC1157 (A Simple Network Management Protocol (SNMP)) and RFC1901 (Introduction to Community-based SNMPv2) will be reclassified as Historic. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by January 31, 2002. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-arch-v2-02.txt http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-mpd-v2-02.txt http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-appl-v3-01.txt http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt http://www.ietf.org/internet-drafts/draft-ietf-snmpv3-vacm-v2-01.txt
- SNMPv1 and SNMPv2c to HISTORIC C. M. Heard