X-Account-Key: account2
Return-Path: <bounce-ldap-1361716@listserver.itd.umich.edu>
Received: from ibm09aec.bellsouth.net ([141.211.2.230])
          by imf02aec.mail.bellsouth.net with ESMTP
          id <20060718215824.IVIP2216.imf02aec.mail.bellsouth.net@ibm09aec.bellsouth.net>
          for <aok123@bellsouth.net>; Tue, 18 Jul 2006 17:58:24 -0400
Received: from listserver.gpcc.itd.umich.edu ([141.211.2.230])
          by ibm09aec.bellsouth.net with SMTP
          id <20060718215824.UISE11203.ibm09aec.bellsouth.net@listserver.gpcc.itd.umich.edu>
          for <aok123@bellsouth.net>; Tue, 18 Jul 2006 17:58:24 -0400
Received: from madman.mr.itd.umich.edu ([141.211.14.75]) by listserver.gpcc.itd.umich.edu with SMTP (Lyris ListManager LINUX version 7.0f); Tue, 18 Jul 2006 17:58:15 -0400
Received: FROM boole.openldap.org (boole.openldap.org [204.152.186.50])
	BY madman.mr.itd.umich.edu ID 44BD5976.D636F.18593 ; 
	18 Jul 2006 17:58:15 -0400
Received: from gypsy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com [24.205.218.53] (may be forged))
	(authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k6ILwBOX006862
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 18 Jul 2006 21:58:11 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060718142308.03424df0@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 18 Jul 2006 14:57:50 -0700
To: richm@stanfordalumni.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: [ldap] Re: Zero length modify request - proper response?
Cc: ldap@umich.edu
In-Reply-To: <44BD43E1.90807@stanfordalumni.org>
References: <44BD43E1.90807@stanfordalumni.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
List-Unsubscribe: <mailto:leave-ldap-1361716G@listserver.itd.umich.edu>
X-LYRIS-Message-Id: <LYRIS-1361716-2118828-2006.07.18-17.58.16--aok123#bellsouth.net@listserver.itd.umich.edu>
Precedence: bulk
List-Help: <http://www.umich.edu/~dirsvcs/ldap/mailinglist.html>

At 01:26 PM 7/18/2006, Rich Megginson wrote:
>What should the response be to a Modify request with no changes?  That is, if in
>
>       ModifyRequest ::= [APPLICATION 6] SEQUENCE {
>            object          LDAPDN,
>            changes         SEQUENCE OF change SEQUENCE {
>
>
>the length of the first SEQUENCE of changes is 0. Is this a valid modify request?

Yes, there is no size constraint on the sequence.  It can be
empty. Semantically, I believe such a request should be regarded
as a request to "touch" the object.  That is, the operational attributes
such as modifiersName and modifyTimestamp, of the target should be
updated.  It is noted as well that such a request might fail for
a variety of reasons (e.g., schema violation, access control).

>I would appreciate any pointers to RFCs or X.500 docs that talk about this.

Though not detailed specifically, I believe the above semantic is
consistent with RFC 4511 and, for DAP, X.511.  That is, the
above semantic doesn't conflict with the RFC 4511 or, for DAP,
X.511.

Regards, Kurt 


---
You are currently subscribed to ldap@umich.edu as: [aok123@bellsouth.net]
To unsubscribe send email to ldap-request@umich.edu with the word UNSUBSCRIBE as the SUBJECT of the message.


