From ldapext-bounces@ietf.org Sat Sep 08 06:24:39 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ITxSn-00089b-K6; Sat, 08 Sep 2007 06:22:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ITxSm-00089Q-7V
	for ldapext@ietf.org; Sat, 08 Sep 2007 06:22:52 -0400
Received: from ns1.sys-net.it ([194.244.21.114] helo=mail.sys-net.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ITxSk-0005h1-Ix
	for ldapext@ietf.org; Sat, 08 Sep 2007 06:22:52 -0400
Received: from [131.175.154.35] (mbdyn-pm.aero.polimi.it [131.175.154.35])
	(authenticated bits=0)
	by mail.sys-net.it (8.13.5.20060308/8.13.3) with ESMTP id
	l88ALPZ4006806
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ldapext@ietf.org>; Sat, 8 Sep 2007 12:21:27 +0200
Message-ID: <46E27756.5010003@sys-net.it>
Date: Sat, 08 Sep 2007 12:20:06 +0200
From: Pierangelo Masarati <ando@sys-net.it>
User-Agent: Thunderbird 1.5.0.8 (X11/20061025)
MIME-Version: 1.0
To: ldapext@ietf.org
Subject: Re: [ldapext] draft-wahl-ldap-session support in OpenLDAP
References: <46CB5FA1.7080201@sys-net.it>
In-Reply-To: <46CB5FA1.7080201@sys-net.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=4.5 tests=BAYES_00,SPF_FAIL
	autolearn=no version=3.2.3
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on www.sys-net.it
X-SysNet-MailScanner-Information: postmaster@sys-net.it
X-SysNet-MailScanner: 
X-MailScanner-From: ando@sys-net.it
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Forgot to post that draft-wahl-ldap-session is now also supported by 
proxy backends in OpenLDAP 2.4.5 (just released), which can now be 
configured to create appropriate control value and attach it to proxied 
requests to allow session tracking in chained directories.

p.



Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Email:   pierangelo.masarati@sys-net.it
---------------------------------------



_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Sat Sep 15 10:12:57 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IWYO9-0007Xa-2e; Sat, 15 Sep 2007 10:12:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IWYO8-0007XV-5E
	for ldapext@ietf.org; Sat, 15 Sep 2007 10:12:48 -0400
Received: from ns1.sys-net.it ([194.244.21.114] helo=mail.sys-net.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IWYO6-00022o-IS
	for ldapext@ietf.org; Sat, 15 Sep 2007 10:12:48 -0400
Received: from [192.168.1.199] (dossi.sys-net.it [82.63.140.131])
	(authenticated bits=0)
	by mail.sys-net.it (8.13.5.20060308/8.13.3) with ESMTP id
	l8FEBRqT029920
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ldapext@ietf.org>; Sat, 15 Sep 2007 16:11:30 +0200
Message-ID: <46EBE8A6.4090100@sys-net.it>
Date: Sat, 15 Sep 2007 16:13:58 +0200
From: Pierangelo Masarati <ando@sys-net.it>
User-Agent: Mail/News 1.5.0.8 (X11/20061210)
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SysNet-MailScanner-Information: postmaster@sys-net.it
X-SysNet-MailScanner: 
X-MailScanner-From: ando@sys-net.it
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Subject: [ldapext] Proposal of a companion control to draft-wahl-ldap-session
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Hi all.

The draft in object proposes a control that a client can send along with
a request, and similarly a server can return along with a response, to
add session tracking information to LDAP operations when a client-server
operation is just part of a larger infrastructure.

I think that, in the spirit of a fair cooperation between components of
the same infrastructure, the session tracking control of
draft-wahl-ldap-session (1.3.6.1.4.1.21008.108.63.1) could be augmented
by a companion control that requests session tracking contents in
response to an operation, to allow the client to request information
about how a proxy handled the operation.  The rationale behind it is
that a proxy, acting as a client in an operation that is chained across
a distributed system (I'm using the term "chain" in a loose manner, with
no direct reference to chained operations as described in X.500), might
want to track how the operation is actually performed only in some
cases, so a server could be configured to return control
1.3.6.1.4.1.21008.108.63.1 only on demand.

I'm proposing this enhancement here instead of in a separate I.D.
because I think I need some preliminary feedback first, and also because
I think it is so closely related to draft-wahl-ldap-session that it
could even be integrated in it, if considered appropriate.  Based on
discussion, if any, I plan to start implementing it in OpenLDAP very soon.

The semantics of the proposed control is discussed below.

Cheers, p.



        - o --- o --- o -

This control solicits a response containing the same type of information
of control 1.3.6.1.4.1.21008.108.63.1 for informational purposes.



request control: sessionTrackingRequest
OID: TBA
criticality: TRUE or FALSE
value: propagate BOOLEAN OPTIONAL

if the server is willing to propagate the control, this occurs only if
propagate is not FALSE.

if the server is not willing to propagate the control and propagate is
TRUE, if criticality is TRUE, the operation is bounced returning
unwillingToPerform, otherwise if criticality is FALSE the control is
ignored.

if the client has no preference about control propagation, the control
value MUST be absent.



response control: sessionTrackingRequest
OID: TBA
criticality: FALSE as per RFC 4511

four response scenarios:

1. [in case of request criticality == FALSE]
   the control is absent (not recognized, or unwillingToPerform
   because of local privacy/security policy considerations)

2. [in case of request criticality == TRUE]
   the response is unwillingToPerform (not recognized, or because
   of local privacy/security policy considerations)

3. [regardless of request criticality]
   the control is present, but the value is absent: the request
   has been handled locally, or the server is pretending so

4. [regardless of request criticality]
   the control is present, with value as per 1.3.6.1.4.1.21008.108.63.1

If value is present, it SHALL contain information as per
1.3.6.1.4.1.21008.108.63.1 related to the remote server that was
contacted to perform the operation.  It is left to the DSA's discretion
(based on local privacy/security policy considerations) to propagate the
control request along with the operation, according to the semantics of
the "propagate" in the request, and to return any other instance of the
control response along with the response to the operation; in this case
there might be multiple instances of the control in the response.

If the server is willing to provide 1.3.6.1.4.1.21008.108.63.1 in the
response, and sessionTrackingRequest was issued and not ignored, it
SHALL return sessionTrackingRequest instead.

The same security considerations of draft-wahl-ldap-session apply.




Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Email:   pierangelo.masarati@sys-net.it
---------------------------------------



_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 10:34:01 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXHfd-0007y9-JL; Mon, 17 Sep 2007 10:33:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXHfc-0007xR-4O
	for ldapext@ietf.org; Mon, 17 Sep 2007 10:33:52 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXHfY-0007yO-QV
	for ldapext@ietf.org; Mon, 17 Sep 2007 10:33:49 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>) id 1IXHfX-000FDH-9w
	for ldapext@ietf.org; Mon, 17 Sep 2007 15:33:47 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>) id 1IXHfM-0001tQ-C7
	for ldapext@ietf.org; Mon, 17 Sep 2007 15:33:36 +0100
Date: Mon, 17 Sep 2007 15:33:36 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: ldapext@ietf.org
Message-ID: <20070917143336.GA7266@tile.skills-1st.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451
Subject: [ldapext] groupOfEntries object class proposal
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

At the recent LDAP conference in Cologne there was wide support for an
effort to improve some of the commonly-used schema definitions. In
particular, the fact that groupOfNames does not permit an empty group
was felt to be a significant problem.

To address this problem, I have published an I-D proposing a new
objectclass called groupOfEntries. The I-D is appended and is also
available at:

http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupofentries-00.txt

To make adoption as easy as possible, the new object class is
identical to groupOfNames except that it has the ability to
describe empty groups without resorting to tricks and workarounds.

I would like to see this new class used in place of groupOfNames in
new designs, so I propose to ask IETF to consider the draft for the
Standards Track.

Comments and suggestions for improvement are welcome, and should be
sent to the ldapext@ietf.org mailing list.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

Network Working Group                                         A. Findlay
Internet-Draft                                            Skills 1st Ltd
Expires: March 16, 2008                               September 13, 2007


                  The LDAP groupOfEntries object class
                  draft-findlay-ldap-groupofentries-00

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 16, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This memo describes the LDAP groupOfEntries object class which is a
   replacement for the existing groupOfNames class.  The new class
   permits the creation of empty groups.

   If approved as a Standards Track document, this document will update
   RFC4519 [2]

Document Intent

   This document is intended to be, after appropriate review and
   revision, submitted to the RFC Editor as a Standards Track document.
   Distribution of this memo is unlimited.  Technical discussion of this
   document will take place on the IETF LDAP Extensions mailing list
   <ldapext@ietf.org>.  Please send editorial comments directly to the
   author <andrew.findlay@skills-1st.co.uk>


1.  Introduction

   A groupOfNames object class has existed since the earliest X.521 [1]
   standard.  It has an identical definition in LDAP (RFC4519 [2]).  The
   class is used to define entries holding DN-valued member attributes,
   each value pointing to an entry that represents a single member of
   the group being described, or to another entry of type groupOfNames.

   groupOfNames is a structural object class, so it is often the only
   class used in the definition of group objects.

   Experience has shown that the definition of groupOfNames causes
   difficulties in practice.  In particular, the fact that 'member' is a
   mandatory attribute means that it is not possible to create an empty
   group or to delete the last member from a group.  This leads to
   artificial tricks such as making every group a member of itself, or
   adding a dummy member to every group when it is created.  These
   tricks in turn make the management of groups more complex and prone
   to error.  Groups are commonly used to control access to resources,
   so management errors can lead to security risks.

   There does not appear to be any good reason for the 'member'
   attribute to be mandatory.  This memo describes a new object class
   called groupOfEntries that is equivalent to groupOfNames in all other
   respects but which makes 'member' an optional attribute.


2.  The existing groupOfNames object class

   RFC4519 [2] contains this definition:

   The 'groupOfNames' object class is the basis of an entry that
   represents a set of named objects including information related to
   the purpose or maintenance of the set.  (Source: X.521 [1])

         ( 2.5.6.9 NAME 'groupOfNames'
            SUP top
            STRUCTURAL
            MUST ( member $
                  cn )
            MAY ( businessCategory $
                  seeAlso $
                  owner $
                  ou $
                  o $
                  description ) )

   The inclusion of 'member' in the 'MUST' section of the definition
   prevents empty groups from being created.


3.  The groupOfEntries object class

   The 'groupOfEntries' object class is the basis of an entry that
   represents a set of named objects including information related to
   the purpose or maintenance of the set.  It should be used in
   preference to the 'groupOfNames' object class.

         ( 1.2.826.0.1.3458854.2.1.1.1 NAME 'groupOfEntries'
            SUP top
            STRUCTURAL
            MUST ( cn )
            MAY ( member $
                  businessCategory $
                  seeAlso $
                  owner $
                  ou $
                  o $
                  description ) )

   This object class allows groups to be empty.  In all other respects
   it behaves like the groupOfNames object class.

   The OID assigned to this object class is delegated by Skills 1st Ltd.


4.  Effect on other documents

   This draft deprecates the use of the groupOfNames object class in
   RFC4519 [2] and replaces it with the groupOfEntries class.


5.  IANA considerations

   It is requested that IANA register upon Standards Action the
   groupOfEntries Object Identifier Descriptor and its associated OID.


6.  Security considerations

   Groups are commonly used to define access permissions to directory
   entries and resources in other services.  Allowing for empty groups
   avoids the risks associated with leaving a dummy placeholder member
   in group entries, so security is improved.


Appendix A.  Acknowledgements

   The author gratefully acknowledges the contributions of Michael
   Stroeder to the first draft of this document.


7.  Informative References

   [1]  "The Directory: Selected Object Classes", ITU-T
        Recommendation X.521, March 1988.

   [2]  "LDAP: Schema for User Applications", RFC 4519, June 2006.


Author's Address

   Andrew Findlay
   Skills 1st Ltd
   2 Cedar Chase
   Taplow
   Maidenhead  SL6 0EU
   GB

   Phone: +44 1628 782565
   Email: andrew.findlay@skills-1st.co.uk
   URI:   http://www.skills-1st.co.uk/


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).



_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 19:01:44 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXPZx-0000Gt-1p; Mon, 17 Sep 2007 19:00:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXPZv-0000Go-Pd
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:00:31 -0400
Received: from au.padl.com ([203.13.32.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXPZu-0007l0-Uq
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:00:31 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8HN0Lgb007842
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 17 Sep 2007 23:00:24 GMT
Message-ID: <46EF07BD.1010801@padl.com>
Date: Tue, 18 Sep 2007 09:03:25 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
In-Reply-To: <20070917143336.GA7266@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Another thing that would be useful might be to define the behaviour of 
nested groups, eg. should the client expand them?

It would make sense to use this object class for rfc2307bis too 
(whenever that is completed :-))

-- Luke

Andrew Findlay wrote:
> At the recent LDAP conference in Cologne there was wide support for an
> effort to improve some of the commonly-used schema definitions. In
> particular, the fact that groupOfNames does not permit an empty group
> was felt to be a significant problem.
>
> To address this problem, I have published an I-D proposing a new
> objectclass called groupOfEntries. The I-D is appended and is also
> available at:
>
> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupofentries-00.txt
>
> To make adoption as easy as possible, the new object class is
> identical to groupOfNames except that it has the ability to
> describe empty groups without resorting to tricks and workarounds.
>
> I would like to see this new class used in place of groupOfNames in
> new designs, so I propose to ask IETF to consider the draft for the
> Standards Track.
>
> Comments and suggestions for improvement are welcome, and should be
> sent to the ldapext@ietf.org mailing list.
>
> Andrew
>   


-- 
www.padl.com | www.lukehoward.com


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 19:23:21 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXPvL-0004YK-SD; Mon, 17 Sep 2007 19:22:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXPvK-0004Sj-Fm
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:22:38 -0400
Received: from ccerelbas01.cce.hp.com ([161.114.21.104])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXPvE-00089h-Uh
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:22:33 -0400
Received: from G3W0060.americas.hpqcorp.net (g3w0060.americas.hpqcorp.net
	[16.232.1.19])
	by ccerelbas01.cce.hp.com (Postfix) with ESMTP id 486E83453E;
	Mon, 17 Sep 2007 18:21:42 -0500 (CDT)
Received: from G3W0067.americas.hpqcorp.net ([16.232.1.13]) by
	G3W0060.americas.hpqcorp.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Sep 2007 23:21:38 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] groupOfEntries object class proposal
Date: Mon, 17 Sep 2007 23:21:37 -0000
Message-ID: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
In-Reply-To: <46EF07BD.1010801@padl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] groupOfEntries object class proposal
Thread-Index: Acf5f861HGEIhMy/RfSpCnE7LCtKBQAAFimw
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
From: "Neal-Joslin, Robert (HP-UX Lab R&D)" <bob.joslin@hp.com>
To: "Luke Howard" <lukeh@padl.com>,
	"Andrew Findlay" <andrew.findlay@skills-1st.co.uk>
X-OriginalArrivalTime: 17 Sep 2007 23:21:38.0158 (UTC)
	FILETIME=[7F15C8E0:01C7F981]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Hi,

I'm almost always in favor of new and better ways to do things.  And I
agree with the statements submitted.  But I can see a need to play
devil's advocate for this one.  Is there really enough justification to
warrant this proposal?  What is the likelihood of its success, given how
entrenched groupOfNames and groupOfUniqueNames is embedded in the
existing LDAP application/server security space?  This is a very
low-level concept to LDAP, and thus convincing all application/server
developers to revolutionize seems a unlikely scenario.  And I would
argue that it would take a sea-change before it would be successful.
I.E. would this proposal be successful if only 50% or even 75% of
applications/servers support it?

Bob
=20

> -----Original Message-----
> From: Luke Howard [mailto:lukeh@padl.com]=20
> Sent: Monday, September 17, 2007 4:03 PM
> To: Andrew Findlay
> Cc: ldapext@ietf.org
> Subject: Re: [ldapext] groupOfEntries object class proposal
>=20
> Another thing that would be useful might be to define the=20
> behaviour of=20
> nested groups, eg. should the client expand them?
>=20
> It would make sense to use this object class for rfc2307bis too=20
> (whenever that is completed :-))
>=20
> -- Luke
>=20
> Andrew Findlay wrote:
> > At the recent LDAP conference in Cologne there was wide=20
> support for an
> > effort to improve some of the commonly-used schema definitions. In
> > particular, the fact that groupOfNames does not permit an=20
> empty group
> > was felt to be a significant problem.
> >
> > To address this problem, I have published an I-D proposing a new
> > objectclass called groupOfEntries. The I-D is appended and is also
> > available at:
> >
> >=20
> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupof
entries-00.txt
> >
> > To make adoption as easy as possible, the new object class is
> > identical to groupOfNames except that it has the ability to
> > describe empty groups without resorting to tricks and workarounds.
> >
> > I would like to see this new class used in place of groupOfNames in
> > new designs, so I propose to ask IETF to consider the draft for the
> > Standards Track.
> >
> > Comments and suggestions for improvement are welcome, and should be
> > sent to the ldapext@ietf.org mailing list.
> >
> > Andrew
> >  =20
>=20
>=20
> --=20
> www.padl.com | www.lukehoward.com
>=20
>=20
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
>=20

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 19:27:08 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXPzH-0003hL-Dq; Mon, 17 Sep 2007 19:26:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXPzF-0003gu-Q8
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:26:41 -0400
Received: from au.padl.com ([203.13.32.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXPzF-0008JN-2E
	for ldapext@ietf.org; Mon, 17 Sep 2007 19:26:41 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8HNQVrN008741
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 17 Sep 2007 23:26:33 GMT
Message-ID: <46EF0DDF.4090806@padl.com>
Date: Tue, 18 Sep 2007 09:29:35 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Neal-Joslin, Robert (HP-UX Lab R&D)" <bob.joslin@hp.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
In-Reply-To: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

I suppose another approach would be to redefine groupOfNames with a new OID?

-- Luke

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 20:03:29 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXQWm-00089g-FI; Mon, 17 Sep 2007 20:01:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXQWl-00088I-A3
	for ldapext@ietf.org; Mon, 17 Sep 2007 20:01:19 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXQWk-0001CN-My
	for ldapext@ietf.org; Mon, 17 Sep 2007 20:01:19 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8I01AQw019250; Mon, 17 Sep 2007 19:01:10 -0500
Message-ID: <46EF14CA.8090102@highlandsun.com>
Date: Mon, 17 Sep 2007 16:59:06 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: "Neal-Joslin, Robert (HP-UX Lab R&D)" <bob.joslin@hp.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
In-Reply-To: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: ldapext@ietf.org, Luke Howard <lukeh@padl.com>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Neal-Joslin, Robert (HP-UX Lab R&D) wrote:
> Hi,
> 
> I'm almost always in favor of new and better ways to do things.  And I
> agree with the statements submitted.  But I can see a need to play
> devil's advocate for this one.  Is there really enough justification to
> warrant this proposal?  What is the likelihood of its success, given how
> entrenched groupOfNames and groupOfUniqueNames is embedded in the
> existing LDAP application/server security space? 

Ah, you've just hit another hot-button - groupOfUniqueNames is utterly 
pointless. I'm all for eradicating the old stuff and pushing groupOfEntries as 
a standard.

nameAndOptionalUID syntax is inherently broken, it cannot be parsed reliably. 
e.g. - "cn=foo#101" could legitimately be a cn with value "foo#101", there's 
no way to disambiguate it from "cn=foo" with UID "101".

The entire concept behind this syntax is flawed. What do you do if you have a 
"unique" named object with children? What if the children have unique names 
too? There's only provision for one unique ID in the DN, but fundamentally 
there should be the possibility of a unique ID for every RDN in the DN. I.e., 
if this is really what you want, you should have been using multivalued RDNs 
from the get-go.

Probably 99% of LDAP applications never even use the UID portion of a 
nameAndOptionalUID attribute, and the other 1% that use it are broken since 
the syntax is inherently broken.

I'll happily write up a standards track document to deprecate 
groupOfUniqueNames and nameAndOptionalUID syntax.

> This is a very
> low-level concept to LDAP, and thus convincing all application/server
> developers to revolutionize seems a unlikely scenario.  And I would
> argue that it would take a sea-change before it would be successful.
> I.E. would this proposal be successful if only 50% or even 75% of
> applications/servers support it?
> 
> Bob
>  
> 
>> -----Original Message-----
>> From: Luke Howard [mailto:lukeh@padl.com] 
>> Sent: Monday, September 17, 2007 4:03 PM
>> To: Andrew Findlay
>> Cc: ldapext@ietf.org
>> Subject: Re: [ldapext] groupOfEntries object class proposal
>>
>> Another thing that would be useful might be to define the 
>> behaviour of 
>> nested groups, eg. should the client expand them?
>>
>> It would make sense to use this object class for rfc2307bis too 
>> (whenever that is completed :-))
>>
>> -- Luke
>>
>> Andrew Findlay wrote:
>>> At the recent LDAP conference in Cologne there was wide 
>> support for an
>>> effort to improve some of the commonly-used schema definitions. In
>>> particular, the fact that groupOfNames does not permit an 
>> empty group
>>> was felt to be a significant problem.
>>>
>>> To address this problem, I have published an I-D proposing a new
>>> objectclass called groupOfEntries. The I-D is appended and is also
>>> available at:
>>>
>>>
>> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupof
> entries-00.txt
>>> To make adoption as easy as possible, the new object class is
>>> identical to groupOfNames except that it has the ability to
>>> describe empty groups without resorting to tricks and workarounds.
>>>
>>> I would like to see this new class used in place of groupOfNames in
>>> new designs, so I propose to ask IETF to consider the draft for the
>>> Standards Track.
>>>
>>> Comments and suggestions for improvement are welcome, and should be
>>> sent to the ldapext@ietf.org mailing list.
>>>
>>> Andrew
>>>   
>>
>> -- 
>> www.padl.com | www.lukehoward.com
>>
>>
>> _______________________________________________
>> Ldapext mailing list
>> Ldapext@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ldapext
>>
> 
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
> 


-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 22:46:49 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXT4u-0000SN-Hc; Mon, 17 Sep 2007 22:44:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXT4t-0000RB-5L
	for ldapext@ietf.org; Mon, 17 Sep 2007 22:44:43 -0400
Received: from mail17.ca.com ([155.35.248.106])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXT4q-00059f-9o
	for ldapext@ietf.org; Mon, 17 Sep 2007 22:44:40 -0400
Received: from ausyms11.ca.com ([155.35.201.2]) by mail17.ca.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Sep 2007 12:44:33 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] groupOfEntries object class proposal
Date: Tue, 18 Sep 2007 12:44:33 +1000
Message-ID: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
In-Reply-To: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] groupOfEntries object class proposal
Thread-Index: Acf5f861HGEIhMy/RfSpCnE7LCtKBQAAFimwAAcfJqA=
References: <20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Andrew Findlay" <andrew.findlay@skills-1st.co.uk>
X-OriginalArrivalTime: 18 Sep 2007 02:44:33.0891 (UTC)
	FILETIME=[D8633330:01C7F99D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Why not try to get the appropriate RFC revised to make 'member'
optional?

Even simply making 'member' optional in your own implementations, though
inviting interoperability problems, would seem to have fewer issues than
introducing a new object class. In fact, I think it is common to find
that 'member' is optional inthe field.

-----Original Message-----
From: Neal-Joslin, Robert (HP-UX Lab R&D) [mailto:bob.joslin@hp.com]=20
Sent: Tuesday, 18 September 2007 9:22 AM
To: Luke Howard; Andrew Findlay
Cc: ldapext@ietf.org
Subject: RE: [ldapext] groupOfEntries object class proposal

Hi,

I'm almost always in favor of new and better ways to do things.  And I
agree with the statements submitted.  But I can see a need to play
devil's advocate for this one.  Is there really enough justification to
warrant this proposal?  What is the likelihood of its success, given how
entrenched groupOfNames and groupOfUniqueNames is embedded in the
existing LDAP application/server security space?  This is a very
low-level concept to LDAP, and thus convincing all application/server
developers to revolutionize seems a unlikely scenario.  And I would
argue that it would take a sea-change before it would be successful.
I.E. would this proposal be successful if only 50% or even 75% of
applications/servers support it?

Bob
=20

> -----Original Message-----
> From: Luke Howard [mailto:lukeh@padl.com]=20
> Sent: Monday, September 17, 2007 4:03 PM
> To: Andrew Findlay
> Cc: ldapext@ietf.org
> Subject: Re: [ldapext] groupOfEntries object class proposal
>=20
> Another thing that would be useful might be to define the=20
> behaviour of=20
> nested groups, eg. should the client expand them?
>=20
> It would make sense to use this object class for rfc2307bis too=20
> (whenever that is completed :-))
>=20
> -- Luke
>=20
> Andrew Findlay wrote:
> > At the recent LDAP conference in Cologne there was wide=20
> support for an
> > effort to improve some of the commonly-used schema definitions. In
> > particular, the fact that groupOfNames does not permit an=20
> empty group
> > was felt to be a significant problem.
> >
> > To address this problem, I have published an I-D proposing a new
> > objectclass called groupOfEntries. The I-D is appended and is also
> > available at:
> >
> >=20
> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupof
entries-00.txt
> >
> > To make adoption as easy as possible, the new object class is
> > identical to groupOfNames except that it has the ability to
> > describe empty groups without resorting to tricks and workarounds.
> >
> > I would like to see this new class used in place of groupOfNames in
> > new designs, so I propose to ask IETF to consider the draft for the
> > Standards Track.
> >
> > Comments and suggestions for improvement are welcome, and should be
> > sent to the ldapext@ietf.org mailing list.
> >
> > Andrew
> >  =20
>=20
>=20
> --=20
> www.padl.com | www.lukehoward.com
>=20
>=20
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
>=20

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 23:00:32 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXTJH-0004x7-Qn; Mon, 17 Sep 2007 22:59:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXTJG-0004wy-A9
	for ldapext@ietf.org; Mon, 17 Sep 2007 22:59:34 -0400
Received: from mail17.ca.com ([155.35.248.106])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXTJB-0005QN-N3
	for ldapext@ietf.org; Mon, 17 Sep 2007 22:59:30 -0400
Received: from ausyms11.ca.com ([155.35.201.2]) by mail17.ca.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Sep 2007 12:59:28 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] groupOfEntries object class proposal
Date: Tue, 18 Sep 2007 12:59:27 +1000
Message-ID: <52681ACFF63C114F8A3C3651FC9D301F825316@AUSYMS11.ca.com>
In-Reply-To: <46EF14CA.8090102@highlandsun.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] groupOfEntries object class proposal
Thread-Index: Acf5iBDH2ma4qPvwSWSCe+uS/6VZdQAFuf6g
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<46EF14CA.8090102@highlandsun.com>
From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
To: "Howard Chu" <hyc@highlandsun.com>
X-OriginalArrivalTime: 18 Sep 2007 02:59:28.0087 (UTC)
	FILETIME=[ED5EAE70:01C7F99F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

1) The ambiguity is a result of converting the concept to LDAP.
2) I don't think you can use nameAndOptionalUID for naming, certainly
not in the 93 standard. So your comments about children are not really
appropriate. It's sole use may be in the groupOfUniqueNames object where
the UID is acting as a generational qualifier. To fully support it,
though, I think would require a UID attribute in the entry having that
DN. Oh yes, access control is supposed to use it, too. But the qualifier
applies to the DN itself and is making a statement about when THIS DN
was relevant.

-----Original Message-----
From: Howard Chu [mailto:hyc@highlandsun.com]=20
Sent: Tuesday, 18 September 2007 9:59 AM
To: Neal-Joslin, Robert (HP-UX Lab R&D)
Cc: ldapext@ietf.org; Luke Howard; Andrew Findlay
Subject: Re: [ldapext] groupOfEntries object class proposal

Neal-Joslin, Robert (HP-UX Lab R&D) wrote:
> Hi,
>=20
> I'm almost always in favor of new and better ways to do things.  And I
> agree with the statements submitted.  But I can see a need to play
> devil's advocate for this one.  Is there really enough justification
to
> warrant this proposal?  What is the likelihood of its success, given
how
> entrenched groupOfNames and groupOfUniqueNames is embedded in the
> existing LDAP application/server security space?=20

Ah, you've just hit another hot-button - groupOfUniqueNames is utterly=20
pointless. I'm all for eradicating the old stuff and pushing
groupOfEntries as=20
a standard.

nameAndOptionalUID syntax is inherently broken, it cannot be parsed
reliably.=20
e.g. - "cn=3Dfoo#101" could legitimately be a cn with value "foo#101",
there's=20
no way to disambiguate it from "cn=3Dfoo" with UID "101".

The entire concept behind this syntax is flawed. What do you do if you
have a=20
"unique" named object with children? What if the children have unique
names=20
too? There's only provision for one unique ID in the DN, but
fundamentally=20
there should be the possibility of a unique ID for every RDN in the DN.
I.e.,=20
if this is really what you want, you should have been using multivalued
RDNs=20
from the get-go.

Probably 99% of LDAP applications never even use the UID portion of a=20
nameAndOptionalUID attribute, and the other 1% that use it are broken
since=20
the syntax is inherently broken.

I'll happily write up a standards track document to deprecate=20
groupOfUniqueNames and nameAndOptionalUID syntax.

> This is a very
> low-level concept to LDAP, and thus convincing all application/server
> developers to revolutionize seems a unlikely scenario.  And I would
> argue that it would take a sea-change before it would be successful.
> I.E. would this proposal be successful if only 50% or even 75% of
> applications/servers support it?
>=20
> Bob
> =20
>=20
>> -----Original Message-----
>> From: Luke Howard [mailto:lukeh@padl.com]=20
>> Sent: Monday, September 17, 2007 4:03 PM
>> To: Andrew Findlay
>> Cc: ldapext@ietf.org
>> Subject: Re: [ldapext] groupOfEntries object class proposal
>>
>> Another thing that would be useful might be to define the=20
>> behaviour of=20
>> nested groups, eg. should the client expand them?
>>
>> It would make sense to use this object class for rfc2307bis too=20
>> (whenever that is completed :-))
>>
>> -- Luke
>>
>> Andrew Findlay wrote:
>>> At the recent LDAP conference in Cologne there was wide=20
>> support for an
>>> effort to improve some of the commonly-used schema definitions. In
>>> particular, the fact that groupOfNames does not permit an=20
>> empty group
>>> was felt to be a significant problem.
>>>
>>> To address this problem, I have published an I-D proposing a new
>>> objectclass called groupOfEntries. The I-D is appended and is also
>>> available at:
>>>
>>>
>> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupof
> entries-00.txt
>>> To make adoption as easy as possible, the new object class is
>>> identical to groupOfNames except that it has the ability to
>>> describe empty groups without resorting to tricks and workarounds.
>>>
>>> I would like to see this new class used in place of groupOfNames in
>>> new designs, so I propose to ask IETF to consider the draft for the
>>> Standards Track.
>>>
>>> Comments and suggestions for improvement are welcome, and should be
>>> sent to the ldapext@ietf.org mailing list.
>>>
>>> Andrew
>>>  =20
>>
>> --=20
>> www.padl.com | www.lukehoward.com
>>
>>
>> _______________________________________________
>> Ldapext mailing list
>> Ldapext@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ldapext
>>
>=20
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
>=20


--=20
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 17 23:32:10 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXTnm-0005bI-C4; Mon, 17 Sep 2007 23:31:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXTnk-0005aK-Hc
	for ldapext@ietf.org; Mon, 17 Sep 2007 23:31:04 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXTnj-0005xP-Qs
	for ldapext@ietf.org; Mon, 17 Sep 2007 23:31:04 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8I3UtVI023248; Mon, 17 Sep 2007 22:30:56 -0500
Message-ID: <46EF45F3.9000003@highlandsun.com>
Date: Mon, 17 Sep 2007 20:28:51 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<46EF14CA.8090102@highlandsun.com>
	<52681ACFF63C114F8A3C3651FC9D301F825316@AUSYMS11.ca.com>
In-Reply-To: <52681ACFF63C114F8A3C3651FC9D301F825316@AUSYMS11.ca.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Ramsay, Ron wrote:
> 1) The ambiguity is a result of converting the concept to LDAP.

Granted, but the fact remains that it is unusable in LDAP.

> 2) I don't think you can use nameAndOptionalUID for naming, certainly
> not in the 93 standard. So your comments about children are not really
> appropriate. It's sole use may be in the groupOfUniqueNames object where
> the UID is acting as a generational qualifier. To fully support it,
> though, I think would require a UID attribute in the entry having that
> DN. Oh yes, access control is supposed to use it, too. But the qualifier
> applies to the DN itself and is making a statement about when THIS DN
> was relevant.

It would require the entry to have an x500UniqueIdentifier attribute, yes. So 
far the only standards track schema that uses it is inetOrgPerson.

But you're pointing out a distinction without a difference. If the 
generational qualifier is significant, then it is significant in every context 
where that DN is referenced. E.g.
	cn=bob,o=foo#1 exists
create  cn=my stuff,cn=bob,o=foo

references to "cn=my stuff,cn=bob,o=foo" (and all children of cn=bob,o=foo) 
now depend on that qualifier. If we remove cn=bob,o=foo and come back at a 
later time and create him again, with his child entry
	cn=bob,o=foo#10
	cn=my stuff,cn=bob,o=foo

then there is no way to uniquely reference the "cn=my stuff" child object or 
distinguish it from the previous generation. You cannot separate the relevance 
of "THIS DN" from the uniqueness of its children. If the parent is unique then 
necessarily all of its children are also, but using the nameAndOptionalUID 
syntax doesn't allow this uniqueness to be expressed. The core concept here is 
flawed (yes, in the original X.500 usage as well).

