[Ietf-caldav] various comments on scheduling outbox

[Arnaud Quillaud]

** Content of outbox **

At 
http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-05#section-3.1.2 
, there is no mention of what the content of the scheduling outbox might 
be (only itip but no freebusy message, auto delete,...). The definition 
of the POST method does not specify either whether a POST may result in 
a resource being created.
The only hint I could find is that in section 8.1.3, the 201 status code 
is listed.

** CALDAV:max-resource-size property on outbox **

The CALDAV:max-resource-size property is not listed in the scheduling 
outbox definition. Nevertheless, it is mentioned in 8.1 in the 
CALDAV:max-resource-size precondition.

** Preconditions **

I guess this one is a remaining from the 04 version and is no longer 
applicable:
<<

(CALDAV:attachments-allowed): The resource submitted in the POST
      request MUST NOT contain any inline ATTACH properties;

 >>

Arnaud Q