Re: Using X.500 to determine presentationAddresses

Peter Yee <> Fri, 07 May 1993 10:01 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa01213; 7 May 93 6:01 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01209; 7 May 93 6:01 EDT
Received: from by CNRI.Reston.VA.US id aa03618; 7 May 93 6:01 EDT
Received: from by with local SMTP id <>; Thu, 6 May 1993 22:10:22 +0100
Received: from by with Internet SMTP id <>; Thu, 6 May 1993 22:09:27 +0100
Received: from by with SMTP (PP); Thu, 6 May 1993 14:05:52 -0700
To: Edwards Reed <>
Subject: Re: Using X.500 to determine presentationAddresses
In-reply-to: Your message of "Thu, 06 May 1993 07:29:17 PDT." <>
Date: Thu, 06 May 1993 14:05:50 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Peter Yee <>
Message-ID: <9305070601.aa03618@CNRI.Reston.VA.US>

>Is your question directed principally at the location of such information
>in a well organized DIT, or at something else?  Have you found
>DASE adequate, otherwise, or are other semantics required?

The discussion came up, principally, around where to place in the information
in a well-organized DIT.  DASE is in adequate since it would require that our
host information be buried in amongst our user information and lead to poor
searching performance for both.

>I'd like to begin looking at placing my global, master NIS maps
>into the DIT - services, rpc, groups, etc... - with the plan
>to extract them at local sites for inclusion with local entries
>ala DCE.  Is that rational?

Not aware of the DCE plan.  We were thinking of dynamic lookups (talk about
a need for fast performance...).

>Most important to me are such matters as User MTA assignments for
>mail routing, etc, but those topics are under discussion in the
>mhsds working group.

Right.  At this point, I would like to be able to use the directory to find
the presentation address for, say, the filestore on (the
hosts DNS name).  And for all the other systems I have here.  Naming, of
course, strongly impacts how I place things in the DIT and what strategies are
required to retrieve it.

>Perhaps we could start with a list of things to go into the
>directory, and consider the database design from the requirements...

I'd be interested to hear more on the topic.

Thanks for your reply!