Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 55225 invoked from network); 21 Sep 2007 23:17:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Sep 2007 23:17:05 -0000 Received: (qmail 8060 invoked by uid 500); 21 Sep 2007 23:16:57 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 7853 invoked by uid 500); 21 Sep 2007 23:16:56 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 7842 invoked by uid 99); 21 Sep 2007 23:16:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 16:16:56 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 66.249.82.234 as permitted sender) Received: from [66.249.82.234] (HELO wx-out-0506.google.com) (66.249.82.234) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 23:16:53 +0000 Received: by wx-out-0506.google.com with SMTP id s8so729494wxc for ; Fri, 21 Sep 2007 16:16:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ctm43VxgVHVPsYanbB/RbL5nNkO0V4Os3pmqVwerCFE=; b=LhT/qYVs5qvz6xepHAvm96kAqvWA4+5BiglNY10xd9+TQKOQwTDJdh8l7gA8GsTJoe+ajj8Et17nNgSiBPXE/kj0oC3gQFVxj4oGyBHm4eWQ24lBzU5PoKy5WeiQHlfM/27Aywa9g6/Txqnc9f/T4NGz7EYiC9o9sTqHjelIPSw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GS1ZdFnqhRuqkVWPxJrDQAsEsyZbIvtBQNhJqukE2g9V+cebbNtHWDTz4B3Y7RyNsND7RRetaVznDnPFc9P1rkml85ditr2XReziPRpxlvftCZ8SJmwtEhfHd7e1T27UnX8uSbs5pNqVrIzG89PlTl/W74hpwFen8I7HwVdvVVw= Received: by 10.90.53.16 with SMTP id b16mr3066870aga.1190416591971; Fri, 21 Sep 2007 16:16:31 -0700 (PDT) Received: by 10.90.31.7 with HTTP; Fri, 21 Sep 2007 16:16:31 -0700 (PDT) Message-ID: Date: Sat, 22 Sep 2007 01:16:31 +0200 From: "Emmanuel Lecharny" Reply-To: elecharny@iktek.com To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Specifying application level subtrees? In-Reply-To: <800df6390709211548y4558cfc6m7e4a8facba66ae1f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <800df6390709211011q5bdef748xcc628ccee0029829@mail.gmail.com> <800df6390709211321j2990c99dhca28eff429195883@mail.gmail.com> <800df6390709211548y4558cfc6m7e4a8facba66ae1f@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Marc, Alex, just a small comment in the body > > IMO LDAP was too lightweight in an adverse reaction to the > > OSI > > weight of X.500. So now people realize we have to embrace X.500 concep= ts > > and in particular the admin model. Lookie here .. > > > > http://www.ietf.org/rfc/rfc3672.txt > > > > OK, so this is starting to get really philosophical but I think LDAP > is just fine. LDAP is a directory ACCESS protocol. LDAP _was_ a directory access protocol. It's not anymore the case. Do you know any X.500 server around there? We are all working on an world of LDAP servers, not on a world of people using LDAP protocol on top of X.500 servers. let's fact the fact : LDAP servers need to evolve now. How that > directory is implemented shouldn't matter. As a matter of practice I > prefer simple to complex. There are many good things about X.500 > (which are the roots of virtual directories), but I don't think we > should confuse the access protocol and the implementation protocol. The LDAP RFCs aren't confusing the protocol itself and the implementation. if you read carefully all those RFCs (4511 to 4520), the sentence 'implementors should ...' is all over them. There is no more difference between Protocol and the implementation. It's over. Let's move to LDAP V4 now ! --=20 Regards, Cordialement, Emmanuel L=E9charny www.iktek.com