This Working Group did not meet
NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.
Last Modifield: 05/03/2002
During the past several years, there have been a number of activities aimed at incorporating security and other improvements to SNMP. Unfortunately, strongly held differences on how to incorporate these improvements into SNMP prevented the SNMPV2 Working Group from coming to closure on a single approach. As a result, two different approaches (commonly called V2u and V2*) have emerged.
The Security and Administrative Framework Evolution for SNMP Advisory Team (the Advisory Team) was formed to provide a single recommended approach for SNMP evolution. The technical starting point for this Working Group will be the recommended approach provided by the Advisory Team.
This approach provides for the convergence of concepts and technical elements of V2u and V2*. The SNMPv3 Working Group is not starting new work and will use as many concepts, technical elements and documentation as practical from the V2u and V2* activities. Previous delays in providing a single standard for the next generation of SNMP core functions dictate that the Working Group move forward as quickly as possible to document and publish Internet Drafts and RFC's. To this end, the Working Group will make use of as much existing documentation as practical. Additionally, functional changes beyond those needed to provide a single approach will be strongly discouraged.
Timely completion of a single approach for SNMPv3 is crucial for the continued success of SNMP. Recognizing the need for prompt completion, the following objectives are provided to the Working Group:
- accommodate the wide range of operational environments with differing management demands;
- facilitate the need to transition from previous, multiple protocols to SNMPv3;
- facilitate the ease of setup and maintenance activities.
Note: SNMPv3 planned specifications:
SNMPv3 Modules and Interface Definitions SNMPv3 Message Processing and Control Module Specification SNMPv3 Security Model Module Specification SNMPv3 Local Processing Mosule Specification SNMPv3 Proxy Specification
| Done | Post first SNMPv3 Internet-Draft, Modules and Interface Definitions. | |
| Done | Working Group meeting at Memphis IETF to discuss SNMPv3 recommended approach, discuss Working Group Charter and the plan for completion. | |
| Done | Post revised SNMPv3 Modules and Interface Definitions Internet-Drafts. | |
| Done | Post initial SNMPv3 Message Processing and Control Module Internet-Draft. | |
| Done | Post initial SNMPv3 Security Model Module Internet-Draft. | |
| Done | Finalize SNMPV3 Modules and Interface Definitions Internet-Draft and review other I-Ds at Munich IETF. | |
| Done | Post revised SNMPv3 Local Processing Module Internet-Draft. | |
| Done | Post revised SNMPv3 Security Model Module Internet-Draft. | |
| Done | Post initial SNMPv3 Proxy Specification Internet-Draft. | |
| Done | Post revised SNMPv3 Message Processing and Control Module Internet-Draft. | |
| Done | Submit SNMPv3 Modules and Interface Definitions to IESG for consideration as a Proposed Standard. | |
| Done | All SNMPv3 specifications submitted to IESG for consideration as Proposed Standards. | |
| Done | Testing of interoperability between independent implementations of SNMPv3 core specifications. | |
| Done | Post the initial Internet Draft of the Intro document. | |
| Done | Post initial Internet Drafts for updating the SNMPv3 core specifications. | |
| Done | Post initial version of the Coexistence document as an Internet-Draft. | |
| Done | SNMPv3 Working Group Meeting at 42nd IETF. | |
| Done | Post revised version of the Intro document Internet-Draft. | |
| Done | Post revised version of the Coexistence document as an Internet-Draft. | |
| Done | Complete Working Group actions on revisions to core specifications and forward documents to the IESG for consideration as Draft Standard RFCs. |
| RFC | Status | Title |
|---|---|---|
| RFC2261 | PS | An Architecture for Describing SNMP Management Frameworks |
| RFC2262 | PS | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) |
| RFC2263 | PS | SNMPv3 Applications |
| RFC2265 | PS | View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
| RFC2264 | PS | User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) |
| RFC2272 | PS | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) |
| RFC2273 | PS | SNMPv3 Applications |
| RFC2271 | PS | An Architecture for Describing SNMP Management Frameworks |
| RFC2274 | PS | User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) |
| RFC2275 | PS | View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
| RFC2571 | DS | An Architecture for Describing SNMP Management Frameworks |
| RFC2572 | DS | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) |
| RFC2575 | DS | View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
| RFC2573 | DS | SNMPv3 Applications |
| RFC2570 | I | Introduction to Version 3 of the Internet standard Network Management Framework |
| RFC2574 | DS | User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) |
| RFC2576 | PS | Coexistence between SNMP versions |