Directory Management

"Ella P. Gardner" <> Mon, 25 January 1993 20:18 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa16872; 25 Jan 93 15:18 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16868; 25 Jan 93 15:18 EST
Received: from by CNRI.Reston.VA.US id aa24351; 25 Jan 93 15:20 EST
Received: from by with local SMTP id <>; Mon, 25 Jan 1993 18:46:04 +0000
Received: from by with Internet SMTP id <>; Mon, 25 Jan 1993 18:45:55 +0000
Return-Path: <>
Received: by (5.61/SMI-2.2) id AA21598; Mon, 25 Jan 93 13:45:45 -0500
Date: Mon, 25 Jan 93 13:45:45 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Ella P. Gardner" <>
Full-Name: Ella P. Gardner
Message-Id: <>
Subject: Directory Management

25 January 1993

As you all know, there's a call for contributions on the use of OSI
Systems Mangement for administration of the Directory, ISO/IEC JTC 1/SC
21 N7024. In case you don't have N7024 handy, I've copied it at the end
of this message.

At MITRE, we're very interested in seeing this work progress for
ourselves as well as for the Defense Message System (DMS).  This year,
we plan to use the Generic Management System (GMS) to write an agent for
QUIPU and to define a few managed objects for a prototype.

We would like to hear from anyone who:

-has defined managed objects for Directory and is willing to share some

-anyone who is using GMS 

-anyone who plans to participate in the Directory Standards arena to
address systems management of the Directory.

Thanks very much!
Ella Gardner


National bodies are requested to consider the Use of OSI Systems
Management for Administration of the Directory, and to submit
contributions to the next ISO/IEC SC 21/WG4 meeting on the Directory
(Yokohama, May 1993). National Bodies are requested to specifically
address the following areas with contributions:

1) Requirements for management of Directory systems, including:

-Performance Management
-Accounting Management
-Fault Management
-Configuration Management
-Security Management

2) Consideration of various types of information used for administration
of the Directory, such as information carried with Directory operations,
information carried outside Directory operations and possibly some
information which needs to be carried in both (i.e., accounting
information carried to a Director user as well as to a management

3) Identification of other objects and associated information required for
purposes of administration of the Directory;

4) Proposed managed object definitions for identified objects; 

5) Consideration and identification of the most appropriate mechanisms
and protocols to be used to provide the various administration services
for the Directory. For example, Common Management Information Protocol
(CMIP) may be appropriate for some aspects of Directory administration,
while the Directory protocols themselves may be appropriate for others.