My input - iCAP and administration.

["Doug Royer [N6AAW]" <dougr@xxxxxxxxxxx>]

>From  the  IETF  meetings  in  LA, I do remember that we had
agreed that it would not be possible for CAP to  be  an  all
encompassing   administration  answer  for  calendaring  and
scheduling.  However I hope that there will be room for some
administration.

Now  that  I have spent some time thinking about some of the
issues, here are some of my thoughts and input  on  CAP  and
administration:

1.    There   needs   to   be  the  concept  of  a  calendar
administrator.

1.1.  An administrator is a calendar user account with extra
permissions   on  one  or  more  calendars  that  allow  the
administrator to configure the calendaring  system  in  ways
that  may restrict the calendar operations performed by non-
administrator users.

1.1.1.  The calendar administrator might or might not be the
owner of the calendar.  [This is based on the input from the
gentleman (who's name escapes me) from MIT, that  needed  to
restrict  a  users ability to delete calendar entries.  This
implies to  me  that  a  calendar  owner  can  not  override
administrator  restrictions  and  creates  the  need  for  a
separate entity.]

1.1.2.  There may be one or more calendar administrators per
system and one or more calendar administrators per calendar.
A  calendar  user  account  simply  has  or  does  not  have
administrator privileges on a given calendar store.

1.2.  Administration tasks that may need to be part of CAP:

(I)  Allow  named  users  or any user permission to create a
     calendar.

(II) Allow named users or any user permission  to  create  a
     sub-calendar.

(III)
     Allow  permission for named users or any user to create
     a sub-calendar under a calendar that they do not own.

(IV) Change the ownership of calendars.

(V)  Allow calendar owners to give  away  the  ownership  of
     calendars to other users.

(VI) Allow calendar users to own calendars.

(VII)
     Give  away  administration privileges to users on named
     calendars or globally.

(VIII)
     Restrict operations on a calendar by  users.  (both  on
     named calendars or globally):

         o Create/Modify/Delete entries that are public/confidential/private.

           How would one restrict a modification in a way that would limit
           it from effectively being a delete?

(IX) Allow/disallow  users to add/modify/delete calendar
     ACLs.


-Doug
-------------------------------------------------------------------
Doug.Royer@Eng.Sun.COM		http://www.royer.com/dougr.html
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL