RFC Compliance/CardDAV

Covering the points in detail and listing where DAViCal is believed to be in compliance with the specification.

Overview
CardDAV has not been a target for *any* kind of support until 0.9.8, so support for this specification is very limited at present and is not advertised. Furthermore, at the time of writing this is still a draft specification and may change before publication.

To advertise support for CardDAV, a server:
 * MUST support vCard [RFC2426] as a media type for the address object resource format;
 * MUST support WebDAV Class 3 [RFC4918];
 * MUST support WebDAV ACL [RFC3744];
 * MUST support secure transport as defined in [RFC2818] using TLS v1.0 [RFC2246] or a subsequent standards-track version of TLS;
 * MUST support ETags [RFC2616] with additional requirements specified in Section 6.3.2.3 of this document;
 * MUST support all address book REPORTs defined in Section 8 of this document; and
 * MUST advertise support on all addressbook collections and address object resources for the addressbook reports in the DAV:supported-report-set property, as defined in Versioning Extensions to WebDAV [RFC3253].

In addition, a server:


 * SHOULD support the extended MKCOL method to create address book collections as defined in Section 6.3.1 of this document.