RFC 2265 on VACM for SNMPv3

[RFC Editor <rfc-ed at ISI.EDU>]

A new Request for Comments is now available in online RFC libraries.


        RFC 2265:

        Title:      View-based Access Control Model (VACM) for the
                    Simple Network Management Protocol (SNMP)
	Author(s):  B. Wijnen, R. Presuhn, K. McCloghrie
        Status:     Proposed Standard
	Date:       January 1998
        Mailbox:    wijnen at vnet.ibm.com, rpresuhn at bmc.com,
		    kzm at cisco.com
        Pages:      36
        Characters: 77807
        Updates/Obsoletes: None

        URL:        ftp://ds.internic.net/rfc/rfc2265.txt

This document describes the View-based Access Control Model for use
in the SNMP architecture [RFC2261].  It defines the Elements of
Procedure for controlling access to management information.  This
document also includes a MIB for remotely managing the configuration
parameters for the View-based Access Control Model.

This document is a product of the SNMPv 3 Working Group of the IETF.

This is now a Proposed 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at ISI.EDU
        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 admin at DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

<ftp://ds.internic.net/rfc/rfc2265.txt>