[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP Server Discovery

To: James Kempf <James.Kempf@eng.Sun.COM>
Subject: Re: LDAP Server Discovery
From: Mark Wahl <M.Wahl@INNOSOFT.COM>
Date: Thu, 09 Sep 1999 19:43:20 -0500
Cc: ietf-ldapext@netscape.com, jayhawk@att.com
In-reply-to: "Your message of Thu, 09 Sep 1999 17:23:16 PDT." <199909100019.RAA20801@hsmpka.eng.sun.com>
Resent-date: Thu, 09 Sep 1999 17:43:41 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"i0wRJB.A.s8F.1QF23"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

> What I'm proposing is a prioritized list of methods to discover 
> LDAP servers that interoperable implementations would use. 

I would have thought that servers could _use_ the same mechanisms as clients
described in Ryan's taxonomy I-D for DNs of the DC form.  There was a draft
in the LSD working group that timed out on interconnecting servers holding
contexts with prefixes of the DC form with servers whose context prefixes were 
not of the DC form.  Neither of these drafts cover how this information is 
made available when a naming context is created, although there are now 
advertising mechanisms for DNS and SLP, and X.500 (DOP), they are not yet too
widely deployed I suspect.  

Mark Wahl, Directory Product Architect
Innosoft International, Inc.

References:
- RE: LDAP Server Discovery
  - From: James Kempf <James.Kempf@eng.Sun.COM>

Prev by Date: RE: LDAP Server Discovery
Next by Date: I-D ACTION:draft-ietf-ldapext-locate-00.txt
Index(es):
- Chronological
- Thread