Re: Extending X.500 Directory Functionality

Thomas Johannsen <> Fri, 01 May 1992 18:16 UTC

Received: from by ietf.NRI.Reston.VA.US id aa02240; 1 May 92 14:16 EDT
Received: from by NRI.Reston.VA.US id aa02852; 1 May 92 14:21 EDT
Received: from by NRI.Reston.VA.US id aa02847; 1 May 92 14:21 EDT
Via:; Fri, 1 May 1992 14:25:23 +0100
Received: from by with Internet SMTP id <>; Fri, 1 May 1992 10:51:55 +0100
Received: from by vax.NSFnet-Relay.AC.UK via NSFnet with SMTP id aa21156; 1 May 92 6:32 BST
Received: from by (5.65+1.6W/2.8Wb-jp-gate/1.2) with SMTP id AA18648; Fri, 1 May 92 14:44:17 JST
Received: from ([]) by (4.1/2.7W) id AA27722; Fri, 1 May 92 14:44:12 JST
Received: from by (4.0/6.4J.6-92/2) id AA05155; Fri, 1 May 92 14:44:08 JST
Received: by (4.1/6.4J.6-91/1/29) id AA01034; Fri, 1 May 92 14:44:07 JST
Date: Fri, 01 May 1992 14:44:07 -0000
From: Thomas Johannsen <>
Return-Path: <>
Message-Id: <>
Subject: Re: Extending X.500 Directory Functionality
Sender: thomas <>

(Sorry, if get this twice. The first mail bounced somewhere.)

> From Fri May  1 07:15:35 1992
> From: CAL@slacvm.earn

>  I having been looking into  putting some network information into
>  my X.500 directory.  In particular I would like to have directory
>  entries which contain a nodename,  ethernet address,  IP address,
>  subnet information,  etc.,  and allow users to inquire via 'WHOIS
>  node,nodename@WP' (or  the equivalent)   on any  system for  that
>  information.

There is already some development going on in this direction. The thing I
know best about is Soft Pages Project, which is intended to include network
configuration information (nodes with Domain Name, IP-address, ...; lines
with certain properties) and information about documents stored at
(Internet-) nodes. If you're interested, there is a document available by
anonymous ftp ( and *.txt). 

>     It seems like a formidable task.  Is there some short cut that
>  I am missing? I certainly have no problem formatting the informa-
>  tion into a flat file for an EDB.   But I don't know what defined
>  fields are available  to hold the information.   

I think the problem is not introducing new object classes and attributes but
to find a proper place within the Directory to store network information.
Probably you are aware of the @o=Internet entry. While one method is keeping
all nodes there (with domains as ou's?) the other is to hold nodes "near"
the organization they belong. This has to be discussed further. Soft Pages
is using both methods at the moment (i.e. hybrid).

Yeong at PSI has done some work in this direction, too.

>  Thanks .... Connie Logg
>   Stanford Linear Accelerator Center



|   Thomas Johannsen                     Internet:   | 
|   AIC Systems Lab.                     BITNET: JOHANNSE at DDDTU1   | 
|   Sendai (Japan)      Tel: +81 22 279 3310   Fax: +81 22 279 3640   |