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

Re: Specifying non-tcp transports referrals

To: Jim Sermersheim <jimse@novell.com>
Subject: Re: Specifying non-tcp transports referrals
From: mcs@netscape.com (Mark C Smith)
Date: Thu, 26 Jun 2003 10:21:02 -0700
Cc: ehall@ehsco.com, Steve McLain <SMCLAIN@novell.com>, Tom Doman <TDoman.PRV-1.PROVO@novell.com>, ietf-ldapbis@OpenLDAP.org
In-reply-to: <sef959fc.076@prv-mail20.provo.novell.com>
Organization: Netscape Communications Corp.
References: <sef959fc.076@prv-mail20.provo.novell.com>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030617 Netscape/7.1 (ax)

Jim Sermersheim wrote:

I assumed it was a bad assumption because as I looked closer at
draft-ietf-ldapbis-url-03.txt, I found nothing to indicate that the
LDAPURL is to be used for any particular transport. From what I can
tell, it is only a defacto standard that this is always used for
TCP/IP.

The only well defined transport for LDAP is TCP. So I just assume that LDAP URLs must use TCP as a transport too. Are you saying that is too limiting?

-Mark

References:
- Re: Specifying non-tcp transports referrals
  - From: "Jim Sermersheim" <jimse@novell.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