Extending X.500 Directory Functionality

CAL@SLACVM.EARN Thu, 30 April 1992 22:07 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa06241; 30 Apr 92 18:07 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa14326; 30 Apr 92 18:12 EDT
Received: from bells.cs.ucl.ac.uk by NRI.Reston.VA.US id aa14322; 30 Apr 92 18:12 EDT
Via: earn-relay.ac.uk; Thu, 30 Apr 1992 21:09:36 +0100
Received: from UKACRL by UK.AC.RL.IB (Mailer R2.07) with BSMTP id 9834; Thu, 30 Apr 92 21:08:58 BST
Received: from SLACVM.SLAC.STANFORD.EDU by UKACRL.BITNET (Mailer R2.07) with BSMTP id 7703; Thu, 30 Apr 92 21:08:53 BST
Received: by SLACVM (Mailer R2.08 R208004) id 8321; Thu, 30 Apr 92 13:08:34 PS
Date: Thu, 30 Apr 1992 13:08:00 -0800
To: osi-ds@cs.ucl.ac.uk
Subject: Extending X.500 Directory Functionality
Message-ID: <9204301812.aa14322@NRI.Reston.VA.US>

 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
    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.    In addition,  I
 think I would have to modify  'whois.c' in the ISODE distribution
 kit to handle responses.  I am not sure even that would do it.  I
 do not have a  lot of time to do coding.   I  was really hoping I
 could simply add a new EDB file and make one or to quick configu-
 ration mods without modifying any code.  Is that possible?
 Thanks .... Connie Logg
  Stanford Linear Accelerator Center