[Ietf-caldav] Comments on: 3.2.3.3. HTTP Methods

[Arnaud Quillaud]

** DELETE of unprocessed iTIP REQUEST on calendar-inbox **

Could we define the behavior of a DELETE on an unprocessed iTIP REQUEST 
in the calendar-inbox as corresponding to a remove action.
By doing that, we would allow a client to directly decline a meeting 
without having to first insert it into one of the owner's calendar to 
just delete it from there to trigger a decline.

** MOVE of unprocessed iTIP REQUEST on calendar-inbox to scheduling 
collection **

Could we define the behavior of a MOVE of an unprocessed iTIP REQUEST on 
calendar-inbox into a scheduling collection as corresponding to the 
automatic processing of an invitation into that scheduling collection.
By doing that, we would allow a client to process an invitation, accept 
and store in one single operation, without even having to to know how to 
translate an iTIP message (potentially containing only info about a 
particular instance, etc...) into a calendar resource.

 We might want to add an http header to specify the PARSTAT to set.

** DELETE on default calendar collection **

Should we add a new precondition when trying to delete the default 
calendar collection ?

Arnaud Q