idnits 2.17.1 draft-ietf-snmpv3-vacm-v2-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 STD 62 4 RFC 3415 6 Title: View-based Access Control Model (VACM) for the 7 Simple Network Management Protocol (SNMP) 8 Author(s): B. Wijnen, R. Presuhn, K. McCloghrie 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: bwijnen@lucent.com, randy_presuhn@bmc.com, 12 kzm@cisco.com 13 Pages: 39 14 Characters: 82046 15 Obsoletes: 2575 16 See Also: STD 62 18 I-D Tag: draft-ietf-snmpv3-vacm-v2-01.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3415.txt 22 This document describes the View-based Access Control Model (VACM) for 23 use in the Simple Network Management Protocol (SNMP) architecture. It 24 defines the Elements of Procedure for controlling access to management 25 information. This document also includes a Management Information 26 Base (MIB) for remotely managing the configuration parameters for the 27 View-based Access Control Model. This document obsoletes RFC 2575. 29 This document is a product of the SNMPv3 Working Group of the IETF. 31 This is now a Standard Protocol. 33 This document specifies an Internet standards track protocol for 34 the Internet community, and requests discussion and suggestions 35 for improvements. Please refer to the current edition of the 36 "Internet Official Protocol Standards" (STD 1) for the 37 standardization state and status of this protocol. Distribution 38 of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.