[Ietf-caldav] calendar-inbox and calendar-access support.

[Arnaud Quillaud]

Hello,

The calendar scheduling draft at 
http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-04 mentions that:

<<

   A CalDAV scheduling server MAY also support the CalDAV calendar-
   access feature [RFC4791 <http://tools.ietf.org/html/rfc4791>], and that adds the following requirements:

      MUST support the CALDAV:calendar-query and CALDAV:multiget REPORTs
      on CALDAV:schedule-inbox and CALDAV:schedule-outbox collection
      resource types.


 >>

While this seems relatively straightforward for the multiget report, 
timerange based filtering brings up a few questions:
1) Some itip objects may not contain any time related property (e.g. 
VEVENT REPLY 
http://tools.ietf.org/html/draft-ietf-calsify-2446bis-07#section-3.2.3). 
Should those be considered as always matching, never matching,... ?
2) May a calendar inbox/outbox be associated with a particular timezone, 
just like a regular calendar collection ?

Extending question 2),  can a client expect a calendar-access enabled 
inbox/outbox to expose the properties listed at 
http://tools.ietf.org/html/rfc4791#section-5.2 ? It seems like it is the 
case (e.g. CALDAV:max-resource-size is mentioned) but this is not 
totally clear (e.g. CALDAV:supported-calendar-component-set is still 
missing).

Thanks,

Arnaud Q