View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3415.
|Authors||Keith McCloghrie, Bert Wijnen , Randy Presuhn|
|Last updated||2020-01-21 (Latest revision 2001-11-30)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 3415 (Internet Standard)|
|Responsible AD||Randy Bush|
Responsible: RFC Editor
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. STD 62 RFC 3415 Title: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) Author(s): B. Wijnen, R. Presuhn, K. McCloghrie Status: Standards Track Date: December 2002 Mailbox: email@example.com, firstname.lastname@example.org, email@example.com Pages: 39 Characters: 82046 Obsoletes: 2575 See Also: STD 62 I-D Tag: draft-ietf-snmpv3-vacm-v2-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3415.txt This document describes the View-based Access Control Model (VACM) for use in the Simple Network Management Protocol (SNMP) architecture. It defines the Elements of Procedure for controlling access to management information. This document also includes a Management Information Base (MIB) for remotely managing the configuration parameters for the View-based Access Control Model. This document obsoletes RFC 2575. This document is a product of the SNMPv3 Working Group of the IETF. This is now a Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. 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.