RFC 3415: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3415
- Published
- December 2002
- Authors
- B. Wijnen; R. Presuhn; K. McCloghrie
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 39
- Also known as
- STD62
- Obsoletes:
- RFC 2575
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2265 (1998)
- RFC 2275 (1998)
- RFC 2575 (1999)
- RFC 3415 (2002)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3414User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)Updated
December 2002
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?