The correct way to handle this is by including the generational qualifier in 
the entry's RDN (making it multivalued), and then you can reference it 
consistently no matter where you need to use it. There is no legitimate use 
for the nameAndOptionalUID syntax at all, in LDAP or X.500.

It's sad, really. They go to the trouble of designing a nice data model with 
consistent naming, then they go and intentionally break it...

> -----Original Message-----
> From: Howard Chu [mailto:hyc@highlandsun.com] 
> Sent: Tuesday, 18 September 2007 9:59 AM
> To: Neal-Joslin, Robert (HP-UX Lab R&D)
> Cc: ldapext@ietf.org; Luke Howard; Andrew Findlay
> Subject: Re: [ldapext] groupOfEntries object class proposal
> 
> Neal-Joslin, Robert (HP-UX Lab R&D) wrote:
>> Hi,
>>
>> I'm almost always in favor of new and better ways to do things.  And I
>> agree with the statements submitted.  But I can see a need to play
>> devil's advocate for this one.  Is there really enough justification
> to
>> warrant this proposal?  What is the likelihood of its success, given
> how
>> entrenched groupOfNames and groupOfUniqueNames is embedded in the
>> existing LDAP application/server security space? 
> 
> Ah, you've just hit another hot-button - groupOfUniqueNames is utterly 
> pointless. I'm all for eradicating the old stuff and pushing
> groupOfEntries as 
> a standard.
> 
> nameAndOptionalUID syntax is inherently broken, it cannot be parsed
> reliably. 
> e.g. - "cn=foo#101" could legitimately be a cn with value "foo#101",
> there's 
> no way to disambiguate it from "cn=foo" with UID "101".
> 
> The entire concept behind this syntax is flawed. What do you do if you
> have a 
> "unique" named object with children? What if the children have unique
> names 
> too? There's only provision for one unique ID in the DN, but
> fundamentally 
> there should be the possibility of a unique ID for every RDN in the DN.
> I.e., 
> if this is really what you want, you should have been using multivalued
> RDNs 
> from the get-go.
> 
> Probably 99% of LDAP applications never even use the UID portion of a 
> nameAndOptionalUID attribute, and the other 1% that use it are broken
> since 
> the syntax is inherently broken.
> 
> I'll happily write up a standards track document to deprecate 
> groupOfUniqueNames and nameAndOptionalUID syntax.

-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 05:41:58 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXZZd-0007So-4G; Tue, 18 Sep 2007 05:40:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXZZc-0007SA-ER
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:40:52 -0400
Received: from 182-7-124-83.dsl.3u.net ([83.124.7.182]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXZZc-0005vE-2P
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:40:52 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 437337A91;
	Tue, 18 Sep 2007 11:40:50 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 07847-10; Tue, 18 Sep 2007 11:40:34 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 5761F7A8F;
	Tue, 18 Sep 2007 11:40:33 +0200 (CEST)
Message-ID: <46EF9D11.3020608@stroeder.com>
Date: Tue, 18 Sep 2007 11:40:33 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Luke Howard <lukeh@padl.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<46EF0DDF.4090806@padl.com>
In-Reply-To: <46EF0DDF.4090806@padl.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Luke Howard wrote:
> I suppose another approach would be to redefine groupOfNames with a new
> OID?

No! Most applications do not look at the OID.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 05:45:19 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXZdl-0003EP-64; Tue, 18 Sep 2007 05:45:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXZdj-00035L-Or
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:45:07 -0400
Received: from 182-7-124-83.dsl.3u.net ([83.124.7.182]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXZdf-00060w-B4
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:45:03 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 2796E7A88;
	Tue, 18 Sep 2007 11:45:02 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 08202-09; Tue, 18 Sep 2007 11:44:45 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id D6EAB70C6;
	Tue, 18 Sep 2007 11:44:44 +0200 (CEST)
Message-ID: <46EF9E0C.1050408@stroeder.com>
Date: Tue, 18 Sep 2007 11:44:44 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: "Neal-Joslin, Robert (HP-UX Lab R&D)" <bob.joslin@hp.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
In-Reply-To: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Neal-Joslin, Robert (HP-UX Lab R&D) wrote:
> What is the likelihood of its success, given how
> entrenched groupOfNames and groupOfUniqueNames is embedded in the
> existing LDAP application/server security space?

For those implementations which are not flexible enough this will take
some time. But in my deployments it's simply a matter of configuration.

Note that this draft does not suggest to completely remove groupOfNames
from core schema. The point is just to deprecate its use in newer
deployments.

> I would
> argue that it would take a sea-change before it would be successful.

web2ldap already supports maintaining groupOfEntries (just
configuration). ;-)

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 05:56:08 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXZnS-0004GM-Ru; Tue, 18 Sep 2007 05:55:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXZnR-0004FM-GP
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:55:09 -0400
Received: from 182-7-124-83.dsl.3u.net ([83.124.7.182]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXZnR-0006GI-1y
	for ldapext@ietf.org; Tue, 18 Sep 2007 05:55:09 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id E52577A93;
	Tue, 18 Sep 2007 11:55:05 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 09455-01; Tue, 18 Sep 2007 11:54:48 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 080A170C5;
	Tue, 18 Sep 2007 11:54:47 +0200 (CEST)
Message-ID: <46EFA067.4050007@stroeder.com>
Date: Tue, 18 Sep 2007 11:54:47 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
In-Reply-To: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Ramsay, Ron wrote:
> Why not try to get the appropriate RFC revised to make 'member'
> optional?

Andrew et al discussed that at LDAPcon. The idea was to stay away from
changing the core LDAPv3 standard specs to avoid too much hassle. IMO
the chance is higher that a new object class specified in a very focused
spec gets easily adopted than all implementors reliably changing an
existing schema element.

> Even simply making 'member' optional in your own implementations, though
> inviting interoperability problems, would seem to have fewer issues than
> introducing a new object class.
> In fact, I think it is common to find
> that 'member' is optional inthe field.

Well, LDAP is for good interop. Isn't it?
I'm too often searching for interop bugs because vendors are not
sticking to standards...

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 06:12:55 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXa3k-00019r-Hl; Tue, 18 Sep 2007 06:12:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXa3j-00013o-AJ
	for ldapext@ietf.org; Tue, 18 Sep 2007 06:11:59 -0400
Received: from colossus.hpl.hp.com ([192.6.10.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXa3a-0002gD-0S
	for ldapext@ietf.org; Tue, 18 Sep 2007 06:11:56 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by colossus.hpl.hp.com (Postfix) with ESMTP id 0D9CC6BA3A
	for <ldapext@ietf.org>; Tue, 18 Sep 2007 11:11:35 +0100 (BST)
X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com
Received: from colossus.hpl.hp.com ([127.0.0.1])
	by localhost (colossus.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id toWurNtkmbHt for <ldapext@ietf.org>;
	Tue, 18 Sep 2007 11:11:34 +0100 (BST)
Received: from kropotkin.hpl.hp.com (kropotkin.hpl.hp.com [16.25.191.14])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by colossus.hpl.hp.com (Postfix) with ESMTP id 8FFF66BA22
	for <ldapext@ietf.org>; Tue, 18 Sep 2007 11:11:33 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
	by kropotkin.hpl.hp.com (Postfix) with ESMTP id B29661480C
	for <ldapext@ietf.org>; Tue, 18 Sep 2007 11:11:32 +0100 (BST)
X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com
Received: from kropotkin.hpl.hp.com ([127.0.0.1])
	by localhost (kropotkin.hpl.hp.com [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP id iRBX4ffqof37 for <ldapext@ietf.org>;
	Tue, 18 Sep 2007 11:11:30 +0100 (BST)
Received: from dunbar-n-1.hpl.hp.com (dunbar-n-1.hpl.hp.com [16.25.171.180])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by kropotkin.hpl.hp.com (Postfix) with ESMTP id CEC9413C69
	for <ldapext@ietf.org>; Tue, 18 Sep 2007 11:11:29 +0100 (BST)
From: Neil Dunbar <neil.dunbar@hp.com>
Organization: TSL, HP Labs, OST
To: ldapext@ietf.org
Subject: Re: [ldapext] groupOfEntries object class proposal
Date: Tue, 18 Sep 2007 11:11:33 +0100
User-Agent: KMail/1.9.7
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
In-Reply-To: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
X-Face: #&?BB/h6:yl&n%g<gVz{,
	rx"c#({r{RxPz!k7v`ymMg<=p">=?utf-8?q?xNnVzL=5CaDDD=60MyMSv7bw=5FS=0A=09?=>2PDR(f,
	8,
	SU1-\w"I&zm0G#K<Gzt9F[b"|oe0X'7'MMw\65E#f=y|R)uwBQE<=?utf-8?q?6*EF=27!2!=0A=09=7CmyR=27f9=3F+ed=24FK=60az75B=7E=7Cv0fQ-NPrh?=
	=?utf-8?q?=3A7=5C?=,uX#t4VGqem&6JA$jiPQ<
	=?utf-8?q?xJr+=3BYhoQV+v7=27f=0A=09z9b0pyN4ghl/OFIaQ2?=@b!/;
	unp|J^]CE$cl"a+5Sq^#K+o$WC}ucL0>lArQ}10xgfle; "
	=?utf-8?q?!=0A=09=24o8zJ1U=3AYPXb=25-M22=7DLk=60RZduOA*q=7DvSlVh?=
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200709181111.33512.neil.dunbar@hp.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Tuesday 18 September 2007 00:21:37 Neal-Joslin, Robert (HP-UX Lab R&D) 
wrote:

> I'm almost always in favor of new and better ways to do things.  And I
> agree with the statements submitted.  But I can see a need to play
> devil's advocate for this one.  Is there really enough justification to
> warrant this proposal?  What is the likelihood of its success, given how
> entrenched groupOfNames and groupOfUniqueNames is embedded in the
> existing LDAP application/server security space?

Well, given that there is already a choice between groupOfUniqueNames and 
groupOfNames, I find that a lot of LDAP apps tend to be parametrised around 
what OC should be considered canonical for the notion of "group". So, in this 
case, sliding in groupOfEntries wouldn't be much of a problem: at least for 
*reading* groups. For creating new ones, that might be irritating. One 
approach might be to sweep periodically and reclassify groupOfNames to 
groupOfEntries within the DIT until apps were writing groupOfEntries 
natively. Since every groupOfNames is also a valid groupOfEntries, you can't 
cause category error by expanding into the superset.

When we shifted to OpenLDAP in HP IT, pretty much all of the Sun ONE groups 
were groupOfUniqueNames - it was a well publicised flag day to shift them 
over to groupOfNames, but I'm pretty sure all apps dealt with the matter 
smoothly. We did some horrible temporary schema hacks before the move, but 
they got tossed as soon as the possibility for group Armageddon had passed 
with very few fatalities.

Cheers,

Neil
-- 
TSL, HP Labs/Office of Strategy and Technology Hewlett-Packard Limited
registered Office:
 Cain Road, Bracknell, Berks
 RG12 1HN                     Registered No: 690597 England

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 07:07:08 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXatY-0006sT-G9; Tue, 18 Sep 2007 07:05:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXatW-0006s8-Mw
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:05:30 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXatW-00086g-A9
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:05:30 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXatV-000IdW-1Q; Tue, 18 Sep 2007 12:05:29 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXatD-0003C2-Pf; Tue, 18 Sep 2007 12:05:11 +0100
Date: Tue, 18 Sep 2007 12:05:11 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: Luke Howard <lukeh@padl.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Message-ID: <20070918110511.GF23300@tile.skills-1st.co.uk>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46EF07BD.1010801@padl.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Tue, Sep 18, 2007 at 09:03:25AM +1000, Luke Howard wrote:

> Another thing that would be useful might be to define the behaviour of 
> nested groups, eg. should the client expand them?

A good point, but I would be wary of being too prescriptive here. Some
servers provide an auxiliary object class that causes the groups to
expanded server-side: that would continue to work with groupOfEntries
(though there is a management issue with anything that triggers
server-side tricks). Whether a *client* should expand groups will
depend on why the client wants the group info in the first place, and I
don't think it is necessary to force the issue one way or the other.

It might be worth adding a statement that makes it clear that
a groupOfEntries can have members of *any* type, so nested groups are
explicitly possible. The precise semantics should be defined by the
application schema designer.

> It would make sense to use this object class for rfc2307bis too 
> (whenever that is completed :-))

Maybe so, but rfc2307bis is a much more complex issue!

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 07:19:05 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXb5d-0001fB-R1; Tue, 18 Sep 2007 07:18:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXb5c-0001X6-C8
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:18:00 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXb5W-0004Tr-5z
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:18:00 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXb5E-000J3x-9Y; Tue, 18 Sep 2007 12:17:36 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXb55-0003F3-Rb; Tue, 18 Sep 2007 12:17:27 +0100
Date: Tue, 18 Sep 2007 12:17:27 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] deprecating groupOfUniqueNames
Message-ID: <20070918111727.GA12296@tile.skills-1st.co.uk>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<46EF14CA.8090102@highlandsun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46EF14CA.8090102@highlandsun.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ldapext@ietf.org, Luke Howard <lukeh@padl.com>, "Neal-Joslin,
	Robert \(HP-UX Lab R&D\)" <bob.joslin@hp.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Mon, Sep 17, 2007 at 04:59:06PM -0700, Howard Chu wrote:

> Probably 99% of LDAP applications never even use the UID portion of a 
> nameAndOptionalUID attribute, and the other 1% that use it are broken since 
> the syntax is inherently broken.

That fits with my experience. I have never yet seen the UID part used,
and no designer who has chosen to use groupOfUniqueNames has ever
given me a good reason for having done so. groupOfUniqueNames also
suffers from the 'no empty groups' problem so it is broken twice over.

> I'll happily write up a standards track document to deprecate 
> groupOfUniqueNames and nameAndOptionalUID syntax.

Good plan. I had considered doing that in the groupOfEntries draft but
decided that the extra justification required would divert attention
from the main point of that draft.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 07:43:39 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXbTl-0005sq-L9; Tue, 18 Sep 2007 07:42:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXbTk-0005sk-Tz
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:42:56 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXbTg-0004wn-N9
	for ldapext@ietf.org; Tue, 18 Sep 2007 07:42:56 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXbTc-000JkS-Qa; Tue, 18 Sep 2007 12:42:48 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXbTP-0003FE-0S; Tue, 18 Sep 2007 12:42:35 +0100
Date: Tue, 18 Sep 2007 12:42:34 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Message-ID: <20070918114234.GB12296@tile.skills-1st.co.uk>
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Tue, Sep 18, 2007 at 12:44:33PM +1000, Ramsay, Ron wrote:

> Why not try to get the appropriate RFC revised to make 'member'
> optional?

The trouble with changing an existing schema element is that users
would have to synchronise the change across all their clients and
servers. It seems a bad idea to create a situation where each end of a
network connection could be working to a different definition.

> Even simply making 'member' optional in your own implementations, though
> inviting interoperability problems, would seem to have fewer issues than
> introducing a new object class. In fact, I think it is common to find
> that 'member' is optional inthe field.

That suggests that people are deliberately changing the standard
schema definitions, which is bad because of the interoperability
problems that could be caused.

I never use groupOfNames in my own designs for exactly this reason, so
I always define a new group class that permits empty groups. While
this is an easy thing to do, it appears that many people do not like
to define new classes which leads to nasty hacks and trouble stored up
for the future. I hope that by defining a standard class with the
behaviour that people actually need we can encourage better practices.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 09:20:57 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXczP-0002Mj-Gd; Tue, 18 Sep 2007 09:19:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXczO-0002KV-DG
	for ldapext@ietf.org; Tue, 18 Sep 2007 09:19:42 -0400
Received: from mlnya402er.ml.com ([199.43.38.100])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXczL-0002o6-NY
	for ldapext@ietf.org; Tue, 18 Sep 2007 09:19:40 -0400
Received: from MLNYA354BH.amrs.win.ml.com (smtp2.wideip.ml.com [146.125.98.4])
	by mlnya402er.ml.com (Postfix) with ESMTP id ED70FD4011;
	Tue, 18 Sep 2007 09:19:39 -0400 (EDT)
Importance: normal
Priority: normal
Received: from MLNYC801BH.amrs.win.ml.com ([141.128.12.13]) by
	MLNYA354BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Tue, 18 Sep 2007 09:19:39 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	MLNYC801BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Tue, 18 Sep 2007 09:19:24 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] groupOfEntries object class proposal
Date: Tue, 18 Sep 2007 09:19:24 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E30900199C279@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] groupOfEntries object class proposal
thread-index: Acf5f861HGEIhMy/RfSpCnE7LCtKBQAAFimwAAcfJqAAFnHEUA==
References: <20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>,
	"Andrew Findlay" <andrew.findlay@skills-1st.co.uk>
X-OriginalArrivalTime: 18 Sep 2007 13:19:24.0722 (UTC)
	FILETIME=[884AC120:01C7F9F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

This approach gets my vote. Is it practical?=20

-----Original Message-----
From: Ramsay, Ron [mailto:Ron.Ramsay@ca.com]=20
Sent: Monday, September 17, 2007 10:45 PM
To: Andrew Findlay
Cc: ldapext@ietf.org
Subject: RE: [ldapext] groupOfEntries object class proposal

Why not try to get the appropriate RFC revised to make 'member'
optional?

Even simply making 'member' optional in your own implementations, though
inviting interoperability problems, would seem to have fewer issues than
introducing a new object class. In fact, I think it is common to find
that 'member' is optional inthe field.

-----Original Message-----
From: Neal-Joslin, Robert (HP-UX Lab R&D) [mailto:bob.joslin@hp.com]=20
Sent: Tuesday, 18 September 2007 9:22 AM
To: Luke Howard; Andrew Findlay
Cc: ldapext@ietf.org
Subject: RE: [ldapext] groupOfEntries object class proposal

Hi,

I'm almost always in favor of new and better ways to do things.  And I
agree with the statements submitted.  But I can see a need to play
devil's advocate for this one.  Is there really enough justification to
warrant this proposal?  What is the likelihood of its success, given how
entrenched groupOfNames and groupOfUniqueNames is embedded in the
existing LDAP application/server security space?  This is a very
low-level concept to LDAP, and thus convincing all application/server
developers to revolutionize seems a unlikely scenario.  And I would
argue that it would take a sea-change before it would be successful.
I.E. would this proposal be successful if only 50% or even 75% of
applications/servers support it?

Bob
=20

> -----Original Message-----
> From: Luke Howard [mailto:lukeh@padl.com]=20
> Sent: Monday, September 17, 2007 4:03 PM
> To: Andrew Findlay
> Cc: ldapext@ietf.org
> Subject: Re: [ldapext] groupOfEntries object class proposal
>=20
> Another thing that would be useful might be to define the=20
> behaviour of=20
> nested groups, eg. should the client expand them?
>=20
> It would make sense to use this object class for rfc2307bis too=20
> (whenever that is completed :-))
>=20
> -- Luke
>=20
> Andrew Findlay wrote:
> > At the recent LDAP conference in Cologne there was wide=20
> support for an
> > effort to improve some of the commonly-used schema definitions. In
> > particular, the fact that groupOfNames does not permit an=20
> empty group
> > was felt to be a significant problem.
> >
> > To address this problem, I have published an I-D proposing a new
> > objectclass called groupOfEntries. The I-D is appended and is also
> > available at:
> >
> >=20
> http://www.ietf.org/internet-drafts/draft-findlay-ldap-groupof
entries-00.txt
> >
> > To make adoption as easy as possible, the new object class is
> > identical to groupOfNames except that it has the ability to
> > describe empty groups without resorting to tricks and workarounds.
> >
> > I would like to see this new class used in place of groupOfNames in
> > new designs, so I propose to ask IETF to consider the draft for the
> > Standards Track.
> >
> > Comments and suggestions for improvement are welcome, and should be
> > sent to the ldapext@ietf.org mailing list.
> >
> > Andrew
> >  =20
>=20
>=20
> --=20
> www.padl.com | www.lukehoward.com
>=20
>=20
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
>=20

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 10:18:56 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXdtr-0006OP-PH; Tue, 18 Sep 2007 10:18:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXdtr-0006C7-9f
	for ldapext@ietf.org; Tue, 18 Sep 2007 10:18:03 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXdtg-000458-MZ
	for ldapext@ietf.org; Tue, 18 Sep 2007 10:17:53 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXdtf-000O0d-9z; Tue, 18 Sep 2007 15:17:51 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXdtS-0003Ji-PM; Tue, 18 Sep 2007 15:17:38 +0100
Date: Tue, 18 Sep 2007 15:17:38 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: "Liben, Michael (GTI)" <michael_liben@ml.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Message-ID: <20070918141738.GC12296@tile.skills-1st.co.uk>
References: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
	<DD9F4CC53AE89944A5C825781D5E30900199C279@MLNYC727MB.amrs.win.ml.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E30900199C279@MLNYC727MB.amrs.win.ml.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ldapext@ietf.org, "Ramsay, Ron" <Ron.Ramsay@ca.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Tue, Sep 18, 2007 at 09:19:24AM -0400, Liben, Michael (GTI) wrote:

> This approach gets my vote. Is it practical? 
> 
> -----Original Message-----
> From: Ramsay, Ron [mailto:Ron.Ramsay@ca.com] 
> Sent: Monday, September 17, 2007 10:45 PM
> Subject: RE: [ldapext] groupOfEntries object class proposal
> 
> Why not try to get the appropriate RFC revised to make 'member'
> optional?

It is clearly *possible* to change the definitions in most existing
LDAP servers. We know that people do it (breaking the standard in the
process). However, I cannot see IETF accepting the re-definition of an
existing class when a cleaner solution is available. (though if the
community *is* prepared to redefine existing things then I have a much
longer list of targets :-))

Adding a new object class to most servers is very easy. I have direct
experience of this with OpenLDAP, IBM Tivoli Directory Server, and
Oracle Internet Directory. In each case I could give you a small file
and simple instructions to add the groupOfEntries class, so
implementors would not have to wait for server suppliers to roll it
into a new release.

People running existing LDAP systems would have a choice: stick with
groupOfNames and its associated workarounds, or switch to
groupOfEntries. IF they choose to switch, they should audit the
searches and writes done by client applications to see whether any
changes are needed.

People designing new systems would also have the same choice, but
adopting groupOfEntries would give them benefits.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 19:35:49 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXmZZ-00082D-Vw; Tue, 18 Sep 2007 19:33:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXmZY-0007tr-QA
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:33:40 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXmZP-0007S7-LH
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:33:37 -0400
Received: from [202.164.192.219] (helo=[192.168.99.100])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IXmYy-0001eg-GO; Wed, 19 Sep 2007 09:33:05 +1000
Message-ID: <46F0602C.2080806@eb2bcom.com>
Date: Wed, 19 Sep 2007 09:33:00 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
	<20070918114234.GB12296@tile.skills-1st.co.uk>
In-Reply-To: <20070918114234.GB12296@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Andrew,

Andrew Findlay wrote:
> I never use groupOfNames in my own designs for exactly this reason, so
> I always define a new group class that permits empty groups. While
> this is an easy thing to do, it appears that many people do not like
> to define new classes which leads to nasty hacks and trouble stored up
> for the future. I hope that by defining a standard class with the
> behaviour that people actually need we can encourage better practices.

Instead of defining a specific object class, perhaps all we need is a
*convention* that any entry that contains the member attribute is to
be treated as a group.

Regards,
Steven

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 19:36:21 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXmbl-0005QF-Ez; Tue, 18 Sep 2007 19:35:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXmbj-0005Aw-JC
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:35:55 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXmbi-0007VJ-CJ
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:35:55 -0400
Received: from [202.164.192.219] (helo=[192.168.99.100])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IXmba-0001h7-Ln; Wed, 19 Sep 2007 09:35:47 +1000
Message-ID: <46F060CD.20008@eb2bcom.com>
Date: Wed, 19 Sep 2007 09:35:41 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
In-Reply-To: <20070918110511.GF23300@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Luke Howard <lukeh@padl.com>, ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Andrew,

Andrew Findlay wrote:
> On Tue, Sep 18, 2007 at 09:03:25AM +1000, Luke Howard wrote:
> 
>> Another thing that would be useful might be to define the behaviour of 
>> nested groups, eg. should the client expand them?
> 
> A good point, but I would be wary of being too prescriptive here. Some
> servers provide an auxiliary object class that causes the groups to
> expanded server-side: that would continue to work with groupOfEntries
> (though there is a management issue with anything that triggers
> server-side tricks). Whether a *client* should expand groups will
> depend on why the client wants the group info in the first place, and I
> don't think it is necessary to force the issue one way or the other.
> 
> It might be worth adding a statement that makes it clear that
> a groupOfEntries can have members of *any* type, so nested groups are
> explicitly possible. The precise semantics should be defined by the
> application schema designer.

The advantage of *not* having nested groups is that it is sufficient
to just read the values of the member attribute to determine group
membership. If there are nested groups, then it is necessary to
read each of the entries named in the values of the member attribute
to see which of them, if any, are themselves groups. That could be
a big performance hit for a group with a large set of members.

If nested groups are to be allowed, then I would rather see the
nested groups listed in a separate attribute, e.g., called nestedGroups,
so that implementations only need to read the entries that really
are nested groups.

Regards,
Steven

> 
>> It would make sense to use this object class for rfc2307bis too 
>> (whenever that is completed :-))
> 
> Maybe so, but rfc2307bis is a much more complex issue!
> 
> Andrew

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 18 19:46:46 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXmlJ-0005By-Fx; Tue, 18 Sep 2007 19:45:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXmlH-0005Bt-QK
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:45:47 -0400
Received: from au.padl.com ([203.13.32.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXmlG-0003y5-W7
	for ldapext@ietf.org; Tue, 18 Sep 2007 19:45:47 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8INjA7m005170
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 18 Sep 2007 23:45:13 GMT
Message-ID: <46F063BE.5020900@padl.com>
Date: Wed, 19 Sep 2007 09:48:14 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
In-Reply-To: <46F060CD.20008@eb2bcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Steven Legg wrote:
>
> If nested groups are to be allowed, then I would rather see the
> nested groups listed in a separate attribute, e.g., called nestedGroups,
> so that implementations only need to read the entries that really
> are nested groups.
This is what Novell did with eDirectory (they also have an option where 
nested members are presented as values of member).

AD and rfc2307bis, however, simply have groups listed a values of 
member; the client is responsible for dereferencing and transiting if 
required.

-- Luke

-- 
www.padl.com | www.lukehoward.com


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 04:51:20 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXvFz-00030d-Hg; Wed, 19 Sep 2007 04:50:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXvFy-0002zu-Hl
	for ldapext@ietf.org; Wed, 19 Sep 2007 04:50:02 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXvFn-0003U6-PL
	for ldapext@ietf.org; Wed, 19 Sep 2007 04:49:57 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXvFM-000MTG-OT; Wed, 19 Sep 2007 09:49:24 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXvF8-0004js-TE; Wed, 19 Sep 2007 09:49:10 +0100
Date: Wed, 19 Sep 2007 09:49:10 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Message-ID: <20070919084910.GD12296@tile.skills-1st.co.uk>
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
	<20070918114234.GB12296@tile.skills-1st.co.uk>
	<46F0602C.2080806@eb2bcom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46F0602C.2080806@eb2bcom.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 09:33:00AM +1000, Steven Legg wrote:

> Instead of defining a specific object class, perhaps all we need is a
> *convention* that any entry that contains the member attribute is to
> be treated as a group.

It would still need an object class that permits the member attribute.
How would such a convention represent an empty group?

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 05:35:20 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXvxE-0002Q5-0m; Wed, 19 Sep 2007 05:34:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXvxB-0002N1-P1
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:34:41 -0400
Received: from 169-62-124-83.dsl.3u.net ([83.124.62.169]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXvxB-0002aE-4x
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:34:41 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 6A5C47A88;
	Wed, 19 Sep 2007 11:34:39 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15961-02; Wed, 19 Sep 2007 11:34:21 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 53E4F7ABC;
	Wed, 19 Sep 2007 11:34:21 +0200 (CEST)
Message-ID: <46F0ED1E.10004@stroeder.com>
Date: Wed, 19 Sep 2007 11:34:22 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
In-Reply-To: <46F060CD.20008@eb2bcom.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ldapext@ietf.org
Subject: [ldapext] Nested group (was: groupOfEntries object class proposal)
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Changed subject because this is another thing to discuss.

Steven Legg wrote:
> 
> The advantage of *not* having nested groups is that it is sufficient
> to just read the values of the member attribute to determine group
> membership. If there are nested groups, then it is necessary to
> read each of the entries named in the values of the member attribute
> to see which of them, if any, are themselves groups. That could be
> a big performance hit for a group with a large set of members.

I fully agree. One really has to think twice whether nested groups are
really needed in a particular use-case and worth the performance hit.

> If nested groups are to be allowed, then I would rather see the
> nested groups listed in a separate attribute, e.g., called nestedGroups,
> so that implementations only need to read the entries that really
> are nested groups.

+1

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 05:43:15 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXw4Y-00022C-7o; Wed, 19 Sep 2007 05:42:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXw4X-0001wy-9C
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:42:17 -0400
Received: from 169-62-124-83.dsl.3u.net ([83.124.62.169]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IXw4R-0004w8-TF
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:42:17 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 9BEE87ABC;
	Wed, 19 Sep 2007 11:41:50 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15961-03; Wed, 19 Sep 2007 11:41:34 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 9ACE87A88;
	Wed, 19 Sep 2007 11:41:33 +0200 (CEST)
Message-ID: <46F0EECE.4090603@stroeder.com>
Date: Wed, 19 Sep 2007 11:41:34 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>	<20070918114234.GB12296@tile.skills-1st.co.uk>
	<46F0602C.2080806@eb2bcom.com>
In-Reply-To: <46F0602C.2080806@eb2bcom.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Steven Legg wrote:
> 
> Instead of defining a specific object class, perhaps all we need is a
> *convention* that any entry that contains the member attribute is to
> be treated as a group.

My first impression was that this would change the semantics of the
member attribute defined in the core schema and I'd like to stay out of
that business. But RFC 4519 already states something similar:

------------------------------- snip -------------------------------
2.17.  'member'

   The 'member' attribute type contains the distinguished names of
   objects that are on a list or in a group.  Each name is one value of
   this multi-valued attribute.
   (Source: X.520 [X.520])
------------------------------- snip -------------------------------

Hmm, I'm not sure whether some deployments (ab)use 'member' for other
purposes.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 05:46:57 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXw8A-0005Vi-D7; Wed, 19 Sep 2007 05:46:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXw88-0005Tz-Q8
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:46:00 -0400
Received: from 169-62-124-83.dsl.3u.net ([83.124.62.169]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IXw83-00053W-7y
	for ldapext@ietf.org; Wed, 19 Sep 2007 05:45:56 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 352E37ABC;
	Wed, 19 Sep 2007 11:45:47 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15485-09; Wed, 19 Sep 2007 11:45:30 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id B263D7A88;
	Wed, 19 Sep 2007 11:45:29 +0200 (CEST)
Message-ID: <46F0EFBA.8010309@stroeder.com>
Date: Wed, 19 Sep 2007 11:45:30 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>	<20070918114234.GB12296@tile.skills-1st.co.uk>	<46F0602C.2080806@eb2bcom.com>
	<20070919084910.GD12296@tile.skills-1st.co.uk>
In-Reply-To: <20070919084910.GD12296@tile.skills-1st.co.uk>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 09:33:00AM +1000, Steven Legg wrote:
> 
>> Instead of defining a specific object class, perhaps all we need is a
>> *convention* that any entry that contains the member attribute is to
>> be treated as a group.
> 
> It would still need an object class that permits the member attribute.
> How would such a convention represent an empty group?

I guess Steven meant that it would be sufficient to simply search for

(member=<DN>)

for determining group membership for <DN> instead of

(&(|(objectClass=groupOfNames)(objectClass=groupOfEntries))(member=<DN>))

So one could use any object class for group entries which suits the
deployment needs as long as it permits 'member'.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 06:48:24 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXx58-0003F2-IU; Wed, 19 Sep 2007 06:46:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXx57-0003Ee-Hr
	for ldapext@ietf.org; Wed, 19 Sep 2007 06:46:57 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXx54-0006LH-5B
	for ldapext@ietf.org; Wed, 19 Sep 2007 06:46:57 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXx4y-0000mB-7Q; Wed, 19 Sep 2007 11:46:48 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IXx4u-0004mh-Dk; Wed, 19 Sep 2007 11:46:44 +0100
Date: Wed, 19 Sep 2007 11:46:44 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: Steven Legg <steven.legg@eb2bcom.com>, Luke Howard <lukeh@padl.com>,
	Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
Subject: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919104644.GE12296@tile.skills-1st.co.uk>
References: <46F0ED1E.10004@stroeder.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <46F0ED1E.10004@stroeder.com> <46F063BE.5020900@padl.com>
	<46F060CD.20008@eb2bcom.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 09:35:41AM +1000, Steven Legg wrote:

> The advantage of *not* having nested groups is that it is sufficient
> to just read the values of the member attribute to determine group
> membership. If there are nested groups, then it is necessary to
> read each of the entries named in the values of the member attribute
> to see which of them, if any, are themselves groups. That could be
> a big performance hit for a group with a large set of members.

Good point. Servers have more options here, but a client dealing with
nested groups has to do a silly amount of work.

> If nested groups are to be allowed, then I would rather see the
> nested groups listed in a separate attribute, e.g., called nestedGroups,
> so that implementations only need to read the entries that really
> are nested groups.

That would be a great improvement in efficiency. There would also need
to be an auxiliary object class to identify groups that might contain
such attributes - nestedGroupObject or perhaps groupOfGroups.
(Or the groupOfEntries class could permit the nestedGroup attribute as
well as the member attribute. I think I would prefer a separate
class.)

On Wed, Sep 19, 2007 at 09:48:14AM +1000, Luke Howard wrote:

> This is what Novell did with eDirectory (they also have an option where 
> nested members are presented as values of member).

It is certainly more efficient if the server is prepared to do things
like that, but it does require new code so it is less likely to
implemented by all servers. There is also the question of how to
manage such an entry as the client clearly cannot read the member
attributes and send updates based on what it sees.

> AD and rfc2307bis, however, simply have groups listed a values of 
> member; the client is responsible for dereferencing and transiting if 
> required.

There are enough performance problems with LDAP NIS group methods
already! Adding client-side nested groups can only make it worse...

On Wed, Sep 19, 2007 at 11:34:22AM +0200, Michael Ströder wrote:

> I fully agree. One really has to think twice whether nested groups are
> really needed in a particular use-case and worth the performance hit.
> 
> > If nested groups are to be allowed, then I would rather see the
> > nested groups listed in a separate attribute, e.g., called nestedGroups,
> > so that implementations only need to read the entries that really
> > are nested groups.
> 
> +1

It looks as if the nested groups issue needs tackling. Should I expand
this I-D to include it? The consensus seems to be:

1)	groupOfEntries member attributes should not point to groups
	whose members are to be considered part of the group being
	described.
	
	I see no problem with allowing them to point to groups if
	expansion/nesting/inclusion is not required.

2)	There should be a new aux class and attribute to support
	client-side group nesting.

	Servers can support group nesting in more efficient ways and
	some of them already do. Should there be an attempt to
	standardise the schema that supports this?

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 09:49:27 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXzql-0006qV-W6; Wed, 19 Sep 2007 09:44:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXzqk-0006mV-58
	for ldapext@ietf.org; Wed, 19 Sep 2007 09:44:18 -0400
Received: from mlnyc901er.ml.com ([199.43.64.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXzqf-0000Nc-Eg
	for ldapext@ietf.org; Wed, 19 Sep 2007 09:44:14 -0400
Received: from mlnyc854bh.amrs.win.ml.com (smtp2.wideip.ml.com
	[141.128.12.204])
	by mlnyc901er.ml.com (Postfix) with ESMTP id 29BD356426;
	Wed, 19 Sep 2007 09:44:14 -0400 (EDT)
Importance: normal
Priority: normal
Received: from mlnya302bh.amrs.win.ml.com ([170.240.239.47]) by
	mlnyc854bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 09:43:47 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	mlnya302bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 09:43:46 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] Nested group (was: groupOfEntries object class proposal)
Date: Wed, 19 Sep 2007 09:43:45 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E3090044981@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group (was: groupOfEntries object class
	proposal)
thread-index: Acf6q17aDbPM/V9OSfiPX67REF6e0QAEbt6g
References: <46F0ED1E.10004@stroeder.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: "Andrew Findlay" <andrew.findlay@skills-1st.co.uk>,
	"Steven Legg" <steven.legg@eb2bcom.com>, "Luke Howard" <lukeh@padl.com>,
	=?iso-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
X-OriginalArrivalTime: 19 Sep 2007 13:43:46.0490 (UTC)
	FILETIME=[19FC99A0:01C7FAC3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

The nestedGroup attribute may not add much value. The members of the =
group would still need to be examined individually to determine if they =
in turn contain the member attribute.

-----Original Message-----
From: Andrew Findlay [mailto:andrew.findlay@skills-1st.co.uk]=20
Sent: Wednesday, September 19, 2007 6:47 AM
To: Steven Legg; Luke Howard; Michael Str=F6der
Cc: ldapext@ietf.org
Subject: [ldapext] Nested group (was: groupOfEntries object class =
proposal)

On Wed, Sep 19, 2007 at 09:35:41AM +1000, Steven Legg wrote:

> The advantage of *not* having nested groups is that it is sufficient
> to just read the values of the member attribute to determine group
> membership. If there are nested groups, then it is necessary to
> read each of the entries named in the values of the member attribute
> to see which of them, if any, are themselves groups. That could be
> a big performance hit for a group with a large set of members.

Good point. Servers have more options here, but a client dealing with
nested groups has to do a silly amount of work.

> If nested groups are to be allowed, then I would rather see the
> nested groups listed in a separate attribute, e.g., called =
nestedGroups,
> so that implementations only need to read the entries that really
> are nested groups.

That would be a great improvement in efficiency. There would also need
to be an auxiliary object class to identify groups that might contain
such attributes - nestedGroupObject or perhaps groupOfGroups.
(Or the groupOfEntries class could permit the nestedGroup attribute as
well as the member attribute. I think I would prefer a separate
class.)

On Wed, Sep 19, 2007 at 09:48:14AM +1000, Luke Howard wrote:

> This is what Novell did with eDirectory (they also have an option =
where=20
> nested members are presented as values of member).

It is certainly more efficient if the server is prepared to do things
like that, but it does require new code so it is less likely to
implemented by all servers. There is also the question of how to
manage such an entry as the client clearly cannot read the member
attributes and send updates based on what it sees.

> AD and rfc2307bis, however, simply have groups listed a values of=20
> member; the client is responsible for dereferencing and transiting if=20
> required.

There are enough performance problems with LDAP NIS group methods
already! Adding client-side nested groups can only make it worse...

On Wed, Sep 19, 2007 at 11:34:22AM +0200, Michael Str=F6der wrote:

> I fully agree. One really has to think twice whether nested groups are
> really needed in a particular use-case and worth the performance hit.
>=20
> > If nested groups are to be allowed, then I would rather see the
> > nested groups listed in a separate attribute, e.g., called =
nestedGroups,
> > so that implementations only need to read the entries that really
> > are nested groups.
>=20
> +1

It looks as if the nested groups issue needs tackling. Should I expand
this I-D to include it? The consensus seems to be:

1)	groupOfEntries member attributes should not point to groups
	whose members are to be considered part of the group being
	described.
=09
	I see no problem with allowing them to point to groups if
	expansion/nesting/inclusion is not required.

2)	There should be a new aux class and attribute to support
	client-side group nesting.

	Servers can support group nesting in more efficient ways and
	some of them already do. Should there be an attempt to
	standardise the schema that supports this?

Andrew
--=20
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 10:07:16 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY0Au-0001Cs-DU; Wed, 19 Sep 2007 10:05:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY0At-0001Ck-Us
	for ldapext@ietf.org; Wed, 19 Sep 2007 10:05:07 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY0An-0002fd-OU
	for ldapext@ietf.org; Wed, 19 Sep 2007 10:05:07 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY0AY-00068M-UM; Wed, 19 Sep 2007 15:04:47 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY0AK-0004sm-QX; Wed, 19 Sep 2007 15:04:32 +0100
Date: Wed, 19 Sep 2007 15:04:32 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: "Liben, Michael (GTI)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919140432.GG12296@tile.skills-1st.co.uk>
References: <20070919104644.GE12296@tile.skills-1st.co.uk>
	<DD9F4CC53AE89944A5C825781D5E3090044981@MLNYC727MB.amrs.win.ml.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044981@MLNYC727MB.amrs.win.ml.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ldapext@ietf.org, Luke Howard <lukeh@padl.com>,
	Steven Legg <steven.legg@eb2bcom.com>,
	Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 09:43:45AM -0400, Liben, Michael (GTI) wrote:

> The nestedGroup attribute may not add much value. The members of the
> group would still need to be examined individually to determine if they
> in turn contain the member attribute.

Only the nestedGroup members would have to be expanded. 'member'
attributes would only point to direct members, so they would not need
to be read.

In a group with 5000 direct members and 25 nested groups the
client could avoid 5000 operations when looking to see if a particular
entry is a member. It would only need to expand the 25 nested groups,
and would not even have to read the direct member entries.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 10:07:41 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY0Cl-0002Ly-Op; Wed, 19 Sep 2007 10:07:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY0Ck-0002Lt-EW
	for ldapext@ietf.org; Wed, 19 Sep 2007 10:07:02 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY0Cj-0000uH-Nm
	for ldapext@ietf.org; Wed, 19 Sep 2007 10:07:02 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id 227851638E5;
	Wed, 19 Sep 2007 14:07:01 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>, ldapext@ietf.org
In-Reply-To: <20070919104644.GE12296@tile.skills-1st.co.uk>
References: <46F0ED1E.10004@stroeder.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=UTF-8
Organization: Samba Team
Date: Wed, 19 Sep 2007 10:07:00 -0400
Message-Id: <1190210820.31971.105.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: Luke Howard <lukeh@padl.com>, Steven Legg <steven.legg@eb2bcom.com>,
	Michael =?ISO-8859-1?Q?Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 11:46 +0100, Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 09:35:41AM +1000, Steven Legg wrote:
>=20
> > The advantage of *not* having nested groups is that it is sufficient
> > to just read the values of the member attribute to determine group
> > membership. If there are nested groups, then it is necessary to
> > read each of the entries named in the values of the member attribute
> > to see which of them, if any, are themselves groups. That could be
> > a big performance hit for a group with a large set of members.
>=20
> Good point. Servers have more options here, but a client dealing with
> nested groups has to do a silly amount of work.

No, its not a good point, as that happens only if the designer of the
directory decides to use this feature.
If he so decides, he knows the limits and the problems he goes on doing
that and it is his responsibility.

Let's not try to be smarter than necessary, a schema should not be used
to enforce a way to do things.

> > If nested groups are to be allowed, then I would rather see the
> > nested groups listed in a separate attribute, e.g., called nestedGrou=
ps,
> > so that implementations only need to read the entries that really
> > are nested groups.
>=20
> That would be a great improvement in efficiency. There would also need
> to be an auxiliary object class to identify groups that might contain
> such attributes - nestedGroupObject or perhaps groupOfGroups.
> (Or the groupOfEntries class could permit the nestedGroup attribute as
> well as the member attribute. I think I would prefer a separate
> class.)

I really don't see any value in using a different attribute.
An apple is always an apple even if you call it orange. If that
attribute is present, the client has to do all the work anyway.
The only difference is that you have to use a more complex filter to
show the members of a group and probably also 2 indexes instead of just
one.

> On Wed, Sep 19, 2007 at 09:48:14AM +1000, Luke Howard wrote:
>=20
> > This is what Novell did with eDirectory (they also have an option whe=
re=20
> > nested members are presented as values of member).

Which is bad because at that point the client have no way to tell which
group exactly a user is member of. It is good only for simple
authorization schemes (and was probably done to keep old unix clients
happy).

> It is certainly more efficient if the server is prepared to do things
> like that, but it does require new code so it is less likely to
> implemented by all servers. There is also the question of how to
> manage such an entry as the client clearly cannot read the member
> attributes and send updates based on what it sees.

exactly, it is just a hack, necessary in some cases, but just an hack.

> > AD and rfc2307bis, however, simply have groups listed a values of=20
> > member; the client is responsible for dereferencing and transiting if=
=20
> > required.
>=20
> There are enough performance problems with LDAP NIS group methods
> already! Adding client-side nested groups can only make it worse...

It's up to you to use nested groups or not. It's not mandatory, and
doing it client side has also benefits.

Suppose I need to check user A is in group A, where group A has 128 sub
groups, with others again.
Now if you do server side resolution at each query of the member
attribute you have to fully unwind all groups every time (sure caching
helps), instead if you are a client, you can stop at the first group you
find containing the user (in case it is group A it is much more
convenient). Also, clients smart enough to understand nested groups, can
probably be smart enough to do some smart caching, and beating the
server a lot less often.

> On Wed, Sep 19, 2007 at 11:34:22AM +0200, Michael Str=C3=B6der wrote:
>=20
> > I fully agree. One really has to think twice whether nested groups ar=
e
> > really needed in a particular use-case and worth the performance hit.
> >=20
> > > If nested groups are to be allowed, then I would rather see the
> > > nested groups listed in a separate attribute, e.g., called nestedGr=
oups,
> > > so that implementations only need to read the entries that really
> > > are nested groups.
> >=20
> > +1
>=20
> It looks as if the nested groups issue needs tackling. Should I expand
> this I-D to include it? The consensus seems to be:

FWIW I think your original proposal is much simpler, and lets architects
decide what to do without artificial separations of members depending on
the fact they are groups or users.

Also it is more consistent, what if I have an Entry object listed as
emmebr in another that lately is added a groupOfEntries objectclass to?
Should the server go around all other groupOfEntries objects in search
for members to be changed to nestedGroupObject ?

Keeping it just a member make this a non-issue from the consistency PoV.

> 1)	groupOfEntries member attributes should not point to groups
> 	whose members are to be considered part of the group being
> 	described.
> =09
> 	I see no problem with allowing them to point to groups if
> 	expansion/nesting/inclusion is not required.

I see no problem, full stop. It's the architect responsibility to find
the right trade-off .

>=20
> 2)	There should be a new aux class and attribute to support
> 	client-side group nesting.
>=20
> 	Servers can support group nesting in more efficient ways and
> 	some of them already do. Should there be an attempt to
> 	standardise the schema that supports this?

IMHO no.

Simo.

--=20
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 11:24:54 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY1NM-0000W3-3m; Wed, 19 Sep 2007 11:22:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY1NK-0000Vh-Jn
	for ldapext@ietf.org; Wed, 19 Sep 2007 11:22:02 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY1NJ-0003C4-NM
	for ldapext@ietf.org; Wed, 19 Sep 2007 11:22:02 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY1NI-0008pF-3j; Wed, 19 Sep 2007 16:22:00 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY1Mz-0004ui-9o; Wed, 19 Sep 2007 16:21:41 +0100
Date: Wed, 19 Sep 2007 16:21:41 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919152141.GH12296@tile.skills-1st.co.uk>
References: <46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1190210820.31971.105.camel@localhost.localdomain>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: Steven Legg <steven.legg@eb2bcom.com>, Luke Howard <lukeh@padl.com>,
	ldapext@ietf.org, Michael =?iso-8859-1?Q?Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 10:07:00AM -0400, simo wrote:

> > > If nested groups are to be allowed, then I would rather see the
> > > nested groups listed in a separate attribute, e.g., called nestedGroups,
> > > so that implementations only need to read the entries that really
> > > are nested groups.
> > 
> > That would be a great improvement in efficiency. There would also need
> > to be an auxiliary object class to identify groups that might contain
> > such attributes - nestedGroupObject or perhaps groupOfGroups.
> > (Or the groupOfEntries class could permit the nestedGroup attribute as
> > well as the member attribute. I think I would prefer a separate
> > class.)
> 
> I really don't see any value in using a different attribute.
> An apple is always an apple even if you call it orange. If that
> attribute is present, the client has to do all the work anyway.
> The only difference is that you have to use a more complex filter to
> show the members of a group and probably also 2 indexes instead of just
> one.

The efficiency gain comes from not having to read the entries of the
direct members just to find out whether they are actually nested
groups or not. This could make a massive difference in cases where a
group has a lot of direct members as well as a few nested groups.

The complexity in determining whether a given DN is a member of
a potentially-nested group is much the same whether we use 'member'
for everything or 'member' and 'nestedGroup', but using the two
different attributes can save a vast number of LDAP operations.
Consider this algorithm:

IsAMember( subjectDN, groupDN ) {
	Match subjectDN against 'member' attribute of group entry:
	stop if it matches, the DN is a member.

	for each nested group {
		if IsAMember( subjectDN, nestedGroupDN )
		then stop, the DN is a member.
	}

	The DN is not a member
}

The first match is a single LDAP search on the basic group entry.

The foreach loop requires one LDAP search on the base, plus:

	If we only use 'member' attributes,
	one LDAP search on each member to find out what it is
	before calling the procedure recursively on each nested group.

	If we separate direct members from nested groups using
	different attributes, we recurse immediately with no extra
	LDAP ops.

Hmm: I think the different-attributes case is actually *simpler* to
code. The algorithm for enumerating members is almost identical.

> > On Wed, Sep 19, 2007 at 09:48:14AM +1000, Luke Howard wrote:
> > 
> > > This is what Novell did with eDirectory (they also have an option where 
> > > nested members are presented as values of member).
> 
> Which is bad because at that point the client have no way to tell which
> group exactly a user is member of. It is good only for simple
> authorization schemes (and was probably done to keep old unix clients
> happy).

This sort of thing has a value in many authorisation cases. Clients
often need to know 'is this user allowed to do X' where the permission
is expressed as membership of a group. Nested groups are extremely
useful in this scenario as you often want one level to classify the
users by roles and a second level to define what each role is allowed
to do. The client just wants a yes/no answer and is not often
interested in which group membership chain actually permitted the
access. If the server supports server-side nesting then a single LDAP
search will answer the question.

> It's up to you to use nested groups or not. It's not mandatory, and
> doing it client side has also benefits.

Indeed, and I would not want to stop anyone doing so.

> Suppose I need to check user A is in group A, where group A has 128 sub
> groups, with others again.
> Now if you do server side resolution at each query of the member
> attribute you have to fully unwind all groups every time (sure caching
> helps), instead if you are a client, you can stop at the first group you
> find containing the user (in case it is group A it is much more
> convenient). Also, clients smart enough to understand nested groups, can
> probably be smart enough to do some smart caching, and beating the
> server a lot less often.

Servers can also take advantage of the fact that group membership
changes a lot less often than it is tested, and pre-calculate it when
entries are added or changed. The server has full knowledge in most
authentication/authorisation scenarios, so it can be *much* more
efficient than a client when doing these tests.

> > It looks as if the nested groups issue needs tackling. Should I expand
> > this I-D to include it? The consensus seems to be:
> 
> FWIW I think your original proposal is much simpler, and lets architects
> decide what to do without artificial separations of members depending on
> the fact they are groups or users.

It is simpler and I would not want to complicate it without good
reason, hence this discussion.

> Also it is more consistent, what if I have an Entry object listed as
> emmebr in another that lately is added a groupOfEntries objectclass to?
> Should the server go around all other groupOfEntries objects in search
> for members to be changed to nestedGroupObject ?

I am not sure that I understand your point there. Remember that
groupOfEntries is a STRUCTURAL class, so it cannot be added to an
existing entry or removed from one.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 12:46:18 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY2dL-0002rv-2H; Wed, 19 Sep 2007 12:42:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY2dJ-0002pQ-8W
	for ldapext@ietf.org; Wed, 19 Sep 2007 12:42:37 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY2dC-0006vw-Bz
	for ldapext@ietf.org; Wed, 19 Sep 2007 12:42:37 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id BFC97162AE4;
	Wed, 19 Sep 2007 16:42:12 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
In-Reply-To: <20070919152141.GH12296@tile.skills-1st.co.uk>
References: <46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 12:42:12 -0400
Message-Id: <1190220132.31971.147.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: ldapext@ietf.org, Luke Howard <lukeh@padl.com>,
	Steven Legg <steven.legg@eb2bcom.com>,
	Michael =?ISO-8859-1?Q?Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:

> The efficiency gain comes from not having to read the entries of the
> direct members just to find out whether they are actually nested
> groups or not. This could make a massive difference in cases where a
> group has a lot of direct members as well as a few nested groups.
> 
> The complexity in determining whether a given DN is a member of
> a potentially-nested group is much the same whether we use 'member'
> for everything or 'member' and 'nestedGroup', but using the two
> different attributes can save a vast number of LDAP operations.
> Consider this algorithm:
> 
> IsAMember( subjectDN, groupDN ) {
> 	Match subjectDN against 'member' attribute of group entry:
> 	stop if it matches, the DN is a member.
> 
> 	for each nested group {
> 		if IsAMember( subjectDN, nestedGroupDN )
> 		then stop, the DN is a member.
> 	}
> 
> 	The DN is not a member
> }
> 
> The first match is a single LDAP search on the basic group entry.
> 
> The foreach loop requires one LDAP search on the base, plus:
> 
> 	If we only use 'member' attributes,
> 	one LDAP search on each member to find out what it is
> 	before calling the procedure recursively on each nested group.
> 
> 	If we separate direct members from nested groups using
> 	different attributes, we recurse immediately with no extra
> 	LDAP ops.
> 
> Hmm: I think the different-attributes case is actually *simpler* to
> code. The algorithm for enumerating members is almost identical.

-	for each nested group {
+	for each member {

The algorithm complexity is the same, although, it is true, a client may
require more operations.

Actually I think this problem would be better solved by a control to ask
the server to do the calculations for us (and IIRC there is a control
like that in the AD implementation called ASQ or something like that)
and use a cache, so we have both an efficient way to do it and avoid the
artificial distinction.

> This sort of thing has a value in many authorisation cases. Clients
> often need to know 'is this user allowed to do X' where the permission
> is expressed as membership of a group. Nested groups are extremely
> useful in this scenario as you often want one level to classify the
> users by roles and a second level to define what each role is allowed
> to do. The client just wants a yes/no answer and is not often
> interested in which group membership chain actually permitted the
> access. If the server supports server-side nesting then a single LDAP
> search will answer the question.

Yes, true, a control that allow you to do that would be a good thing,
but it is just convenient, not mandatory, doing the "un-rolling" by
default is what I think is bad.

> > It's up to you to use nested groups or not. It's not mandatory, and
> > doing it client side has also benefits.
> 
> Indeed, and I would not want to stop anyone doing so.

No doubt :)

> > Suppose I need to check user A is in group A, where group A has 128 sub
> > groups, with others again.
> > Now if you do server side resolution at each query of the member
> > attribute you have to fully unwind all groups every time (sure caching
> > helps), instead if you are a client, you can stop at the first group you
> > find containing the user (in case it is group A it is much more
> > convenient). Also, clients smart enough to understand nested groups, can
> > probably be smart enough to do some smart caching, and beating the
> > server a lot less often.
> 
> Servers can also take advantage of the fact that group membership
> changes a lot less often than it is tested, and pre-calculate it when
> entries are added or changed. The server has full knowledge in most
> authentication/authorisation scenarios, so it can be *much* more
> efficient than a client when doing these tests.

Yep a control would be the right place to do a complex operation like
that, still does not warrant a different attribute imo.

> > > It looks as if the nested groups issue needs tackling. Should I expand
> > > this I-D to include it? The consensus seems to be:
> > 
> > FWIW I think your original proposal is much simpler, and lets architects
> > decide what to do without artificial separations of members depending on
> > the fact they are groups or users.
> 
> It is simpler and I would not want to complicate it without good
> reason, hence this discussion.

Yep, I was just posting my opinion in favor of simplicity.

> > Also it is more consistent, what if I have an Entry object listed as
> > emmebr in another that lately is added a groupOfEntries objectclass to?
> > Should the server go around all other groupOfEntries objects in search
> > for members to be changed to nestedGroupObject ?
> 
> I am not sure that I understand your point there. Remember that
> groupOfEntries is a STRUCTURAL class, so it cannot be added to an
> existing entry or removed from one.

AHHH Right, that was the other thing in the back of my mind that kept
bogging me, but I forgot to post about it.

STRUCTURAL classes are often annoying and I think they should be used
only when the object is meant to be incompatible with other ones and/or
embed a unique new concept that should make it naturally incompatible
with other objectClasses.

What is the reasoning for it being STRUCTURAL here?

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 13:10:07 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY31a-00067H-Bf; Wed, 19 Sep 2007 13:07:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY31Z-00066Z-W3
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:07:41 -0400
Received: from mlnyc903er.ml.com ([199.43.64.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY31T-0007cz-Ph
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:07:41 -0400
Received: from MLNYC851BH.amrs.win.ml.com (unknown [141.128.12.201])
	by mlnyc903er.ml.com (Postfix) with ESMTP id 9C6735668A;
	Wed, 19 Sep 2007 13:07:24 -0400 (EDT)
Importance: normal
Priority: normal
Received: from mlnya302bh.amrs.win.ml.com ([170.240.239.47]) by
	MLNYC851BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 13:07:20 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	mlnya302bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 13:07:13 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] Nested group (was: groupOfEntries object class proposal)
Date: Wed, 19 Sep 2007 13:07:13 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group (was: groupOfEntries object class
	proposal)
thread-index: Acf63gsFB5QrKeYjTXG7y6D5fywsigAACQEA
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com><20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: "simo" <idra@samba.org>, "Andrew Findlay" <andrew.findlay@skills-1st.co.uk>
X-OriginalArrivalTime: 19 Sep 2007 17:07:13.0927 (UTC)
	FILETIME=[862FA970:01C7FADF]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: Steven Legg <steven.legg@eb2bcom.com>, Luke Howard <lukeh@padl.com>,
	ldapext@ietf.org, =?iso-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

This anticipates a reliable mechanism that ensures direct members are =
not added to the nestedGroups attribute and that nested groups are not =
inadvertently added to the member attribute. How would the server =
respond if an object is included in both attributes?

-----Original Message-----
From: simo [mailto:idra@samba.org]=20
Sent: Wednesday, September 19, 2007 12:42 PM
To: Andrew Findlay
Cc: ldapext@ietf.org; Luke Howard; Steven Legg; Michael Str=F6der
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class =
proposal)

On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:

> The efficiency gain comes from not having to read the entries of the
> direct members just to find out whether they are actually nested
> groups or not. This could make a massive difference in cases where a
> group has a lot of direct members as well as a few nested groups.
>=20
> The complexity in determining whether a given DN is a member of
> a potentially-nested group is much the same whether we use 'member'
> for everything or 'member' and 'nestedGroup', but using the two
> different attributes can save a vast number of LDAP operations.
> Consider this algorithm:
>=20
> IsAMember( subjectDN, groupDN ) {
> 	Match subjectDN against 'member' attribute of group entry:
> 	stop if it matches, the DN is a member.
>=20
> 	for each nested group {
> 		if IsAMember( subjectDN, nestedGroupDN )
> 		then stop, the DN is a member.
> 	}
>=20
> 	The DN is not a member
> }
>=20
> The first match is a single LDAP search on the basic group entry.
>=20
> The foreach loop requires one LDAP search on the base, plus:
>=20
> 	If we only use 'member' attributes,
> 	one LDAP search on each member to find out what it is
> 	before calling the procedure recursively on each nested group.
>=20
> 	If we separate direct members from nested groups using
> 	different attributes, we recurse immediately with no extra
> 	LDAP ops.
>=20
> Hmm: I think the different-attributes case is actually *simpler* to
> code. The algorithm for enumerating members is almost identical.

-	for each nested group {
+	for each member {

The algorithm complexity is the same, although, it is true, a client may
require more operations.

Actually I think this problem would be better solved by a control to ask
the server to do the calculations for us (and IIRC there is a control
like that in the AD implementation called ASQ or something like that)
and use a cache, so we have both an efficient way to do it and avoid the
artificial distinction.

> This sort of thing has a value in many authorisation cases. Clients
> often need to know 'is this user allowed to do X' where the permission
> is expressed as membership of a group. Nested groups are extremely
> useful in this scenario as you often want one level to classify the
> users by roles and a second level to define what each role is allowed
> to do. The client just wants a yes/no answer and is not often
> interested in which group membership chain actually permitted the
> access. If the server supports server-side nesting then a single LDAP
> search will answer the question.

Yes, true, a control that allow you to do that would be a good thing,
but it is just convenient, not mandatory, doing the "un-rolling" by
default is what I think is bad.

> > It's up to you to use nested groups or not. It's not mandatory, and
> > doing it client side has also benefits.
>=20
> Indeed, and I would not want to stop anyone doing so.

No doubt :)

> > Suppose I need to check user A is in group A, where group A has 128 =
sub
> > groups, with others again.
> > Now if you do server side resolution at each query of the member
> > attribute you have to fully unwind all groups every time (sure =
caching
> > helps), instead if you are a client, you can stop at the first group =
you
> > find containing the user (in case it is group A it is much more
> > convenient). Also, clients smart enough to understand nested groups, =
can
> > probably be smart enough to do some smart caching, and beating the
> > server a lot less often.
>=20
> Servers can also take advantage of the fact that group membership
> changes a lot less often than it is tested, and pre-calculate it when
> entries are added or changed. The server has full knowledge in most
> authentication/authorisation scenarios, so it can be *much* more
> efficient than a client when doing these tests.

Yep a control would be the right place to do a complex operation like
that, still does not warrant a different attribute imo.

> > > It looks as if the nested groups issue needs tackling. Should I =
expand
> > > this I-D to include it? The consensus seems to be:
> >=20
> > FWIW I think your original proposal is much simpler, and lets =
architects
> > decide what to do without artificial separations of members =
depending on
> > the fact they are groups or users.
>=20
> It is simpler and I would not want to complicate it without good
> reason, hence this discussion.

Yep, I was just posting my opinion in favor of simplicity.

> > Also it is more consistent, what if I have an Entry object listed as
> > emmebr in another that lately is added a groupOfEntries objectclass =
to?
> > Should the server go around all other groupOfEntries objects in =
search
> > for members to be changed to nestedGroupObject ?
>=20
> I am not sure that I understand your point there. Remember that
> groupOfEntries is a STRUCTURAL class, so it cannot be added to an
> existing entry or removed from one.

AHHH Right, that was the other thing in the back of my mind that kept
bogging me, but I forgot to post about it.

STRUCTURAL classes are often annoying and I think they should be used
only when the object is meant to be incompatible with other ones and/or
embed a unique new concept that should make it naturally incompatible
with other objectClasses.

What is the reasoning for it being STRUCTURAL here?

Simo.

--=20
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 13:11:07 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY34D-0008EA-EH; Wed, 19 Sep 2007 13:10:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY34B-0008A3-D5
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:10:23 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY34B-0006Rw-0Q
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:10:23 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8JHABjo007973; Wed, 19 Sep 2007 12:10:11 -0500
Message-ID: <46F15776.4090804@highlandsun.com>
Date: Wed, 19 Sep 2007 10:08:06 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>	<1190210820.31971.105.camel@localhost.localdomain>	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
In-Reply-To: <1190220132.31971.147.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ldapext@ietf.org, Steven Legg <steven.legg@eb2bcom.com>,
	Luke Howard <lukeh@padl.com>, =?ISO-8859-1?Q?Michael_Str=F6de?=,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>,
	=?ISO-8859-1?Q?r?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:
>> Hmm: I think the different-attributes case is actually *simpler* to
>> code. The algorithm for enumerating members is almost identical.
> 
> -	for each nested group {
> +	for each member {
> 
> The algorithm complexity is the same, although, it is true, a client may
> require more operations.

You're saying "in theory these are the same." That may be true, but in 
practice, your "simplification" creates more work both the client and the 
server. We can do better, therefore we should.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 13:35:58 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY3QG-0001hA-Vi; Wed, 19 Sep 2007 13:33:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY3QG-0001h5-A5
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:33:12 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY3QF-00077u-LH
	for ldapext@ietf.org; Wed, 19 Sep 2007 13:33:12 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY3QE-000DhW-S0; Wed, 19 Sep 2007 18:33:11 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY3Q1-0004zK-Qm; Wed, 19 Sep 2007 18:32:57 +0100
Date: Wed, 19 Sep 2007 18:32:57 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919173257.GJ12296@tile.skills-1st.co.uk>
References: <46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1190220132.31971.147.camel@localhost.localdomain>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 12:42:12PM -0400, simo wrote:

> The algorithm complexity is the same, although, it is true, a client may
> require more operations.
> 
> Actually I think this problem would be better solved by a control to ask
> the server to do the calculations for us (and IIRC there is a control
> like that in the AD implementation called ASQ or something like that)
> and use a cache, so we have both an efficient way to do it and avoid the
> artificial distinction.

Server support would certainly be valuable in many cases and a control
sounds like a good way to ask for it. However, I think that is
orthogonal to the question of whether there should be two attributes.

Consider the case of a group giving access to some resource. As the
owner of the resource I have control of the group, so I can give user
X access to it by putting the DN of X's entry into the group as a
member. I might also control another group called Q whose members
should have access to the resource so I add that too. So far so good,
but if there is no distinction between leaf members and nested groups
*in the group entry itself* it would be possible for user X to give
access to my resource to other people by adding member attributes to
his own entry. As the resource owner I would not want that to be
possible. This alone seems like a good reason not to allow nesting via
the 'member' attribute.

> > > Also it is more consistent, what if I have an Entry object listed as
> > > emmebr in another that lately is added a groupOfEntries objectclass to?
> > > Should the server go around all other groupOfEntries objects in search
> > > for members to be changed to nestedGroupObject ?
> > 
> > I am not sure that I understand your point there. Remember that
> > groupOfEntries is a STRUCTURAL class, so it cannot be added to an
> > existing entry or removed from one.
> 
> AHHH Right, that was the other thing in the back of my mind that kept
> bogging me, but I forgot to post about it.
> 
> STRUCTURAL classes are often annoying and I think they should be used
> only when the object is meant to be incompatible with other ones and/or
> embed a unique new concept that should make it naturally incompatible
> with other objectClasses.
> 
> What is the reasoning for it being STRUCTURAL here?

I also avoid structural classes where possible. In this case it seems
reasonable though. A group is a fairly basic concept and if it did not
have a structural class of it own then group objects would have to be
based on something else. The closest I can think of is
organizationalUnit, but that is not really a good model for the common
uses of groups to control authorisation.

A further reason for it being structural is that groupOfNames is
structural. If groupOfEntries is to replace it then this should not
change.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:04:13 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY3sL-0000ph-1A; Wed, 19 Sep 2007 14:02:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY3sJ-0000kS-9W
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:02:11 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY3s5-0000iz-2j
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:02:01 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY3rv-000EaR-6H; Wed, 19 Sep 2007 19:01:47 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY3rb-000519-9q; Wed, 19 Sep 2007 19:01:27 +0100
Date: Wed, 19 Sep 2007 19:01:27 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: "Liben, Michael (GTI)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919180127.GK12296@tile.skills-1st.co.uk>
References: <1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 01:07:13PM -0400, Liben, Michael (GTI) wrote:

> This anticipates a reliable mechanism that ensures direct members
> are not added to the nestedGroups attribute and that nested groups are
> not inadvertently added to the member attribute.

I don't think there needs to be any server-side control on that. There
are many cases in LDAP where the protocol and schema allow the client
to do 'silly' things. If we try to tie things down too hard there is
no room for flexibility. A designer can choose to use ACLs or
structure definitions to apply some measure of control, or can rely on
'business logic' in the update process to do so.

> How would the server respond if an object is included in both attributes?

OK, suppose we have a group A containing nestedGroup B and members B
and C.  B is itself a group containing members D and E.

If server-side nesting/expansion is *not* requested then there is no
issue: it is up the client to interpret the data (though it would be
good to define the algorithm so that client and server get the same
results!).

If server-side support *is* requested, then:

Group expansion of A results in a list of member attributes:
	B C D E

It so happens that one of those DNs is a group. The others could be
anything. I see no problem here.

Now, if C is added to group B as a member, the expansion will find C
twice. The server should suppress the duplicate.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:10:01 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY3yi-00080P-1l; Wed, 19 Sep 2007 14:08:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY3yg-0007vJ-K0
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:08:46 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY3yg-0008Aq-2I
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:08:46 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id C25C0162AF7;
	Wed, 19 Sep 2007 18:08:45 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
In-Reply-To: <20070919173257.GJ12296@tile.skills-1st.co.uk>
References: <46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 14:08:35 -0400
Message-Id: <1190225315.31971.153.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 18:32 +0100, Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 12:42:12PM -0400, simo wrote:
> 
> > The algorithm complexity is the same, although, it is true, a client may
> > require more operations.
> > 
> > Actually I think this problem would be better solved by a control to ask
> > the server to do the calculations for us (and IIRC there is a control
> > like that in the AD implementation called ASQ or something like that)
> > and use a cache, so we have both an efficient way to do it and avoid the
> > artificial distinction.
> 
> Server support would certainly be valuable in many cases and a control
> sounds like a good way to ask for it. However, I think that is
> orthogonal to the question of whether there should be two attributes.
> 
> Consider the case of a group giving access to some resource. As the
> owner of the resource I have control of the group, so I can give user
> X access to it by putting the DN of X's entry into the group as a
> member. I might also control another group called Q whose members
> should have access to the resource so I add that too. So far so good,
> but if there is no distinction between leaf members and nested groups
> *in the group entry itself* it would be possible for user X to give
> access to my resource to other people by adding member attributes to
> his own entry. As the resource owner I would not want that to be
> possible. This alone seems like a good reason not to allow nesting via
> the 'member' attribute.

This is an interesting view, but clashes with the fact that
groupOfEntries is defined STRUCTURAL, so it is not possible for a user
to add this class to its own object (and even if it were possible you
imply that user X has access to his own entry which is usually not true)
and therefore not possible to add members.

If you agree I'd say this is a non issue and would not consider it in
the debate.

> > > > Also it is more consistent, what if I have an Entry object listed as
> > > > emmebr in another that lately is added a groupOfEntries objectclass to?
> > > > Should the server go around all other groupOfEntries objects in search
> > > > for members to be changed to nestedGroupObject ?
> > > 
> > > I am not sure that I understand your point there. Remember that
> > > groupOfEntries is a STRUCTURAL class, so it cannot be added to an
> > > existing entry or removed from one.
> > 
> > AHHH Right, that was the other thing in the back of my mind that kept
> > bogging me, but I forgot to post about it.
> > 
> > STRUCTURAL classes are often annoying and I think they should be used
> > only when the object is meant to be incompatible with other ones and/or
> > embed a unique new concept that should make it naturally incompatible
> > with other objectClasses.
> > 
> > What is the reasoning for it being STRUCTURAL here?
> 
> I also avoid structural classes where possible. In this case it seems
> reasonable though. A group is a fairly basic concept and if it did not
> have a structural class of it own then group objects would have to be
> based on something else. The closest I can think of is
> organizationalUnit, but that is not really a good model for the common
> uses of groups to control authorisation.
> 
> A further reason for it being structural is that groupOfNames is
> structural. If groupOfEntries is to replace it then this should not
> change.

Make sense, I was interested in the reason, and actually the scenario
above is more a reason for keeping groupOfNames structural than a reason
to keep 2 separate attributes.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:17:48 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY45t-0008S7-3m; Wed, 19 Sep 2007 14:16:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY45r-0008Rs-Lm
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:16:11 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY45r-0008NC-7S
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:16:11 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id D6788162AE4;
	Wed, 19 Sep 2007 18:16:10 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
In-Reply-To: <20070919180127.GK12296@tile.skills-1st.co.uk>
References: <1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
	<20070919180127.GK12296@tile.skills-1st.co.uk>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 14:16:00 -0400
Message-Id: <1190225760.31971.161.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 19:01 +0100, Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 01:07:13PM -0400, Liben, Michael (GTI) wrote:
> 
> > This anticipates a reliable mechanism that ensures direct members
> > are not added to the nestedGroups attribute and that nested groups are
> > not inadvertently added to the member attribute.
> 
> I don't think there needs to be any server-side control on that. There
> are many cases in LDAP where the protocol and schema allow the client
> to do 'silly' things. If we try to tie things down too hard there is
> no room for flexibility. A designer can choose to use ACLs or
> structure definitions to apply some measure of control, or can rely on
> 'business logic' in the update process to do so.

The problem is that you have a generic "DN" container that is given
specific semanthics. IE nestedGroupObject is supposed to contain only
entries that have groupOfEntries as its STRUCTURAL class, but you do not
enforce it. So it may contain anything. Same for member.

This just means clients have to cope with bad entries.

I think that the problem is caused by artificial separation of members
in 2 classes.

> > How would the server respond if an object is included in both attributes?
> 
> OK, suppose we have a group A containing nestedGroup B and members B
> and C.  B is itself a group containing members D and E.
> 
> If server-side nesting/expansion is *not* requested then there is no
> issue: it is up the client to interpret the data (though it would be
> good to define the algorithm so that client and server get the same
> results!).
> 
> If server-side support *is* requested, then:
> 
> Group expansion of A results in a list of member attributes:
> 	B C D E
> 
> It so happens that one of those DNs is a group. The others could be
> anything. I see no problem here.
> 
> Now, if C is added to group B as a member, the expansion will find C
> twice. The server should suppress the duplicate.

The server will always have to suppress duplicates, this is not a
problem.

You will have the same in this perfectly legit scenario:

Group A contains Group B and Group C
Group B has users a, b, c
Group C has users a, d, e

Also another thing servers and clients MUST be aware is that this may
introduce recursion problems

Group A -memberof-> Group B -memberof-> Group A -repeat ad nauseam-|

Nested groups have advantages and issues, but that's not what we are
discussing, we are discussing whether splitting membership in 2
attributes by type is good or not, AFAICT.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:30:02 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4H3-00031f-Vr; Wed, 19 Sep 2007 14:27:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4H2-00031Y-9z
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:27:44 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4Gw-0001PG-6r
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:27:44 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id 08F07162BD9;
	Wed, 19 Sep 2007 18:27:38 +0000 (GMT)
Subject: Re: [ldapext] Nested group
From: simo <idra@samba.org>
To: Howard Chu <hyc@highlandsun.com>
In-Reply-To: <46F15776.4090804@highlandsun.com>
References: <46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<46F15776.4090804@highlandsun.com>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 14:27:37 -0400
Message-Id: <1190226457.31971.163.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 10:08 -0700, Howard Chu wrote:
> simo wrote:
> > On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:
> >> Hmm: I think the different-attributes case is actually *simpler* to
> >> code. The algorithm for enumerating members is almost identical.
> > 
> > -	for each nested group {
> > +	for each member {
> > 
> > The algorithm complexity is the same, although, it is true, a client may
> > require more operations.
> 
> You're saying "in theory these are the same." That may be true, but in 
> practice, your "simplification" creates more work both the client and the 
> server. We can do better, therefore we should.

"Better" depends on the context I guess.
Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:45:45 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4WM-0006LU-Vd; Wed, 19 Sep 2007 14:43:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4WL-0006K0-SJ
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:43:33 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4WF-0001w1-9d
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:43:33 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY4W5-000GAa-HI; Wed, 19 Sep 2007 19:43:17 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY4Vs-00052T-2g; Wed, 19 Sep 2007 19:43:04 +0100
Date: Wed, 19 Sep 2007 19:43:04 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919184304.GL12296@tile.skills-1st.co.uk>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
	<1190225315.31971.153.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1190225315.31971.153.camel@localhost.localdomain>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 02:08:35PM -0400, simo wrote:

> > Consider the case of a group giving access to some resource. As the
> > owner of the resource I have control of the group, so I can give user
> > X access to it by putting the DN of X's entry into the group as a
> > member. I might also control another group called Q whose members
> > should have access to the resource so I add that too. So far so good,
> > but if there is no distinction between leaf members and nested groups
> > *in the group entry itself* it would be possible for user X to give
> > access to my resource to other people by adding member attributes to
> > his own entry. As the resource owner I would not want that to be
> > possible. This alone seems like a good reason not to allow nesting via
> > the 'member' attribute.
> 
> This is an interesting view, but clashes with the fact that
> groupOfEntries is defined STRUCTURAL, so it is not possible for a user
> to add this class to its own object (and even if it were possible you
> imply that user X has access to his own entry which is usually not true)
> and therefore not possible to add members.

That depends on whether the expansion rule incudes a check on the
objectclass of the nested groups. I was expecting it to work with any
entry that contains member attributes, in order to allow for a mix of
groupOfEntries and other group-like things that have been given an aux
class to permit members (e.g. organizationalUnit might sometimes get
this).

Perhaps my example was not general enough anyway. Maybe user X is in
some part of the tree controlled by different administrators. I am
prepared to grant access to my resource to that one user, but I dont
want one of 'their' admins replacing the user entry with a group that
gets expanded. This is like X.509 certificate authorities: they will
give you a cert for your own ID but not one that allows you to certify
others. We are talking about control and trust here, and trust is not
always transitive.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 14:52:21 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4dd-0003h4-Tj; Wed, 19 Sep 2007 14:51:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4dc-0003dx-4d
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:51:04 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4dV-0002TD-U3
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:51:04 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8JIodOA009985; Wed, 19 Sep 2007 13:50:40 -0500
Message-ID: <46F16F02.1060807@highlandsun.com>
Date: Wed, 19 Sep 2007 11:48:34 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
References: <1190220132.31971.147.camel@localhost.localdomain>	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>	<20070919180127.GK12296@tile.skills-1st.co.uk>
	<1190225760.31971.161.camel@localhost.localdomain>
In-Reply-To: <1190225760.31971.161.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.7 (+)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> On Wed, 2007-09-19 at 19:01 +0100, Andrew Findlay wrote:
>> On Wed, Sep 19, 2007 at 01:07:13PM -0400, Liben, Michael (GTI) wrote:
>>
>>> This anticipates a reliable mechanism that ensures direct members
>>> are not added to the nestedGroups attribute and that nested groups are
>>> not inadvertently added to the member attribute.
>> I don't think there needs to be any server-side control on that. There
>> are many cases in LDAP where the protocol and schema allow the client
>> to do 'silly' things. If we try to tie things down too hard there is
>> no room for flexibility. A designer can choose to use ACLs or
>> structure definitions to apply some measure of control, or can rely on
>> 'business logic' in the update process to do so.
> 
> The problem is that you have a generic "DN" container that is given
> specific semanthics. IE nestedGroupObject is supposed to contain only
> entries that have groupOfEntries as its STRUCTURAL class, but you do not
> enforce it. So it may contain anything. Same for member.

As usual, garbage-in-garbage-out. You can probably implement enforcement in 
the server, but that doesn't need to be mandated in the specification. There 
are plenty of standards track schema elements that use a very general syntax, 
but whose description says a value of a particular form is expected.

Also, even if the server doesn't enforce the semantics, the end result is a 
benign failure. I.e., if someone puts the DN of a groupOfEntries into the 
member attribute of a group, the worst that can happen is that those group 
members will not get the privilege that group membership was intended to 
convey. You cannot introduce a security breach here by accidentally giving 
privilege to a larger member set than intended. Likewise, the worst that can 
happen by putting the DN of a non-group entry into a nestedGroup attribute is 
that that specific user will not have his intended privilege.

On the other hand, by throwing everything together into a single member 
attribute, you can accidentally nest groups together and there is no obvious 
audit trail that will highlight your mistake. Compartmentalization here is a 
good thing, from a security standpoint.

> This just means clients have to cope with bad entries.
> 
> I think that the problem is caused by artificial separation of members
> in 2 classes.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:01:03 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4l8-0006zv-FX; Wed, 19 Sep 2007 14:58:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4l7-0006zo-7F
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:58:49 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4l5-0002jP-HM
	for ldapext@ietf.org; Wed, 19 Sep 2007 14:58:49 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8JIwZnF010151; Wed, 19 Sep 2007 13:58:35 -0500
Message-ID: <46F170DE.1010205@highlandsun.com>
Date: Wed, 19 Sep 2007 11:56:30 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>	<46F063BE.5020900@padl.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com><20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk>	<1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Andrew Findlay <andrew.findlay@skills-1st.co.uk>,
	Luke Howard <lukeh@padl.com>, simo <idra@samba.org>,
	ldapext@ietf.org, Steven Legg <steven.legg@eb2bcom.com>,
	=?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Liben, Michael (GTI) wrote:
> This anticipates a reliable mechanism that ensures direct members are not
added to the nestedGroups attribute and that nested groups are not
inadvertently added to the member attribute. How would the server respond if
an object is included in both attributes?

Actually that's not a requirement. A group can legitimately be a user in LDAP. 
It may be perfectly valid for a group object to appear in both the member and 
nestedGroup attribute. It would be meaningless for a non-group object to 
appear in the nestedGroup attribute. Whether that should be rejected or 
silently ignored is an open question, but pretty trivial either way.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:04:30 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4oo-0001Vk-1G; Wed, 19 Sep 2007 15:02:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4om-0001U7-Ap
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:02:36 -0400
Received: from mlnyc905er.ml.com ([199.43.64.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4od-0002qQ-5Y
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:02:33 -0400
Received: from mlnyc852bh.amrs.win.ml.com (unknown [141.128.12.202])
	by mlnyc905er.ml.com (Postfix) with ESMTP id 2BD2456696;
	Wed, 19 Sep 2007 15:02:09 -0400 (EDT)
Importance: normal
Priority: normal
Received: from mlnya301bh.amrs.win.ml.com ([170.240.239.46]) by
	mlnyc852bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 15:01:51 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	mlnya301bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Wed, 19 Sep 2007 15:01:40 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] Nested group
Date: Wed, 19 Sep 2007 15:01:34 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E3090044983@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group
thread-index: Acf67G9k2L9nDY6QSVK82OKZaYtQYgAAV2sQ
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com><46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk><1190220132.31971.147.camel@localhost.localdomain><46F15776.4090804@highlandsun.com>
	<1190226457.31971.163.camel@localhost.localdomain>
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: "simo" <idra@samba.org>,
	"Howard Chu" <hyc@highlandsun.com>
X-OriginalArrivalTime: 19 Sep 2007 19:01:40.0536 (UTC)
	FILETIME=[83010B80:01C7FAEF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

In Active Directory, Microsoft maintains 'back link' attributes. One of
these is memberOf. When an object is added or removed from a group, a
process runs that updates the back link attribute on the object. If the
member object is moved or deleted, another process updates the group's
member attribute accordingly.=20

Clients still have to evaluate all of the members to determine a nested
resultant set of members. However, clients can easily view all the
groups to which an object is a member, walking up the tree instead of
downward.

-----Original Message-----
From: simo [mailto:idra@samba.org]=20
Sent: Wednesday, September 19, 2007 2:28 PM
To: Howard Chu
Cc: ldapext@ietf.org
Subject: Re: [ldapext] Nested group

On Wed, 2007-09-19 at 10:08 -0700, Howard Chu wrote:
> simo wrote:
> > On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:
> >> Hmm: I think the different-attributes case is actually *simpler* to
> >> code. The algorithm for enumerating members is almost identical.
> >=20
> > -	for each nested group {
> > +	for each member {
> >=20
> > The algorithm complexity is the same, although, it is true, a client
may
> > require more operations.
>=20
> You're saying "in theory these are the same." That may be true, but in

> practice, your "simplification" creates more work both the client and
the=20
> server. We can do better, therefore we should.

"Better" depends on the context I guess.
Simo.

--=20
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:08:20 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY4t8-0003lo-Kl; Wed, 19 Sep 2007 15:07:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY4t7-0003lc-RV
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:07:05 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY4t6-0002xH-8Z
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:07:05 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8JJ72er010347
	for <ldapext@ietf.org>; Wed, 19 Sep 2007 14:07:02 -0500
Message-ID: <46F172D9.1060801@highlandsun.com>
Date: Wed, 19 Sep 2007 12:04:57 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: ldapext@ietf.org
Subject: Re: [ldapext] Nested group expansion control
References: <46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>	<1190210820.31971.105.camel@localhost.localdomain>	<20070919152141.GH12296@tile.skills-1st.co.uk>	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
In-Reply-To: <20070919173257.GJ12296@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 12:42:12PM -0400, simo wrote:
> 
>> The algorithm complexity is the same, although, it is true, a client may
>> require more operations.
>>
>> Actually I think this problem would be better solved by a control to ask
>> the server to do the calculations for us (and IIRC there is a control
>> like that in the AD implementation called ASQ or something like that)
>> and use a cache, so we have both an efficient way to do it and avoid the
>> artificial distinction.
> 
> Server support would certainly be valuable in many cases and a control
> sounds like a good way to ask for it. However, I think that is
> orthogonal to the question of whether there should be two attributes.

Digressing down this path briefly... Such a control should probably have a 
depth/recursion limit as a parameter. Servers would have to be smart about how 
this control is propagated in a distributed environment, e.g. if certain 
nestedGroup DNs reside on remote servers. (Though in practice, just as with 
search limits, clients will probably most often ask for "unlimited" and leave 
it up to the server to restrict it.)
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:30:36 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY5Cz-0004lH-36; Wed, 19 Sep 2007 15:27:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY5Cx-0004l2-Cu
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:27:35 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY5Ct-0003Y5-7P
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:27:35 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id 1392C162AE4;
	Wed, 19 Sep 2007 19:27:26 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Howard Chu <hyc@highlandsun.com>
In-Reply-To: <46F16F02.1060807@highlandsun.com>
References: <1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
	<20070919180127.GK12296@tile.skills-1st.co.uk>
	<1190225760.31971.161.camel@localhost.localdomain>
	<46F16F02.1060807@highlandsun.com>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 15:27:25 -0400
Message-Id: <1190230045.31971.173.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 11:48 -0700, Howard Chu wrote:
> simo wrote:
> > On Wed, 2007-09-19 at 19:01 +0100, Andrew Findlay wrote:
> >> On Wed, Sep 19, 2007 at 01:07:13PM -0400, Liben, Michael (GTI) wrote:
> >>
> >>> This anticipates a reliable mechanism that ensures direct members
> >>> are not added to the nestedGroups attribute and that nested groups are
> >>> not inadvertently added to the member attribute.
> >> I don't think there needs to be any server-side control on that. There
> >> are many cases in LDAP where the protocol and schema allow the client
> >> to do 'silly' things. If we try to tie things down too hard there is
> >> no room for flexibility. A designer can choose to use ACLs or
> >> structure definitions to apply some measure of control, or can rely on
> >> 'business logic' in the update process to do so.
> > 
> > The problem is that you have a generic "DN" container that is given
> > specific semanthics. IE nestedGroupObject is supposed to contain only
> > entries that have groupOfEntries as its STRUCTURAL class, but you do not
> > enforce it. So it may contain anything. Same for member.
> 
> As usual, garbage-in-garbage-out. You can probably implement enforcement in 
> the server, but that doesn't need to be mandated in the specification. There 
> are plenty of standards track schema elements that use a very general syntax, 
> but whose description says a value of a particular form is expected.
> 
> Also, even if the server doesn't enforce the semantics, the end result is a 
> benign failure. I.e., if someone puts the DN of a groupOfEntries into the 
> member attribute of a group, the worst that can happen is that those group 
> members will not get the privilege that group membership was intended to 
> convey. You cannot introduce a security breach here by accidentally giving 
> privilege to a larger member set than intended. Likewise, the worst that can 
> happen by putting the DN of a non-group entry into a nestedGroup attribute is 
> that that specific user will not have his intended privilege.
> 
> On the other hand, by throwing everything together into a single member 
> attribute, you can accidentally nest groups together and there is no obvious 
> audit trail that will highlight your mistake. Compartmentalization here is a 
> good thing, from a security standpoint.

While I agree with the general concept, I don't with the specific
example. If you accidentally put a group into the member attribute you
can as well put it accidentally into the nestedGroup one as well.
I don't see why one should me more probable than the other.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:33:54 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY5Hp-0007Do-VE; Wed, 19 Sep 2007 15:32:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY5Hn-0007C9-P9
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:32:35 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY5Hn-0002x7-AX
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:32:35 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id 1CE69162AE4;
	Wed, 19 Sep 2007 19:32:35 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
In-Reply-To: <20070919184304.GL12296@tile.skills-1st.co.uk>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
	<1190225315.31971.153.camel@localhost.localdomain>
	<20070919184304.GL12296@tile.skills-1st.co.uk>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 15:32:34 -0400
Message-Id: <1190230354.31971.178.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 19:43 +0100, Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 02:08:35PM -0400, simo wrote:
> 
> > > Consider the case of a group giving access to some resource. As the
> > > owner of the resource I have control of the group, so I can give user
> > > X access to it by putting the DN of X's entry into the group as a
> > > member. I might also control another group called Q whose members
> > > should have access to the resource so I add that too. So far so good,
> > > but if there is no distinction between leaf members and nested groups
> > > *in the group entry itself* it would be possible for user X to give
> > > access to my resource to other people by adding member attributes to
> > > his own entry. As the resource owner I would not want that to be
> > > possible. This alone seems like a good reason not to allow nesting via
> > > the 'member' attribute.
> > 
> > This is an interesting view, but clashes with the fact that
> > groupOfEntries is defined STRUCTURAL, so it is not possible for a user
> > to add this class to its own object (and even if it were possible you
> > imply that user X has access to his own entry which is usually not true)
> > and therefore not possible to add members.
> 
> That depends on whether the expansion rule incudes a check on the
> objectclass of the nested groups. I was expecting it to work with any
> entry that contains member attributes, in order to allow for a mix of
> groupOfEntries and other group-like things that have been given an aux
> class to permit members (e.g. organizationalUnit might sometimes get
> this).
> 
> Perhaps my example was not general enough anyway. Maybe user X is in
> some part of the tree controlled by different administrators. I am
> prepared to grant access to my resource to that one user, but I dont
> want one of 'their' admins replacing the user entry with a group that
> gets expanded. This is like X.509 certificate authorities: they will
> give you a cert for your own ID but not one that allows you to certify
> others. We are talking about control and trust here, and trust is not
> always transitive.

Sorry but I see a fault here as well.
Once you add, as a member, a user controlled by a foreign entity your
security is already screwed if you don't trust that entity.
If you trust it then you trust they will not try to use their power to
exploit your system.
That said, this example makes much more sense.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:43:04 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY5Pz-0004ya-29; Wed, 19 Sep 2007 15:41:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY5Px-0004y2-A0
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:41:01 -0400
Received: from ccerelbas03.cce.hp.com ([161.114.21.106])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY5Pt-0003G2-RT
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:40:58 -0400
Received: from cceexg13.americas.cpqcorp.net (cceexg13.americas.cpqcorp.net
	[16.81.1.58])
	by ccerelbas03.cce.hp.com (Postfix) with ESMTP id F06E234DFF;
	Wed, 19 Sep 2007 14:40:11 -0500 (CDT)
Received: from G3W0067.americas.hpqcorp.net ([16.232.1.13]) by
	cceexg13.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Sep 2007 14:40:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] Nested group (was: groupOfEntries object class proposal)
Date: Wed, 19 Sep 2007 19:39:18 -0000
Message-ID: <22F5E36297524347B40AFAA7CDD4CB4D01F2E0B1@G3W0067.americas.hpqcorp.net>
In-Reply-To: <46F16F02.1060807@highlandsun.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group (was: groupOfEntries object class
	proposal)
Thread-Index: Acf67y6WTtdqyKiFRDq/E8WOWrUP5gABQHJQ
References: <1190220132.31971.147.camel@localhost.localdomain>	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>	<20070919180127.GK12296@tile.skills-1st.co.uk><1190225760.31971.161.camel@localhost.localdomain>
	<46F16F02.1060807@highlandsun.com>
From: "Neal-Joslin, Robert (HP-UX Lab R&D)" <bob.joslin@hp.com>
To: "Howard Chu" <hyc@highlandsun.com>, "simo" <idra@samba.org>
X-OriginalArrivalTime: 19 Sep 2007 19:40:10.0279 (UTC)
	FILETIME=[E3B7DB70:01C7FAF4]
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Andrew Findlay <andrew.findlay@skills-1st.co.uk>,
	LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

>=20
> > The problem is that you have a generic "DN" container that is given
> > specific semanthics. IE nestedGroupObject is supposed to=20
> contain only
> > entries that have groupOfEntries as its STRUCTURAL class,=20
> but you do not
> > enforce it. So it may contain anything. Same for member.
>=20
> As usual, garbage-in-garbage-out. You can probably implement=20
> enforcement in=20
> the server, but that doesn't need to be mandated in the=20
> specification. There=20
> are plenty of standards track schema elements that use a very=20
> general syntax,=20
> but whose description says a value of a particular form is expected.
>=20
> Also, even if the server doesn't enforce the semantics, the=20
> end result is a=20
> benign failure. I.e., if someone puts the DN of a=20
> groupOfEntries into the=20
> member attribute of a group, the worst that can happen is=20
> that those group=20
> members will not get the privilege that group membership was=20
> intended to=20
> convey. You cannot introduce a security breach here by=20
> accidentally giving=20
> privilege to a larger member set than intended. Likewise, the=20
> worst that can=20
> happen by putting the DN of a non-group entry into a=20
> nestedGroup attribute is=20
> that that specific user will not have his intended privilege.

What?  It seems to me you are assuming how the security policy makes
use of the group (only for granting of privledge).  Membership in a
group can also (and is) used by a security policy to DENY access.
This is one reason I brought up my original concern.


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 15:50:43 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY5XY-0002Oj-Bi; Wed, 19 Sep 2007 15:48:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY5XW-0002K4-K0
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:48:50 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY5XR-00049B-BL
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:48:50 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8JJlIlW017871
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Sep 2007 15:48:34 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8JJN7vn001909;
	Wed, 19 Sep 2007 15:23:08 -0400
Received: from [172.16.25.166] (dhcp-172-16-25-166.sfbay.redhat.com
	[172.16.25.166])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8JJN6sG020559; Wed, 19 Sep 2007 15:23:06 -0400
Message-ID: <46F17719.8020302@redhat.com>
Date: Wed, 19 Sep 2007 12:23:05 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
References: <1190220132.31971.147.camel@localhost.localdomain>	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>	<20070919180127.GK12296@tile.skills-1st.co.uk>	<1190225760.31971.161.camel@localhost.localdomain>
	<46F16F02.1060807@highlandsun.com>
In-Reply-To: <46F16F02.1060807@highlandsun.com>
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>, simo <idra@samba.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0082821760=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0082821760==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms040709070706070301090705"

This is a cryptographically signed message in MIME format.

--------------ms040709070706070301090705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Howard Chu wrote:
> Also, even if the server doesn't enforce the semantics, the end result 
> is a benign failure. I.e., if someone puts the DN of a groupOfEntries 
> into the member attribute of a group, the worst that can happen is 
> that those group members will not get the privilege that group 
> membership was intended to convey. You cannot introduce a security 
> breach here by accidentally giving privilege to a larger member set 
> than intended. Likewise, the worst that can happen by putting the DN 
> of a non-group entry into a nestedGroup attribute is that that 
> specific user will not have his intended privilege.
>
Any divergence from the intended membership and the derived membership 
of a group used for security purposes can introduce a security breach. 
Any access control mechanism that allows an explicit denial of  
privilege would be an issue.


-- 
Pete


--------------ms040709070706070301090705
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MTkxOTIzMDVaMCMGCSqGSIb3DQEJBDEWBBRTpj4r6FZCbXaw
oXzM/98Ft0Xg+TBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEABqlpbx9wS8mAuZ52x2efwWzyNOralcsYd/sywbtRFDmblz6QjWj01UzFY+CU
JAjRqsdnJPmHbb5LYWleQmSdPeP3+vfyb6UR84/a5Kz7Qf2ccMwYPkjY+07liWWVldJoTHcw
KePS2+6+IxH+JCZFooFFu/8WvwKwqNSyr9TeYN6bLqeOmBnyC43G8+db1RZLJspna+JEOsy/
k9GZdRi3gVO48GVoMJZkxxSZ34W9y6Hjz9Il1uiMJMenEnOiPqr5fINs1LOrw363wieSLrfy
/ykDuPOP2FXSi+/C6D/v9yBLo1XXMvsMhdsV+lleYUL9VpKZkpyXbLtnLiAJPn4r/gAAAAAA
AA==
--------------ms040709070706070301090705--


--===============0082821760==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0082821760==--




From ldapext-bounces@ietf.org Wed Sep 19 15:54:01 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY5b0-0005PW-Hz; Wed, 19 Sep 2007 15:52:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY5ay-0005PE-MF
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:52:24 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY5ay-0003dn-8z
	for ldapext@ietf.org; Wed, 19 Sep 2007 15:52:24 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8JJqHkZ011272; Wed, 19 Sep 2007 14:52:18 -0500
Message-ID: <46F17D74.30300@highlandsun.com>
Date: Wed, 19 Sep 2007 12:50:12 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Pete Rowley <prowley@redhat.com>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
References: <1190220132.31971.147.camel@localhost.localdomain>	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>	<20070919180127.GK12296@tile.skills-1st.co.uk>	<1190225760.31971.161.camel@localhost.localdomain>
	<46F16F02.1060807@highlandsun.com> <46F17719.8020302@redhat.com>
In-Reply-To: <46F17719.8020302@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>, simo <idra@samba.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Pete Rowley wrote:
> Howard Chu wrote:
>> Also, even if the server doesn't enforce the semantics, the end result 
>> is a benign failure. I.e., if someone puts the DN of a groupOfEntries 
>> into the member attribute of a group, the worst that can happen is 
>> that those group members will not get the privilege that group 
>> membership was intended to convey. You cannot introduce a security 
>> breach here by accidentally giving privilege to a larger member set 
>> than intended. Likewise, the worst that can happen by putting the DN 
>> of a non-group entry into a nestedGroup attribute is that that 
>> specific user will not have his intended privilege.
>>
> Any divergence from the intended membership and the derived membership 
> of a group used for security purposes can introduce a security breach. 
> Any access control mechanism that allows an explicit denial of  
> privilege would be an issue.

Right, point taken, thanks.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 17:07:09 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY6hm-00025h-4I; Wed, 19 Sep 2007 17:03:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY6hi-00023t-7J
	for ldapext@ietf.org; Wed, 19 Sep 2007 17:03:28 -0400
Received: from cat.ourshack.com ([212.74.28.153])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY6hh-000655-OV
	for ldapext@ietf.org; Wed, 19 Sep 2007 17:03:26 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by cat.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY6hg-000KFC-Lq; Wed, 19 Sep 2007 22:03:25 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>)
	id 1IY6hS-00056x-MP; Wed, 19 Sep 2007 22:03:10 +0100
Date: Wed, 19 Sep 2007 22:03:10 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
Message-ID: <20070919210310.GN12296@tile.skills-1st.co.uk>
References: <20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
	<1190225315.31971.153.camel@localhost.localdomain>
	<20070919184304.GL12296@tile.skills-1st.co.uk>
	<1190230354.31971.178.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1190230354.31971.178.camel@localhost.localdomain>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, Sep 19, 2007 at 03:32:34PM -0400, simo wrote:

> Sorry but I see a fault here as well.
> Once you add, as a member, a user controlled by a foreign entity your
> security is already screwed if you don't trust that entity.
> If you trust it then you trust they will not try to use their power to
> exploit your system.

True, but the separation of attributes can limit how much of my
resource a malicious admin can give away.

Howard's suggestion of a limit on the 'expand groups' control leads to
another idea: split the nestedGroup attribute into two again:

	nestedGroupOfEntries
		The group entry that we point to can only contain
		leaf-nodes

	nestedRecursiveGroup
		The group entry that we point to may contain further
		nested groups as well as leaf-nodes.

That would give a structural way to limit the nesting of groups.
The expansion algorithm is now slightly larger, but not exactly
complex.

> That said, this example makes much more sense.

Thanks. The discussion is certainly helping me to clarify some ideas.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 18:31:47 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY81U-0002mv-Qi; Wed, 19 Sep 2007 18:27:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY81S-0002mh-Rp
	for ldapext@ietf.org; Wed, 19 Sep 2007 18:27:54 -0400
Received: from mail.samba.org ([66.70.73.150] helo=lists.samba.org)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IY81S-0000BD-FU
	for ldapext@ietf.org; Wed, 19 Sep 2007 18:27:54 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by lists.samba.org (Postfix) with ESMTP id BA16E162AE4;
	Wed, 19 Sep 2007 22:27:53 +0000 (GMT)
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
From: simo <idra@samba.org>
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
In-Reply-To: <20070919210310.GN12296@tile.skills-1st.co.uk>
References: <20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<20070919173257.GJ12296@tile.skills-1st.co.uk>
	<1190225315.31971.153.camel@localhost.localdomain>
	<20070919184304.GL12296@tile.skills-1st.co.uk>
	<1190230354.31971.178.camel@localhost.localdomain>
	<20070919210310.GN12296@tile.skills-1st.co.uk>
Content-Type: text/plain
Organization: Samba Team
Date: Wed, 19 Sep 2007 18:27:53 -0400
Message-Id: <1190240873.31971.192.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On Wed, 2007-09-19 at 22:03 +0100, Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 03:32:34PM -0400, simo wrote:
> 
> > Sorry but I see a fault here as well.
> > Once you add, as a member, a user controlled by a foreign entity your
> > security is already screwed if you don't trust that entity.
> > If you trust it then you trust they will not try to use their power to
> > exploit your system.
> 
> True, but the separation of attributes can limit how much of my
> resource a malicious admin can give away.

How? The malicious admin has already full access to the resources he can
have access to, he does not need more. The "malicious" one, will never
add other entries, as you would spot them monitoring the system, he will
just use the one "you" gave access to, to not make you suspect.

> Howard's suggestion of a limit on the 'expand groups' control leads to
> another idea: split the nestedGroup attribute into two again:
> 
> 	nestedGroupOfEntries
> 		The group entry that we point to can only contain
> 		leaf-nodes
> 
> 	nestedRecursiveGroup
> 		The group entry that we point to may contain further
> 		nested groups as well as leaf-nodes.

Why not also:

nestedRecursiveGroupTwoLevels
nestedRecursiveGroupOnlyThirdLevelButNotFirstOrSecond
SCNR :-)

Seriously, this may seem a good idea on the paper, but what people will
use in the end is always nestedRecursiveGroup as soon as they get burned
with the limitation of nestedGroupOfEntries.
So you will effectively gain nothing, except adding complexity.

I don't think we should be in the business of deciding policies, just
providing generic mechanisms that architects can use. They will add the
policies they think they need on top.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 19:51:52 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY9G7-00065c-N5; Wed, 19 Sep 2007 19:47:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY9G6-00065O-0t
	for ldapext@ietf.org; Wed, 19 Sep 2007 19:47:06 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY9G0-0002EV-Ox
	for ldapext@ietf.org; Wed, 19 Sep 2007 19:47:06 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8JNkmR9001250
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Sep 2007 19:46:48 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8JNklmU006569;
	Wed, 19 Sep 2007 19:46:47 -0400
Received: from [172.16.25.166] (dhcp-172-16-25-166.sfbay.redhat.com
	[172.16.25.166])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8JNkkCZ025726; Wed, 19 Sep 2007 19:46:46 -0400
Message-ID: <46F1B4E6.90808@redhat.com>
Date: Wed, 19 Sep 2007 16:46:46 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
In-Reply-To: <20070917143336.GA7266@tile.skills-1st.co.uk>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1159185327=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1159185327==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050303000403040105070503"

This is a cryptographically signed message in MIME format.

--------------ms050303000403040105070503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Andrew Findlay wrote:
> At the recent LDAP conference in Cologne there was wide support for an
> effort to improve some of the commonly-used schema definitions. In
> particular, the fact that groupOfNames does not permit an empty group
> was felt to be a significant problem.
>
>   
So the discussion about this highlights the basic issues around the 
current approach to grouping. Fundamentally there are two classes of 
user for a grouping mechanism 1) those who need to know how to build and 
generally administer groups 2) those who need to use groups but care not 
a whit how they came to be. Currently, every time a new group type is 
invented both classes need to understand all the ins and outs of the new 
group type and they must agree on what those ins and outs mean.

This is broken. Non-administrative clients should be able to write to a 
single group interface once and forever after be left to get on with 
clientship.  Innovation for the first class of user is then left to 
prosper without hindrance, without client breakage, and without chickens 
and eggs. There is a suitable way to do this: the memberof attribute, if 
populated it will supply all the needs of the second class of user both 
now and into the future, it even solves some of sticky performance 
problems around gathering suitable attribute values from each memberof 
the group. It is also agnostic to method of attaining membership, 
membership simply is.

Agreeing on something like this will allow the conversation to move 
forward on the mechanisms of group membership without requiring clients 
and servers to be modified every time a new method is developed. It 
allows for both proprietary and custom grouping mechanisms without 
stepping on toes or requiring IETF sanction to be generally useful and 
so reduces the barrier to adoption. Most of all, it is a stable platform 
for interoperability for at least the second class of user.

-- 
Pete


--------------ms050303000403040105070503
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MTkyMzQ2NDZaMCMGCSqGSIb3DQEJBDEWBBSUNHKbW6kZ5VbX
N4ERb6RhdoDVdjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEAiQr6OU0NAIlziSJnaBmFGPUyasCMv8ea8bPDNL2PlO44+cDxDOh/GtYEPnv3
Ws1SOW8IZD/zxviqKcQvXfeqUzFS7eMU/tVyWTtI0vtuUvtnVThOvq1h+Lk60Q0YCoxj2Wn2
szNaRdFcCCWkAoDgfYg6QIWhJ83TANHtab1LCYxWIgCT1TrqC/qtzsRB9azAAligRCppa7Sq
4030RvLjzKIliDW7ij0yq0h4G0zUuxY2IsPpg9fzvVtti4SPc6zNPeOz1zP2yZW924DsU/UI
LN4cMmCPFuy803TQVldXlRReLlj4nBFN//96WvgWcwe8u9IeN4RfH1Vsp0njK3ujegAAAAAA
AA==
--------------ms050303000403040105070503--


--===============1159185327==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1159185327==--




From ldapext-bounces@ietf.org Wed Sep 19 20:22:30 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IY9ku-0004r1-6I; Wed, 19 Sep 2007 20:18:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IY9kt-0004qc-Gk
	for ldapext@ietf.org; Wed, 19 Sep 2007 20:18:55 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IY9kn-0002tv-AC
	for ldapext@ietf.org; Wed, 19 Sep 2007 20:18:55 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8K0Ic3A017737; Wed, 19 Sep 2007 19:18:38 -0500
Message-ID: <46F1BBE1.3060605@highlandsun.com>
Date: Wed, 19 Sep 2007 17:16:33 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Pete Rowley <prowley@redhat.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46F1B4E6.90808@redhat.com>
In-Reply-To: <46F1B4E6.90808@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Pete Rowley wrote:
> Andrew Findlay wrote:
>> At the recent LDAP conference in Cologne there was wide support for an
>> effort to improve some of the commonly-used schema definitions. In
>> particular, the fact that groupOfNames does not permit an empty group
>> was felt to be a significant problem.
>>   
> So the discussion about this highlights the basic issues around the 
> current approach to grouping. Fundamentally there are two classes of 
> user for a grouping mechanism 1) those who need to know how to build and 
> generally administer groups 2) those who need to use groups but care not 
> a whit how they came to be. Currently, every time a new group type is 
> invented both classes need to understand all the ins and outs of the new 
> group type and they must agree on what those ins and outs mean.
> 
> This is broken. Non-administrative clients should be able to write to a 
> single group interface once and forever after be left to get on with 
> clientship.  Innovation for the first class of user is then left to 
> prosper without hindrance, without client breakage, and without chickens 
> and eggs. There is a suitable way to do this: the memberof attribute, if 
> populated it will supply all the needs of the second class of user both 
> now and into the future, it even solves some of sticky performance 
> problems around gathering suitable attribute values from each memberof 
> the group. It is also agnostic to method of attaining membership, 
> membership simply is.

Ah, if only it were so easy. But will memberOf expand for recursions? If user 
A is a member of a group B that is nested in group C, will it list only group 
B or both group B and group C? Attacking the problem from the opposite 
direction doesn't actually eliminate the question of whether and how nesting 
should be handled. All of the same ambiguities still exist.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 20:41:24 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYA4H-0003fP-7j; Wed, 19 Sep 2007 20:38:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYA4F-0003fJ-Uw
	for ldapext@ietf.org; Wed, 19 Sep 2007 20:38:55 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYA4F-0003Dn-LP
	for ldapext@ietf.org; Wed, 19 Sep 2007 20:38:55 -0400
Received: from [202.164.192.219] (helo=[192.168.99.100])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IYA4D-0006Vm-IQ; Thu, 20 Sep 2007 10:38:54 +1000
Message-ID: <46F1C120.8080609@eb2bcom.com>
Date: Thu, 20 Sep 2007 10:38:56 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>	<20070918114234.GB12296@tile.skills-1st.co.uk>	<46F0602C.2080806@eb2bcom.com>
	<20070919084910.GD12296@tile.skills-1st.co.uk>
In-Reply-To: <20070919084910.GD12296@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Andrew,

Andrew Findlay wrote:
> On Wed, Sep 19, 2007 at 09:33:00AM +1000, Steven Legg wrote:
> 
>> Instead of defining a specific object class, perhaps all we need is a
>> *convention* that any entry that contains the member attribute is to
>> be treated as a group.
> 
> It would still need an object class that permits the member attribute.
> How would such a convention represent an empty group?

I stated it badly. What I meant was: any entry of an object class that
permits the member attribute is to be treated as a group. An empty group
is an entry of an object class where the member attribute is defined to
be optional, and the member attribute does not currently appear in the
entry. The convention could also be extended object classes where the
member attribute is permitted by a content rule.

Regards,
Steven

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 21:23:02 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYAhX-00028L-Vp; Wed, 19 Sep 2007 21:19:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYAhW-000274-Qa
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:19:30 -0400
Received: from rufus.isode.com ([62.3.217.251])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYAhW-0004Hw-C1
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:19:30 -0400
Received: from [192.168.1.200] ((unknown) [24.180.46.142]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <RvHKnwBEpj-T@rufus.isode.com>; Thu, 20 Sep 2007 02:19:28 +0100
X-SMTP-Protocol-Errors: NORDNS
In-Reply-To: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
References: <20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
Message-Id: <C329EB91-5CD8-4157-9B15-6DE4E507D7AE@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Date: Wed, 19 Sep 2007 14:19:57 +0100
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
X-Mailer: Apple Mail (2.752.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


On Sep 18, 2007, at 3:44 AM, Ramsay, Ron wrote:

> Why not try to get the appropriate RFC revised to make 'member'
> optional?

X.501:
> The definition of information objects such as object classes,  
> attribute types, matching rules and name forms which have been  
> registered (i.e., assigned a name of type object identifier) are  
> static and cannot be modified. Changes to the semantics of such  
> information objects require the assignment of new object identifiers.

BCP 118 [RFC 4512]:
>    Published schema elements SHALL NOT be redefined.  Replacement  
> schema
>    elements (new OIDs, new NAMEs) SHOULD be defined as needed.

-- Kurt


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

From ldapext-bounces@ietf.org Wed Sep 19 21:23:02 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYAiu-0003Hm-0T; Wed, 19 Sep 2007 21:20:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYAis-0003HV-RF
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:20:54 -0400
Received: from rufus.isode.com ([62.3.217.251])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYAir-0004Jg-MZ
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:20:54 -0400
Received: from [192.168.1.200] ((unknown) [24.180.46.142]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <RvHK8ABEpiSg@rufus.isode.com>; Thu, 20 Sep 2007 02:20:49 +0100
X-SMTP-Protocol-Errors: NORDNS
In-Reply-To: <20070917143336.GA7266@tile.skills-1st.co.uk>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
Message-Id: <47CDF66D-F949-4CD9-AA46-09A2E688CC06@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Date: Wed, 19 Sep 2007 14:20:02 +0100
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-Mailer: Apple Mail (2.752.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew,

Glad to see you following through on this.

 > The LDAP groupOfEntries object class

I don't like the name of the class.  It's not a group of entrys, but  
a group of names of objects (entries), in particular a group of  
distinguished names.  I suggest the class be named 'groupOfDNs'.

> Abstract
>
>    This memo describes the LDAP groupOfEntries object class

I suggest:
	This memo describes the LDAP/X.500 'groupOfEntries' object class...


> which is a
>    replacement for the existing groupOfNames class.

I rather the I-D say:
	... for representing groups.  The new class is introduced as an  
alternative to the 'groupOfNames' class.


I dislike any language that suggests this new class deprecates the  
groupOfNames.   I rather the I-D propose an alternative to  
groupOfNames, and leave the choice of which group class to use to  
directory applications (preferable stated in an applicability  
statement).

> The new class
>    permits the creation of empty groups.

I suggest:
	Unlike 'groupOfNames', 'groupOfEntries' can represent a group whose  
membership is empty.



>    If approved as a Standards Track document, this document will  
> update RFC4519 [2]

I recommend this I-D propose an extension, not an update any document  
(e.g., RFC 4519) which is part of the LDAP technical specification  
[RFC 4510].  In particular, I recommend this I-D not "update" RFC  
4519.  That is, I recommend this sentence be stricken.

(Editorial note: no citations should be used within the Abstract of  
the document.)

> 1.  Introduction

I think the Introduction doesn't stand well be itself.  That is, it  
seems to rely on information provided in the Abstract.  I suggest the  
Introduction start by restating (in new words, with cites), and  
expanding upon, the Abstract.

>    A groupOfNames object class has existed since the earliest X.521  
> [1]
>    standard.  It has an identical definition in LDAP (RFC4519 [2]).

I suggest the second sentence read:
	An LDAP [RFC4510] description [RFC4512] for this class is provided  
in RFC 4519 [RFC4519].

I suggest you then include the LDAP description:
	That description is:
		      ( 2.5.6.9 NAME 'groupOfNames' SUP top STRUCTURAL
			MUST ( member $ cn )
			MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) )

> The
>    class is used to define entries holding DN-valued member  
> attributes,

I suggest
	The class is used to represent groups of names.

>    each value pointing to an entry that represents a single member of
>    the group being described, or to another entry of type  
> groupOfNames.

Suggest:
	Each group object may contain a 'member' [X.520][RFC4519] attribute  
whose values are name members.  Each value is a distinguished name of  
an object.  The entity represented by the named object is consider a  
member of group.  If the member attribute is not present in the  
object, the group membership is empty.


Which raises an interesting question which the I-D needs to address:  
how does a DUA determine reading a group returned without any member  
attribute determine whether the group is empty or wether the DSA was  
unwilling (or unable) to provide the membership?  The DSA could, I  
guess, return member without its values to represent the group was  
non-empty and only return the entry less the member attribute if the  
entry didn't contain member.  However, this is likely problematic.  I  
think this needs further list discussion.

	
>
>    groupOfNames is a structural object class, so it is often the only
>    class used in the definition of group objects.
>
>    Experience has shown that the definition of groupOfNames causes
>    difficulties in practice.  In particular, the fact that 'member'  
> is a
>    mandatory attribute means that it is not possible to create an  
> empty
>    group or to delete the last member from a group.  This leads to
>    artificial tricks such as making every group a member of itself, or
>    adding a dummy member to every group when it is created.  These
>    tricks in turn make the management of groups more complex and prone
>    to error.  Groups are commonly used to control access to resources,
>    so management errors can lead to security risks.

Yes.  For instance, if one adds the empty DN to a group is  
problematic as the empty DN is often used to represent anonymous  
users, hence adding an empty DN to member implies anonymous users are  
members of the group.

>
>    There does not appear to be any good reason for the 'member'
>    attribute to be mandatory.  This memo describes a new object class
>    called groupOfEntries that is equivalent to groupOfNames in all  
> other
>    respects but which makes 'member' an optional attribute.
>
>
> 2.  The existing groupOfNames object class

I would fold this section into the Introduction.
>
>    RFC4519 [2] contains this definition:
>
>    The 'groupOfNames' object class is the basis of an entry that
>    represents a set of named objects including information related to
>    the purpose or maintenance of the set.  (Source: X.521 [1])

I now notice this description is bit off.  The X.521 description is  
better: "The Group Of Names object class is used to define entries  
representing an unordered set of names which represent individual  
objects or other groups of names."  I rather include the X.521 text  
(early in the Introduction).

>
>          ( 2.5.6.9 NAME 'groupOfNames'
>             SUP top
>             STRUCTURAL
>             MUST ( member $
>                   cn )
>             MAY ( businessCategory $
>                   seeAlso $
>                   owner $
>                   ou $
>                   o $
>                   description ) )
>
>    The inclusion of 'member' in the 'MUST' section of the definition
>    prevents empty groups from being created.
>
>
> 3.  The groupOfEntries object class

I rather the description of this class instead be a rewording of the  
X.521 groupOfNames description.
>
>    The 'groupOfEntries' object class is the basis of an entry that
>    represents a set of named objects including information related to
>    the purpose or maintenance of the set.  It should be used in
>    preference to the 'groupOfNames' object class.

I think the last sentence should be stricken (see above).
>
>          ( 1.2.826.0.1.3458854.2.1.1.1 NAME 'groupOfEntries'
>             SUP top
>             STRUCTURAL
>             MUST ( cn )
>             MAY ( member $
>                   businessCategory $
>                   seeAlso $
>                   owner $
>                   ou $
>                   o $
>                   description ) )
>
>    This object class allows groups to be empty.  In all other respects
>    it behaves like the groupOfNames object class.
>
>    The OID assigned to this object class is delegated by Skills 1st  
> Ltd.
>
>
> 4.  Effect on other documents
>
>    This draft deprecates the use of the groupOfNames object class in
>    RFC4519 [2] and replaces it with the groupOfEntries class.

I think this section should be stricken (see above).

I suggest adding a section here addressing the 'interesting question'  
I raised above.

There should also be a section discussing nested group semantics.   
This needs further discussion I think. From ldapext-bounces@ietf.org Wed Sep 19 21:23:02 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYAhX-00028L-Vp; Wed, 19 Sep 2007 21:19:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYAhW-000274-Qa
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:19:30 -0400
Received: from rufus.isode.com ([62.3.217.251])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYAhW-0004Hw-C1
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:19:30 -0400
Received: from [192.168.1.200] ((unknown) [24.180.46.142]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <RvHKnwBEpj-T@rufus.isode.com>; Thu, 20 Sep 2007 02:19:28 +0100
X-SMTP-Protocol-Errors: NORDNS
In-Reply-To: <52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
References: <20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>
	<22F5E36297524347B40AFAA7CDD4CB4D01F08F0B@G3W0067.americas.hpqcorp.net>
	<52681ACFF63C114F8A3C3651FC9D301F825312@AUSYMS11.ca.com>
Message-Id: <C329EB91-5CD8-4157-9B15-6DE4E507D7AE@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Date: Wed, 19 Sep 2007 14:19:57 +0100
To: "Ramsay, Ron" <Ron.Ramsay@ca.com>
X-Mailer: Apple Mail (2.752.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


On Sep 18, 2007, at 3:44 AM, Ramsay, Ron wrote:

> Why not try to get the appropriate RFC revised to make 'member'
> optional?

X.501:
> The definition of information objects such as object classes,  
> attribute types, matching rules and name forms which have been  
> registered (i.e., assigned a name of type object identifier) are  
> static and cannot be modified. Changes to the semantics of such  
> information objects require the assignment of new object identifiers.

BCP 118 [RFC 4512]:
>    Published schema elements SHALL NOT be redefined.  Replacement  
> schema
>    elements (new OIDs, new NAMEs) SHOULD be defined as needed.

-- Kurt


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

From ldapext-bounces@ietf.org Wed Sep 19 21:40:32 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYAze-0006DJ-DB; Wed, 19 Sep 2007 21:38:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYAzc-0006BW-Hz
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:38:12 -0400
Received: from rufus.isode.com ([62.3.217.251])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYAzc-0004q6-3r
	for ldapext@ietf.org; Wed, 19 Sep 2007 21:38:12 -0400
Received: from [192.168.1.200] ((unknown) [24.180.46.142]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <RvHPAABEpiYd@rufus.isode.com>; Thu, 20 Sep 2007 02:38:09 +0100
X-SMTP-Protocol-Errors: NORDNS
In-Reply-To: <46EF07BD.1010801@padl.com>
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
Message-Id: <6ABF4435-91C1-4BCC-B35B-43817E39A8A3@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
Date: Wed, 19 Sep 2007 18:37:56 -0700
To: Luke Howard <lukeh@padl.com>
X-Mailer: Apple Mail (2.752.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


On Sep 18, 2007, at 12:03 AM, Luke Howard wrote:

> Another thing that would be useful might be to define the behaviour  
> of nested groups, eg. should the client expand them?

The entity making use of the group should do the expansion.  If a DSA  
is using them in access controls, then it should expand them.  If a  
DUA is using them for its purposes, it should expand them.  That is,  
same semantics/expectations as groupOfNames nested groups.

If there is desire to introduce a group class with a different  
semantic/expectations, I think it should be proposed separately.

-- Kurt

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 22:48:46 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYC1O-0001Pz-FM; Wed, 19 Sep 2007 22:44:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYC1N-0001Ov-Da
	for ldapext@ietf.org; Wed, 19 Sep 2007 22:44:05 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYC1N-0006Le-0t
	for ldapext@ietf.org; Wed, 19 Sep 2007 22:44:05 -0400
Received: from cust3803.vic01.dataco.com.au ([202.164.192.219]
	helo=[192.168.99.100]) by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IYC1B-0002TL-Jn; Thu, 20 Sep 2007 12:43:54 +1000
Message-ID: <46F1DE64.1040509@eb2bcom.com>
Date: Thu, 20 Sep 2007 12:43:48 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group
References: <46F0ED1E.10004@stroeder.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<1190210820.31971.105.camel@localhost.localdomain>
In-Reply-To: <1190210820.31971.105.camel@localhost.localdomain>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> On Wed, 2007-09-19 at 11:46 +0100, Andrew Findlay wrote:
>> On Wed, Sep 19, 2007 at 09:35:41AM +1000, Steven Legg wrote:
>>
>>> The advantage of *not* having nested groups is that it is sufficient
>>> to just read the values of the member attribute to determine group
>>> membership. If there are nested groups, then it is necessary to
>>> read each of the entries named in the values of the member attribute
>>> to see which of them, if any, are themselves groups. That could be
>>> a big performance hit for a group with a large set of members.
>> Good point. Servers have more options here, but a client dealing with
>> nested groups has to do a silly amount of work.
> 
> No, its not a good point, as that happens only if the designer of the
> directory decides to use this feature.
> If he so decides, he knows the limits and the problems he goes on doing
> that and it is his responsibility.

But how does a directory client know that the directory administrator is
using nested groups in the member attribute ? It would have to read the
entries listed in the member attribute to find out, so it incurs the
overhead even if nested groups are not being used. On the other hand,
the presence of a nestedGroup attribute is a dead giveaway, and also
limits the amount work the client has to do when nested groups are
being used.

Regards,
Steven


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 19 23:09:22 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYCNP-0005i4-GN; Wed, 19 Sep 2007 23:06:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYCNN-0005gJ-Tf
	for ldapext@ietf.org; Wed, 19 Sep 2007 23:06:49 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYCNN-00071g-Jn
	for ldapext@ietf.org; Wed, 19 Sep 2007 23:06:49 -0400
Received: from [202.164.192.219] (helo=[192.168.99.100])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IYCNN-0003DE-0w; Thu, 20 Sep 2007 13:06:49 +1000
Message-ID: <46F1E3C4.1090901@eb2bcom.com>
Date: Thu, 20 Sep 2007 13:06:44 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] Nested group
References: <46F0ED1E.10004@stroeder.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
In-Reply-To: <20070919104644.GE12296@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Andrew,

Andrew Findlay wrote:
> It looks as if the nested groups issue needs tackling. Should I expand
> this I-D to include it?

I think that would be a good idea.

 > The consensus seems to be:
> 
> 1)	groupOfEntries member attributes should not point to groups
> 	whose members are to be considered part of the group being
> 	described.
> 	
> 	I see no problem with allowing them to point to groups if
> 	expansion/nesting/inclusion is not required.

It is okay to restrict the interpretation of the member attribute
as an attribute of the groupOfEntries object class, but if we
consider a group as being any entry of an object class that
permits a member attribute (and/or the nestedGroup attribute),
then restricting the interpretation of the member attribute in the
more general context will conflict with some current deployments.
If we are going to allow a variety of object classes to define groups,
then we should define a new attribute, e.g., called directMember, to
replace the member attribute.

Regards,
Steven

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 00:46:59 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYDs3-0007qm-Lz; Thu, 20 Sep 2007 00:42:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYDs1-0007h3-J1
	for ldapext@ietf.org; Thu, 20 Sep 2007 00:42:33 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYDru-0000OJ-Om
	for ldapext@ietf.org; Thu, 20 Sep 2007 00:42:33 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8K4fvVJ017273
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 20 Sep 2007 04:42:00 GMT
Message-ID: <46F1FACB.1060903@padl.com>
Date: Thu, 20 Sep 2007 14:44:59 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com><46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk><1190220132.31971.147.camel@localhost.localdomain><46F15776.4090804@highlandsun.com>	<1190226457.31971.163.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044983@MLNYC727MB.amrs.win.ml.com>
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044983@MLNYC727MB.amrs.win.ml.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ldapext@ietf.org, simo <idra@samba.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Liben, Michael (GTI) wrote:
> In Active Directory, Microsoft maintains 'back link' attributes. One of
> these is memberOf. When an object is added or removed from a group, a
> process runs that updates the back link attribute on the object. If the
> member object is moved or deleted, another process updates the group's
> member attribute accordingly. 
>   
This isn't quite correct. Linked references are maintained in a separate 
table in the DIB, and returned dynamically at search time. The 
background process you're referring to handles references (linked or 
not) to entries in non-local partitions.

-- Luke

-- 
www.padl.com | www.lukehoward.com


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 04:05:02 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYGxb-0002hB-OC; Thu, 20 Sep 2007 04:00:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYGxb-0002dg-0F
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:00:31 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYGxa-0006NI-4J
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:00:30 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 730B17AE0;
	Thu, 20 Sep 2007 10:00:28 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 21854-06; Thu, 20 Sep 2007 10:00:11 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id EED9E7ACE;
	Thu, 20 Sep 2007 10:00:10 +0200 (CEST)
Message-ID: <46F22889.7000902@stroeder.com>
Date: Thu, 20 Sep 2007 10:00:09 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
References: <46F0ED1E.10004@stroeder.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com> <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>
In-Reply-To: <20070919104644.GE12296@tile.skills-1st.co.uk>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew Findlay wrote:
> 
> It looks as if the nested groups issue needs tackling.

Which is IMO out of scope.

> Should I expand this I-D to include it?

-1

> 1)	groupOfEntries member attributes should not point to groups
> 	whose members are to be considered part of the group being
> 	described.
> 	
> 	I see no problem with allowing them to point to groups if
> 	expansion/nesting/inclusion is not required.

+1

But the client MAY do expansion of nested groups.

> 2)	There should be a new aux class and attribute to support
> 	client-side group nesting.
> 
> 	Servers can support group nesting in more efficient ways and
> 	some of them already do. Should there be an attempt to
> 	standardise the schema that supports this?

The nested group thing should be defined in a separate draft defining a
separate AUXILIARY object class.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 04:38:04 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHUq-0003Lf-5f; Thu, 20 Sep 2007 04:34:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHUo-0003Ks-R6
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:34:50 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYHUi-0006Ov-HO
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:34:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 116777AE0;
	Thu, 20 Sep 2007 10:34:28 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22414-06; Thu, 20 Sep 2007 10:34:11 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 5939E7ACE;
	Thu, 20 Sep 2007 10:34:11 +0200 (CEST)
Message-ID: <46F23083.7040209@stroeder.com>
Date: Thu, 20 Sep 2007 10:34:11 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com><20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Michael,

please keep citations for reference.

Liben, Michael (GTI) wrote:
>> [..discussion about separate attribute for nested groups..]
> This anticipates a reliable mechanism that ensures direct members are
> not added to the nestedGroups attribute and that nested groups are
> not inadvertently added to the member attribute.

Good point. But note that this is a pertinent problem with many
attributes where additional constraints are defined in a specification
but cannot be enforced by most server implementations.

> How would the server
> respond if an object is included in both attributes?

If the server can detect this I'd think 'constraintViolation' would be
appropriate.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

From ldapext-bounces@ietf.org Thu Sep 20 04:38:04 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHWF-0004J3-Pv; Thu, 20 Sep 2007 04:36:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHWE-0004IL-From ldapext-bounces@ietf.org Thu Sep 20 04:38:04 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHUq-0003Lf-5f; Thu, 20 Sep 2007 04:34:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHUo-0003Ks-R6
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:34:50 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYHUi-0006Ov-HO
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:34:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 116777AE0;
	Thu, 20 Sep 2007 10:34:28 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22414-06; Thu, 20 Sep 2007 10:34:11 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 5939E7ACE;
	Thu, 20 Sep 2007 10:34:11 +0200 (CEST)
Message-ID: <46F23083.7040209@stroeder.com>
Date: Thu, 20 Sep 2007 10:34:11 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com>
	<46F063BE.5020900@padl.com><20070917143336.GA7266@tile.skills-1st.co.uk><46EF07BD.1010801@padl.com><20070918110511.GF23300@tile.skills-1st.co.uk><46F060CD.20008@eb2bcom.com><20070919104644.GE12296@tile.skills-1st.co.uk><1190210820.31971.105.camel@localhost.localdomain><20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Michael,

please keep citations for reference.

Liben, Michael (GTI) wrote:
>> [..discussion about separate attribute for nested groups..]
> This anticipates a reliable mechanism that ensures direct members are
> not added to the nestedGroups attribute and that nested groups are
> not inadvertently added to the member attribute.

Good point. But note that this is a pertinent problem with many
attributes where additional constraints are defined in a specification
but cannot be enforced by most server implementations.

> How would the server
> respond if an object is included in both attributes?

If the server can detect this I'd think 'constraintViolation' would be
appropriate.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

From ldapext-bounces@ietf.org Thu Sep 20 04:38:04 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHWF-0004J3-Pv; Thu, 20 Sep 2007 04:36:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHWE-0004IL-F0
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:36:18 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYHWD-0006Rk-3z
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:36:18 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 4390C7AE0;
	Thu, 20 Sep 2007 10:36:16 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 21854-09; Thu, 20 Sep 2007 10:35:58 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 4C2467ACE;
	Thu, 20 Sep 2007 10:35:58 +0200 (CEST)
Message-ID: <46F230EE.7050304@stroeder.com>
Date: Thu, 20 Sep 2007 10:35:58 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com>	
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>	 <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>	
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>	
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>	
	<1190210820.31971.105.camel@localhost.localdomain>	
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
In-Reply-To: <1190220132.31971.147.camel@localhost.localdomain>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> 
> Actually I think this problem would be better solved by a control to ask
> the server to do the calculations for us

Or better an extended operation?
Some query like "Is user X member of the groups A, B and C with
resolving nested groups?"

> On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:
>> I am not sure that I understand your point there. Remember that
>> groupOfEntries is a STRUCTURAL class, so it cannot be added to an
>> existing entry or removed from one.
> 
> AHHH Right, that was the other thing in the back of my mind that kept
> bogging me, but I forgot to post about it.

I'd like to keep two separate threads with different subjects. 1. for
discussing directly the draft itself and 2. discussing ways for defining
nested groups. Whether the new group object class should be STRUCTURAL
should be discussed under 1, please.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext





F0
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:36:18 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IYHWD-0006Rk-3z
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:36:18 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 4390C7AE0;
	Thu, 20 Sep 2007 10:36:16 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 21854-09; Thu, 20 Sep 2007 10:35:58 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 4C2467ACE;
	Thu, 20 Sep 2007 10:35:58 +0200 (CEST)
Message-ID: <46F230EE.7050304@stroeder.com>
Date: Thu, 20 Sep 2007 10:35:58 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group
References: <46EF07BD.1010801@padl.com>	
	<20070918110511.GF23300@tile.skills-1st.co.uk>
	<46F060CD.20008@eb2bcom.com>	 <46F063BE.5020900@padl.com>
	<20070917143336.GA7266@tile.skills-1st.co.uk>	
	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>	
	<46F060CD.20008@eb2bcom.com>
	<20070919104644.GE12296@tile.skills-1st.co.uk>	
	<1190210820.31971.105.camel@localhost.localdomain>	
	<20070919152141.GH12296@tile.skills-1st.co.uk>
	<1190220132.31971.147.camel@localhost.localdomain>
In-Reply-To: <1190220132.31971.147.camel@localhost.localdomain>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> 
> Actually I think this problem would be better solved by a control to ask
> the server to do the calculations for us

Or better an extended operation?
Some query like "Is user X member of the groups A, B and C with
resolving nested groups?"

> On Wed, 2007-09-19 at 16:21 +0100, Andrew Findlay wrote:
>> I am not sure that I understand your point there. Remember that
>> groupOfEntries is a STRUCTURAL class, so it cannot be added to an
>> existing entry or removed from one.
> 
> AHHH Right, that was the other thing in the back of my mind that kept
> bogging me, but I forgot to post about it.

I'd like to keep two separate threads with different subjects. 1. for
discussing directly the draft itself and 2. discussing ways for defining
nested groups. Whether the new group object class should be STRUCTURAL
should be discussed under 1, please.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext





From ldapext-bounces@ietf.org Thu Sep 20 04:46:10 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHei-0007BW-TK; Thu, 20 Sep 2007 04:45:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHeh-000795-KQ
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:45:03 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYHeh-0007cL-40
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:45:03 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id 1664A7AD7;
	Thu, 20 Sep 2007 10:45:00 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22414-08; Thu, 20 Sep 2007 10:44:43 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 63DB27ACC;
	Thu, 20 Sep 2007 10:44:42 +0200 (CEST)
Message-ID: <46F232FA.6040702@stroeder.com>
Date: Thu, 20 Sep 2007 10:44:42 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: simo <idra@samba.org>
Subject: Re: [ldapext] Nested group (was: groupOfEntries object class proposal)
References: <1190220132.31971.147.camel@localhost.localdomain>	<DD9F4CC53AE89944A5C825781D5E3090044982@MLNYC727MB.amrs.win.ml.com>	<20070919180127.GK12296@tile.skills-1st.co.uk>
	<1190225760.31971.161.camel@localhost.localdomain>
In-Reply-To: <1190225760.31971.161.camel@localhost.localdomain>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

simo wrote:
> On Wed, 2007-09-19 at 19:01 +0100, Andrew Findlay wrote:
>> On Wed, Sep 19, 2007 at 01:07:13PM -0400, Liben, Michael (GTI) wrote:
>>
>>> This anticipates a reliable mechanism that ensures direct members
>>> are not added to the nestedGroups attribute and that nested groups are
>>> not inadvertently added to the member attribute.
>> I don't think there needs to be any server-side control on that. There
>> are many cases in LDAP where the protocol and schema allow the client
>> to do 'silly' things. If we try to tie things down too hard there is
>> no room for flexibility. A designer can choose to use ACLs or
>> structure definitions to apply some measure of control, or can rely on
>> 'business logic' in the update process to do so.
> 
> The problem is that you have a generic "DN" container that is given
> specific semanthics. IE nestedGroupObject is supposed to contain only
> entries that have groupOfEntries as its STRUCTURAL class, but you do not
> enforce it. So it may contain anything. Same for member.
> 
> This just means clients have to cope with bad entries.
> 
> I think that the problem is caused by artificial separation of members
> in 2 classes.

NACK. Looking at the constraint enforcing in some server implementations
I'd guess having two separate attributes makes it easier to define and
enforce such constraints.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 04:57:22 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYHo2-0004Yx-PM; Thu, 20 Sep 2007 04:54:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYHo1-0004Vq-4P
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:54:41 -0400
Received: from 188-32-124-83.dsl.3u.net ([83.124.32.188]
	helo=mstroeder.homeip.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYHo0-0007sp-NY
	for ldapext@ietf.org; Thu, 20 Sep 2007 04:54:41 -0400
Received: from localhost (localhost [127.0.0.1])
	by mstroeder.homeip.net (Postfix) with ESMTP id DAB107ACC;
	Thu, 20 Sep 2007 10:54:39 +0200 (CEST)
Received: from mstroeder.homeip.net ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22414-10; Thu, 20 Sep 2007 10:54:12 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2])
	by mstroeder.homeip.net (Postfix) with ESMTP id 12DB07AE4;
	Thu, 20 Sep 2007 10:54:12 +0200 (CEST)
Message-ID: <46F23533.6080604@stroeder.com>
Date: Thu, 20 Sep 2007 10:54:11 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] Nested group
References: <46F0ED1E.10004@stroeder.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>
	<46F1E3C4.1090901@eb2bcom.com>
In-Reply-To: <46F1E3C4.1090901@eb2bcom.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Steven Legg wrote:
> 
> If we are going to allow a variety of object classes to define groups,
> then we should define a new attribute, e.g., called directMember, to
> replace the member attribute.

Steven, so the whole thing would boil down to define two new attributes
'directMember' and 'nestedGroup' with a clear specification how to
interprete them?

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 13:16:37 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYPaM-0003qJ-0A; Thu, 20 Sep 2007 13:13:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYPaJ-0003nF-7h
	for ldapext@ietf.org; Thu, 20 Sep 2007 13:13:03 -0400
Received: from dns.daasi.de ([134.2.217.130] helo=hera.daasi.de)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYPaI-0005VI-GL
	for ldapext@ietf.org; Thu, 20 Sep 2007 13:13:02 -0400
Received: by hera.daasi.de (Postfix, from userid 65534)
	id 801D110E90F; Thu, 20 Sep 2007 19:14:28 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on hera.daasi.de
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.3
Received: from localhost (localhost [127.0.0.1])
	by hera.daasi.de (Postfix) with ESMTP id F3E1710E90E;
	Thu, 20 Sep 2007 19:14:26 +0200 (CEST)
Received: from hera.daasi.de ([127.0.0.1])
	by localhost (hera [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 27386-07; Thu, 20 Sep 2007 19:14:25 +0200 (CEST)
Received: from [134.2.217.63] (ariadne.int.daasi.de [134.2.217.63])
	by hera.daasi.de (Postfix) with ESMTP id C616010E90C;
	Thu, 20 Sep 2007 19:14:25 +0200 (CEST)
Message-ID: <46F2A965.8040209@daasi.de>
Date: Thu, 20 Sep 2007 19:09:57 +0200
From: Peter Gietz <peter.gietz@daasi.de>
User-Agent: Thunderbird 2.0.0.0 (X11/20070425)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>
	<20070918110511.GF23300@tile.skills-1st.co.uk>
In-Reply-To: <20070918110511.GF23300@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: by amavisd-new at daasi.de
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Luke Howard <lukeh@padl.com>, ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew Findlay wrote:
> On Tue, Sep 18, 2007 at 09:03:25AM +1000, Luke Howard wrote:
>
>  =20
>> Another thing that would be useful might be to define the behaviour of=
=20
>> nested groups, eg. should the client expand them?
>>    =20
>
> A good point, but I would be wary of being too prescriptive here. Some
> servers provide an auxiliary object class that causes the groups to
> expanded server-side: that would continue to work with groupOfEntries
> (though there is a management issue with anything that triggers
> server-side tricks). Whether a *client* should expand groups will
> depend on why the client wants the group info in the first place, and I
> don't think it is necessary to force the issue one way or the other.
>
> It might be worth adding a statement that makes it clear that
> a groupOfEntries can have members of *any* type, so nested groups are
> explicitly possible. The precise semantics should be defined by the
> application schema designer.
>  =20
Yes this sound very good to me (+1).
>  =20
>> It would make sense to use this object class for rfc2307bis too=20
>> (whenever that is completed :-))
>>    =20
>
> Maybe so, but rfc2307bis is a much more complex issue!
>  =20
Yes but work on finishing that would really help a lot. @Luke: please=20
find some time for that, you will help the whole LDAP world, even more=20
than you already did with RFC2307. I am sure a new draft from you will=20
revive discussion and eventually lead to  consensus.

Cheers,

Peter

> Andrew
>  =20


--=20
_______________________________________________________________________

Peter Gietz (CEO)
DAASI International GmbH                   phone: +49 7071 2970334
Wilhelmstr. 106                            Fax:   +49 7071 295114
D-72074 T=FCbingen                           mail:  peter.gietz@daasi.de
Germany                                    Web:   www.daasi.de

DAASI International GmbH, T=FCbingen
Gesch=E4ftsf=FChrer Peter Gietz, Amtsgericht Stuttgart HRB 382175

Directory Applications for Advanced Security and Information Management
_______________________________________________________________________




_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 13:27:08 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYPld-0007vj-Rk; Thu, 20 Sep 2007 13:24:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYPlc-0007vO-8s
	for ldapext@ietf.org; Thu, 20 Sep 2007 13:24:44 -0400
Received: from mlnya404er.ml.com ([199.43.38.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYPlV-000423-U9
	for ldapext@ietf.org; Thu, 20 Sep 2007 13:24:44 -0400
Received: from MLNYC851BH.amrs.win.ml.com (unknown [141.128.12.201])
	by mlnya404er.ml.com (Postfix) with ESMTP id 9516955DF3;
	Thu, 20 Sep 2007 13:24:26 -0400 (EDT)
Importance: normal
Priority: normal
Received: from MLNYC803BH.amrs.win.ml.com ([141.128.12.21]) by
	MLNYC851BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Thu, 20 Sep 2007 13:24:26 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	MLNYC803BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Thu, 20 Sep 2007 13:24:26 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [ldapext] Nested group
Date: Thu, 20 Sep 2007 13:24:25 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E30900199C2A6@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group
thread-index: Acf7QK4H+hJnNj6KSqK50HOF8em2CgAammSy
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: <lukeh@padl.com>
X-OriginalArrivalTime: 20 Sep 2007 17:24:26.0299 (UTC)
	FILETIME=[17F0E0B0:01C7FBAB]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Cc: ldapext@ietf.org, idra@samba.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0788905595=="
Errors-To: ldapext-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0788905595==
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7FBAB.17A31141"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7FBAB.17A31141
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Regardless of the implementation (which is not visible from the =
interface), the memberOf attribute contains a list of group and =
groupOfNames objects of which the object is a member. The server =
maintains the integrity of the respective member and memberOf attribute =
values when objects are added, moved or deleted.

This makes it simple toi answer the question, "of what groups is the =
object a member?"=20

=20
--------------------------
Sent from Michael Liben's wireless handheld
=20

-----Original Message-----
From: Luke Howard <lukeh@padl.com>
To: Liben, Michael (GTI)
CC: simo <idra@samba.org>; Howard Chu <hyc@highlandsun.com>; =
ldapext@ietf.org <ldapext@ietf.org>
Sent: Thu Sep 20 00:44:59 2007
Subject: Re: [ldapext] Nested group

Liben, Michael (GTI) wrote:
> In Active Directory, Microsoft maintains 'back link' attributes. One =
of
> these is memberOf. When an object is added or removed from a group, a
> process runs that updates the back link attribute on the object. If =
the
> member object is moved or deleted, another process updates the group's
> member attribute accordingly.=20
>  =20
This isn't quite correct. Linked references are maintained in a separate =

table in the DIB, and returned dynamically at search time. The=20
background process you're referring to handles references (linked or=20
not) to entries in non-local partitions.

-- Luke

--=20
www.padl.com | www.lukehoward.com
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

------_=_NextPart_001_01C7FBAB.17A31141
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<HTML xmlns:eXclaimer=3D"http://www.exclaimer.co.uk" =
xmlns:msxsl=3D"urn:schemas-microsoft-com:xslt" =
xmlns:exc=3D"http://www.exclaimer.co.uk/rtf">
<HEAD>
<META http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-16">


<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dutf-8">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6619.12">
<TITLE>Re: [ldapext] Nested group</TITLE>
</HEAD>
<BODY >
<DIV>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Regardless of the implementation (which is not visible =
from the interface), the memberOf attribute contains a list of group and =
groupOfNames objects of which the object is a member. The server =
maintains the integrity of the respective member and memberOf attribute =
values when objects are added, moved or deleted.<BR>
<BR>
This makes it simple toi answer the question, &quot;of what groups is =
the object a member?&quot;<BR>
<BR>
<BR>
--------------------------<BR>
Sent from Michael Liben's wireless handheld<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Luke Howard &lt;lukeh@padl.com&gt;<BR>
To: Liben, Michael (GTI)<BR>
CC: simo &lt;idra@samba.org&gt;; Howard Chu &lt;hyc@highlandsun.com&gt;; =
ldapext@ietf.org &lt;ldapext@ietf.org&gt;<BR>
Sent: Thu Sep 20 00:44:59 2007<BR>
Subject: Re: [ldapext] Nested group<BR>
<BR>
Liben, Michael (GTI) wrote:<BR>
&gt; In Active Directory, Microsoft maintains 'back link' attributes. =
One of<BR>
&gt; these is memberOf. When an object is added or removed from a group, =
a<BR>
&gt; process runs that updates the back link attribute on the object. If =
the<BR>
&gt; member object is moved or deleted, another process updates the =
group's<BR>
&gt; member attribute accordingly.<BR>
&gt;&nbsp;&nbsp;<BR>
This isn't quite correct. Linked references are maintained in a =
separate<BR>
table in the DIB, and returned dynamically at search time. The<BR>
background process you're referring to handles references (linked or<BR>
not) to entries in non-local partitions.<BR>
<BR>
-- Luke<BR>
<BR>
--<BR>
www.padl.com | www.lukehoward.com<BR>
<BR>
</FONT>
</P>

</DIV>
<DIV>
<HR COLOR=3D"gray">
</DIV>
<DIV><BODY >This message w/attachments (message) may be privileged, =
confidential or proprietary, and if you are not an intended recipient, =
please notify the sender, do not use or share it and delete it. Unless =
specifically indicated, this message is not an offer to sell or a =
solicitation of any investment products or other financial product or =
service, an official confirmation of any transaction, or an official =
statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may =
monitor, review and retain e-communications (EC) traveling through its =
networks/systems. The laws of the country of each sender/recipient may =
impact the handling of EC, and EC may be archived, supervised and =
produced in countries other than the country in which you are located. =
This message cannot be guaranteed to be secure or error-free. This =
message is subject to terms available at the following link: <A =
HREF=3D"http://www.ml.com/e-communications_terms/">http://www.ml.com/e-co=
mmunications_terms/</A>. By messaging with Merrill Lynch you consent to =
the foregoing.</BODY></DIV>
<DIV>
<HR COLOR=3D"gray">
</DIV>
<DIV>
<FONT COLOR=3D"#008000">
</FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<P>
<FONT COLOR=3D"#008000">
</FONT>&nbsp;</P></BODY></HTML>

------_=_NextPart_001_01C7FBAB.17A31141--


--===============0788905595==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0788905595==--




From ldapext-bounces@ietf.org Thu Sep 20 14:34:01 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYQnc-0002GL-3b; Thu, 20 Sep 2007 14:30:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYQna-00029g-Dr
	for ldapext@ietf.org; Thu, 20 Sep 2007 14:30:50 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYQnU-0008AQ-Py
	for ldapext@ietf.org; Thu, 20 Sep 2007 14:30:45 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8KIUhPC005213
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 20 Sep 2007 14:30:43 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8KIUga3001942;
	Thu, 20 Sep 2007 14:30:42 -0400
Received: from [172.16.25.166] (dhcp-172-16-25-166.sfbay.redhat.com
	[172.16.25.166])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8KIUe98017373; Thu, 20 Sep 2007 14:30:41 -0400
Message-ID: <46F2BC4A.9060900@redhat.com>
Date: Thu, 20 Sep 2007 11:30:34 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] groupOfEntries object class proposal
References: <20070917143336.GA7266@tile.skills-1st.co.uk>
	<46F1B4E6.90808@redhat.com> <46F1BBE1.3060605@highlandsun.com>
In-Reply-To: <46F1BBE1.3060605@highlandsun.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: ldapext@ietf.org, Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1654289288=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1654289288==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms060106010706080807070400"

This is a cryptographically signed message in MIME format.

--------------ms060106010706080807070400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Howard Chu wrote:
> Pete Rowley wrote:
>> Andrew Findlay wrote:
>>> At the recent LDAP conference in Cologne there was wide support for an
>>> effort to improve some of the commonly-used schema definitions. In
>>> particular, the fact that groupOfNames does not permit an empty group
>>> was felt to be a significant problem.
>>>   
>> So the discussion about this highlights the basic issues around the 
>> current approach to grouping. Fundamentally there are two classes of 
>> user for a grouping mechanism 1) those who need to know how to build 
>> and generally administer groups 2) those who need to use groups but 
>> care not a whit how they came to be. Currently, every time a new 
>> group type is invented both classes need to understand all the ins 
>> and outs of the new group type and they must agree on what those ins 
>> and outs mean.
>>
>> This is broken. Non-administrative clients should be able to write to 
>> a single group interface once and forever after be left to get on 
>> with clientship.  Innovation for the first class of user is then left 
>> to prosper without hindrance, without client breakage, and without 
>> chickens and eggs. There is a suitable way to do this: the memberof 
>> attribute, if populated it will supply all the needs of the second 
>> class of user both now and into the future, it even solves some of 
>> sticky performance problems around gathering suitable attribute 
>> values from each memberof the group. It is also agnostic to method of 
>> attaining membership, membership simply is.
>
> Ah, if only it were so easy. But will memberOf expand for recursions? 
> If user A is a member of a group B that is nested in group C, will it 
> list only group B or both group B and group C? Attacking the problem 
> from the opposite direction doesn't actually eliminate the question of 
> whether and how nesting should be handled. All of the same ambiguities 
> still exist.
Nesting of membership is a design detail of a particular grouping 
mechanism, it has no bearing on memberof since if a group is not listed 
in memberof, it the entry is not a member. This actually a supporting 
point in that the set of non-management clients don't need to care.

-- 
Pete


--------------ms060106010706080807070400
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjAxODMwMzVaMCMGCSqGSIb3DQEJBDEWBBS62U2LiJRBGSYh
qrv8Pu/FXUEFbjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEAb785CHp/yBs6UOLEYaz3vGsJ0zXqhPxAt1qY8bcYjIBxLppfyMwfoL6BgkZ3
1dBGpGzsZMUI0yOMqyf1jVKodoWLkO4f1zdTh6MU+jmnR/O8M/xIS/ovYzK1hBE5Uv49vweh
NlSJFLWRxOavVHCUwbjGHmdxhvYkg09KjWYSbaC3Lsj7UKLNZKAREalFvTK7dt1jj6hDf0u0
D5NrXxWlddpPHaoIpwtfHMYDB6ziJODH8yL9V6CqA54lqEId37euOT5+6vytjAaK3gN4vPq+
XOAJ3ZbaHi5T016t+5+GmWaZeWi5ijQTXIrZ66k9cQPV7VOIFW+j0pwyziVD74aMuwAAAAAA
AA==
--------------ms060106010706080807070400--


--===============1654289288==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1654289288==--




From ldapext-bounces@ietf.org Thu Sep 20 19:13:23 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYV8R-0005yK-6f; Thu, 20 Sep 2007 19:08:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYV8Q-0005ep-1N
	for ldapext@ietf.org; Thu, 20 Sep 2007 19:08:38 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYV8F-0004mr-Cz
	for ldapext@ietf.org; Thu, 20 Sep 2007 19:08:34 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8KN84qk014753
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 20 Sep 2007 23:08:07 GMT
Message-ID: <46F2FE0A.1070702@padl.com>
Date: Fri, 21 Sep 2007 09:11:06 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
Subject: Re: [ldapext] Nested group
References: <DD9F4CC53AE89944A5C825781D5E30900199C2A6@MLNYC727MB.amrs.win.ml.com>
In-Reply-To: <DD9F4CC53AE89944A5C825781D5E30900199C2A6@MLNYC727MB.amrs.win.ml.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: idra@samba.org, ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Liben, Michael (GTI) wrote:
>
> This makes it simple toi answer the question, "of what groups is the 
> object a member?"
>
Not entirely, because it does not answer this question with respect to 
transitive memberships.

-- Luke

-- 
www.padl.com | www.lukehoward.com


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 20 21:12:20 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYX0s-0002zB-De; Thu, 20 Sep 2007 21:08:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYX0q-0002nD-PD
	for ldapext@ietf.org; Thu, 20 Sep 2007 21:08:56 -0400
Received: from mlnya403er.ml.com ([199.43.38.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYX0f-0007B3-KZ
	for ldapext@ietf.org; Thu, 20 Sep 2007 21:08:51 -0400
Received: from MLNYC851BH.amrs.win.ml.com (unknown [141.128.12.201])
	by mlnya403er.ml.com (Postfix) with ESMTP id BF56C56174;
	Thu, 20 Sep 2007 21:08:25 -0400 (EDT)
Importance: normal
Priority: normal
Received: from mlnya303bh.amrs.win.ml.com ([170.240.239.48]) by
	MLNYC851BH.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Thu, 20 Sep 2007 21:08:25 -0400
Received: from MLNYC727MB.amrs.win.ml.com ([141.128.12.71]) by
	mlnya303bh.amrs.win.ml.com with Microsoft
	SMTPSVC(5.0.2195.6920); Thu, 20 Sep 2007 21:08:25 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ldapext] Nested group
Date: Thu, 20 Sep 2007 21:08:24 -0400
Message-ID: <DD9F4CC53AE89944A5C825781D5E30900199C2B4@MLNYC727MB.amrs.win.ml.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ldapext] Nested group
thread-index: Acf720cFJ9C3k768TKaALa6k3bVeRwAEHLYw
References: <DD9F4CC53AE89944A5C825781D5E30900199C2A6@MLNYC727MB.amrs.win.ml.com>
	<46F2FE0A.1070702@padl.com>
From: "Liben, Michael \(GTI\)" <michael_liben@ml.com>
To: "Luke Howard" <lukeh@padl.com>
X-OriginalArrivalTime: 21 Sep 2007 01:08:25.0199 (UTC)
	FILETIME=[E937E7F0:01C7FBEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: idra@samba.org, ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Recurse upward until parent group does not have memberOf attribute.=20

-----Original Message-----
From: Luke Howard [mailto:lukeh@padl.com]=20
Sent: Thursday, September 20, 2007 7:11 PM
To: Liben, Michael (GTI)
Cc: ldapext@ietf.org; idra@samba.org
Subject: Re: [ldapext] Nested group

Liben, Michael (GTI) wrote:
>
> This makes it simple toi answer the question, "of what groups is the=20
> object a member?"
>
Not entirely, because it does not answer this question with respect to=20
transitive memberships.

-- Luke

--=20
www.padl.com | www.lukehoward.com
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or =
proprietary, and if you are not an intended recipient, please notify the =
sender, do not use or share it and delete it. Unless specifically =
indicated, this message is not an offer to sell or a solicitation of any =
investment products or other financial product or service, an official =
confirmation of any transaction, or an official statement of Merrill =
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and =
retain e-communications (EC) traveling through its networks/systems. The =
laws of the country of each sender/recipient may impact the handling of =
EC, and EC may be archived, supervised and produced in countries other =
than the country in which you are located. This message cannot be =
guaranteed to be secure or error-free. This message is subject to terms =
available at the following link: =
http://www.ml.com/e-communications_terms/. By messaging with Merrill =
Lynch you consent to the foregoing.
--------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 24 15:50:13 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IZtqz-0004Dg-Vz; Mon, 24 Sep 2007 15:44:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IZtqx-0003zN-AS
	for ldapext@ietf.org; Mon, 24 Sep 2007 15:44:23 -0400
Received: from [84.45.68.116] (helo=dog.ourshack.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZtql-0003Cg-Q1
	for ldapext@ietf.org; Mon, 24 Sep 2007 15:44:19 -0400
Received: from 88-97-25-132.dsl.zen.co.uk ([88.97.25.132]
	helo=tile.skills-1st.co.uk)
	by dog.ourshack.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.68 (FreeBSD))
	(envelope-from <andrew.findlay@skills-1st.co.uk>) id 1IZtqL-00084z-Nk
	for ldapext@ietf.org; Mon, 24 Sep 2007 20:43:45 +0100
Received: from andrew by tile.skills-1st.co.uk with local (Exim 4.63)
	(envelope-from <andrew.findlay@skills-1st.co.uk>) id 1IZtqI-0002aC-3T
	for ldapext@ietf.org; Mon, 24 Sep 2007 20:43:42 +0100
Date: Mon, 24 Sep 2007 20:43:42 +0100
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
To: LDAP Extensions list <ldapext@ietf.org>
Message-ID: <20070924194342.GA9926@tile.skills-1st.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.13 (2006-08-11)
X-SA-Exim-Connect-IP: 88.97.25.132
X-SA-Exim-Mail-From: andrew.findlay@skills-1st.co.uk
X-SA-Exim-Scanned: No (on dog.ourshack.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Subject: [ldapext] Summary of group discussion
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

draft-findlay-ldap-groupofentries-00.txt discussion summary 2007-09-24
======================================================================

On September 17th I introduced an I-D to create an LDAP group class
that was capable of representing an empty group. The initial proposal
was for the smallest possible change from the existing groupOfNames
class.

Most people who joined the discussion on ldapext@ietf.org were broadly
in support of allowing empty groups, though some thought that any
changes away from the status quo were doomed to fail.

Howard Chu pointed out that groupOfUniqueNames is even worse than
groupOfNames as the LDAP syntax for the nameAndOptionalUID attribute
type cannot be parsed reliably.

Kurt Zeilenga provided much detailed editorial advice, and posed a
question about how to handle groups where the DSA is unwilling or
unable to return some or all member names.

Luke Howard suggested that the behaviour of nested groups should be
defined. I was initially against an explicit definition, but was soon
persuaded that there could be significant performance and security
problems with ad-hoc nesting. At this point the discussion moved
almost entirely to the consideration of nesting issues.

Pete Rowley wanted an interface to be used by read-only clients to find
out what groups a particular entry is a member of without caring about
how the groups are defined. He suggested a memberOf attribute (presumably
server-maintained) for this purpose. Michael Liben also liked this
approach.

Simo Sorce proposed a control for server-side group expansion, and
Michael Ströder suggested that an extended operation for asking specific
membership questions would be better. Howard Chu suggested that any such
operation would need a depth limit parameter.

Steven Legg proposed directMember and nestedGroups attributes, and
Michael Ströder suggested that these might be a sufficient set to
describe nested groups. I wondered whether nested groups should be split
into those that could in turn have their own nested groups and those
that could not, but Simo Sorce thought that people would never choose
to use the more restrictive case. I was initially against dropping the
original 'member' attribute, but Steven pointed out that having a new
directMember attribute would allow people to define their own group
classes and still take advantage of defined nesting semantics.


Current situation
=================

It seems to me that we now have these threads of development:

1)	A new structural group class that can represent empty groups.
	This could go forward with the existing ambiguous member
	attribute or it could become the basis of a group
	representation with more carefully defined semantics using
	directMember.

2)	A new auxiliary class and one or more attributes to represent
	groups that may contain other groups. For this to make much
	sense it would require the well-defined version of (1).
	
	In (1) and (2) I see the definitions of the attributes being
	the key, and would avoid requiring the use of the object
	classes to obtain the defined semantics.

3)	A new control or extended operation so that a client can ask
	the server to do the heavy lifting involved with nested
	groups.

4)	A new server-maintained attribute called memberOf to give an
	alternative way for clients to ask for membership information.
	AD already has such an attribute, and Pierangelo Masarati
	recently proposed one for OpenLDAP so there may be useful
	existing work to build on.

5)	A document explaining why groupOfUniqueNames,
	uniqueMember and nameAndOptionalUID are bad, possibly leading
	to them being deprecated in the next revision of the core LDAP
	standards.


I am willing to co-ordinate work on (1) and (2). Are there volunteers
to take on the others?

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 24 20:18:16 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IZy4H-0003j1-6z; Mon, 24 Sep 2007 20:14:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IZy4G-0003iw-45
	for ldapext@ietf.org; Mon, 24 Sep 2007 20:14:24 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IZy4F-0004X9-Kx
	for ldapext@ietf.org; Mon, 24 Sep 2007 20:14:23 -0400
Received: from [202.182.84.118] (helo=[192.168.1.180])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1IZy4E-00028k-MI; Tue, 25 Sep 2007 10:14:23 +1000
Message-ID: <46F852DA.7020705@eb2bcom.com>
Date: Tue, 25 Sep 2007 10:14:18 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
Subject: Re: [ldapext] Nested group
References: <46F0ED1E.10004@stroeder.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<46F063BE.5020900@padl.com>	<20070917143336.GA7266@tile.skills-1st.co.uk>	<46EF07BD.1010801@padl.com>	<20070918110511.GF23300@tile.skills-1st.co.uk>	<46F060CD.20008@eb2bcom.com>	<20070919104644.GE12296@tile.skills-1st.co.uk>	<46F1E3C4.1090901@eb2bcom.com>
	<46F23533.6080604@stroeder.com>
In-Reply-To: <46F23533.6080604@stroeder.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Michael,

Michael Ströder wrote:
> Steven Legg wrote:
>> If we are going to allow a variety of object classes to define groups,
>> then we should define a new attribute, e.g., called directMember, to
>> replace the member attribute.
> 
> Steven, so the whole thing would boil down to define two new attributes
> 'directMember' and 'nestedGroup' with a clear specification how to
> interprete them?

Yes. Any object class that permits the directMember and/or nestedGroup
attributes defines a group. These attributes would always have the same
effects regardless of the object class. One or more classes that include
either or both of the attributes could be defined as a convenience for
users that don't want to create their own classes.

Regards,
Steven

> 
> Ciao, Michael.
> 
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 24 22:09:07 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IZzmi-0002GY-3V; Mon, 24 Sep 2007 22:04:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IZzmg-0002C3-FT
	for ldapext@ietf.org; Mon, 24 Sep 2007 22:04:22 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZzma-0005dV-7t
	for ldapext@ietf.org; Mon, 24 Sep 2007 22:04:22 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8P23qXP005714; Mon, 24 Sep 2007 21:03:53 -0500
Message-ID: <46F86C11.8080203@highlandsun.com>
Date: Mon, 24 Sep 2007 19:01:53 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
In-Reply-To: <20070924194342.GA9926@tile.skills-1st.co.uk>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew Findlay wrote:

