[Ietf-caldav] sending attendee PARSTAT update and iMIP - default
value for
schedule-calendar-transp - creation of attendee scheduling object
Arnaud Quillaud
Arnaud.Quillaud at Sun.COM
Fri Sep 26 07:44:10 PDT 2008
** 3.3.1.1. Processing an "Attendee" reply **
When processing an attendee reply we have this MUST:
<<
The server MUST send scheduling messages to all the other "Attendees"
indicating the change in participation status of the "Attendee"
replying, subject to the recurrence requirements of Section 3.5.1 <http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-05#section-3.5.1>.
>>
Does this also apply to ATTENDEEs to whom the server has to send an iMIP
message ? For a meeting with a large number of attendees, this might
become really annoying.
** 6.1. CALDAV:schedule-calendar-transp Property **
What is the default value when not present ? opaque ?
** creation of attendee scheduling object resources **
<<
The creation of attendee scheduling object resources will typically
be done by the server in cases where a default scheduling calendar
collection is defined. In cases where no default scheduling calendar
collection is defined, the server MAY prevent calendar user agents
from forging attendee scheduling object resources by forbidding their
creation or imposing restrictions on their creation. For instance, a
server MAY require the presence of a scheduling message, received
from the "ORGANIZER" with the same "UID" property value, in the
scheduling Inbox collection of the owner of the scheduling calendar
collection.
>>
About "forbidding their creation": This would make it impossible for
clients to process any "schedule-unprocessed" invitation so I think this
case should be removed.
About "imposing restrictions" and the particular example that you take:
The server would prevent clients from inserting any messages received
through other means (e.g. iMIP message). So even a MAY does not sound right.
More information about the Ietf-caldav
mailing list