A new Request for Comments is now available from the Network Information
Center in the online library at NIC.DDN.MIL.

	RFC 1215:

        Title:      A Convention for Defining Traps
                    for use with the SNMP
       	Author:     M. Rose, Editor
	Mailbox:    mrose@psi.com
	Pages:      9      
	Characters: 19,336 
	Updates/Obsoletes:  none

		pathname: RFC:RFC1215.TXT


This memo suggests a straight-forward approach towards defining traps
used with the SNMP.  Readers should note that the use of traps in the
Internet-standard network management framework is controversial.  As
such, this memo is being put forward for information purposes.
Network management practitioners who employ traps are encouraged to
make use of this document.  Practitioners who do not employ traps can
safely ignore this document.

This memo provides information for the Internet community.  It does
not specify an Internet standard.  Distribution of this memo is
unlimited.

RFCs can be obtained via FTP from NIC.DDN.MIL, NIS.NSF.NET, or
NISC.JVNC.NET.

RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT (where "nnnn" refers to the number of the RFC).  Login
with FTP, username "anonymous" and password "guest".

The NIC also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to SERVICE@NIC.DDN.MIL and in the
subject field of the message indicate the RFC number, as in "Subject:
RFC nnnn".

To obtain RFCs from NIS.NSF.NET via FTP, login with username
"anonymous" and password "guest"; then connect to the RFC directory
("cd RFC").  The file name is of the form RFCnnnn.TXT-1 (where "nnnn"
refers to the number of the RFC).

The NIS also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank.  The first line of the text of
the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by
the RFC number.

RFCs can also be obtained via FTP from NISC.JVNC.NET, with the
pathname rfc/RFCnnnn.TXT.v.Z (where "nnnn" refers to the number of the
RFC and "v" refers to the version number of the RFC).  There are a
number of RFCs available in postscript format.  Those RFCs have
modifiers of .PS instead of .TXT.  Login with FTP, username
"anonymous" and your e-mail address as your password.

JvNCnet also provides a mail service for those sites which cannot use
FTP.  Address the request to NISC@JVNC.NET and in the subject field of
the message indicate the RFC number, as in "Subject: RFC nnnn".

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute