Re: [ldapext] Attribute type ref, usage distributedOperation and Manage DSA ITmode
"Jim Sermersheim" <jimse@novell.com> Wed, 05 May 2004 15:11 UTC
Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19749 for <ldapext-archive@lists.ietf.org>; Wed, 5 May 2004 11:11:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLNvJ-0000qd-9a; Wed, 05 May 2004 11:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLNgX-0002R5-Vi for ldapext@optimus.ietf.org; Wed, 05 May 2004 10:47:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17330 for <ldapext@ietf.org>; Wed, 5 May 2004 10:47:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLNgV-0004RM-Cd for ldapext@ietf.org; Wed, 05 May 2004 10:47:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLNff-0004Cm-00 for ldapext@ietf.org; Wed, 05 May 2004 10:46:51 -0400
Received: from sinclair.provo.novell.com ([137.65.81.169]) by ietf-mx with esmtp (Exim 4.12) id 1BLNf4-0003v1-00 for ldapext@ietf.org; Wed, 05 May 2004 10:46:14 -0400
Received: from INET-PRV-MTA by sinclair.provo.novell.com with Novell_GroupWise; Wed, 05 May 2004 08:45:43 -0600
Message-Id: <s098a9b7.065@sinclair.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta
Date: Wed, 05 May 2004 08:45:16 -0600
From: Jim Sermersheim <jimse@novell.com>
To: ldapext@ietf.org, michael@stroeder.com
Subject: Re: [ldapext] Attribute type ref, usage distributedOperation and Manage DSA ITmode
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: ldapext-admin@ietf.org
Errors-To: ldapext-admin@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
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-Transfer-Encoding: quoted-printable
Michael, are you assuming that operational attributes are always non-user-editable? >>> Michael Ströder <michael@stroeder.com> 5/5/04 1:15:52 AM >>> HI! The USAGE of attribute type 'ref' is distributedOperation. From draft-ietf-ldapbis-models-10: A usage of directoryOperation, distributedOperation, or dSAOperation indicates that attributes of this type represent operational and/or administrative information. That is, they are operational attributes. So far, so good. But if a client is in Manage DSA IT mode 'ref' is not an operational attribute from the client's perspective. How should the client behave? Background: In web2ldap I solely present non-operational and user-editable attributes to the user when generating input forms. Hmm, I probably have to add special treatment for 'ref' considering the Manage DSA IT mode. 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
- Re: [ldapext] Attribute type ref, usage distribut… Jim Sermersheim
- Re: [ldapext] Attribute type ref, usage distribut… Michael Ströder