> It seems to me that we now have these threads of development:
> 
> 1)	A new structural group class that can represent empty groups.
> 	This could go forward with the existing ambiguous member
> 	attribute or it could become the basis of a group
> 	representation with more carefully defined semantics using
> 	directMember.
> 
> 2)	A new auxiliary class and one or more attributes to represent
> 	groups that may contain other groups. For this to make much
> 	sense it would require the well-defined version of (1).
> 	
> 	In (1) and (2) I see the definitions of the attributes being
> 	the key, and would avoid requiring the use of the object
> 	classes to obtain the defined semantics.

I think you should avoid dwelling on this last point. It just confuses the 
issue. It seems certain that we're defining new attributes, and therefore at 
least a new objectclass is needed to make use of them. Also the notion of 
placing all the semantics solely in the attribute begs the question "is a 
group with no members no longer a group?" (Yes, it's a silly question, but it 
can be easily avoided by not focusing too much on the attribute.)

> 3)	A new control or extended operation so that a client can ask
> 	the server to do the heavy lifting involved with nested
> 	groups.
> 
> 4)	A new server-maintained attribute called memberOf to give an
> 	alternative way for clients to ask for membership information.
> 	AD already has such an attribute, and Pierangelo Masarati
> 	recently proposed one for OpenLDAP so there may be useful
> 	existing work to build on.

Pierangelo's code is already released in OpenLDAP 2.4.5.

> 5)	A document explaining why groupOfUniqueNames,
> 	uniqueMember and nameAndOptionalUID are bad, possibly leading
> 	to them being deprecated in the next revision of the core LDAP
> 	standards.

I'll write this up.

-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 24 22:16:52 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IZzwu-0006zM-Re; Mon, 24 Sep 2007 22:14:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IZzwt-0006zG-Pu
	for ldapext@ietf.org; Mon, 24 Sep 2007 22:14:55 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZzwr-0005qe-5T
	for ldapext@ietf.org; Mon, 24 Sep 2007 22:14:55 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8P2EiNx005893
	for <ldapext@ietf.org>; Mon, 24 Sep 2007 21:14:45 -0500
Message-ID: <46F86E9D.3050908@highlandsun.com>
Date: Mon, 24 Sep 2007 19:12:45 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Ldapext <ldapext@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [ldapext] X.509, RFC4523, RFC3641, big Ints
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Something that we've recently encountered while testing our Certificate 
validation rules is certificates whose serial numbers are integers whose 
values are larger than 4 octets. I'm wondering how other folks deal with these 
things. Integers that occur within the LDAP protocol are generally constrained 
to maxInt, 2^31 - 1, but no such constraint applies anywhere else. Do you use 
a multi-precision math library to generate the decimal representation of these 
integers?

For now we've copied the OpenSSL library's behavior, which is to use decimal 
for up to 31 bit numbers, and just output the hexadecimal octets for anything 
larger. But this clearly doesn't conform to the GSER definition of INTEGER.

As an aside, I really wish we were using hex for the canonical Integer 
representation; then any system could manipulate integers of any size 
independently of any native word size...
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Sep 24 23:26:45 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ia0zL-0005ZL-BZ; Mon, 24 Sep 2007 23:21:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ia0zK-0005U8-Ix
	for ldapext@ietf.org; Mon, 24 Sep 2007 23:21:30 -0400
