A new Request for Comments is now available in online RFC libraries.


        RFC 2263:

        Title:      SNMPv3 Applications
	Author(s):  D. Levi, P. Meyer, B. Stewart
        Status:     Proposed Standard
	Date:       January 1998
        Mailbox:    levi@snmp.com, paul_meyer@securecomputing.com,
		    bstewart@cisco.com
        Pages:      70
        Characters: 143493
        Updates/Obsoletes: None

        URL:        ftp://ds.internic.net/rfc/rfc2263.txt


This memo describes five types of SNMP applications which make use of
an SNMP engine as described in [RFC2261].  The types of application
described are Command Generators, Command Responders, Notification
Originators, Notification Receivers, and Proxy Forwarders. This memo
also defines MIB modules for specifying targets of management
operations, for notification filtering, and for proxy forwarding.

This document is a product of the SNMPv 3 Working Group of the IETF.

This is now a Proposed 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@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute