[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Specifying non-tcp transports referrals
All,
Currently, either an LDAPURL or "Other kind of URL" may be specified in
an LDAP referral.
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.
If/when someone wants to specify a non-TCP transport be used to follow
a referral, how would that be done? So far, all I can think of is to use
different URI schemes like:
ldap.udp
ldap.mobileip
Is there another way I'm not seeing?
Also, in [Protocol], there is this wording (Section 4.1.10)
>URLs for servers implementing the LDAP protocol are written according
>to [LDAPURL].
and
>Other kinds of URLs may be returned, so long as the operation could
>be performed using that protocol.
This implies (maybe it's more than an implication) that if the LDAP
protocol is to be used, the Referral will adhere to [LDAPURL]. This
means an ldap referral shouldn't contain a scheme like "ldaps". I think
the wording is either unclear or too restrictive. Why shouldn't I be
able to name a server supporting the LDAP protocol using some non
[LDAPURL] URI?
Jim