RE: (ITS#8847) New LDAP URL syntax to support binding to specific IP address at client side

[sudhir.singam@nokia.com]

Hi,

>From NOKIA, we are picking up this patch -> to add new ldap option, to be a=
ble to set specific IPv4/IPv6 bind address. We will come back with design d=
etails soon.

Regards,
Sudhir Singam

DELIVERING BEST-IN-CLASS PLATFORM is our vision

-----Original Message-----
From: Ryan Tandy <ryan@openldap.org>=20
Sent: Sunday, May 06, 2018 10:25 PM
To: openldap-its@OpenLDAP.org; Singam, Sudhir (Nokia - IN/Bangalore) <sudhi=
r.singam@nokia.com>
Cc: arekkusu@r42.ch
Subject: Re: (ITS#8847) New LDAP URL syntax to support binding to specific =
IP address at client side

On Sun, May 06, 2018 at 01:50:23PM +0000, arekkusu@r42.ch wrote:
>Adding a source IP to an URI feels wrong to it.
>
>I have not read RFC dealing with URI, however having a quick look [1] seem=
s to
>indicate that using the at sign in this way is non-standard.

I agree. @ in URIs is already defined as separating credentials (or just=20
username) from the host. I don't recall whether OpenLDAP supports that=20
usage but in any case we shouldn't re-define it.

I believe ITS#8654 is about the same feature? That one implemented this=20
by copying a Microsoft option, LDAP_OPT_SOCKET_BIND_ADDRESSES. I would=20
think that's probably a better approach. Maybe you could pick up where=20
the author of that one left off? He disappeared after posting his patch=20
for review...

thanks
Ryan