RFC 2575 on VACM for SNMP

RFC Editor <rfc-ed@ISI.EDU> Wed, 12 May 1999 16:35 UTC

Message-Id: <199905121551.IAA13678@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2575 on VACM for SNMP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 12 May 1999 08:51:16 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2575: 

        Title:	    View-based Access Control Model (VACM) for the
                    Simple Network Management Protocol (SNMP)
	Author(s):  B. Wijnen, R. Presuhn, K. McCloghrie
        Status:     Draft Standard
	Date:       April 1999
        Mailbox:    wijnen@vnet.ibm.com, randy_presuhn@bmc.com,
		    kzm@cisco.com
        Pages:      38
        Characters: 79642
        Obsoletes:  2275
        I-D Tag:    draft-ietf-snmpv3-vacm-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2575.txt


This document describes the View-based Access Control Model for use in
the SNMP architecture [RFC2571].  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 is now a Draft Standard Protocol.
 
This document is a product of the SNMP Version 3 Working Group of the
IETF.
 
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.


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://ftp.isi.edu/in-notes/rfc2575.txt"><ftp://ftp.isi.edu/in-notes/rfc2575.txt>

RFC 2575 on VACM for SNMP RFC Editor