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

Re: Specifying non-tcp transports referrals

To: "Eric A. Hall" <ehall@ehsco.com>
Subject: Re: Specifying non-tcp transports referrals
From: mcs@netscape.com (Mark C Smith)
Date: Tue, 24 Jun 2003 22:42:16 -0700
Cc: Jim Sermersheim <jimse@novell.com>, ietf-ldapbis@OpenLDAP.org, Steve McLain <SMCLAIN@novell.com>, Tom Doman <TDoman@novell.com>
In-reply-to: <3EF8BA04.9000004@ehsco.com>
Organization: Netscape Communications Corp.
References: <sef840a4.079@prv-mail20.provo.novell.com> <3EF8BA04.9000004@ehsco.com>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030617 Netscape/7.1 (ax)

Eric A. Hall wrote:

on 6/24/2003 1:12 PM Jim Sermersheim wrote:

I believe it's assumed that the address in an LDAP URL
(draft-ietf-ldapbis-url-03.txt) points to an LDAP server capable of
communicating over TCP/IP. This is probably a bad assumption.

Why is that a bad assumption? If and when someone wants to use URLs that support LDAP over a non-TCP transport, they can define an LDAP URL extension or a new URL scheme (as both Jim and Eric suggested). I do not think the LDAPBis documents need to say much if anything about this.

-Mark

References:
- Specifying non-tcp transports referrals
  - From: "Jim Sermersheim" <jimse@novell.com>
- Re: Specifying non-tcp transports referrals
  - From: "Eric A. Hall" <ehall@ehsco.com>

Prev by Date: Re: ldapbis WG Last Call on ldapbis-syntaxes, ldapbis-strprep
Next by Date: Re: Specifying non-tcp transports referrals
Index(es):
- Chronological
- Thread