The following are examples of response codes one would expect to get in a response to a MKCALENDAR request. Note that this list is by no means exhaustive.
201 (Created) - The calendar collection resource was created in its entirety;
207 (Multi-Status) - The calendar collection resource was not created since one or more DAV:set instructions specified in the request body could not be processed successfully. The following are examples of response codes one would expect to be used in a 207 (Multi-Status) response in this situation:
403 (Forbidden) - The client, for reasons the server chooses not to specify, cannot alter one of the properties;
409 (Conflict) - The client has provided a value whose semantics are not appropriate for the property. This includes trying to set read-only properties;
424 (Failed Dependency) - The DAV:set instruction on the specified resource would have succeeded if it were not for the failure of another DAV:set instruction specified in the request body;
423 (Locked) - The specified resource is locked and the client either is not a lock owner or the lock type requires a lock token to be submitted and the client did not submit it; and
507 (Insufficient Storage) - The server did not have sufficient space to record the property;
403 (Forbidden) - This indicates at least one of two conditions: 1) the server does not allow the creation of calendar collections at the given location in its namespace, or 2) the parent collection of the Request-URI exists but cannot accept members;
409 (Conflict) - A collection cannot be made at the Request-URI until one or more intermediate collections have been created;
415 (Unsupported Media Type) - The server does not support the request type of the body; and
507 (Insufficient Storage) - The resource does not have sufficient space to record the state of the resource after the execution of this method.