idnits 2.17.1 draft-ietf-snmpv3-arch-v2-02.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 3411 6 Title: An Architecture for Describing Simple Network 7 Management Protocol (SNMP) Management Frameworks 8 Author(s): D. Harrington, R. Presuhn, B. Wijnen 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: dbh@enterasys.com, randy_presuhn@bmc.com, 12 bwijnen@lucent.com 13 Pages: 64 14 Characters: 140096 15 Obsoletes: 2571 16 See Also: STD 62 18 I-D Tag: draft-ietf-snmpv3-arch-v2-02.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3411.txt 22 This document describes an architecture for describing Simple Network 23 Management Protocol (SNMP) Management Frameworks. The architecture is 24 designed to be modular to allow the evolution of the SNMP protocol 25 standards over time. The major portions of the architecture are an 26 SNMP engine containing a Message Processing Subsystem, a Security 27 Subsystem and an Access Control Subsystem, and possibly multiple SNMP 28 applications which provide specific functional processing of 29 management data. This document obsoletes RFC 2571. 31 This document is a product of the SNMPv3 Working Group of the IETF. 33 This is now a Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.