Re: [ldapext] DBIS commentary

[Jordan Brown <[e-mail]>]

On 12/2/2015 12:59 AM, Bannister, Mark wrote:
>
> Jordan Brown wrote:
>
> > Do note again that RFC 4876 mapping would let you redirect the clients to use a custom
>
> > case-sensitive attribute, or attributes from different auxiliary classes.
>
> I should really have made it clear that DBIS supersedes RFC 4876, and introduces 
> more
>
> powerful mapping constructs.  With DBIS, you can support an RFC2307 schema (case
>
> insensitive) and the DBIS schema (case sensitive) from the same client if you so 
> choose,
>
> and at several levels.  You could have groups of hosts with case sensitive maps 
> vs. groups
>
> of host with case insensitive maps.  You could have a host where some maps are case
>
> sensitive and some are not.  You can even have parts of a map provided via one 
> schema
>
> and parts from another, i.e. case sensitivity for some entries and insensitivity 
> for others
>
> if that’s really what you wished to do.  If you use DBIS, you certainly have no 
> need to
>
> use RFC 4876.
>

Ah, indeed.  So if there were case-sensitive and case-insensitive attributes 
available (presumably in different auxiliary classes), you could use those mapping 
constructs to choose the non-default variation.

It doesn't look like you've got 4876 completely covered, though. Attribute mapping 
is only one of the things it does - it also tells the clients which servers to 
connect to and what authentication schemes to use.  If you're replacing 4876, 
there should be a plan for replacing that capability.

> Jordan Brown wrote:
>
> > Mark Bannister wrote:
>
> > > Btw, what was your plan for case sensitivity in filesystems?
>
> >
>
> > Baby steps :-)
>
> >
>
> > I do think that that's inevitable too, just not as soon as user names
>
> Wow.  Good luck with that.  (Boiling oceans comes to mind).
>

I work in name services, not file systems, so it's not an active project.  I just 
think it'll happen eventually, that interoperability with Windows will force it.