Re: [ldapext] DBIS commentary

Jordan Brown <> Tue, 01 December 2015 22:49 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id DCC9D1AD351 for <>; Tue, 1 Dec 2015 14:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id irBKv28e3Sxk for <>; Tue, 1 Dec 2015 14:49:31 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 766541AD2D5 for <>; Tue, 1 Dec 2015 14:49:31 -0800 (PST)
Received: from ( []) by (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id tB1MnUCO002252 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Dec 2015 22:49:30 GMT
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id tB1MnTSk023368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Dec 2015 22:49:30 GMT
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id tB1MnTpO003619; Tue, 1 Dec 2015 22:49:29 GMT
Received: from [] (/ by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 01 Dec 2015 14:49:29 -0800
To: Charlie <>
References: <> <> <> <> <> <>
From: Jordan Brown <>
Message-ID: <>
Date: Tue, 01 Dec 2015 14:49:22 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------040103040900080104070007"
X-Source-IP: []
Archived-At: <>
Cc: "" <>
Subject: Re: [ldapext] DBIS commentary
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 01 Dec 2015 22:49:33 -0000

[ Splitting off a specific subthread as Michael requested ]
[ Resend with correct distribution ]

On 12/1/2015 2:06 PM, Charlie wrote:
> A directory backend that is intended to serve multiple existing
> operating systems probably shouldn't be telling any of those operating
> systems whether or not they should be case-sensitive.  It's out of
> scope for the project and causes arguments.

Well, but... if the various OSes are sharing the same naming attribute, it seems 
like there's an unbreakable chain of connections between them.  Either the 
attribute is case-sensitive, in which case the natively-case-insensitive OS will 
be confused, or the attribute is case-insensitive, in which case the 
natively-case-sensitive OS will be confused.

The way that I look at it is not that the directory is serving the OSes, but that 
the directory is defining a world that the OSes are choosing to play in... and 
when they choose to play in the directory's world, they have to live by its rules.

> That being said, options are great to have.  If you can support
> existing systems while also giving people the ability to do whatever
> you happen to think is better, you'll automatically win any such
> arguments.

It's tempting to suggest that a single entry could have one name attribute that's 
case-sensitive and another that's case-insensitive (presumably from different 
auxiliary classes), and technically that'd be possible, but seems like an 
administrative nightmare... a very high cost to pay for the 0.1% of names where 
case-sensitivity is important.