Dismiss
IP.com applications will be updated on Sunday, March 5, from 11 am to 2 pm ET, to add new functionality and content. You may experience brief service interruptions during this period. We apologize for any inconvenience.
Browse Prior Art Database

Directory Server Monitoring MIB (RFC2605)

IP.com Disclosure Number: IPCOM000003192D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 22 page(s) / 45K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Mansfield: AUTHOR [+2]

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1567, "X.500 Directory Monitoring MIB". This memo extends that specification to a more generic MIB for monitoring one or more directory servers each of which may support multiple access protocols. The MIB defined in this memo will be used in conjunction with the NETWORK-SERVICES-MIB [19] for monitoring Directory Servers.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group G. Mansfield

Request for Comments: 2605 Cyber Solutions Inc.

Obsoletes: 1567 S. Kille

Category: Standards Track MessagingDirect Ltd.

June 1999

Directory Server 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.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This memo defines a portion of the Management Information Base (MIB)

for use with network management protocols in the Internet community.

This memo obsoletes RFC 1567, "X.500 Directory Monitoring MIB". This

memo extends that specification to a more generic MIB for monitoring

one or more directory servers each of which may support multiple

access protocols. The MIB defined in this memo will be used in

conjunction with the NETWORK-SERVICES-MIB [19] for monitoring

Directory Servers.

Table of Contents

1. The SNMP Network Management Framework ....................... 2

2. The Directory Services Model ................................ 3

3. MIB Model for Directory Management .......................... 4

4. MIB design .................................................. 5

5. The Directory Server Monitoring MIB ......................... 5

6. Intellectual Property .......................................22

7. Changes from RFC1567 ........................................22

8. Acknowledgements ............................................22

9. References ..................................................23

Security Considerations .........................................24

Authors' Addresses ..............................................25

Full Copyright Statement ........................................26

1. The SNMP Network Management Framework

The SNMP Network Management Framework presently consists of five

major components:

o An overall architecture, described in RFC 2571 [1].

o Mechanisms for describing and naming objects and events for the

purpose of management. The first version of this Structure of

Management Information (SMI) is called SMIv1 and described in

STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The

second version, called SMIv2, is described in STD 58, RFC 2578

[5], RFC 2579 [6] and RFC 2580 [7].

o Message protocols for transferring management information. The

first version of the SNMP message protocol is called SNMPv1 and

described in STD 15, RFC 1157 [8]. A secon...