RFC 2575 (rfc2575) - Page 2 of 38

View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 2575                     VACM for SNMP                    April 1999


   4.  Definitions                                             10
   5.  Intellectual Property                                   27
   6.  Acknowledgements                                        28
   7.  Security Considerations                                 29
   7.1.  Recommended Practices                                 29
   7.2.  Defining Groups                                       30
   7.3.  Conformance                                           30
   7.4.  Access to the SNMP-VIEW-BASED-ACM-MIB                 30
   8.  References                                              31
   9.  Editors' Addresses                                      32
   A.1.  Installation Parameters                               33
   B.  Change Log                                              37
   C.  Full Copyright Statement                                38


1.  Introduction

   The Architecture for describing Internet Management Frameworks
   [RFC 2571] describes that an SNMP engine is composed of:

     1) a Dispatcher
     2) a Message Processing Subsystem,
     3) a Security Subsystem, and
     4) an Access Control Subsystem.

   Applications make use of the services of these subsystems.

   It is important to understand the SNMP architecture and its
   terminology to understand where the View-based Access Control Model
   described in this document fits into the architecture and interacts
   with other subsystems within the architecture.  The reader is
   expected to have read and understood the description and terminology
   of the SNMP architecture, as defined in [RFC 2571].

   The Access Control Subsystem of an SNMP engine has the responsibility
   for checking whether a specific type of access (read, write, notify)
   to a particular object (instance) is allowed.

   It is the purpose of this document to define a specific model of the
   Access Control Subsystem, designated the View-based Access Control
   Model. Note that this is not necessarily the only Access Control
   Model.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].





Wijnen, et al.              Standards Track