Received: from host.eb2bcom.com ([72.232.34.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ia0zG-0006xV-AV
	for ldapext@ietf.org; Mon, 24 Sep 2007 23:21:27 -0400
Received: from [202.182.84.118] (helo=[192.168.1.180])
	by host.eb2bcom.com with esmtpa (Exim 4.68)
	(envelope-from <steven.legg@eb2bcom.com>)
	id 1Ia0yz-000085-5J; Tue, 25 Sep 2007 13:21:09 +1000
Message-ID: <46F87EA0.2050609@eb2bcom.com>
Date: Tue, 25 Sep 2007 13:21:04 +1000
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] X.509, RFC4523, RFC3641, big Ints
References: <46F86E9D.3050908@highlandsun.com>
In-Reply-To: <46F86E9D.3050908@highlandsun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.eb2bcom.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Ldapext <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Howard,

Howard Chu wrote:
> Something that we've recently encountered while testing our Certificate 
> validation rules is certificates whose serial numbers are integers whose 
> values are larger than 4 octets. I'm wondering how other folks deal with 
> these things. Integers that occur within the LDAP protocol are generally 
> constrained to maxInt, 2^31 - 1, but no such constraint applies anywhere 
> else. Do you use a multi-precision math library to generate the decimal 
> representation of these integers?

I represent large integers in two's complement as a variable length array
of octets. I wrote my own routines to do the multiply by 10 and divide by 10
that is required to convert to and from decimal. I treat the octet array
as a number in base 256 (so each octet is a "digit") and coded the routines
to perform the operations in the way I would if I were doing it by hand
(with carries and remainders and such). The operations turn out to be
fairly simple because one of the operands is only ever one "digit".

> 
> For now we've copied the OpenSSL library's behavior, which is to use 
> decimal for up to 31 bit numbers, and just output the hexadecimal octets 
> for anything larger. But this clearly doesn't conform to the GSER 
> definition of INTEGER.
> 
> As an aside, I really wish we were using hex for the canonical Integer 
> representation; then any system could manipulate integers of any size 
> independently of any native word size...

It would always be possible to define hexadecimal as an alternative
representation for integers in GSER, perhaps distinguished from decimal
by a leading 0x .

Regards,
Steven

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 25 04:25:50 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ia5fB-0001on-Ed; Tue, 25 Sep 2007 04:21:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ia5f9-0001k4-LU
	for ldapext@ietf.org; Tue, 25 Sep 2007 04:20:59 -0400
Received: from au.padl.com ([203.13.32.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ia5f8-0007jR-PG
	for ldapext@ietf.org; Tue, 25 Sep 2007 04:20:59 -0400
Received: from [203.13.32.93] (tankstream.off.padl.com [203.13.32.93] (may be
	forged)) (authenticated bits=0)
	by au.padl.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id
	l8P8KjHG025582
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 25 Sep 2007 08:20:47 GMT
Message-ID: <46F8C58F.6090109@padl.com>
Date: Tue, 25 Sep 2007 18:23:43 +1000
From: Luke Howard <lukeh@padl.com>
Organization: PADL Software Pty Ltd
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] X.509, RFC4523, RFC3641, big Ints
References: <46F86E9D.3050908@highlandsun.com>
In-Reply-To: <46F86E9D.3050908@highlandsun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Ldapext <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

There's the LargeInteger syntax which AD, eDirectory 8.8 SP2 and I think 
OpenLDAP support.

-- Luke

Howard Chu wrote:
> Something that we've recently encountered while testing our 
> Certificate validation rules is certificates whose serial numbers are 
> integers whose values are larger than 4 octets. I'm wondering how 
> other folks deal with these things. Integers that occur within the 
> LDAP protocol are generally constrained to maxInt, 2^31 - 1, but no 
> such constraint applies anywhere else. Do you use a multi-precision 
> math library to generate the decimal representation of these integers?
>
> For now we've copied the OpenSSL library's behavior, which is to use 
> decimal for up to 31 bit numbers, and just output the hexadecimal 
> octets for anything larger. But this clearly doesn't conform to the 
> GSER definition of INTEGER.
>
> As an aside, I really wish we were using hex for the canonical Integer 
> representation; then any system could manipulate integers of any size 
> independently of any native word size...


-- 
www.padl.com | www.lukehoward.com


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 25 08:44:35 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ia9hp-0003iH-Ty; Tue, 25 Sep 2007 08:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ia9ho-0003i2-9Q
	for ldapext@ietf.org; Tue, 25 Sep 2007 08:40:00 -0400
Received: from gmp-eb-mail-1.sun.com ([192.18.6.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ia9he-0004Dc-Tp
	for ldapext@ietf.org; Tue, 25 Sep 2007 08:40:00 -0400
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10])
	by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l8PCdZO5023351 for <ldapext@ietf.org>; Tue, 25 Sep 2007 12:39:35 GMT
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0JOX00B01CAY6700@fe-emea-10.sun.com>
	(original mail from Ludovic.Poitou@Sun.COM) for ldapext@ietf.org; Tue,
	25 Sep 2007 13:39:34 +0100 (BST)
Received: from [129.157.211.104] by fe-emea-10.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0JOX00JG7CH81TC0@fe-emea-10.sun.com>; Tue,
	25 Sep 2007 13:39:09 +0100 (BST)
Date: Tue, 25 Sep 2007 14:39:05 +0200
From: Ludovic Poitou <Ludovic.Poitou@Sun.COM>
Subject: Re: [ldapext] Summary of group discussion
In-reply-to: <46F86C11.8080203@highlandsun.com>
To: Howard Chu <hyc@highlandsun.com>
Message-id: <598D2001-BB82-434D-9571-0B2F140303EE@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.752.3)
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46F86C11.8080203@highlandsun.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: da41e01217ab11ad82db577473e913ae
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1716818158=="
Errors-To: ldapext-bounces@ietf.org


--===============1716818158==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_lWgM73O3CeWasHKTNV8qdA)"


--Boundary_(ID_lWgM73O3CeWasHKTNV8qdA)
Content-type: text/plain; format=flowed; delsp=yes; charset=US-ASCII
Content-transfer-encoding: 7BIT


On Sep 25, 2007, at 4:01 AM, Howard Chu wrote:

> Andrew Findlay wrote:
>
>> It seems to me that we now have these threads of development:
>> 1)	A new structural group class that can represent empty groups.
>> 	This could go forward with the existing ambiguous member
>> 	attribute or it could become the basis of a group
>> 	representation with more carefully defined semantics using
>> 	directMember.
>> 2)	A new auxiliary class and one or more attributes to represent
>> 	groups that may contain other groups. For this to make much
>> 	sense it would require the well-defined version of (1).
>> 	
>> 	In (1) and (2) I see the definitions of the attributes being
>> 	the key, and would avoid requiring the use of the object
>> 	classes to obtain the defined semantics.
>
> I think you should avoid dwelling on this last point. It just  
> confuses the issue. It seems certain that we're defining new  
> attributes, and therefore at least a new objectclass is needed to  
> make use of them. Also the notion of placing all the semantics  
> solely in the attribute begs the question "is a group with no  
> members no longer a group?" (Yes, it's a silly question, but it can  
> be easily avoided by not focusing too much on the attribute.)
>
>> 3)	A new control or extended operation so that a client can ask
>> 	the server to do the heavy lifting involved with nested
>> 	groups.
>> 4)	A new server-maintained attribute called memberOf to give an
>> 	alternative way for clients to ask for membership information.
>> 	AD already has such an attribute, and Pierangelo Masarati
>> 	recently proposed one for OpenLDAP so there may be useful
>> 	existing work to build on.
>
> Pierangelo's code is already released in OpenLDAP 2.4.5.

Similar functionality is already present in Sun Directory Server 6,  
although the operational attribute is called isMemberOf (because the  
Sun messaging product using the memberOf attribute with a different  
semantic :-( ).

Samba AD schema
( 1.2.840.113556.1.2.102
         NAME 'memberOf'
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
         NO-USER-MODIFICATION )

Sun Delegated Admin
( 1.2.840.113556.1.2.102 NAME 'memberOf' DESC 'Group that the entry  
belongs to' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )

Note that the memberOf attribute is not defined as Operational and is  
specifically listed as allowed in a number of objectclasses.

Sun isMemberOf
  ( 1.3.6.1.4.1.42.2.27.9.1.792 NAME 'isMemberOf' SYNTAX  
1.3.6.1.4.1.1466.115.121.1.12 NO-USER-MODIFICATION USAGE  
directoryOperation )

IBM defined its own attribute for the same purpose, and has the same  
semantic as Sun's isMemberOf (at least for Static Groups):
attributetypes=( 1.3.18.0.2.4.2244
NAME 'ibm-allGroups'
DESC 'All groups to which an entry belongs. An entry may be a member
directly via member, uniqueMember or memberURL attributes, or
indirectly via ibm-memberGroup attributes. Read-only operational
attribute (not allowed in filter).'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
NO-USER-MODIFICATION
USAGE directoryOperation )
IBMAttributetypes=( 1.3.18.0.2.4.2244
DBNAME( 'allGroups'  'allGroups' )
ACCESS-CLASS normal
LENGTH 1000 )

So, yes, it would be really nice to see some harmonization in that  
space.

Ludovic.

>
>> 5)	A document explaining why groupOfUniqueNames,
>> 	uniqueMember and nameAndOptionalUID are bad, possibly leading
>> 	to them being deprecated in the next revision of the core LDAP
>> 	standards.
>
> I'll write this up.
>
> -- 
>   -- Howard Chu
>   Chief Architect, Symas Corp.  http://www.symas.com
>   Director, Highland Sun        http://highlandsun.com/hyc/
>   Chief Architect, OpenLDAP     http://www.openldap.org/project/
>
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext

Ludovic Poitou                                    Sun Microsystems Inc.
Software Architect                                   Directory Services
http://blogs.sun.com/Ludo/         Grenoble Engineering Center - France

Sun Microsystems requires the following notice:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




--Boundary_(ID_lWgM73O3CeWasHKTNV8qdA)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; ">
<br><div><div>On Sep 25, 2007, at 4:01 AM, Howard Chu wrote:</div><br=
 class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div s=
tyle=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; ">Andrew Findlay wrote:</div><div style=3D"margin-top: 0=
px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-heig=
ht: 14px; "><br></div> <blockquote type=3D"cite"><div style=3D"margin=
-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "=
>It seems to me that we now have these threads of development:</div><=
div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">1)<span class=3D"Apple-tab-span" style=3D"white-s=
pace:pre">=09</span>A new structural group class that can represent e=
mpty groups.</div><div style=3D"margin-top: 0px; margin-right: 0px; m=
argin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span"=
 style=3D"white-space:pre">=09</span>This could go forward with the e=
xisting ambiguous member</div><div style=3D"margin-top: 0px; margin-r=
ight: 0px; margin-bottom: 0px; margin-left: 0px; "><span class=3D"App=
le-tab-span" style=3D"white-space:pre">=09</span>attribute or it coul=
d become the basis of a group</div><div style=3D"margin-top: 0px; mar=
gin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class=
=3D"Apple-tab-span" style=3D"white-space:pre">=09</span>representatio=
n with more carefully defined semantics using</div><div style=3D"marg=
in-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;=
 "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=09</span=
>directMember.</div><div style=3D"margin-top: 0px; margin-right: 0px;=
 margin-bottom: 0px; margin-left: 0px; ">2)<span class=3D"Apple-tab-s=
pan" style=3D"white-space:pre">=09</span>A new auxiliary class and on=
e or more attributes to represent</div><div style=3D"margin-top: 0px;=
 margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span cla=
ss=3D"Apple-tab-span" style=3D"white-space:pre">=09</span>groups that=
 may contain other groups. For this to make much</div><div style=3D"m=
argin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0=
px; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=09</s=
pan>sense it would require the well-defined version of (1).</div><p s=
tyle=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><span cl=
ass=3D"Apple-tab-span" style=3D"white-space:pre">=09</span><br class=
=3D"khtml-block-placeholder"></p><div style=3D"margin-top: 0px; margi=
n-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class=
=3D"Apple-tab-span" style=3D"white-space:pre">=09</span>In (1) and (2=
) I see the definitions of the attributes being</div><div style=3D"ma=
rgin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0p=
x; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=09</sp=
an>the key, and would avoid requiring the use of the object</div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; mar=
gin-left: 0px; "><span class=3D"Apple-tab-span" style=3D"white-space:=
pre">=09</span>classes to obtain the defined semantics.</div> </block=
quote><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom=
: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-le=
ft: 0px; ">I think you should avoid dwelling on this last point. It j=
ust confuses the issue. It seems certain that we're defining new attr=
ibutes, and therefore at least a new objectclass is needed to make us=
e of them. Also the notion of placing all the semantics solely in the=
 attribute begs the question "is a group with no members no longer a =
group?" (Yes, it's a silly question, but it can be easily avoided by =
not focusing too much on the attribute.)</div><div style=3D"margin-to=
p: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-=
height: 14px; "><br></div> <blockquote type=3D"cite"><div style=3D"ma=
rgin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0p=
x; ">3)<span class=3D"Apple-tab-span" style=3D"white-space:pre">=09</=
span>A new control or extended operation so that a client can ask</di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0p=
x; margin-left: 0px; "><span class=3D"Apple-tab-span" style=3D"white-=
space:pre">=09</span>the server to do the heavy lifting involved with=
 nested</div><div style=3D"margin-top: 0px; margin-right: 0px; margin=
-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" styl=
e=3D"white-space:pre">=09</span>groups.</div><div style=3D"margin-top=
: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">4)<=
span class=3D"Apple-tab-span" style=3D"white-space:pre">=09</span>A n=
ew server-maintained attribute called memberOf to give an</div><div s=
tyle=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; "><span class=3D"Apple-tab-span" style=3D"white-space:pr=
e">=09</span>alternative way for clients to ask for membership inform=
ation.</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-=
bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" style=
=3D"white-space:pre">=09</span>AD already has such an attribute, and =
Pierangelo Masarati</div><div style=3D"margin-top: 0px; margin-right:=
 0px; margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-ta=
b-span" style=3D"white-space:pre">=09</span>recently proposed one for=
 OpenLDAP so there may be useful</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span clas=
s=3D"Apple-tab-span" style=3D"white-space:pre">=09</span>existing wor=
k to build on.</div> </blockquote><div style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px=
; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0px; ">Pierangelo's code is already relea=
sed in OpenLDAP 2.4.5.</div></blockquote><div><br class=3D"webkit-blo=
ck-placeholder"></div><div>Similar functionality is already present i=
n Sun Directory Server 6, although the operational attribute is calle=
d isMemberOf (because the Sun messaging product using the memberOf at=
tribute with a different semantic :-( ).</div><div><br class=3D"webki=
t-block-placeholder"></div><div>Samba AD schema</div><div><p style=
=3D"margin: 0.0px 0.0px 16.0px 0.0px"><font face=3D"Courier" size=
=3D"4" style=3D"font: 13.0px Courier">( 1.2.840.113556.1.2.102</font>=
<font face=3D"Times" size=3D"5" style=3D"font: 16.0px Times"> <br> </=
font><font face=3D"Courier" size=3D"4" style=3D"font: 13.0px Courier"=
>=A0=A0=A0=A0=A0=A0=A0 NAME 'memberOf'</font><font face=3D"Times" siz=
e=3D"5" style=3D"font: 16.0px Times"> <br> </font><font face=3D"Couri=
er" size=3D"4" style=3D"font: 13.0px Courier">=A0=A0=A0=A0=A0=A0=A0 S=
YNTAX 1.3.6.1.4.1.1466.115.121.1.12</font><font face=3D"Times" size=
=3D"5" style=3D"font: 16.0px Times"> <br> </font><font face=3D"Courie=
r" size=3D"4" style=3D"font: 13.0px Courier">=A0=A0=A0=A0=A0=A0=A0 NO=
-USER-MODIFICATION )</font></p> </div><div>Sun Delegated Admin</div><=
div>( 1.2.840.113556.1.2.102 NAME 'memberOf' DESC 'Group that the ent=
ry belongs to' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )</div></div><div=
><br class=3D"webkit-block-placeholder"></div><div>Note that the memb=
erOf attribute is not defined as Operational and is specifically list=
ed as allowed in a number of objectclasses.</div><div><br class=3D"we=
bkit-block-placeholder"></div><div>Sun isMemberOf</div><div>=A0( 1.3.=
6.1.4.1.42.2.27.9.1.792 NAME 'isMemberOf' SYNTAX 1.3.6.1.4.1.1466.115=
.121.1.12 NO-USER-MODIFICATION USAGE directoryOperation )</div><div><=
br class=3D"webkit-block-placeholder"></div><div>IBM defined its own =
attribute for the same purpose, and has the same semantic as Sun's is=
MemberOf (at least for Static Groups):</div><div><div style=3D"margin=
-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; b=
ackground-color: rgb(218, 218, 218); "><font face=3D"Courier" size=
=3D"3" style=3D"font: 12.0px Courier; background-color: #bcd5fa">attr=
ibutetype</font><font face=3D"Courier" size=3D"3" style=3D"font: 12.0=
px Courier">s=3D( 1.3.18.0.2.4.2244=A0</font></div><div style=3D"marg=
in-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;=
 background-color: rgb(188, 213, 250); "><font face=3D"Courier" size=
=3D"3" style=3D"font: 12.0px Courier; background-color: #dadada">NAME=
 '</font><font face=3D"Courier" size=3D"3" style=3D"font: 12.0px Cour=
ier">ibm-allGroups</font><font face=3D"Courier" size=3D"3" style=3D"f=
ont: 12.0px Courier; background-color: #dadada">'=A0</font></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; mar=
gin-left: 0px; background-color: rgb(218, 218, 218); "><font face=
=3D"Courier" size=3D"3" style=3D"font: 12.0px Courier">DESC 'All grou=
ps to which an entry belongs. An entry may be a member=A0</font></div=
><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px=
; margin-left: 0px; background-color: rgb(218, 218, 218); "><font fac=
e=3D"Courier" size=3D"3" style=3D"font: 12.0px Courier">directly via =
member, uniqueMember or memberURL attributes, or=A0</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; marg=
in-left: 0px; background-color: rgb(218, 218, 218); "><font face=3D"C=
ourier" size=3D"3" style=3D"font: 12.0px Courier">indirectly via ibm-=
memberGroup attributes. Read-only operational=A0</font></div><div sty=
le=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-=
left: 0px; background-color: rgb(218, 218, 218); "><font face=3D"Cour=
ier" size=3D"3" style=3D"font: 12.0px Courier">attribute (not allowed=
 in filter).'=A0</font></div><div style=3D"margin-top: 0px; margin-ri=
ght: 0px; margin-bottom: 0px; margin-left: 0px; background-color: rgb=
(218, 218, 218); "><font face=3D"Courier" size=3D"3" style=3D"font: 1=
2.0px Courier">SYNTAX 1.3.6.1.4.1.1466.115.121.1.12=A0</font></div><d=
iv style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; m=
argin-left: 0px; background-color: rgb(218, 218, 218); "><font face=
=3D"Courier" size=3D"3" style=3D"font: 12.0px Courier">NO-USER-MODIFI=
CATION=A0</font></div><div style=3D"margin-top: 0px; margin-right: 0p=
x; margin-bottom: 0px; margin-left: 0px; background-color: rgb(218, 2=
18, 218); "><font face=3D"Courier" size=3D"3" style=3D"font: 12.0px C=
ourier">USAGE directoryOperation )</font></div><div style=3D"margin-t=
op: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; bac=
kground-color: rgb(218, 218, 218); "><font face=3D"Courier" size=3D"3=
" style=3D"font: 12.0px Courier">IBM</font><font face=3D"Courier" siz=
e=3D"3" style=3D"font: 12.0px Courier; background-color: #bcd5fa">Att=
ributetype</font><font face=3D"Courier" size=3D"3" style=3D"font: 12.=
0px Courier">s=3D( 1.3.18.0.2.4.2244=A0</font></div><div style=3D"mar=
gin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px=
; background-color: rgb(218, 218, 218); "><font face=3D"Courier" size=
=3D"3" style=3D"font: 12.0px Courier">DBNAME( 'allGroups'=A0 'allGrou=
ps' )=A0</font></div><div style=3D"margin-top: 0px; margin-right: 0px=
; margin-bottom: 0px; margin-left: 0px; background-color: rgb(218, 21=
8, 218); "><font face=3D"Courier" size=3D"3" style=3D"font: 12.0px Co=
urier">ACCESS-CLASS normal=A0</font></div><div style=3D"margin-top: 0=
px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; backgrou=
nd-color: rgb(218, 218, 218); "><font face=3D"Courier" size=3D"3" sty=
le=3D"font: 12.0px Courier">LENGTH 1000 )</font></div> <br class=3D"w=
ebkit-block-placeholder"></div><div>So, yes, it would be really nice =
to see some=A0harmonization=A0in that space.</div><div><br></div><div=
>Ludovic.</div><div><br><blockquote type=3D"cite"><div style=3D"margi=
n-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div> <blockquote type=3D"cite"><div style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-le=
ft: 0px; ">5)<span class=3D"Apple-tab-span" style=3D"white-space:pre"=
>=09</span>A document explaining why groupOfUniqueNames,</div><div st=
yle=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin=
-left: 0px; "><span class=3D"Apple-tab-span" style=3D"white-space:pre=
">=09</span>uniqueMember and nameAndOptionalUID are bad, possibly lea=
ding</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bo=
ttom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" style=
=3D"white-space:pre">=09</span>to them being deprecated in the next r=
evision of the core LDAP</div><div style=3D"margin-top: 0px; margin-r=
ight: 0px; margin-bottom: 0px; margin-left: 0px; "><span class=3D"App=
le-tab-span" style=3D"white-space:pre">=09</span>standards.</div> </b=
lockquote><div style=3D"margin-top: 0px; margin-right: 0px; margin-bo=
ttom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-le=
ft: 0px; ">I'll write this up.</div><div style=3D"margin-top: 0px; ma=
rgin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14=
px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; mar=
gin-bottom: 0px; margin-left: 0px; ">--<span class=3D"Apple-converted=
-space">=A0</span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-con=
verted-space">=A0 </span>-- Howard Chu</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><spa=
n class=3D"Apple-converted-space">=A0 </span>Chief Architect, Symas C=
orp.<span class=3D"Apple-converted-space">=A0 </span><a href=3D"http:=
//www.symas.com">http://www.symas.com</a></div><div style=3D"margin-t=
op: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><=
span class=3D"Apple-converted-space">=A0 </span>Director, Highland Su=
n<span class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </span><a href=
=3D"http://highlandsun.com/hyc/">http://highlandsun.com/hyc/</a></div=
><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px=
; margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 </spa=
n>Chief Architect, OpenLDAP <span class=3D"Apple-converted-space">=
=A0 =A0 </span><a href=3D"http://www.openldap.org/project/">http://ww=
w.openldap.org/project/</a></div><div style=3D"margin-top: 0px; margi=
n-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px;=
 "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; margin=
-bottom: 0px; margin-left: 0px; ">___________________________________=
____________</div><div style=3D"margin-top: 0px; margin-right: 0px; m=
argin-bottom: 0px; margin-left: 0px; ">Ldapext mailing list</div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; mar=
gin-left: 0px; "><a href=3D"mailto:Ldapext@ietf.org">Ldapext@ietf.org=
</a></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bo=
ttom: 0px; margin-left: 0px; "><a href=3D"https://www1.ietf.org/mailm=
an/listinfo/ldapext">https://www1.ietf.org/mailman/listinfo/ldapext</=
a></div> </blockquote></div><br><div> <span class=3D"Apple-style-span=
" style=3D"border-collapse: separate; border-spacing: 0px 0px; color:=
 rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: n=
ormal; font-variant: normal; font-weight: normal; letter-spacing: nor=
mal; line-height: normal; text-align: auto; -khtml-text-decorations-i=
n-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text=
-transform: none; orphans: 2; white-space: normal; widows: 2; word-sp=
acing: 0px; "><div style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0px; ">Ludovic Poitou=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<span class=
=3D"Apple-converted-space">=A0</span>Sun Microsystems Inc.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; marg=
in-left: 0px; ">Software Architect<span class=3D"Apple-converted-spac=
e">=A0</span>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0<span class=3D"Apple-converted-space">=A0</span>Direct=
ory Services</div><div style=3D"margin-top: 0px; margin-right: 0px; m=
argin-bottom: 0px; margin-left: 0px; "><a href=3D"http://blogs.sun.co=
m/Ludo/">http://blogs.sun.com/Ludo/</a><span class=3D"Apple-converted=
-space">=A0</span>=A0 =A0 =A0 =A0<span class=3D"Apple-converted-space=
">=A0</span>Grenoble Engineering Center - France</div><div style=3D"m=
argin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0=
px; min-height: 14px; "><br></div><div style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Sun Microsyste=
ms requires the following notice:</div><div style=3D"margin-top: 0px;=
 margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><=
div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">NOTICE:=A0<span class=3D"Apple-converted-space">=
=A0</span>This email message is for the sole use of the intended</div=
><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px=
; margin-left: 0px; ">recipient(s) and may contain confidential and p=
rivileged information.</div><div style=3D"margin-top: 0px; margin-rig=
ht: 0px; margin-bottom: 0px; margin-left: 0px; ">Any unauthorized rev=
iew, use, disclosure or distribution is prohibited.</div><div style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-le=
ft: 0px; ">If you are not the intended recipient, please contact the =
sender by</div><div style=3D"margin-top: 0px; margin-right: 0px; marg=
in-bottom: 0px; margin-left: 0px; ">reply email and destroy all copie=
s of the original message.</div><div style=3D"margin-top: 0px; margin=
-right: 0px; margin-bottom: 0px; margin-left: 0px; ">~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><div sty=
le=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-=
left: 0px; "><br class=3D"khtml-block-placeholder"></div><br class=
=3D"Apple-interchange-newline"></span> </div><br></body></html>

--Boundary_(ID_lWgM73O3CeWasHKTNV8qdA)--


--===============1716818158==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1716818158==--




From ldapext-bounces@ietf.org Tue Sep 25 11:48:13 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaCbA-0006mn-U4; Tue, 25 Sep 2007 11:45:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaCb9-0006dd-A6
	for ldapext@ietf.org; Tue, 25 Sep 2007 11:45:19 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaCay-0000Pb-42
	for ldapext@ietf.org; Tue, 25 Sep 2007 11:45:14 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8PFiaoL022181; Tue, 25 Sep 2007 10:44:36 -0500
Message-ID: <46F92C6E.9030203@highlandsun.com>
Date: Tue, 25 Sep 2007 08:42:38 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] X.509, RFC4523, RFC3641, big Ints
References: <46F86E9D.3050908@highlandsun.com> <46F87EA0.2050609@eb2bcom.com>
In-Reply-To: <46F87EA0.2050609@eb2bcom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Ldapext <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Steven Legg wrote:
>> As an aside, I really wish we were using hex for the canonical Integer 
>> representation; then any system could manipulate integers of any size 
>> independently of any native word size...
> 
> It would always be possible to define hexadecimal as an alternative
> representation for integers in GSER, perhaps distinguished from decimal
> by a leading 0x .

I think this is an absolute necessity. In particular, the ASN.1 Integer type 
does not exclude negative numbers, but it's impossible to determine where the 
sign bit resides since the word size isn't specified. So the only safe thing 
to do is to treat it all as unsigned hex.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Sep 25 11:59:52 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaCnH-0002oP-5W; Tue, 25 Sep 2007 11:57:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaCnF-0002o7-TT
	for ldapext@ietf.org; Tue, 25 Sep 2007 11:57:50 -0400
Received: from highlandsun.propagation.net ([66.221.212.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaCnF-0003qW-HW
	for ldapext@ietf.org; Tue, 25 Sep 2007 11:57:49 -0400
Received: from [127.0.0.1] (highlandsun.com [66.221.212.169])
	by highlandsun.propagation.net (8.13.3/8.13.3) with ESMTP id
	l8PFvW22022408; Tue, 25 Sep 2007 10:57:32 -0500
Message-ID: <46F92F77.6070700@highlandsun.com>
Date: Tue, 25 Sep 2007 08:55:35 -0700
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686;
	rv:1.9a8pre) Gecko/2007091708 SeaMonkey/2.0a1pre
MIME-Version: 1.0
To: Steven Legg <steven.legg@eb2bcom.com>
Subject: Re: [ldapext] X.509, RFC4523, RFC3641, big Ints
References: <46F86E9D.3050908@highlandsun.com> <46F87EA0.2050609@eb2bcom.com>
	<46F92C6E.9030203@highlandsun.com>
In-Reply-To: <46F92C6E.9030203@highlandsun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: Ldapext <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Howard Chu wrote:
> I think this is an absolute necessity. In particular, the ASN.1 Integer type 
> does not exclude negative numbers, but it's impossible to determine where the 
> sign bit resides since the word size isn't specified. So the only safe thing 
> to do is to treat it all as unsigned hex.

Bah. I just re-read X.690, never mind... The sign bit is always the top bit of 
the top octet; an unsigned int with all 1's in the top octet just has to 
encoded with a leading all-zero octet.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 26 10:04:13 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaXQj-0006kj-4z; Wed, 26 Sep 2007 09:59:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaXQh-0006hR-Cn
	for ldapext@ietf.org; Wed, 26 Sep 2007 09:59:55 -0400
Received: from public.id2-vpn.continvity.gns.novell.com ([195.33.99.129]
	helo=gwia-smtp.id2.novell.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaXQg-0007vY-Kp
	for ldapext@ietf.org; Wed, 26 Sep 2007 09:59:55 -0400
Received: from [192.168.1.139] (id2-L4-foundry2.gns.novell.com
	[::ffff:149.44.117.248])
	by gwia-smtp.id2.novell.com with ESMTP (TLS encrypted);
	Wed, 26 Sep 2007 14:59:22 +0100
Message-ID: <46FA65A4.6080700@novell.com>
Date: Wed, 26 Sep 2007 19:29:00 +0530
From: Jaimon Jose <jjaimon@novell.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
In-Reply-To: <20070924194342.GA9926@tile.skills-1st.co.uk>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jjaimon@novell.com
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Andrew,
I didn't have a chance to follow the complete discussion thread.  So,
I'm taking the liberty to comment on the items that you mentioned in
this summary.

Andrew Findlay wrote, On 09/25/2007 01:13 AM:
> Most people who joined the discussion on ldapext@ietf.org were broadly
> in support of allowing empty groups, though some thought that any
> changes away from the status quo were doomed to fail.

I'm in agreement as well.  We already support empty group though its
against the standard.

> Luke Howard suggested that the behaviour of nested groups should be
> defined. I was initially against an explicit definition, but was soon
> persuaded that there could be significant performance and security
> problems with ad-hoc nesting. At this point the discussion moved
> almost entirely to the consideration of nesting issues.

Good suggestion.  This is very much needed for interoperability as more
and more vendors supporting nested groups.

> Pete Rowley wanted an interface to be used by read-only clients to find
> out what groups a particular entry is a member of without caring about
> how the groups are defined. He suggested a memberOf attribute (presumably
> server-maintained) for this purpose. Michael Liben also liked this
> approach.

This can even be a virtual attribute for which the implementation can be
left to the vendor.  Should this include all sort of membership?  For
eg. static groups, member status through group nesting, dynamic groups...


> Simo Sorce proposed a control for server-side group expansion, and
> Michael Ströder suggested that an extended operation for asking specific
> membership questions would be better. Howard Chu suggested that any such
> operation would need a depth limit parameter.

Our experience shows that there needs to be a server side configuration
as well which can override the client request. If not, a malicious
client can create DoS attacks as the nesting operation is quite
expensive from a server side. A nested group objectclass definition
should also have a depth limit (Already suggested by Howard Chu).  There
should also be a parameter that defines if the server should chain a
request if there are groups from remote servers.

> Current situation
> =================
> 
> It seems to me that we now have these threads of development:
> 
> 1)	A new structural group class that can represent empty groups.
> 	This could go forward with the existing ambiguous member
> 	attribute or it could become the basis of a group
> 	representation with more carefully defined semantics using
> 	directMember.
> 
> 2)	A new auxiliary class and one or more attributes to represent
> 	groups that may contain other groups. For this to make much
> 	sense it would require the well-defined version of (1).
> 	
> 	In (1) and (2) I see the definitions of the attributes being
> 	the key, and would avoid requiring the use of the object
> 	classes to obtain the defined semantics.

Here is a suggestion:
groupMember
	This attribute value contains the DN of another group.
	( 2.16.840.1.113719.1.1.4.711 NAME 'groupMember'
	   SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )

nestedConfig
	This bitmap contains the configuration options for a nested group.
	( 2.16.840.1.113719.1.1.4.712 NAME 'nestedConfig'
	  SYNTAX 1.3.6.1.4.1.1466.115.121.1.6)

excludedMember
	This attribute value contains the DNs that need to be excluded from
being a member of a group through nested evaluation. Thus, an entry is a
member of a nestedGroup only if it is listed in the member attribute of
any of the group objects in the nested hierarchy and it is not listed in
the excludedMember attribute
	( 2.16.840.1.113719.1.1.4.711 NAME 'excludedMember'
	   SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )

nestedGroupAux
	This auxiliary class defines required attributes to represent groups
that may contain other groups.
	( 2.16.840.1.113719.1.1.6.1.91 NAME 'nestedGroupAux'
	  AUXILIARY
	  MAY ( groupMember $
		excludedMember $
		nestedConfig ) )



> 3)	A new control or extended operation so that a client can ask
> 	the server to do the heavy lifting involved with nested
> 	groups.
> 
> 4)	A new server-maintained attribute called memberOf to give an
> 	alternative way for clients to ask for membership information.
> 	AD already has such an attribute, and Pierangelo Masarati
> 	recently proposed one for OpenLDAP so there may be useful
> 	existing work to build on.
> 
> 5)	A document explaining why groupOfUniqueNames,
> 	uniqueMember and nameAndOptionalUID are bad, possibly leading
> 	to them being deprecated in the next revision of the core LDAP
> 	standards.
> 
> 
> I am willing to co-ordinate work on (1) and (2). Are there volunteers
> to take on the others?

I can co-ordinate (3) and (4).

--jaimon

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Sep 26 17:16:48 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaeCn-0007PN-8c; Wed, 26 Sep 2007 17:14:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaeCm-0007KW-3H
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:14:00 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaeCd-0000wZ-Ug
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:13:58 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLDVRG011217
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Sep 2007 17:13:31 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLDUlo018043;
	Wed, 26 Sep 2007 17:13:31 -0400
Received: from [10.13.248.84] (vpn-248-84.boston.redhat.com [10.13.248.84])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8QLDQw0007358; Wed, 26 Sep 2007 17:13:27 -0400
Message-ID: <46FACB77.1070307@redhat.com>
Date: Wed, 26 Sep 2007 14:13:27 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: jjaimon@novell.com
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com>
In-Reply-To: <46FA65A4.6080700@novell.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1654172129=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1654172129==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms060708060407070406030901"

This is a cryptographically signed message in MIME format.

