X.500 Directory Monitoring MIB
RFC 1567

 
Document Type RFC - Proposed Standard (January 1994; No errata)
Obsoleted by RFC 2605
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1567 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       G. Mansfield
Request for Comments: 1567                        AIC Systems Laboratory
Category: Standards Track                                       S. Kille
                                                        ISODE Consortium
                                                            January 1994

                     X.500 Directory Monitoring MIB

Status of this Memo

   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.

Abstract

   This document defines a portion of the Management Information Base
   (MIB).  It defines the MIB for monitoring Directory System Agents
   (DSA), a component of the OSI Directory. This MIB will be used in
   conjunction with the APPLICATION-MIB for monitoring DSAs.

Table of Contents

   1.  The SNMPv2 Network Management Framework ....................... 1
   2.  MIB Model for DSA  Management ................................. 2
   3.  The DSA functions and operations .............................. 2
   4.  MIB design .................................................... 3
   5.  The Directory Monitoring MIB .................................. 3
   6.  Acknowledgements ..............................................17
   7.  References ....................................................17
   Security Considerations ...........................................18
   Authors' Addresses ................................................18

1.  The SNMPv2 Network Management Framework

   The major components of the SNMPv2 Network Management framework  are
   described in the documents listed below.

      o RFC 1442 [1] defines the Structure of Management Information
        (SMI), the mechanisms used for describing and naming objects
        for the purpose of management.

      o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
        objects (MO) for the Internet suite of protocols.

Mansfield & Kille                                               [Page 1]
RFC 1567             X.500 Directory Monitoring MIB         January 1994

      o RFC 1445 [3] defines the administrative and other
        architectural aspects of the management framework.

      o RFC 1448 [4] defines the protocol used for network access to
        managed objects.

   The framework is adaptable/extensible by defining new MIBs to suit
   the requirements of specific applications/protocols/situations.

   Managed objects are accessed via a virtual information store, the
   MIB.  Objects in the MIB are defined using the subset of Abstract
   Syntax Notation One (ASN.1) defined in the SMI. In particular, each
   object type is named by an OBJECT IDENTIFIER, which is an
   administratively assigned name. The object type together with an
   object instance serves to uniquely identify a specific instantiation
   of the object. For human convenience, often a textual string, termed
   the descriptor, is used to refer to the object type.

2.  MIB Model for DSA Management

   A DSA-manager may wish to monitor several aspects of the operational
   DSA.  He/she may want to know the process related aspects-the
   resource utilization of the operational DSA; the network service
   related aspects e.g., inbound-associations, outbound-associations,
   operational status, and finally the information specific to the DSA
   application - its operations and performance.

   The MIB defined in this document covers the portion which is specific
   to the DSA-application. The network service related part of the MIB,
   and the host-resources related part of the MIB, as well other parts
   of interest to a Manager monitoring the DSA-application, are covered
   in separate documents [6] [7].

3.  The DSA functions and operations

   The Directory System Agent [DSA], a component of the OSI-Directory
   [5] [9], is an application process. It provides access to the
   Directory Information Base [DIB] to Directory User Agents [DUA]
   and/or other DSAs.  Functionally , a User [DUA] and the Directory are
   bound together for a period of time at an access point to the
   Directory [DSA].  A DSA may use information stored in its local
   database or interact with (chain the request to) other DSAs to
   service requirements.  Alternatively, a DSA may return a reference to
   another DSA.

   The local database of a DSA consists of the part of the DIT that is
   mastered by the DSA, the part of the DIT for which it keeps slave
   copies and cached information that is gathered during the operation
Show full document text