Re: Using X.500 to determine presentationAddresses Mon, 17 May 1993 11:29 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa21659; 17 May 93 7:29 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa21655; 17 May 93 7:29 EDT
Received: from by CNRI.Reston.VA.US id aa28750; 17 May 93 7:29 EDT
Via:; Mon, 17 May 1993 12:23:14 +0100
Received: from by via UKIP with SMTP (PP) id <>; Mon, 17 May 1993 12:22:18 +0100
Received: from by via EUnet with SMTP (PP) id <>; Mon, 17 May 1993 12:22:07 +0100
Received: from by via ITEnet with SMTP; id AA05869 (5.65c/FORTH-ICS-3.0-MHS-7.0); Mon, 17 May 1993 14:25:48 +0300
Date: Mon, 17 May 93 14:19:43 +0300
Message-Id: <>
Organization: FORTH - ICS, P.O.Box 1385, Heraklio, Crete, Greece 711 10 tel: +30(81)221171, 229368,02 fax: +30(81)229342,3 tlx: 262389 CCI
Subject: Re: Using X.500 to determine presentationAddresses
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US


>   We have been investigating the use of X.500 in the Network, Systems and
>Applications management frameworks for the last couple of years.
>For those who are not aware yet, I would like to refer to our paper that was
>presented at the 3rd International Symposium on Integrated Network Management,
>San Fransisco, CA, April 1993, pp. 149-160, which discusses our experience of
>using the X.500 Directory Service in the network management framework.

I got your paper two weeks ago and I have read it. It is really interesting!
But I didn't find a lot of work related to the global naming of the network 
elements therein. Ok, I understand that this was not your objective, but 
I suppose you have thought about a global naming schema for NEs. 
Anyone who deals with such an issue as "Integrating the X.500 in the Network
Management Framework" sooner or later asks for a way to name a NE in the DIT!

Although your prototype Quipu Objects: csdDomain and csdMachine are enough
for your experiment (I have defined my own objects for my prototype, too)
a more standardized schema is needed. Any ideas on such a schema?