Skip to main content

Simple Network Management Protocol (SNMP) Applications

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3413.
Authors paul meyer , David B. Levi , Bob Stewart
Last updated 2020-01-21 (Latest revision 2001-11-27)
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3413 (Internet Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Randy Bush
IESG note Approved
Responsible: RFC Editor
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        STD 62
        RFC 3413
        Title:      Simple Network Management Protocol (SNMP)
        Author(s):  D. Levi, P. Meyer, B. Stewart
        Status:     Standards Track
        Date:       December 2002
        Pages:      74
        Characters: 153719
        Obsoletes:  2573
        See Also:   STD 62
        I-D Tag:    draft-ietf-snmpv3-appl-v3-01.txt


This document describes five types of Simple Network Management
Protocol (SNMP) applications which make use of an SNMP engine as
described in STD 62, RFC 3411.  The types of application described are
Command Generators, Command Responders, Notification Originators,
Notification Receivers, and Proxy Forwarders.

This document also defines Management Information Base (MIB) modules
for specifying targets of management operations, for notification
filtering, and for proxy forwarding.  This document obsoletes RFC

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

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.