--------------ms060708060407070406030901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jaimon Jose wrote:
> Andrew,
> I didn't have a chance to follow the complete discussion thread.  So,
> I'm taking the liberty to comment on the items that you mentioned in
> this summary.
>
> Andrew Findlay wrote, On 09/25/2007 01:13 AM:
>   
>> Most people who joined the discussion on ldapext@ietf.org were broadly
>> in support of allowing empty groups, though some thought that any
>> changes away from the status quo were doomed to fail.
>>     
>
> I'm in agreement as well.  We already support empty group though its
> against the standard.
>
>   
>> Luke Howard suggested that the behaviour of nested groups should be
>> defined. I was initially against an explicit definition, but was soon
>> persuaded that there could be significant performance and security
>> problems with ad-hoc nesting. At this point the discussion moved
>> almost entirely to the consideration of nesting issues.
>>     
>
> Good suggestion.  This is very much needed for interoperability as more
> and more vendors supporting nested groups.
>
>   
>> Pete Rowley wanted an interface to be used by read-only clients to find
>> out what groups a particular entry is a member of without caring about
>> how the groups are defined. He suggested a memberOf attribute (presumably
>> sFrom ldapext-bounces@ietf.org Wed Sep 26 17:16:48 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaeCn-0007PN-8c; Wed, 26 Sep 2007 17:14:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaeCm-0007KW-3H
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:14:00 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaeCd-0000wZ-Ug
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:13:58 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLDVRG011217
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Sep 2007 17:13:31 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLDUlo018043;
	Wed, 26 Sep 2007 17:13:31 -0400
Received: from [10.13.248.84] (vpn-248-84.boston.redhat.com [10.13.248.84])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8QLDQw0007358; Wed, 26 Sep 2007 17:13:27 -0400
Message-ID: <46FACB77.1070307@redhat.com>
Date: Wed, 26 Sep 2007 14:13:27 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: jjaimon@novell.com
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com>
In-Reply-To: <46FA65A4.6080700@novell.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1654172129=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1654172129==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms060708060407070406030901"

This is a cryptographically signed message in MIME format.

--------------ms060708060407070406030901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jaimon Jose wrote:
> Andrew,
> I didn't have a chance to follow the complete discussion thread.  So,
> I'm taking the liberty to comment on the items that you mentioned in
> this summary.
>
> Andrew Findlay wrote, On 09/25/2007 01:13 AM:
>   
>> Most people who joined the discussion on ldapext@ietf.org were broadly
>> in support of allowing empty groups, though some thought that any
>> changes away from the status quo were doomed to fail.
>>     
>
> I'm in agreement as well.  We already support empty group though its
> against the standard.
>
>   
>> Luke Howard suggested that the behaviour of nested groups should be
>> defined. I was initially against an explicit definition, but was soon
>> persuaded that there could be significant performance and security
>> problems with ad-hoc nesting. At this point the discussion moved
>> almost entirely to the consideration of nesting issues.
>>     
>
> Good suggestion.  This is very much needed for interoperability as more
> and more vendors supporting nested groups.
>
>   
>> Pete Rowley wanted an interface to be used by read-only clients to find
>> out what groups a particular entry is a member of without caring about
>> how the groups are defined. He suggested a memberOf attribute (presumably
>> server-maintained) for this purpose. Michael Liben also liked this
>> approach.
>>     
>
> This can even be a virtual attribute for which the implementation can be
> left to the vendor.  Should this include all sort of membership?  For
> eg. static groups, member status through group nesting, dynamic groups...
>
>   
I think the memberOf (or isMemberOf) attribute should be regarded as 
authoritative as to membership - that is, if the server recognizes a 
particular class as a group then it should should include the DNs of 
those entries it considers to be the set of members in the value set - 
this is so that clients can free themselves from deep knowledge of 
grouping mechanics. For group types that can be nested this would also 
include derived membership, but I believe that is a matter between the 
group types specification document and the implementation.

-- 
Pete


--------------ms060708060407070406030901
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEerver-maintained) for this purpose. Michael Liben also liked this
>> approach.
>>     
>
> This can even be a virtual attribute for which the implementation can be
> left to the vendor.  Should this include all sort of membership?  For
> eg. static groups, member status through group nesting, dynamic groups...
>
>   
I think the memberOf (or isMemberOf) attribute should be regarded as 
authoritative as to membership - that is, if the server recognizes a 
particular class as a group then it should should include the DNs of 
those entries it considers to be the set of members in the value set - 
this is so that clients can free themselves from deep knowledge of 
grouping mechanics. For group types that can be nested this would also 
include derived membership, but I believe that is a matter between the 
group types specification document and the implementation.

-- 
Pete


--------------ms060708060407070406030901
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjYyMTEzMjdaMCMGCSqGSIb3DQEJBDEWBBQWfqDN6XUCCExI
48lqbSChvb4jYTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEAI+nzYJGbUuN1W/w2Jjd9tbY8tt+r5Dkngl5TDTyC+2GYbtXweB5o8HXTNa7U
AwFA9sVTSbBRd5qU6ya4s4G7RxtVZk74pYAjtFDsJIiqj0+TvTLILhCirPS465hEQOJnx+cY
+64SFNIXdnXfzWvSh64sa1iDRm/0Aaiz5hkibysWRMlaM7cenqd+OOiupbMf5jUsxs0deuEb
ycqZuTj3fJt6kRysFvh39xQvtaa/kks8AJEYvC0D7zn8dp1tJ8UVe/fY8hWwi7B8ZpV6Pm2s
g0PQLVhBnglO0hd7Vqa1dWW4lO1W2yI0XYKRnayOhN0EMbr9meTecefcnWZmZndtCgAAAAAA
AA==
--------------ms060708060407070406030901--


--===============1654172129==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1654172129==--


From ldapext-bounces@ietf.org Wed Sep 26 17:16:48 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaeE1-00027z-4i; Wed, 26 Sep 2007 17:15:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaeDy-00023U-8q
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:15:14 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaeDy-0008L6-0a
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:15:14 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLFCXC012127
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Sep 2007 17:15:12 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLFCKE019058;
	Wed, 26 Sep 2007 17:15:12 -0400
Received: from [10.13.248.84] (vpn-248-84.boston.redhat.com [10.13.248.84])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8QLF8pn007592; Wed, 26 Sep 2007 17:15:09 -0400
Message-ID: <46FACBDD.7080008@redhat.com>
Date: Wed, 26 Sep 2007 14:15:09 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: Ludovic Poitou <Ludovic.Poitou@Sun.COM>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>	<46F86C11.8080203@highlandsun.com>
	<598D2001-BB82-434D-9571-0B2F140303EE@sun.com>
In-Reply-To: <598D2001-BB82-434D-9571-0B2F140303EE@sun.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Andrew Findlay <andrew.findlay@skills-1st.co.uk>,
	LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://wwAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjYyMTEzMjdaMCMGCSqGSIb3DQEJBDEWBBQWfqDN6XUCCExI
48lqbSChvb4jYTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEAI+nzYJGbUuN1W/w2Jjd9tbY8tt+r5Dkngl5TDTyC+2GYbtXweB5o8HXTNa7U
AwFA9sVTSbBRd5qU6ya4s4G7RxtVZk74pYAjtFDsJIiqj0+TvTLILhCirPS465hEQOJnx+cY
+64SFNIXdnXfzWvSh64sa1iDRm/0Aaiz5hkibysWRMlaM7cenqd+OOiupbMf5jUsxs0deuEb
ycqZuTj3fJt6kRysFvh39xQvtaa/kks8AJEYvC0D7zn8dp1tJ8UVe/fY8hWwi7B8ZpV6Pm2s
g0PQLVhBnglO0hd7Vqa1dWW4lO1W2yI0XYKRnayOhN0EMbr9meTecefcnWZmZndtCgAAAAAA
AA==
--------------ms060708060407070406030901--


--===============1654172129==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1654172129==--


From ldapext-bounces@ietf.org Wed Sep 26 17:16:48 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaeE1-00027z-4i; Wed, 26 Sep 2007 17:15:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaeDy-00023U-8q
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:15:14 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaeDy-0008L6-0a
	for ldapext@ietf.org; Wed, 26 Sep 2007 17:15:14 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLFCXC012127
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Sep 2007 17:15:12 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8QLFCKE019058;
	Wed, 26 Sep 2007 17:15:12 -0400
Received: from [10.13.248.84] (vpn-248-84.boston.redhat.com [10.13.248.84])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8QLF8pn007592; Wed, 26 Sep 2007 17:15:09 -0400
Message-ID: <46FACBDD.7080008@redhat.com>
Date: Wed, 26 Sep 2007 14:15:09 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: Ludovic Poitou <Ludovic.Poitou@Sun.COM>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>	<46F86C11.8080203@highlandsun.com>
	<598D2001-BB82-434D-9571-0B2F140303EE@sun.com>
In-Reply-To: <598D2001-BB82-434D-9571-0B2F140303EE@sun.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Andrew Findlay <andrew.findlay@skills-1st.co.uk>,
	LDAP Extensions list <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0870265823=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0870265823==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms070009050600060108020307"

This is a cryptographically signed message in MIME format.

--------------ms070009050600060108020307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ludovic Poitou wrote:
>
> So, yes, it would be really nice to see some harmonization in that space.
Very cool, I agree.

I recently wrote a memberof plugin for FDS that currently supports 
static groups only. Definitely a good idea to standardize this I think.

-- 
Pete


--------------ms070009050600060108020307
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHw1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0870265823=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0870265823==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms070009050600060108020307"

This is a cryptographically signed message in MIME format.

--------------ms070009050600060108020307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ludovic Poitou wrote:
>
> So, yes, it would be really nice to see some harmonization in that space.
Very cool, I agree.

I recently wrote a memberof plugin for FDS that currently supports 
static groups only. Definitely a good idea to standardize this I think.

-- 
Pete


--------------ms070009050600060108020307
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjYyMTE1MDlaMCMGCSqGSIb3DQEJBDEWBBSAfaBT95JObDPj
zS1m5Lb7q1U7hzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEALTx8qJ6XaMxvplurWe80bPfEBbzKP+n2CWoMZSLvhxRmdFiMRQlJeYnmYiJN
fGOpLJIzGQf3hJdYN9cBcMtDjpiCncsHXLk7vAVA6gTy5JAy2fcI+fgxohqcDD53wpfVrarR
RIhlblJjBmqJaV2JlZCuvG/Ve9d0AdXKkboJPwj6jQBPSmQrMMFDhjOvEqVw3k4uxxqFoaOf
L+KV5tCh/6C26/qURQc0m3F1MA3YpOIIBYFq5ZIfBAjxglu/ZrVlsJmdugdENghfU+3EG3Io
jLwI/MhtehdtCQNSMXB8F8ZFzafzAAlyonZRE/iWfurXcUlnL0XDIV5sJizFot1eOAAAAAAA
AA==
--------------ms070009050600060108020307--


--===============0870265823==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0870265823==--






DEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjYyMTE1MDlaMCMGCSqGSIb3DQEJBDEWBBSAfaBT95JObDPj
zS1m5Lb7q1U7hzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEALTx8qJ6XaMxvplurWe80bPfEBbzKP+n2CWoMZSLvhxRmdFiMRQlJeYnmYiJN
fGOpLJIzGQf3hJdYN9cBcMtDjpiCncsHXLk7vAVA6gTy5JAy2fcI+fgxohqcDD53wpfVrarR
RIhlblJjBmqJaV2JlZCuvG/Ve9d0AdXKkboJPwj6jQBPSmQrMMFDhjOvEqVw3k4uxxqFoaOf
L+KV5tCh/6C26/qURQc0m3F1MA3YpOIIBYFq5ZIfBAjxglu/ZrVlsJmdugdENghfU+3EG3Io
jLwI/MhtehdtCQNSMXB8F8ZFzafzAAlyonZRE/iWfurXcUlnL0XDIV5sJizFot1eOAAAAAAA
AA==
--------------ms070009050600060108020307--


--===============0870265823==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0870265823==--






From ldapext-bounces@ietf.org Thu Sep 27 05:02:25 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IapDE-0000ee-HM; Thu, 27 Sep 2007 04:59:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IapDC-0000eI-8X
	for ldapext@ietf.org; Thu, 27 Sep 2007 04:59:10 -0400
Received: from public.id2-vpn.continvity.gns.novell.com ([195.33.99.129]
	helo=gwia-smtp.id2.novell.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IapDB-0000Wn-PW
	for ldapext@ietf.org; Thu, 27 Sep 2007 04:59:10 -0400
Received: from [192.168.1.139] (id2-L4-foundry2.gns.novell.com
	[::ffff:149.44.117.248])
	by gwia-smtp.id2.novell.com with ESMTP (TLS encrypted);
	Thu, 27 Sep 2007 09:58:39 +0100
Message-ID: <46FB70A6.1080900@novell.com>
Date: Thu, 27 Sep 2007 14:28:14 +0530
From: Jaimon Jose <jjaimon@novell.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Pete Rowley <prowley@redhat.com>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com> <46FACB77.1070307@redhat.com>
In-Reply-To: <46FACB77.1070307@redhat.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jjaimon@novell.com
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Pete Rowley wrote, On 09/27/2007 02:43 AM:
> I think the memberOf (or isMemberOf) attribute should be regarded as
> authoritative as to membership - that is, if the server recognizes a
> particular class as a group then it should should include the DNs of
> those entries it considers to be the set of members in the value set -
> this is so that clients can free themselves from deep knowledge of
> grouping mechanics. For group types that can be nested this would also
> include derived membership, but I believe that is a matter between the
> group types specification document and the implementation.

I think there should be a way to read direct membership and membership
through nested group hierarchy.  There is already a proposal to have a
control or extension to achieve this.  This functionality will be
required for management consoles to efficiently display member DNs
(non-group) and member groups.  At the same time, having a separate
attribute to hold member groups will be more convenient to  implement
from both client and server perspective.

While I agree that loop detection while evaluating nested groups is a
server implementation detail, how about, duplicate value elimination.
Should the standard say anything about this?

--jaimon


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Sep 27 14:50:18 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IayPc-0000MD-Iu; Thu, 27 Sep 2007 14:48:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IayPb-0000Eo-7F
	for ldapext@ietf.org; Thu, 27 Sep 2007 14:48:35 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IayPR-0007b9-TD
	for ldapext@ietf.org; Thu, 27 Sep 2007 14:48:31 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8RIm5dq024727
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 27 Sep 2007 14:48:05 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8RIm4Gm018241;
	Thu, 27 Sep 2007 14:48:04 -0400
Received: from [10.13.248.11] (vpn-248-11.boston.redhat.com [10.13.248.11])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8RIm1Kw020865; Thu, 27 Sep 2007 14:48:02 -0400
Message-ID: <46FBFADF.1050702@redhat.com>
Date: Thu, 27 Sep 2007 11:47:59 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: jjaimon@novell.com
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com> <46FACB77.1070307@redhat.com>
	<46FB70A6.1080900@novell.com>
In-Reply-To: <46FB70A6.1080900@novell.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0419255729=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0419255729==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms080005040901010507080908"

This is a cryptographically signed message in MIME format.

--------------ms080005040901010507080908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jaimon Jose wrote:
> Pete Rowley wrote, On 09/27/2007 02:43 AM:
>   
>> I think the memberOf (or isMemberOf) attribute should be regarded as
>> authoritative as to membership - that is, if the server recognizes a
>> particular class as a group then it should should include the DNs of
>> those entries it considers to be the set of members in the value set -
>> this is so that clients can free themselves from deep knowledge of
>> grouping mechanics. For group types that can be nested this would also
>> include derived membership, but I believe that is a matter between the
>> group types specification document and the implementation.
>>     
>
> I think there should be a way to read direct membership and membership
> through nested group hierarchy.
What purpose would this have in a member entry?
>   There is already a proposal to have a
> control or extension to achieve this.  This functionality will be
> required for management consoles to efficiently display member DNs
> (non-group) and member groups.
Management consoles would deal directly with groups entries since they 
do need to understand grouping mechanics.
>   At the same time, having a separate
> attribute to hold member groups will be more convenient to  implement
> from both client and server perspective.
>   
I don't think it is more convenient for general clients, I think it is 
actually less value due to the requirement to merge the two value sets 
in order to get the group list. The vast majority of clients really 
don't care why an entry is a member of a group, they just want to know 
that it is.
> While I agree that loop detection while evaluating nested groups is a
> server implementation detail, how about, duplicate value elimination.
> Should the standard say anything about this?
>   
Hmm, are you thinking I was referring to the group proposal?  I was 
confining my comment to the memberof attribute.



-- 
Pete


--------------ms080005040901010507080908
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjcxODQ3NTlaMCMGCSqGSIb3DQEJBDEWBBTa1or3Gug/G1YI
hj7QQlSVFplk4jBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEAjtCD70W5L0HOBpZfJpL5mirTQ/coTzs8qyPpqsno64uBhHfnRisTPa6wG9+f
Jfl1w5KLFrRCcLrex8azC09BmRuWXIs8wpiflmF5BmxNXmFq7CAcPt6lrL7NifxXZYx+AqKw
ZqM9P+7+mPmrYw7xDA3ygjLTVLgHW8CoPJ42R/497E0iIJxfdNTE3ktFD4m349+WyjWa9qO4
k9zFUajCGLdcsLWAwBFthCdmplb7yMCoeaKgnthizSrR/NyWGCRg6SVLkz1N8K/tP769coPR
cISWussX0YrGPhV2KZFyYMfosrmxBm3zW1zqbORoO8qDkk18s9iYxwinW3hKXIrFEwAAAAAA
AA==
--------------ms080005040901010507080908--


--===============0419255729==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0419255729==--




From ldapext-bounces@ietf.org Fri Sep 28 05:49:11 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbCPq-0001D9-QG; Fri, 28 Sep 2007 05:45:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbCPo-00076U-Ff
	for ldapext@ietf.org; Fri, 28 Sep 2007 05:45:44 -0400
Received: from public.id2-vpn.continvity.gns.novell.com ([195.33.99.129]
	helo=gwia-smtp.id2.novell.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IbCPa-0000dn-Mo
	for ldapext@ietf.org; Fri, 28 Sep 2007 05:45:31 -0400
Received: from [192.168.1.139] (id2-L4-foundry2.gns.novell.com
	[::ffff:149.44.117.248])
	by gwia-smtp.id2.novell.com with ESMTP (TLS encrypted);
	Fri, 28 Sep 2007 10:45:28 +0100
Message-ID: <46FCCD1E.1040602@novell.com>
Date: Fri, 28 Sep 2007 15:15:02 +0530
From: Jaimon Jose <jjaimon@novell.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Pete Rowley <prowley@redhat.com>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com> <46FACB77.1070307@redhat.com>
	<46FB70A6.1080900@novell.com> <46FBFADF.1050702@redhat.com>
In-Reply-To: <46FBFADF.1050702@redhat.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jjaimon@novell.com
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Pete Rowley wrote, On 09/28/2007 12:17 AM:
> Jaimon Jose wrote:
>> Pete Rowley wrote, On 09/27/2007 02:43 AM:
>>  
>>> I think the memberOf (or isMemberOf) attribute should be regarded as
>>> authoritative as to membership - that is, if the server recognizes a
>>> particular class as a group then it should should include the DNs of
>>> those entries it considers to be the set of members in the value set -
>>> this is so that clients can free themselves from deep knowledge of
>>> grouping mechanics. For group types that can be nested this would also
>>> include derived membership, but I believe that is a matter between the
>>> group types specification document and the implementation.
>>>     
>>
>> I think there should be a way to read direct membership and membership
>> through nested group hierarchy.
> What purpose would this have in a member entry?

This is from an administrative perspective.  Our experience in
implementing dynamic groups and nested groups (yet to be released
eDirectory 8.8.2) in eDirectory is that, Administrators always wanted to
know how an entry becomes member of a group.  They also wanted to know
the direct(static) members of a group and members through nested or
dynamic relationship.  This is because, the hierarchy can be pretty
complex in a deeply nested scenario and administrators will not know who
 gets rights when they make a group as a trustee of an object.

>>   There is already a proposal to have a
>> control or extension to achieve this.  This functionality will be
>> required for management consoles to efficiently display member DNs
>> (non-group) and member groups.
> Management consoles would deal directly with groups entries since they
> do need to understand grouping mechanics.

Right.  So, they should be able to read groups entries and non-group
entries.

>>   At the same time, having a separate
>> attribute to hold member groups will be more convenient to  implement
>> from both client and server perspective.
>>   
> I don't think it is more convenient for general clients, I think it is
> actually less value due to the requirement to merge the two value sets
> in order to get the group list. The vast majority of clients really
> don't care why an entry is a member of a group, they just want to know
> that it is.

Clients need not know about this when they just read "member" attribute.
 The server implementation should be such that, unless the request
accompany a control or extension, the result set should contain direct
members and members of the groupMember (member DN of type group - nested
or dynamic) .

--jaimon

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Fri Sep 28 13:41:03 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbJns-00010N-UY; Fri, 28 Sep 2007 13:39:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbJnr-0000wW-4o
	for ldapext@ietf.org; Fri, 28 Sep 2007 13:39:03 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbJng-0008A4-4a
	for ldapext@ietf.org; Fri, 28 Sep 2007 13:38:58 -0400
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com
	[172.16.52.254])
	by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l8SHcMK2022795
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 28 Sep 2007 13:38:22 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l8SHcJ3Z007879;
	Fri, 28 Sep 2007 13:38:20 -0400
Received: from [10.13.248.76] (vpn-248-76.boston.redhat.com [10.13.248.76])
	by potter.sfbay.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id
	l8SHcACB010741; Fri, 28 Sep 2007 13:38:12 -0400
Message-ID: <46FD3C03.9050506@redhat.com>
Date: Fri, 28 Sep 2007 10:38:11 -0700
From: Pete Rowley <prowley@redhat.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061215)
MIME-Version: 1.0
To: jjaimon@novell.com
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46FA65A4.6080700@novell.com> <46FACB77.1070307@redhat.com>
	<46FB70A6.1080900@novell.com> <46FBFADF.1050702@redhat.com>
	<46FCCD1E.1040602@novell.com>
In-Reply-To: <46FCCD1E.1040602@novell.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2081728275=="
Errors-To: ldapext-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============2081728275==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020105090703020708060100"

This is a cryptographically signed message in MIME format.

--------------ms020105090703020708060100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jaimon Jose wrote:
> Pete Rowley wrote, On 09/28/2007 12:17 AM:
>   
>> Jaimon Jose wrote:
>>     
>>> Pete Rowley wrote, On 09/27/2007 02:43 AM:
>>>  
>>>       
>>>> I think the memberOf (or isMemberOf) attribute should be regarded as
>>>> authoritative as to membership - that is, if the server recognizes a
>>>> particular class as a group then it should should include the DNs of
>>>> those entries it considers to be the set of members in the value set -
>>>> this is so that clients can free themselves from deep knowledge of
>>>> grouping mechanics. For group types that can be nested this would also
>>>> include derived membership, but I believe that is a matter between the
>>>> group types specification document and the implementation.
>>>>     
>>>>         
>>> I think there should be a way to read direct membership and membership
>>> through nested group hierarchy.
>>>       
>> What purpose would this have in a member entry?
>>     
>
> This is from an administrative perspective.  Our experience in
> implementing dynamic groups and nested groups (yet to be released
> eDirectory 8.8.2) in eDirectory is that, Administrators always wanted to
> know how an entry becomes member of a group.  They also wanted to know
> the direct(static) members of a group and members through nested or
> dynamic relationship.  This is because, the hierarchy can be pretty
> complex in a deeply nested scenario and administrators will not know who
>  gets rights when they make a group as a trustee of an object.
>
>   
>
OK. It seems like this would be useful even for management client thats 
don't fully understand all grouping mechanics.
>
> Clients need not know about this when they just read "member" attribute.
>  The server implementation should be such that, unless the request
> accompany a control or extension, the result set should contain direct
> members and members of the groupMember (member DN of type group - nested
> or dynamic) .
>
>   
I prefer more attributes to controls (they are generally more 
universally compatible), but I wonder if there isn't a case here for 
using a control that allows the client to follow the chain of membership 
i.e. ask the question of any group entry "how does this group come to 
call this member a member?", the answer for which is either it doesn't, 
by direct inclusion, or through this list of DN's of other group entries 
(and perhaps a combination of the last two).


-- 
Pete


--------------ms020105090703020708060100
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBzCC
At4wggJHoAMCAQICEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoX
DTA3MTExNTA4MDUyMFowRDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8G
CSqGSIb3DQEJARYScHJvd2xleUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEApRABgFPN60gQLIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/
lBTwxDIncumO3HBJraWx8dUdimys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZ
FOYN0xcAOAKyaSrnHIl7N7PFF1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H
5O7ZZGl6ra04MT19hsYkdZFT/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVo
YD4fx+PFAgcSxLo7TBM9DBftPAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQAB
oy8wLTAdBgNVHREEFjAUgRJwcm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQUFAAOBgQA5oUNvfvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQx
UMFCze6IMLecAt+zRYh0i09oeMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbl
eP/3B4rADYzdlxa63n5akR2EvDkwi0/a2byeLU/MMk9LFDCCAt4wggJHoAMCAQICEDviSvkt
A94T6A8TxUShd9AwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo
YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTExNTA4MDUyMFoXDTA3MTExNTA4MDUyMFowRDEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYScHJvd2xl
eUByZWRoYXQuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApRABgFPN60gQ
LIQRuuKGvf1ZEPfxgVykZrd3uIzpJ8ipQlQMujFQMIT+i6Q/lBTwxDIncumO3HBJraWx8dUd
imys4dG+zOsI0ajjO4TeIRMFkS9/njnsKbNH6j721WY+VuaZFOYN0xcAOAKyaSrnHIl7N7PF
F1VlUwGdd/QlzgBsXnFDIJrejBE0EDM9iXEVvnoDiMQQg81H5O7ZZGl6ra04MT19hsYkdZFT
/ajuD6+Rr5LjqoIE2vYlpBj5gL0z1Mg6NNygtOT91UQN4BVoYD4fx+PFAgcSxLo7TBM9DBft
PAkgHsHlWWuVSXl0kbvO1ps/TRo31Y8yO463mrHEpQIDAQABoy8wLTAdBgNVHREEFjAUgRJw
cm93bGV5QHJlZGhhdC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQA5oUNv
fvaG1tRLI1BM8Pn3eENhvv6b8VR5aG07MXCsqhw5MNXkTzQxUMFCze6IMLecAt+zRYh0i09o
eMJXudctJZCPXSRg4ygSDJ0dIVhz7v5ExIyEm5DCfzEBlIbleP/3B4rADYzdlxa63n5akR2E
vDkwi0/a2byeLU/MMk9LFDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa
MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vy
dmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcw
MDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUg
Q29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW
y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEE
QB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2
oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3Js
MAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0x
MzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf
qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9l
X5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIIDYAIBATB2
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQO+JK+S0D
3hPoDxPFRKF30DAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0wNzA5MjgxNzM4MTFaMCMGCSqGSIb3DQEJBDEWBBT3KpJOh5KRmCO4
F7pFnKUQ8+ssWzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAE
MXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDvi
SvktA94T6A8TxUShd9AwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDviSvktA94T6A8TxUShd9AwDQYJKoZIhvcN
AQEBBQAEggEABHCn0WzLgJCu/a4uYjV31VjZ0+dsLmALkxxEtDiERsyAenuE7A8+MvB7MKyt
F2BHO1Rm6zz2po2qFFuCbDLtDsZI17d3bKlE/F2rcanuuzsyu70wD9VnLY/Pxs9JZf2Ad/Jj
lr9xlkzLEr974woGP++BqOrjmFJapldq19VrnJMmTU47cHYjRh8rBOock5+irs3K/5pqo1zg
iuY9wj49oPfmrTeuutqK/1HGjElgV79dsNdV6p55lnbJhnoKoPBXaVsMVKEWBd8eKG8azwwD
HpKZ8/Evph+J3sY5HRSM3O5DmUghm40VT2nsRUtF1yEi7zylRie4W9A5xzDkMFYulAAAAAAA
AA==
--------------ms020105090703020708060100--


--===============2081728275==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============2081728275==--




From ldapext-bounces@ietf.org Sat Sep 29 19:33:49 2007
Return-path: <ldapext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbllB-00056Y-0u; Sat, 29 Sep 2007 19:30:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ibll9-0004yc-QY
	for ldapext@ietf.org; Sat, 29 Sep 2007 19:30:07 -0400
Received: from ptb-relay01.plus.net ([212.159.14.212])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iblkz-0002I5-F7
	for ldapext@ietf.org; Sat, 29 Sep 2007 19:30:03 -0400
Received: from [80.229.93.1] (helo=suretecsystems.com)
	by ptb-relay01.plus.net with esmtp (Exim) id 1IblkL-0000Cq-JU;
	Sun, 30 Sep 2007 00:29:17 +0100
Received: from ldap-slave.suretecsystems.com ([192.168.100.90])
	by suretecsystems.com with esmtp (Exim 4.63)
	(envelope-from <ghenry@suretecsystems.com>)
	id 1IblkI-0002Pb-53; Sun, 30 Sep 2007 00:29:17 +0100
Message-ID: <46FEDFC8.5020403@suretecsystems.com>
Date: Sun, 30 Sep 2007 00:29:12 +0100
From: Gavin Henry <ghenry@suretecsystems.com>
Organization: Suretec Systems Ltd.
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] Summary of group discussion
References: <20070924194342.GA9926@tile.skills-1st.co.uk>
	<46F86C11.8080203@highlandsun.com>
In-Reply-To: <46F86C11.8080203@highlandsun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.4 (-)
X-Spam-Report: Spam detection software, running on the system "dax", has
	identified this incoming email as possible spam. The original message
	has been attached to this so you can view it (if it isn't spam) or
	label similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview: Howard Chu wrote: > Andrew Findlay wrote: > >> It
	seems to
	me that we now have these threads of development: >> >> 1) A new
	structural
	group class that can represent empty groups. >> This could go forward
	with
	the existing ambiguous member >> attribute or it could become the basis
	of
	a group >> representation with more carefully defined semantics using
	>>
	directMember. >> >> 2) A new auxiliary class and one or more attributes
	to
	represent >> groups that may contain other groups. For this to make
	much
	>> sense it would require the well-defined version of (1). >> >> In (1)
	and
	(2) I see the definitions of the attributes being >> the key,
	and would avoid
	requiring the use of the object >> classes to obtain the defined
	semantics.
	> > I think you should avoid dwelling on this last point. It just
	confuses
	> the issue. It seems certain that we're defining new attributes,
	and > therefore
	at least a new objectclass is needed to make use of them. Also > the
	notion
	of placing all the semantics solely in the attribute begs the >
	question "is a group with no members no longer a group?" (Yes,
	it's a > silly question, 
	but it can be easily avoided by not focusing too much on > the
	attribute.)
	> >> 3) A new control or extended operation so that a client can ask >>
	the
	server to do the heavy lifting involved with nested >> groups. >> >> 4)
	A new server-maintained attribute called memberOf to give an >>
	alternative
	way for clients to ask for membership information. >> AD already has
	such an attribute,
	and Pierangelo Masarati >> recently proposed one for OpenLDAP
	so there may be useful >> existing work to build on. > > Pierangelo's
	code
	is already released in OpenLDAP 2.4.5. > >> 5) A document explaining
	why
	groupOfUniqueNames, >> uniqueMember and nameAndOptionalUID are bad,
	possibly
	leading >> to them being deprecated in the next revision of the core
	LDAP >> standards. > > I'll write this up. > [...] 
	Content analysis details:   (-1.4 points, 5.0 required)
	pts rule name              description
	---- ----------------------
	--------------------------------------------------
	-1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-Scan-Signature: 25b2cef2de3c02b7605ef0327976f9d6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: LDAP Extensions list <ldapext@ietf.org>,
	Andrew Findlay <andrew.findlay@skills-1st.co.uk>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Howard Chu wrote:
> Andrew Findlay wrote:
> 
>> It seems to me that we now have these threads of development:
>>
>> 1)    A new structural group class that can represent empty groups.
>>     This could go forward with the existing ambiguous member
>>     attribute or it could become the basis of a group
>>     representation with more carefully defined semantics using
>>     directMember.
>>
>> 2)    A new auxiliary class and one or more attributes to represent
>>     groups that may contain other groups. For this to make much
>>     sense it would require the well-defined version of (1).
>>     
>>     In (1) and (2) I see the definitions of the attributes being
>>     the key, and would avoid requiring the use of the object
>>     classes to obtain the defined semantics.
> 
> I think you should avoid dwelling on this last point. It just confuses 
> the issue. It seems certain that we're defining new attributes, and 
> therefore at least a new objectclass is needed to make use of them. Also 
> the notion of placing all the semantics solely in the attribute begs the 
> question "is a group with no members no longer a group?" (Yes, it's a 
> silly question, but it can be easily avoided by not focusing too much on 
> the attribute.)
> 
>> 3)    A new control or extended operation so that a client can ask
>>     the server to do the heavy lifting involved with nested
>>     groups.
>>
>> 4)    A new server-maintained attribute called memberOf to give an
>>     alternative way for clients to ask for membership information.
>>     AD already has such an attribute, and Pierangelo Masarati
>>     recently proposed one for OpenLDAP so there may be useful
>>     existing work to build on.
> 
> Pierangelo's code is already released in OpenLDAP 2.4.5.
> 
>> 5)    A document explaining why groupOfUniqueNames,
>>     uniqueMember and nameAndOptionalUID are bad, possibly leading
>>     to them being deprecated in the next revision of the core LDAP
>>     standards.
> 
> I'll write this up.
> 

Where would this be linked to/from? Format?

-- 
Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghenry@suretecsystems.com

Open Source. Open Solutions(tm).

http://www.suretecsystems.com/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



