idnits 2.17.1 draft-ietf-snmpv3-mpd-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 3412 6 Title: Message Processing and Dispatching for the Simple 7 Network Management Protocol (SNMP) 8 Author(s): J. Case, D. Harrington, R. Presuhn, B. Wijnen 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: case@snmp.com, dbh@enterasys.com, 12 randy_presuhn@bmc.com, bwijnen@lucent.com 13 Pages: 43 14 Characters: 95710 15 Obsoletes: 2572 16 See Also: STD 62 18 I-D Tag: draft-ietf-snmpv3-mpd-v2-02.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3412.txt 22 This document describes the Message Processing and Dispatching for 23 Simple Network Management Protocol (SNMP) messages within the SNMP 24 architecture. It defines the procedures for dispatching potentially 25 multiple versions of SNMP messages to the proper SNMP Message 26 Processing Models, and for dispatching PDUs to SNMP applications. 27 This document also describes one Message Processing Model - the SNMPv3 28 Message Processing Model. This document obsoletes RFC 2572. 30 This document is a product of the SNMPv3 Working Group of the IETF. 32 This is now a Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.