Re: [ldapext] DBIS - new IETF drafts

Luke Howard <lukeh@padl.com> Fri, 10 January 2014 14:17 UTC

Return-Path: <lukeh@padl.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB0A1ADF8A for <ldapext@ietfa.amsl.com>; Fri, 10 Jan 2014 06:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmkW-LjYtkNu for <ldapext@ietfa.amsl.com>; Fri, 10 Jan 2014 06:17:11 -0800 (PST)
Received: from us.padl.com (us.padl.com [216.154.215.154]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF271ADF73 for <ldapext@ietf.org>; Fri, 10 Jan 2014 06:17:11 -0800 (PST)
Received: by us.padl.com with ESMTP id s0AEGq2Z001129; Fri, 10 Jan 2014 09:16:55 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Luke Howard <lukeh@padl.com>
In-Reply-To: <52CFFFFB.8060105@proseconsulting.co.uk>
Date: Sat, 11 Jan 2014 01:16:51 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D1C420E-A625-4391-B929-6400C3EAF70D@padl.com>
References: <1389133522.4574.30.camel@sorbet.thuis.net> <52CDBFD2.10905@proseconsulting.co.uk> <52CEC4D5.1070703@stroeder.com> <1389290636.27654.125.camel@pico.ipa.ssimo.org> <52CFFFFB.8060105@proseconsulting.co.uk>
To: Mark R Bannister <dbis@proseconsulting.co.uk>
X-Mailer: Apple Mail (2.1822)
X-SMTP-Vilter-Version: 1.3.6
Cc: Simo <s@ssimo.org>, Ldapext <ldapext@ietf.org>, =?iso-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
Subject: Re: [ldapext] DBIS - new IETF drafts
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 14:17:12 -0000

> UNIX is traditionally case sensitive.  I am currently working at a large installation where there is an important distinction between lower-case and upper-case user names.  This debate isn't just about user names anyway.  There are loads of NIS fields that were case sensitive, and UNIX isn't going to change.  They will always be case sensitive.  So trying to represent them in case insensitive fields is just, well, wrong.

Unfortunately once again this exists for historical reasons (mostly to do with Netscape's original internal deployment, if my memory serves me correctly). Obviously you can fix it with client-side schema mapping, but it's also good to have a schema to map to, agreed.

-- Luke