FYI - buried below is the IESG agreeing that SNMPv1 and SNMPv2 will
reclassified as Historic (that is, REMOVED from the 'standards-track')
as part of the advancement of SNMPv3 to (full) Standard status.
- Ira McDonald
PS - Ron Bergman agrees with me that there is probably no printer
in the universe that CURRENTLY implements SNMPv3. Anyone planning
to do so? This de-certification of SNMPv1 strikes me as a problem
for vendors of non-network-infrastructure network-connected boxes.
From: The IESG [mailto:iesg-secretary at ietf.org]
Sent: Thursday, August 15, 2002 2:40 PM
To: IETF-Announce; @tislabs.com
Cc: RFC Editor; Internet Architecture Board; snmpv3 at lists.tislabs.com
Subject: Document Action: Introduction to Version 3 of the
Internet-standard Network Management Framework to Informational
The IESG has approved the internet draft Introduction to Version 3 of
the Internet-Standard Management Framework
<draft-ietf-snmpv3-rfc2570bis-03.txt> as an Informational RFC.
The IESG also agrees with the recommendation to reclassify RFCs 1157,
1441, 1901, 1909 and 1910 as Historic and has approved this
This document is the product of the SNMPv3 Working Group. The IESG
contact persons are Randy Bush and Bert Wijnen.
This document is an introduction to the third version of the
Internet-Standard Management Framework, termed the SNMP version 3
Management Framework (SNMPv3).
It describes the relationship between the SNMP version 3 (SNMPv3)
specifications and the specifications of the SNMP version 1
(SNMPv1) Management Framework, the SNMP version 2 (SNMPv2)
Management Framework, and the Community-based Administrative
Framework for SNMPv2.
It also provides a roadmap to the multiple documents which contain
the relevant specifications.
The document further recommends reclassification of RFCs 1157,
1441, 1901, 1909 and 1910 as Historic and explains why.
Working Group Summary
The Working Group reached consensus on this document and its
Bert Wijnen and Randy Bush reviewed the specification for the IESG.
Note to RFC Editor:
Please add the following to the end of section 7.8:
Work is underway to specify how AES is to be used within the
User-based Security Model (USM). This will be a separate