New Request for Comments are now available in online RFC libraries:


        RFC 1351:

        Title:      SNMP Administrative Model
        Author:     J. Davin, J. Galvin, & K. McCloghrie
        Mailbox:    jrd@ptt.lcs.mit.edu, galvin@tis.com, kzm@hls.com
        Pages:      35
        Characters: 80,721
        Obsoletes/Updates: none

This memo presents an elaboration of the SNMP administrative model set
forth in RFC 1157.  This model provides a unified conceptual basis for
administering SNMP protocol entities to support authentication and
integrity, privacy, access control, and the cooperation of multiple
protocol entities.  This RFC is the product of the SNMP Security
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an IAB standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "IAB
Official Protocol Standards" 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@NRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, or NIC.DDN.MIL.

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 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
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute