A new Request for Comments is now available in online RFC libraries. STD 62 RFC 3412 Title: Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) Author(s): J. Case, D. Harrington, R. Presuhn, B. Wijnen Status: Standards Track Date: December 2002 Mailbox: case@snmp.com, dbh@enterasys.com, randy_presuhn@bmc.com, bwijnen@lucent.com Pages: 43 Characters: 95710 Obsoletes: 2572 See Also: STD 62 I-D Tag: draft-ietf-snmpv3-mpd-v2-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3412.txt This document describes the Message Processing and Dispatching for Simple Network Management Protocol (SNMP) messages within the SNMP architecture. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. This document obsoletes RFC 2572. This document is a product of the SNMPv3 Working Group of the IETF. This is now a 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@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.