W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2001


From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 21 Aug 2001 00:18:30 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F492E3@SUS-MA1IT01>
To: Webdav WG <w3c-dist-auth@w3c.org>
Well, that's a really easy change, i.e. all you have to do is
absolutely nothing (:-).  Currently, section 11 in 2518 places
no constraints on who can do an UNLOCK operation (i.e. if you
can discover the lock token, you can request an UNLOCK).  The ACL spec
introduces ways to constrain who can do an operation.  So we're done (:-).


-----Original Message-----
From: Jason Crawford [mailto:ccjason@us.ibm.com]
Sent: Monday, August 20, 2001 11:57 PM
To: Webdav WG
Subject: RE: Webdav issue: UNLOCK_BY_NON_LOCK_OWNERS

It sounds like we might have consensus opinion that the power to unlock
someone else's locked resource should be under ACL control.   Could someone
that feels strongly about this propose a wording and placement in 2518 that
makes this proposal concrete?



Phone: 914-784-7569,   ccjason@us.ibm.com
Received on Tuesday, 21 August 2001 00:09:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:23 UTC