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


        RFC 1902:

        Title:      Structure of Management Information
                    for Version 2 of the
                    Simple Network Management Protocol (SNMPv2)
        Author:     SNMPv2 Working Group, J. Case, K. McCloghrie, 
                    M. Rose & S. Waldbusser
        Date:       January 1996
        Mailbox:    case@snmp.com, kzm@cisco.com,
                    mrose@dbc.mtview.ca.us, stevew@uni.ins.com
        Pages:      40
        Characters: 77,453
        Obsoletes:  1442

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


A management system contains: several (potentially many) nodes, each
with a processing entity, termed an agent, which has access to
management instrumentation; at least one management station; and, a
management protocol, used to convey management information between the
agents and management stations.  Operations of the protocol are
carried out under an administrative framework which defines
authentication, authorization, access control, and privacy policies.
Management stations execute management applications which monitor and
control managed elements.  Managed elements are devices such as hosts,
routers, terminal servers, etc., which are monitored and controlled
via access to their management information.  Management information is
viewed as a collection of managed objects, residing in a virtual
information store, termed the Management Information Base (MIB).
Collections of related objects are defined in MIB modules.  These
modules are written using an adapted subset of OSI's Abstract Syntax
Notation One (ASN.1) [1].  It is the purpose of this document, the
Structure of Management Information (SMI), to define that adapted
subset, and to assign a set of associated administrative values.  The
SMI is divided into three parts: module definitions, object
definitions, and, notification definitions.  This RFC is the product
of the SNMP Version 2 Working Group of the IETF.

This is now a Draft 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@CNRI.RESTON.VA.US.  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
USC/Information Sciences Institute