Difference between revisions of "RFC Compliance/CardDAV"

From Davical
Jump to navigationJump to search
m
m
 
Line 72: Line 72:
 
|{{Todo}}
 
|{{Todo}}
 
|}
 
|}
'''Texte gras'''
 

Latest revision as of 19:14, 20 February 2011

Help
Available languages

Covering the RFC6352{{#if:vCard Extensions to WebDAV (CardDAV)|:  |}}vCard Extensions to WebDAV (CardDAV) 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:

Details of Unsupported Features

Section Feature Requirement Status as at 0.9.9.1
3. MUST support vCard [RFC2426] as a media type for the address object resource format MUST Supported
3. MUST support WebDAV Class 3 MUST :  |}}largely supported, except COPY, but needs checking.)
3. MUST support WebDAV ACL MUST :  |}}significantly supported, see separate status)
3. MUST support secure transport MUST Supported
3. MUST support ETags MUST Supported
3. MUST support all address book REPORTs defined in Section 8 MUST Supported
3. MUST advertise support on all addressbook collections and address object resources for the addressbook reports via supported-report-set MUST Supported
3. SHOULD support the extended MKCOL method SHOULD Supported
3. MUST :  |}})