headers
Ken Murchison | 25 Aug 2011 18:04
Picon

DAV ACL question

Folks,

Still a relative DAV newbie and trying to wrap my head around RFC 3744. 
  If I have an implementation where DAV:read-current-user-privilege-set 
can not be split from DAV:read, and DAV:read-acl, DAV:write-acl, 
DAV:unlock can not be separated from one another, is the response below 
correct?

I have DAV:read-current-user-privilege-set as abstract under DAV:read, 
and I have DAV:read-acl, DAV:write-acl, DAV:unlock all as abstract under 
a private aggregate right CYRUS:admin.

Actually, looking at this again, since all of the member privileges 
contained in the DAV:write aggregate have been granted to the current 
user, should DAV:write also be listed?

<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"
	       xmlns:CY="http://cyrusimap.org/ns/">
   <D:response>
     <D:href>/calendars/user/ken/events/≤/D:href>
     <D:propstat>
       <D:status>HTTP/1.1 200 OK</D:status>
       <D:prop>
         <D:supported-privilege-set>
           <D:supported-privilege>
             <D:privilege><D:all/></D:privilege>
             <D:abstract/>
             <D:description xml:lang="en">
	      Any operation</D:description>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Cyrus Daboo | 30 Aug 2011 15:38
Favicon

WebDAV sync last call

Hi folks,
The authors believe the WebDAv Sync document 
(<https://datatracker.ietf.org/doc/draft-daboo-webdav-sync/>) is ready to 
go to the IESG for consideration of publishing as an RFC. We'd like to get 
final reviews from this list along with a list of existing or planned 
implementations of this draft to include as supporting documentation for 
the IESG. Please review and provide feedback, thanks.

--

-- 
Cyrus Daboo
Permalink | Reply | 5 comments |

Gmane