draft-ietf-vcarddav-carddav-10.txt   rfc6352.txt 
Network Working Group C. Daboo Internet Engineering Task Force (IETF) C. Daboo
Internet-Draft Apple Request for Comments: 6352 Apple
Intended status: Standards Track November 9, 2009 Category: Standards Track August 2011
Expires: May 13, 2010 ISSN: 2070-1721
vCard Extensions to WebDAV (CardDAV)
draft-ietf-vcarddav-carddav-10
Status of this Memo CardDAV: vCard Extensions to
Web Distributed Authoring and Versioning (WebDAV)
This Internet-Draft is submitted to IETF in full conformance with the Abstract
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering This document defines extensions to the Web Distributed Authoring and
Task Force (IETF), its areas, and its working groups. Note that Versioning (WebDAV) protocol to specify a standard way of accessing,
other groups may also distribute working documents as Internet- managing, and sharing contact information based on the vCard format.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on May 13, 2010. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6352.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document defines extensions to the Web Distributed Authoring and This document may contain material from IETF Documents or IETF
Versioning (WebDAV) protocol to specify a standard way of accessing, Contributions published or made publicly available before November
managing, and sharing contact information based on the vCard format. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction and Overview . . . . . . . . . . . . . . . . . . 4 1. Introduction and Overview . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements Overview . . . . . . . . . . . . . . . . . . . . 6 3. Requirements Overview . . . . . . . . . . . . . . . . . . . . 6
4. Address Book Data Model . . . . . . . . . . . . . . . . . . . 7 4. Address Book Data Model . . . . . . . . . . . . . . . . . . . 7
4.1. Address Book Server . . . . . . . . . . . . . . . . . . . 7 4.1. Address Book Server . . . . . . . . . . . . . . . . . . . 7
5. Address Book Resources . . . . . . . . . . . . . . . . . . . . 7 5. Address Book Resources . . . . . . . . . . . . . . . . . . . . 7
5.1. Address Object Resources . . . . . . . . . . . . . . . . . 8 5.1. Address Object Resources . . . . . . . . . . . . . . . . . 7
5.1.1. Data Type Conversion . . . . . . . . . . . . . . . . . 8 5.1.1. Data Type Conversion . . . . . . . . . . . . . . . . . 8
5.1.1.1. Additional Precondition for GET . . . . . . . . . 9 5.1.1.1. Additional Precondition for GET . . . . . . . . . 8
5.2. Address Book Collections . . . . . . . . . . . . . . . . . 9 5.2. Address Book Collections . . . . . . . . . . . . . . . . . 9
6. Address Book Feature . . . . . . . . . . . . . . . . . . . . . 10 6. Address Book Feature . . . . . . . . . . . . . . . . . . . . . 10
6.1. Address Book Support . . . . . . . . . . . . . . . . . . . 10 6.1. Address Book Support . . . . . . . . . . . . . . . . . . . 10
6.1.1. Example: Using OPTIONS for the Discovery of 6.1.1. Example: Using OPTIONS for the Discovery of
Support for CardDAV . . . . . . . . . . . . . . . . . 10 Support for CardDAV . . . . . . . . . . . . . . . . . 10
6.2. Address Book Properties . . . . . . . . . . . . . . . . . 10 6.2. Address Book Properties . . . . . . . . . . . . . . . . . 10
6.2.1. CARDDAV:addressbook-description Property . . . . . . . 11 6.2.1. CARDDAV:addressbook-description Property . . . . . . . 10
6.2.2. CARDDAV:supported-address-data Property . . . . . . . 11 6.2.2. CARDDAV:supported-address-data Property . . . . . . . 11
6.2.3. CARDDAV:max-resource-size Property . . . . . . . . . . 12 6.2.3. CARDDAV:max-resource-size Property . . . . . . . . . . 12
6.3. Creating Resources . . . . . . . . . . . . . . . . . . . . 13 6.3. Creating Resources . . . . . . . . . . . . . . . . . . . . 13
6.3.1. Extended MKCOL Method . . . . . . . . . . . . . . . . 13 6.3.1. Extended MKCOL Method . . . . . . . . . . . . . . . . 13
6.3.1.1. Example - Successful MKCOL request . . . . . . . . 14 6.3.1.1. Example - Successful MKCOL Request . . . . . . . . 14
6.3.2. Creating Address Object Resources . . . . . . . . . . 16 6.3.2. Creating Address Object Resources . . . . . . . . . . 15
6.3.2.1. Additional Preconditions for PUT, COPY and MOVE . 17 6.3.2.1. Additional Preconditions for PUT, COPY, and
6.3.2.2. Non-Standard vCard Properties, and Parameters . . 18 MOVE . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.2.2. Non-Standard vCard Properties and Parameters . . . 17
6.3.2.3. Address Object Resource Entity Tag . . . . . . . . 18 6.3.2.3. Address Object Resource Entity Tag . . . . . . . . 18
7. Address Book Access Control . . . . . . . . . . . . . . . . . 19 7. Address Book Access Control . . . . . . . . . . . . . . . . . 18
7.1. Additional Principal Properties . . . . . . . . . . . . . 19 7.1. Additional Principal Properties . . . . . . . . . . . . . 18
7.1.1. CARDDAV:addressbook-home-set Property . . . . . . . . 19 7.1.1. CARDDAV:addressbook-home-set Property . . . . . . . . 19
7.1.2. CARDDAV:principal-address Property . . . . . . . . . . 20 7.1.2. CARDDAV:principal-address Property . . . . . . . . . . 19
8. Address Book Reports . . . . . . . . . . . . . . . . . . . . . 21 8. Address Book Reports . . . . . . . . . . . . . . . . . . . . . 20
8.1. REPORT Method . . . . . . . . . . . . . . . . . . . . . . 21 8.1. REPORT Method . . . . . . . . . . . . . . . . . . . . . . 20
8.2. Ordinary Collections . . . . . . . . . . . . . . . . . . . 21 8.2. Ordinary Collections . . . . . . . . . . . . . . . . . . . 21
8.3. Searching Text: Collations . . . . . . . . . . . . . . . . 21 8.3. Searching Text: Collations . . . . . . . . . . . . . . . . 21
8.3.1. CARDDAV:supported-collation-set Property . . . . . . . 22 8.3.1. CARDDAV:supported-collation-set Property . . . . . . . 22
8.4. Partial Retrieval . . . . . . . . . . . . . . . . . . . . 23 8.4. Partial Retrieval . . . . . . . . . . . . . . . . . . . . 23
8.5. Non-standard Properties and Parameters . . . . . . . . . . 23 8.5. Non-Standard Properties and Parameters . . . . . . . . . . 23
8.6. CARDDAV:addressbook-query Report . . . . . . . . . . . . . 24 8.6. CARDDAV:addressbook-query Report . . . . . . . . . . . . . 23
8.6.1. Limiting Results . . . . . . . . . . . . . . . . . . . 25 8.6.1. Limiting Results . . . . . . . . . . . . . . . . . . . 25
8.6.2. Truncation of Results . . . . . . . . . . . . . . . . 26 8.6.2. Truncation of Results . . . . . . . . . . . . . . . . 25
8.6.3. Example: Partial Retrieval of vCards Matching 8.6.3. Example: Partial Retrieval of vCards Matching
NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26 NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26
8.6.4. Example: Partial Retrieval of vCards Matching a 8.6.4. Example: Partial Retrieval of vCards Matching a
Full Name or Email Address . . . . . . . . . . . . . . 28 Full Name or Email Address . . . . . . . . . . . . . . 27
8.6.5. Example: Truncated Results . . . . . . . . . . . . . . 31 8.6.5. Example: Truncated Results . . . . . . . . . . . . . . 29
8.7. CARDDAV:addressbook-multiget Report . . . . . . . . . . . 32 8.7. CARDDAV:addressbook-multiget Report . . . . . . . . . . . 31
8.7.1. Example: CARDDAV:addressbook-multiget Report . . . . . 34 8.7.1. Example: CARDDAV:addressbook-multiget Report . . . . . 32
8.7.2. Example: CARDDAV:addressbook-multiget Report . . . . . 35 8.7.2. Example: CARDDAV:addressbook-multiget Report . . . . . 33
9. Client Guidelines . . . . . . . . . . . . . . . . . . . . . . 36 9. Client Guidelines . . . . . . . . . . . . . . . . . . . . . . 34
9.1. Restrict the Properties Returned . . . . . . . . . . . . . 36 9.1. Restrict the Properties Returned . . . . . . . . . . . . . 34
9.2. Avoiding Lost Updates . . . . . . . . . . . . . . . . . . 37 9.2. Avoiding Lost Updates . . . . . . . . . . . . . . . . . . 35
9.3. Client Configuration . . . . . . . . . . . . . . . . . . . 37 9.3. Client Configuration . . . . . . . . . . . . . . . . . . . 35
9.4. Finding Other Users' Address Books . . . . . . . . . . . . 37 9.4. Finding Other Users' Address Books . . . . . . . . . . . . 35
10. XML Element Definitions . . . . . . . . . . . . . . . . . . . 38 10. XML Element Definitions . . . . . . . . . . . . . . . . . . . 36
10.1. CARDDAV:addressbook XML Element . . . . . . . . . . . . . 38 10.1. CARDDAV:addressbook XML Element . . . . . . . . . . . . . 36
10.2. CARDDAV:supported-collation XML Element . . . . . . . . . 38 10.2. CARDDAV:supported-collation XML Element . . . . . . . . . 36
10.3. CARDDAV:addressbook-query XML Element . . . . . . . . . . 39 10.3. CARDDAV:addressbook-query XML Element . . . . . . . . . . 37
10.4. CARDDAV:address-data XML Element . . . . . . . . . . . . . 39 10.4. CARDDAV:address-data XML Element . . . . . . . . . . . . . 37
10.4.1. CARDDAV:allprop XML Element . . . . . . . . . . . . . 41 10.4.1. CARDDAV:allprop XML Element . . . . . . . . . . . . . 39
10.4.2. CARDDAV:prop XML Element . . . . . . . . . . . . . . . 41 10.4.2. CARDDAV:prop XML Element . . . . . . . . . . . . . . . 39
10.5. CARDDAV:filter XML Element . . . . . . . . . . . . . . . . 42 10.5. CARDDAV:filter XML Element . . . . . . . . . . . . . . . . 40
10.5.1. CARDDAV:prop-filter XML Element . . . . . . . . . . . 43 10.5.1. CARDDAV:prop-filter XML Element . . . . . . . . . . . 40
10.5.2. CARDDAV:param-filter XML Element . . . . . . . . . . . 44 10.5.2. CARDDAV:param-filter XML Element . . . . . . . . . . . 41
10.5.3. CARDDAV:is-not-defined XML Element . . . . . . . . . . 45 10.5.3. CARDDAV:is-not-defined XML Element . . . . . . . . . . 42
10.5.4. CARDDAV:text-match XML Element . . . . . . . . . . . . 45 10.5.4. CARDDAV:text-match XML Element . . . . . . . . . . . . 42
10.6. CARDDAV:limit XML Element . . . . . . . . . . . . . . . . 46 10.6. CARDDAV:limit XML Element . . . . . . . . . . . . . . . . 43
10.6.1. CARDDAV:nresults XML Element . . . . . . . . . . . . . 46 10.6.1. CARDDAV:nresults XML Element . . . . . . . . . . . . . 44
10.7. CARDDAV:addressbook-multiget XML Element . . . . . . . . . 47 10.7. CARDDAV:addressbook-multiget XML Element . . . . . . . . . 44
11. Service Discovery via SRV Records . . . . . . . . . . . . . . 47 11. Service Discovery via SRV Records . . . . . . . . . . . . . . 45
12. Internationalization Considerations . . . . . . . . . . . . . 48 12. Internationalization Considerations . . . . . . . . . . . . . 45
13. Security Considerations . . . . . . . . . . . . . . . . . . . 48 13. Security Considerations . . . . . . . . . . . . . . . . . . . 45
14. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 49 14. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 46
14.1. Namespace Registration . . . . . . . . . . . . . . . . . . 49 14.1. Namespace Registration . . . . . . . . . . . . . . . . . . 46
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47
16.1. Normative References . . . . . . . . . . . . . . . . . . . 49 16.1. Normative References . . . . . . . . . . . . . . . . . . . 47
16.2. Informative References . . . . . . . . . . . . . . . . . . 51 16.2. Informative References . . . . . . . . . . . . . . . . . . 48
Appendix A. Change History (to be removed prior to
publication as an RFC) . . . . . . . . . . . . . . . 51
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 56
1. Introduction and Overview 1. Introduction and Overview
Address books containing contact information are a key component of Address books containing contact information are a key component of
personal information management tools, such as email, calendaring and personal information management tools, such as email, calendaring and
scheduling, and instant messaging clients. To date several protocols scheduling, and instant messaging clients. To date several protocols
have been used for remote access to contact data, including have been used for remote access to contact data, including the
Lightweight Directory Access Protocol (LDAP) [RFC4510], Internet Lightweight Directory Access Protocol (LDAP) [RFC4510], Internet
Message Support Protocol (IMSP) [IMSP] and Application Configuration Message Support Protocol [IMSP], and Application Configuration Access
Access Protocol (ACAP) [RFC2244], together with SyncML used for Protocol (ACAP) [RFC2244], together with SyncML used for
synchronization of such data. synchronization of such data.
WebDAV [RFC4918] offers a number of advantages as a framework or WebDAV [RFC4918] offers a number of advantages as a framework or
basis for address book access and management. Most of these basis for address book access and management. Most of these
advantages boil down to a significant reduction in design costs, advantages boil down to a significant reduction in the costs of
implementation costs, interoperability test costs and deployment design, implementation, interoperability testing, and deployment.
costs.
The key features of address book support with WebDAV are: The key features of address book support with WebDAV are:
1. Ability to use multiple address books with hierarchical layout. 1. Ability to use multiple address books with hierarchical layout.
2. Ability to control access to individual address books and address 2. Ability to control access to individual address books and address
entries as per WebDAV ACL [RFC3744]. entries as per WebDAV Access Control List (ACL) [RFC3744].
3. Principal collections can be used to enumerate and query other 3. Principal collections can be used to enumerate and query other
users on the system as per WebDAV ACL [RFC3744]. users on the system as per WebDAV ACL [RFC3744].
4. Server-side searching of address data, avoiding the need for 4. Server-side searching of address data, avoiding the need for
clients to download an entire address book in order to do a quick clients to download an entire address book in order to do a quick
address 'expansion' operation. address 'expansion' operation.
5. Well-defined internationalization support through WebDAV's use of 5. Well-defined internationalization support through WebDAV's use of
XML. XML.
6. Use of vCards [RFC2426] for well defined address schema to 6. Use of vCards [RFC2426] for well-defined address schema to
enhance client interoperability. enhance client interoperability.
7. Many limited clients (e.g. mobile devices) contain an HTTP stack 7. Many limited clients (e.g., mobile devices) contain an HTTP stack
which makes implementing WebDAV much easier than other protocols. that makes implementing WebDAV much easier than other protocols.
The key disadvantages of address book support in WebDAV are: The key disadvantage of address book support in WebDAV is:
1. Lack of change notification. Many of the alternative protocols 1. Lack of change notification. Many of the alternative protocols
also lack this ability. However, an extension for push also lack this ability. However, an extension for push
notifications could easily be developed. notifications could easily be developed.
vCard is a MIME directory profile aimed at encapsulating personal vCard is a MIME directory profile aimed at encapsulating personal
addressing and contact information about people. The specification addressing and contact information about people. The specification
of vCard was originally done by the Versit consortium, with a of vCard was originally done by the Versit consortium, with a
subsequent 3.0 version standardized by the IETF [RFC2426]. vCard is subsequent 3.0 version standardized by the IETF [RFC2426]. vCard is
in wide spread use in email clients and mobile devices as a means of in widespread use in email clients and mobile devices as a means of
encapsulating address information for transport via email, or for encapsulating address information for transport via email or for
import/export and synchronization operations. import/export and synchronization operations.
An update to vCard - vCard v4 - is currently being developed An update to vCard -- vCard v4 -- is currently being developed
[I-D.ietf-vcarddav-vcardrev]and is compatible with this [RFC6350] and is compatible with this specification.
specification.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The term "protected" is used in the Conformance field of property The term "protected" is used in the Conformance field of property
definitions as defined in Section 15 of [RFC4918]. definitions as defined in Section 15 of [RFC4918].
This document uses XML DTD fragments ([W3C.REC-xml-20081126], Section This document uses XML DTD fragments ([W3C.REC-xml-20081126], Section
3.2) as a purely notational convention. WebDAV request and response 3.2) as a purely notational convention. WebDAV request and response
bodies cannot be validated by a DTD due to the specific extensibility bodies cannot be validated by a DTD due to the specific extensibility
rules defined in Section 17 of [RFC4918] and due to the fact that all rules defined in Section 17 of [RFC4918] and due to the fact that all
XML elements defined by this specification use the XML namespace name XML elements defined by that specification use the XML namespace name
"DAV:". In particular: "DAV:". In particular:
1. element names use the "DAV:" namespace, 1. Element names use the "DAV:" namespace.
2. element ordering is irrelevant unless explicitly stated, 2. Element ordering is irrelevant unless explicitly stated.
3. extension elements (elements not already defined as valid child 3. Extension elements (elements not already defined as valid child
elements) may be added anywhere, except when explicitly stated elements) may be added anywhere, except when explicitly stated
otherwise, otherwise.
4. extension attributes (attributes not already defined as valid for 4. Extension attributes (attributes not already defined as valid for
this element) may be added anywhere, except when explicitly this element) may be added anywhere, except when explicitly
stated otherwise. stated otherwise.
The namespace "urn:ietf:params:xml:ns:carddav" is reserved for the The namespace "urn:ietf:params:xml:ns:carddav" is reserved for the
XML elements defined in this specification, its revisions, and XML elements defined in this specification, its revisions, and
related CardDAV specifications. XML elements defined by individual related CardDAV specifications. XML elements defined by individual
implementations MUST NOT use the "urn:ietf:params:xml:ns:carddav" implementations MUST NOT use the "urn:ietf:params:xml:ns:carddav"
namespace, and instead should use a namespace that they control. namespace, and instead should use a namespace that they control.
When XML element types in the namespaces "DAV:" and When XML element types in the namespaces "DAV:" and
"urn:ietf:params:xml:ns:carddav" are referenced in this document "urn:ietf:params:xml:ns:carddav" are referenced in this document
outside of the context of an XML fragment, the strings "DAV:" and outside of the context of an XML fragment, the strings "DAV:" and
"CARDDAV:" will be prefixed to the element types, respectively. "CARDDAV:" will be prefixed to the element types, respectively.
This document inherits, and sometimes extends, DTD productions from This document inherits, and sometimes extends, DTD productions from
Section 14 of [RFC4918]. Section 14 of [RFC4918].
Also note that some CardDAV XML element names are identical to WebDAV Also, note that some CardDAV XML element names are identical to
XML element names, though their namespace differs. Care must be WebDAV XML element names, though their namespace differs. Care must
taken not to confuse the two sets of names. be taken not to confuse the two sets of names.
3. Requirements Overview 3. Requirements Overview
This section lists what functionality is required of a CardDAV This section lists what functionality is required of a CardDAV
server. To advertise support for CardDAV, a server: server. To advertise support for CardDAV, a server:
o MUST support vCard v3 [RFC2426] as a media type for the address o MUST support vCard v3 [RFC2426] as a media type for the address
object resource format; object resource format;
o MUST support WebDAV Class 3 [RFC4918]; o MUST support WebDAV Class 3 [RFC4918];
o MUST support WebDAV ACL [RFC3744]; o MUST support WebDAV ACL [RFC3744];
o MUST support secure transport as defined in [RFC2818] using TLS o MUST support secure transport as defined in [RFC2818] using
[RFC5246] and using the certificate validation procedures Transport Layer Security (TLS) [RFC5246] and using the certificate
described in [RFC5280]; validation procedures described in [RFC5280];
o MUST support ETags [RFC2616] with additional requirements o MUST support ETags [RFC2616] with additional requirements
specified in Section 6.3.2.3 of this document; specified in Section 6.3.2.3 of this document;
o MUST support all address book reports defined in Section 8 of this o MUST support all address book reports defined in Section 8 of this
document; and document; and
o MUST advertise support on all address book collections and address o MUST advertise support on all address book collections and address
object resources for the address book reports in the DAV: object resources for the address book reports in the
supported-report-set property, as defined in Versioning Extensions DAV:supported-report-set property, as defined in Versioning
to WebDAV [RFC3253]. Extensions to WebDAV [RFC3253].
In addition, a server: In addition, a server:
o SHOULD support vCard v4 [I-D.ietf-vcarddav-vcardrev] as a media o SHOULD support vCard v4 [RFC6350] as a media type for the address
type for the address object resource format; object resource format;
o SHOULD support the extended MKCOL method [RFC5689] to create o SHOULD support the extended MKCOL method [RFC5689] to create
address book collections as defined in Section 6.3.1 of this address book collections as defined in Section 6.3.1 of this
document. document.
o SHOULD support the DAV:current-user-principal-URL property as o SHOULD support the DAV:current-user-principal-URL property as
defined in [RFC5397] to give clients a fast way to locate user defined in [RFC5397] to give clients a fast way to locate user
principals. principals.
4. Address Book Data Model 4. Address Book Data Model
As a brief overview, a CardDAV address book is modeled as a WebDAV As a brief overview, a CardDAV address book is modeled as a WebDAV
collection with a well defined structure; each of these address book collection with a well-defined structure; each of these address book
collections contain a number of resources representing address collections contains a number of resources representing address
objects as their direct child resources. Each resource representing objects as their direct child resources. Each resource representing
an address object is called an "address object resource". Each an address object is called an "address object resource". Each
address object resource and each address book collection can be address object resource and each address book collection can be
individually locked and have individual WebDAV properties. individually locked and have individual WebDAV properties.
Requirements derived from this model are provided in Section 5.1 and Requirements derived from this model are provided in Sections 5.1 and
Section 5.2. 5.2.
4.1. Address Book Server 4.1. Address Book Server
A CardDAV server is an address-aware engine combined with a WebDAV A CardDAV server is an address-aware engine combined with a WebDAV
server. The server may include address data in some parts of its URL server. The server may include address data in some parts of its URL
namespace, and non-address data in other parts. namespace and non-address data in other parts.
A WebDAV server can advertise itself as a CardDAV server if it A WebDAV server can advertise itself as a CardDAV server if it
supports the functionality defined in this specification at any point supports the functionality defined in this specification at any point
within the root of its repository. That might mean that address data within the root of its repository. That might mean that address data
is spread throughout the repository and mixed with non-address data is spread throughout the repository and mixed with non-address data
in nearby collections (e.g. address data may be found in /lisa/ in nearby collections (e.g., address data may be found in /lisa/
addressbook/ as well as in /bernard/addressbook/, and non-address addressbook/ as well as in /bernard/addressbook/, and non-address
data in /lisa/calendars/). Or, it might mean that address data can data in /lisa/calendars/). Or, it might mean that address data can
be found only in certain sections of the repository (e.g. be found only in certain sections of the repository (e.g.,
/addressbooks/user/). Address book features are only required in the /addressbooks/user/). Address book features are only required in the
repository sections that are or contain address objects. So a repository sections that are or contain address objects. So, a
repository confining address data to the /carddav/ collection would repository confining address data to the /carddav/ collection would
only need to support the CardDAV required features within that only need to support the CardDAV required features within that
collection. collection.
The CardDAV server is the canonical location for address data and The CardDAV server is the canonical location for address data and
state information. Clients may submit requests to change data or state information. Clients may submit requests to change data or
download data. Clients may store address objects offline and attempt download data. Clients may store address objects offline and attempt
to synchronize at a later time. Address data on the server can to synchronize at a later time. Address data on the server can
change between the time of last synchronization and when attempting change between the time of last synchronization and when attempting
an update, as address book collections may be shared and accessible an update, as address book collections may be shared and accessible
skipping to change at page 8, line 4 skipping to change at page 7, line 46
The CardDAV server is the canonical location for address data and The CardDAV server is the canonical location for address data and
state information. Clients may submit requests to change data or state information. Clients may submit requests to change data or
download data. Clients may store address objects offline and attempt download data. Clients may store address objects offline and attempt
to synchronize at a later time. Address data on the server can to synchronize at a later time. Address data on the server can
change between the time of last synchronization and when attempting change between the time of last synchronization and when attempting
an update, as address book collections may be shared and accessible an update, as address book collections may be shared and accessible
via multiple clients. Entity tags and locking help this work. via multiple clients. Entity tags and locking help this work.
5. Address Book Resources 5. Address Book Resources
5.1. Address Object Resources 5.1. Address Object Resources
This specification uses vCard as the default format for address or This specification uses vCard as the default format for address or
contact information being stored on the server. However, this contact information being stored on the server. However, this
specification does allow other formats for address data provided that specification does allow other formats for address data provided that
the server advertises support for those additional formats as the server advertises support for those additional formats as
described below. The requirements in this section pertain to vCard described below. The requirements in this section pertain to vCard
address data, or formats that follow the semantics of vCard data. address data or formats that follow the semantics of vCard data.
Address object resources contained in address book collections MUST Address object resources contained in address book collections MUST
contain a single vCard component only. contain a single vCard component only.
vCard components in an address book collection MUST have a UID vCard components in an address book collection MUST have a UID
property value that MUST be unique in the scope of the address book property value that MUST be unique in the scope of the address book
collection in which it is contained. collection in which it is contained.
5.1.1. Data Type Conversion 5.1.1. Data Type Conversion
Servers might support more than one primary media type for address Servers might support more than one primary media type for address
object resources, for example vCard v3.0 and vCard v4.0. In such object resources, for example, vCard v3.0 and vCard v4.0. In such
cases servers have to accept all media types that they advertise via cases, servers have to accept all media types that they advertise via
the CARDDAV:supported-address-data WebDAV property (see the CARDDAV:supported-address-data WebDAV property (see
Section 6.2.2). Section 6.2.2).
However, clients can use standard HTTP content negotiation behavior However, clients can use standard HTTP content negotiation behavior
(the Accept request header defined in Section 14.1 of [RFC2616]) to (the Accept request header defined in Section 14.1 of [RFC2616]) to
request that an address object resource's data be returned in a request that an address object resource's data be returned in a
specific media type format. For example, a client only capable of specific media type format. For example, a client merely capable of
handling vCard v3.0 would only want to have address object resources handling vCard v3.0 would only want to have address object resources
returned in v3.0 format. returned in v3.0 format.
Additionally, REPORT requests, defined later in this specification, Additionally, REPORT requests, defined later in this specification,
allow for the return of address object resource data within an XML allow for the return of address object resource data within an XML
response body. Again, the client can use content negotiation to response body. Again, the client can use content negotiation to
request that data be returned in a specific media type by specifying request that data be returned in a specific media type by specifying
appropriate attributes on the CARDDAV:address-data XML element used appropriate attributes on the CARDDAV:address-data XML element used
in the request body (see Section 10.4). in the request body (see Section 10.4).
In some cases it might not be possible for a server to convert from In some cases, it might not be possible for a server to convert from
one media type to another. When that happens, the server MUST return one media type to another. When that happens, the server MUST return
the CARDDAV:supported-address-data-conversion precondition (see the CARDDAV:supported-address-data-conversion precondition (see
below) in the response body (when the failure to convert applies to below) in the response body (when the failure to convert applies to
the entire response) or use that same precondition code in the DAV: the entire response) or use that same precondition code in the
response XML element in the response for the targeted address object DAV:response XML element in the response for the targeted address
resource when one of the REPORTs defined below is used. See object resource when one of the REPORTs defined below is used. See
Section 8.7.2 for an example of this. Section 8.7.2 for an example of this.
5.1.1.1. Additional Precondition for GET 5.1.1.1. Additional Precondition for GET
This specification creates additional preconditions for the GET This specification creates additional preconditions for the GET
method. method.
The new precondition is: The new precondition is:
(CARDDAV:supported-address-data-conversion): The resource targeted (CARDDAV:supported-address-data-conversion): The resource targeted
by the GET request can be converted to the media type specified in by the GET request can be converted to the media type specified in
the Accept request header included with the request; the Accept request header included with the request.
5.2. Address Book Collections 5.2. Address Book Collections
Address book collections appear to clients as a WebDAV collection Address book collections appear to clients as a WebDAV collection
resource, identified by a URL. An address book collection MUST resource, identified by a URL. An address book collection MUST
report the DAV:collection and CARDDAV:addressbook XML elements in the report the DAV:collection and CARDDAV:addressbook XML elements in the
value of the DAV:resourcetype property. The element type declaration value of the DAV:resourcetype property. The element type declaration
for CARDDAV:addressbook is: for CARDDAV:addressbook is:
<!ELEMENT addressbook EMPTY> <!ELEMENT addressbook EMPTY>
An address book collection can be created through provisioning (e.g., An address book collection can be created through provisioning (e.g.,
automatically created when a user's account is provisioned), or it automatically created when a user's account is provisioned), or it
can be created with the extended MKCOL method (see Section 6.3.1). can be created with the extended MKCOL method (see Section 6.3.1).
This can be used by a user to create additional address books (e.g., This can be used by a user to create additional address books (e.g.,
"soccer team members") or for users to share an address book (e.g., "soccer team members") or for users to share an address book (e.g.,
"sales team contacts"). Note however that this document doesn't "sales team contacts"). However, note that this document doesn't
define what extra address book collections are for. Users must rely define what extra address book collections are for. Users must rely
on non-standard cues to find out what an address book collection is on non-standard cues to find out what an address book collection is
for, or use the CARDDAV:addressbook-description property defined in for, or use the CARDDAV:addressbook-description property defined in
Section 6.2.1 to provide such a cue. Section 6.2.1 to provide such a cue.
The following restrictions are applied to the resources within an The following restrictions are applied to the resources within an
address book collection: address book collection:
a. Address book collections MUST only contain address object a. Address book collections MUST only contain address object
resources and collections that are not address book collections. resources and collections that are not address book collections.
i.e., the only "top-level" non-collection resources allowed in an That is, the only "top-level" non-collection resources allowed in
address book collection are address object resources. This an address book collection are address object resources. This
ensures that address book clients do not have to deal with non- ensures that address book clients do not have to deal with non-
address data in an address book collection, though they do have address data in an address book collection, though they do have
to distinguish between address object resources and collections to distinguish between address object resources and collections
when using standard WebDAV techniques to examine the contents of when using standard WebDAV techniques to examine the contents of
a collection. a collection.
b. Collections contained in address book collections MUST NOT b. Collections contained in address book collections MUST NOT
contain address book collections at any depth. i.e., "nesting" of contain address book collections at any depth. That is,
address book collections within other address book collections at "nesting" of address book collections within other address book
any depth is not allowed. This specification does not define how collections at any depth is not allowed. This specification does
collections contained in an address book collection are used or not define how collections contained in an address book
how they relate to any address object resources contained in the collection are used or how they relate to any address object
address book collection. resources contained in the address book collection.
Multiple address book collections MAY be children of the same Multiple address book collections MAY be children of the same
collection. collection.
6. Address Book Feature 6. Address Book Feature
6.1. Address Book Support 6.1. Address Book Support
A server supporting the features described in this document, MUST A server supporting the features described in this document MUST
include "addressbook" as a field in the DAV response header from an include "addressbook" as a field in the DAV response header from an
OPTIONS request on any resource that supports any address book OPTIONS request on any resource that supports any address book
properties, reports, or methods. A value of "addressbook" in the DAV properties, reports, or methods. A value of "addressbook" in the DAV
response header MUST indicate that the server supports all MUST level response header MUST indicate that the server supports all MUST level
requirements and REQUIRED features specified in this document. requirements and REQUIRED features specified in this document.
6.1.1. Example: Using OPTIONS for the Discovery of Support for CardDAV 6.1.1. Example: Using OPTIONS for the Discovery of Support for CardDAV
>> Request << >> Request <<
skipping to change at page 10, line 41 skipping to change at page 10, line 37
HTTP/1.1 200 OK HTTP/1.1 200 OK
Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE
Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, REPORT, ACL Allow: MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, REPORT, ACL
DAV: 1, 2, 3, access-control, addressbook DAV: 1, 2, 3, access-control, addressbook
DAV: extended-mkcol DAV: extended-mkcol
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
Content-Length: 0 Content-Length: 0
In this example, the OPTIONS response indicates that the server In this example, the OPTIONS response indicates that the server
supports CardDAV in this namespace, therefore the '/addressbooks/ supports CardDAV in this namespace; therefore, the '/addressbooks/
users/' collection may be used as a parent for address book users/' collection may be used as a parent for address book
collections as the extended MKCOL method is available, and as a collections as the extended MKCOL method is available and as a
possible target for REPORT requests for address book reports. possible target for REPORT requests for address book reports.
6.2. Address Book Properties 6.2. Address Book Properties
6.2.1. CARDDAV:addressbook-description Property 6.2.1. CARDDAV:addressbook-description Property
Name: addressbook-description Name: addressbook-description
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Provides a human-readable description of the address book Purpose: Provides a human-readable description of the address book
collection. collection.
Value: Any text. Value: Any text.
skipping to change at page 12, line 20 skipping to change at page 12, line 7
allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop
request. request.
Description: The CARDDAV:supported-address-data property is used to Description: The CARDDAV:supported-address-data property is used to
specify the media type supported for the address object resources specify the media type supported for the address object resources
contained in a given address book collection (e.g., vCard version contained in a given address book collection (e.g., vCard version
3.0). Any attempt by the client to store address object resources 3.0). Any attempt by the client to store address object resources
with a media type not listed in this property MUST result in an with a media type not listed in this property MUST result in an
error, with the CARDDAV:supported-address-data precondition error, with the CARDDAV:supported-address-data precondition
(Section 6.3.2.1) being violated. In the absence of this property (Section 6.3.2.1) being violated. In the absence of this
the server MUST only accept data with the media type "text/vcard" property, the server MUST only accept data with the media type
and vCard version 3.0, and clients can assume that. "text/vcard" and vCard version 3.0, and clients can assume that is
all the server will accept.
Definition: Definition:
<!ELEMENT supported-address-data (address-data-type+)> <!ELEMENT supported-address-data (address-data-type+)>
<!ELEMENT address-data-type EMPTY> <!ELEMENT address-data-type EMPTY>
<!ATTLIST address-data-type content-type CDATA "text/vcard" <!ATTLIST address-data-type content-type CDATA "text/vcard"
version CDATA "3.0"> version CDATA "3.0">
<!-- content-type value: a MIME media type --> <!-- content-type value: a MIME media type -->
<!-- version value: a version string --> <!-- version value: a version string -->
skipping to change at page 13, line 22 skipping to change at page 13, line 11
allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop
request. request.
Description: The CARDDAV:max-resource-size is used to specify a Description: The CARDDAV:max-resource-size is used to specify a
numeric value that represents the maximum size in octets that the numeric value that represents the maximum size in octets that the
server is willing to accept when an address object resource is server is willing to accept when an address object resource is
stored in an address book collection. Any attempt to store an stored in an address book collection. Any attempt to store an
address book object resource exceeding this size MUST result in an address book object resource exceeding this size MUST result in an
error, with the CARDDAV:max-resource-size precondition error, with the CARDDAV:max-resource-size precondition
(Section 6.3.2.1) being violated. In the absence of this property (Section 6.3.2.1) being violated. In the absence of this
the client can assume that the server will allow storing a property, the client can assume that the server will allow storing
resource of any reasonable size. a resource of any reasonable size.
Definition: Definition:
<!ELEMENT max-resource-size (#PCDATA)> <!ELEMENT max-resource-size (#PCDATA)>
<!-- PCDATA value: a numeric value (positive decimal integer) --> <!-- PCDATA value: a numeric value (positive decimal integer) -->
Example: Example:
<C:max-resource-size xmlns:C="urn:ietf:params:xml:ns:carddav" <C:max-resource-size xmlns:C="urn:ietf:params:xml:ns:carddav"
>102400</C:max-resource-size> >102400</C:max-resource-size>
6.3. Creating Resources 6.3. Creating Resources
Address book collections and address object resources may be created Address book collections and address object resources may be created
by either a CardDAV client or by the CardDAV server. This by either a CardDAV client or the CardDAV server. This specification
specification defines restrictions and a data model that both clients defines restrictions and a data model that both clients and servers
and servers MUST adhere to when manipulating such address data. MUST adhere to when manipulating such address data.
6.3.1. Extended MKCOL Method 6.3.1. Extended MKCOL Method
An HTTP request using the extended MKCOL method [RFC5689] can be used An HTTP request using the extended MKCOL method [RFC5689] can be used
to create a new address book collection resource. A server MAY to create a new address book collection resource. A server MAY
restrict address book collection creation to particular collections. restrict address book collection creation to particular collections.
To create an address book, the client sends an extended MKCOL request To create an address book, the client sends an extended MKCOL request
to the server and in the body of the request sets the DAV: to the server and in the body of the request sets the
resourcetype property to the resource type for an address book DAV:resourcetype property to the resource type for an address book
collection as defined in Section 5.2. collection as defined in Section 5.2.
Support for creating address books on the server is only RECOMMENDED Support for creating address books on the server is only RECOMMENDED
and not REQUIRED because some address book stores only support one and not REQUIRED because some address book stores only support one
address book per user (or principal), and those are typically pre- address book per user (or principal), and those are typically pre-
created for each account. However, servers and clients are strongly created for each account. However, servers and clients are strongly
encouraged to support address book creation whenever possible to encouraged to support address book creation whenever possible to
allow users to create multiple address book collections to help allow users to create multiple address book collections to help
organize their data better. organize their data better.
The DAV:displayname property can be used for a human-readable name of The DAV:displayname property can be used for a human-readable name of
the address book. Clients can either specify the value of the DAV: the address book. Clients can either specify the value of the
displayname property in the request body of the extended MKCOL DAV:displayname property in the request body of the extended MKCOL
request, or alternatively issue a PROPPATCH request to change the request or, alternatively, issue a PROPPATCH request to change the
DAV:displayname property to the appropriate value immediately after DAV:displayname property to the appropriate value immediately after
using the extended MKCOL request. When displaying address book using the extended MKCOL request. When displaying address book
collections to users, clients SHOULD check the DAV:displayname collections to users, clients SHOULD check the DAV:displayname
property and use that value as the name of the address book. In the property and use that value as the name of the address book. In the
event that the DAV:displayname property is not set, the client MAY event that the DAV:displayname property is not set, the client MAY
use the last part of the address book collection URI as the name, use the last part of the address book collection URI as the name;
however that path segment may be "opaque" and not represent any however, that path segment may be "opaque" and not represent any
meaningful human-readable text. meaningful human-readable text.
6.3.1.1. Example - Successful MKCOL request 6.3.1.1. Example - Successful MKCOL Request
This example creates an address book collection called /home/lisa/ This example creates an address book collection called /home/lisa/
addressbook/ on the server addressbook.example.com with specific addressbook/ on the server addressbook.example.com with specific
values for the properties DAV:resourcetype, DAV:displayname and values for the properties DAV:resourcetype, DAV:displayname, and
CARDDAV:addressbook-description. CARDDAV:addressbook-description.
>> Request << >> Request <<
MKCOL /home/lisa/addressbook/ HTTP/1.1 MKCOL /home/lisa/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
skipping to change at page 16, line 9 skipping to change at page 15, line 29
<C:addressbook-description/> <C:addressbook-description/>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:mkcol-response> </D:mkcol-response>
6.3.2. Creating Address Object Resources 6.3.2. Creating Address Object Resources
Clients populate address book collections with address object Clients populate address book collections with address object
resources. The URL for each address object resource is entirely resources. The URL for each address object resource is entirely
arbitrary, and does not need to bear a specific relationship (but arbitrary and does not need to bear a specific relationship (but
might) to the address object resource's vCard properties or other might) to the address object resource's vCard properties or other
metadata. New address object resources MUST be created with a PUT metadata. New address object resources MUST be created with a PUT
request targeted at an unmapped URI. A PUT request targeted at a request targeted at an unmapped URI. A PUT request targeted at a
mapped URI updates an existing address object resource. mapped URI updates an existing address object resource.
When servers create new resources, it's not hard for the server to When servers create new resources, it's not hard for the server to
choose a unique URL. It's slightly tougher for clients, because a choose a unique URL. It's slightly tougher for clients, because a
client might not want to examine all resources in the collection, and client might not want to examine all resources in the collection and
might not want to lock the entire collection to ensure that a new one might not want to lock the entire collection to ensure that a new one
isn't created with a name collision. However, there is an HTTP isn't created with a name collision. However, there is an HTTP
feature to mitigate this. If the client intends to create a new feature to mitigate this. If the client intends to create a new
address resource the client SHOULD use the HTTP header "If-None- address resource, the client SHOULD use the HTTP header "If-None-
Match: *" on the PUT request. The Request-URI on the PUT request Match: *" on the PUT request. The Request-URI on the PUT request
MUST include the target collection, where the resource is to be MUST include the target collection, where the resource is to be
created, plus the name of the resource in the last path segment. The created, plus the name of the resource in the last path segment. The
"If-None-Match" header ensures that the client will not inadvertently "If-None-Match" header ensures that the client will not inadvertently
overwrite an existing resource even, if the last path segment turned overwrite an existing resource even if the last path segment turned
out to already be used. out to already be used.
>> Request << >> Request <<
PUT /lisa/addressbook/newvcard.vcf HTTP/1.1 PUT /lisa/addressbook/newvcard.vcf HTTP/1.1
If-None-Match: * If-None-Match: *
Host: addressbook.example.com Host: addressbook.example.com
Content-Type: text/vcard Content-Type: text/vcard
Content-Length: xxx Content-Length: xxx
skipping to change at page 17, line 4 skipping to change at page 16, line 27
ADR;TYPE=POSTAL:;2822 Email HQ;Suite 2821;RFCVille;PA;15213;USA ADR;TYPE=POSTAL:;2822 Email HQ;Suite 2821;RFCVille;PA;15213;USA
EMAIL;TYPE=INTERNET,PREF:cyrus@example.com EMAIL;TYPE=INTERNET,PREF:cyrus@example.com
NICKNAME:me NICKNAME:me
NOTE:Example VCard. NOTE:Example VCard.
ORG:Self Employed ORG:Self Employed
TEL;TYPE=WORK,VOICE:412 605 0499 TEL;TYPE=WORK,VOICE:412 605 0499
TEL;TYPE=FAX:412 605 0705 TEL;TYPE=FAX:412 605 0705
URL:http://www.example.com URL:http://www.example.com
UID:1234-5678-9000-1 UID:1234-5678-9000-1
END:VCARD END:VCARD
>> Response << >> Response <<
HTTP/1.1 201 Created HTTP/1.1 201 Created
Date: Thu, 02 Sep 2004 16:53:32 GMT Date: Thu, 02 Sep 2004 16:53:32 GMT
Content-Length: 0 Content-Length: 0
ETag: "123456789-000-111" ETag: "123456789-000-111"
The request to change an existing address object resource without The request to change an existing address object resource without
overwriting a change made on the server, uses a specific ETag in an overwriting a change made on the server uses a specific ETag in an
"If-Match" header, rather than the "If-None-Match" header. "If-Match" header, rather than the "If-None-Match" header.
File names for vCards are commonly suffixed by ".vcf", and clients File names for vCards are commonly suffixed by ".vcf", and clients
may choose to use the same convention for URLs. may choose to use the same convention for URLs.
6.3.2.1. Additional Preconditions for PUT, COPY and MOVE 6.3.2.1. Additional Preconditions for PUT, COPY, and MOVE
This specification creates additional Preconditions for PUT, COPY and This specification creates additional preconditions for the PUT,
MOVE methods. These preconditions apply: COPY, and MOVE methods. These preconditions apply:
o When a PUT operation of an address object resource into an address o When a PUT operation of an address object resource into an address
book collection occurs. book collection occurs.
o When a COPY or MOVE operation of an address object resource into o When a COPY or MOVE operation of an address object resource into
an address book collection occurs. an address book collection occurs.
The new preconditions are: The new preconditions are:
(CARDDAV:supported-address-data): The resource submitted in the (CARDDAV:supported-address-data): The resource submitted in the
PUT request, or targeted by a COPY or MOVE request MUST be a PUT request, or targeted by a COPY or MOVE request, MUST be a
supported media type (i.e., vCard) for address object resources; supported media type (i.e., vCard) for address object resources.
(CARDDAV:valid-address-data): The resource submitted in the PUT (CARDDAV:valid-address-data): The resource submitted in the PUT
request, or targeted by a COPY or MOVE request MUST be valid data request, or targeted by a COPY or MOVE request, MUST be valid data
for the media type being specified (i.e., MUST contain valid vCard for the media type being specified (i.e., MUST contain valid vCard
data); data).
(CARDDAV:no-uid-conflict): The resource submitted in the PUT (CARDDAV:no-uid-conflict): The resource submitted in the PUT
request, or targeted by a COPY or MOVE request MUST NOT specify a request, or targeted by a COPY or MOVE request, MUST NOT specify a
vCard UID property value already in use in the targeted address vCard UID property value already in use in the targeted address
book collection or overwrite an existing address object resource book collection or overwrite an existing address object resource
with one that has a different UID property value. Servers SHOULD with one that has a different UID property value. Servers SHOULD
report the URL of the resource that is already making use of the report the URL of the resource that is already making use of the
same UID property value in the DAV:href element; same UID property value in the DAV:href element.
<!ELEMENT no-uid-conflict (DAV:href)> <!ELEMENT no-uid-conflict (DAV:href)>
(CARDDAV:addressbook-collection-location-ok): In a COPY or MOVE (CARDDAV:addressbook-collection-location-ok): In a COPY or MOVE
request, when the Request-URI is an address book collection, the request, when the Request-URI is an address book collection, the
URI targeted by the Destination HTTP Request header MUST identify URI targeted by the Destination HTTP Request header MUST identify
a location where an address book collection can be created; a location where an address book collection can be created.
(CARDDAV:max-resource-size): The resource submitted in the PUT (CARDDAV:max-resource-size): The resource submitted in the PUT
request, or targeted by a COPY or MOVE request MUST have a size in request, or targeted by a COPY or MOVE request, MUST have a size
octets less than or equal to the value of the CARDDAV:max- in octets less than or equal to the value of the
resource-size property value (Section 6.2.3) on the address book CARDDAV:max-resource-size property value (Section 6.2.3) on the
collection where the resource will be stored; address book collection where the resource will be stored.
6.3.2.2. Non-Standard vCard Properties, and Parameters 6.3.2.2. Non-Standard vCard Properties and Parameters
vCard provides a "standard mechanism for doing non-standard things". vCard provides a "standard mechanism for doing non-standard things".
This extension support allows implementers to make use of non- This extension support allows implementers to make use of non-
standard vCard properties and parameters whose names are prefixed standard vCard properties and parameters whose names are prefixed
with the text "X-". with the text "X-".
Servers MUST support the use of non-standard properties and Servers MUST support the use of non-standard properties and
parameters in address object resources stored via the PUT method. parameters in address object resources stored via the PUT method.
Servers may need to enforce rules for their own "private" properties Servers may need to enforce rules for their own "private" properties
or parameters, so servers MAY reject any attempt by the client to or parameters, so servers MAY reject any attempt by the client to
change those or use values for those outside of any restrictions the change those or use values for those outside of any restrictions the
server may have. Servers SHOULD ensure that any "private" properties server may have. A server SHOULD ensure that any "private"
or parameters it uses follow the convention of including a vendor id properties or parameters it uses follow the convention of including a
in the "X-" name, as described in Section 3.8 of [RFC2426], e.g., vendor ID in the "X-" name, as described in Section 3.8 of [RFC2426],
"X-ABC-PRIVATE". e.g., "X-ABC-PRIVATE".
6.3.2.3. Address Object Resource Entity Tag 6.3.2.3. Address Object Resource Entity Tag
The DAV:getetag property MUST be defined and set to a strong entity The DAV:getetag property MUST be defined and set to a strong entity
tag on all address object resources. tag on all address object resources.
A response to a GET request targeted at an address object resource A response to a GET request targeted at an address object resource
MUST contain an ETag response header field indicating the current MUST contain an ETag response header field indicating the current
value of the strong entity tag of the address object resource. value of the strong entity tag of the address object resource.
Servers SHOULD return a strong entity tag (ETag header) in a PUT Servers SHOULD return a strong entity tag (ETag header) in a PUT
response when the stored address object resource is equivalent by response when the stored address object resource is equivalent by
octet equality to the address object resource submitted in the body octet equality to the address object resource submitted in the body
of the PUT request. This allows clients to reliably use the returned of the PUT request. This allows clients to reliably use the returned
strong entity tag for data synchronization purposes. For instance, strong entity tag for data synchronization purposes. For instance,
the client can do a PROPFIND request on the stored address object the client can do a PROPFIND request on the stored address object
resource and have the DAV:getetag property returned, and compare that resource, have the DAV:getetag property returned, compare that value
value with the strong entity tag it received on the PUT response, and with the strong entity tag it received on the PUT response, and know
know that if they are equal, then the address object resource on the that if they are equal, then the address object resource on the
server has not been changed. server has not been changed.
In the case where the data stored by a server as a result of a PUT In the case where the data stored by a server as a result of a PUT
request is not equivalent by octet equality to the submitted address request is not equivalent by octet equality to the submitted address
object resource, the behavior of the ETag response header is not object resource, the behavior of the ETag response header is not
specified here, with the exception that a strong entity tag MUST NOT specified here, with the exception that a strong entity tag MUST NOT
be returned in the response. As a result, clients may need to be returned in the response. As a result, a client may need to
retrieve the modified address object resource (and ETag) as a basis retrieve the modified address object resource (and ETag) as a basis
for further changes, rather than use the address object resource it for further changes, rather than use the address object resource it
had sent with the PUT request. had sent with the PUT request.
7. Address Book Access Control 7. Address Book Access Control
CardDAV servers MUST support and adhere to the requirements of WebDAV CardDAV servers MUST support and adhere to the requirements of WebDAV
ACL [RFC3744]. WebDAV ACL provides a framework for an extensible set ACL [RFC3744]. WebDAV ACL provides a framework for an extensible set
of privileges that can be applied to WebDAV collections and ordinary of privileges that can be applied to WebDAV collections and ordinary
resources. resources.
skipping to change at page 19, line 49 skipping to change at page 19, line 28
COPY/MOVE behavior: This property value MUST be preserved in COPY COPY/MOVE behavior: This property value MUST be preserved in COPY
and MOVE operations. and MOVE operations.
allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop
request. request.
Description: The CARDDAV:addressbook-home-set property is meant to Description: The CARDDAV:addressbook-home-set property is meant to
allow users to easily find the address book collections owned by allow users to easily find the address book collections owned by
the principal. Typically, users will group all the address book the principal. Typically, users will group all the address book
collections that they own under a common collection. This collections that they own under a common collection. This
property specifies the URL of collections that either are address property specifies the URL of collections that are either address
book collections or ordinary collections that have child or book collections or ordinary collections that have child or
descendant address book collections owned by the principal. descendant address book collections owned by the principal.
Definition: Definition:
<!ELEMENT addressbook-home-set (DAV:href*)> <!ELEMENT addressbook-home-set (DAV:href*)>
Example: Example:
<C:addressbook-home-set xmlns:D="DAV:" <C:addressbook-home-set xmlns:D="DAV:"
skipping to change at page 21, line 11 skipping to change at page 20, line 39
xmlns:C="urn:ietf:params:xml:ns:carddav"> xmlns:C="urn:ietf:params:xml:ns:carddav">
<D:href>/system/cyrus.vcf</D:href> <D:href>/system/cyrus.vcf</D:href>
</C:principal-address> </C:principal-address>
8. Address Book Reports 8. Address Book Reports
This section defines the reports that CardDAV servers MUST support on This section defines the reports that CardDAV servers MUST support on
address book collections and address object resources. address book collections and address object resources.
CardDAV servers MUST advertise support for these reports on all CardDAV servers MUST advertise support for these reports on all
address book collections and address object resources with the DAV: address book collections and address object resources with the
supported-report-set property defined in Section 3.1.5 of [RFC3253]. DAV:supported-report-set property defined in Section 3.1.5 of
CardDAV servers MAY also advertise support for these reports on [RFC3253]. CardDAV servers MAY also advertise support for these
ordinary collections. reports on ordinary collections.
Some of these reports allow address data (from possibly multiple Some of these reports allow address data (from possibly multiple
resources) to be returned. resources) to be returned.
8.1. REPORT Method 8.1. REPORT Method
The REPORT method (defined in Section 3.6 of [RFC3253]) provides an The REPORT method (defined in Section 3.6 of [RFC3253]) provides an
extensible mechanism for obtaining information about a resource. extensible mechanism for obtaining information about a resource.
Unlike the PROPFIND method, which returns the value of one or more Unlike the PROPFIND method, which returns the value of one or more
named properties, the REPORT method can involve more complex named properties, the REPORT method can involve more complex
processing. REPORT is valuable in cases where the server has access processing. REPORT is valuable in cases where the server has access
to all of the information needed to perform the complex request (such to all of the information needed to perform the complex request (such
as a query), and where it would require multiple requests for the as a query), and where it would require multiple requests for the
client to retrieve the information needed to perform the same client to retrieve the information needed to perform the same
request. request.
A server that supports this specification MUST support the DAV: A server that supports this specification MUST support the
expand-property report (defined in Section 3.8 of [RFC3253]). DAV:expand-property report (defined in Section 3.8 of [RFC3253]).
8.2. Ordinary Collections 8.2. Ordinary Collections
Servers MAY support the reports defined in this document on ordinary Servers MAY support the reports defined in this document on ordinary
collections (collections that are not address book collections) in collections (collections that are not address book collections) in
addition to address book collections or address object resources. In addition to address book collections or address object resources. In
computing responses to the reports on ordinary collections, servers computing responses to the reports on ordinary collections, servers
MUST only consider address object resources contained in address book MUST only consider address object resources contained in address book
collections that are targeted by the REPORT based on the value of the collections that are targeted by the REPORT based on the value of the
Depth request header. Depth request header.
skipping to change at page 22, line 10 skipping to change at page 21, line 37
address data. Since vCard data is by default encoded in the UTF-8 address data. Since vCard data is by default encoded in the UTF-8
charset and may include characters outside of the US-ASCII charset charset and may include characters outside of the US-ASCII charset
range in some property and parameter values, there is a need to range in some property and parameter values, there is a need to
ensure that text matching follows well-defined rules. ensure that text matching follows well-defined rules.
To deal with this, this specification makes use of the IANA Collation To deal with this, this specification makes use of the IANA Collation
Registry defined in [RFC4790] to specify collations that may be used Registry defined in [RFC4790] to specify collations that may be used
to carry out the text comparison operations with a well-defined rule. to carry out the text comparison operations with a well-defined rule.
Collations supported by the server MUST support "equality" and Collations supported by the server MUST support "equality" and
"substring" match operations as per [RFC4790] Section 4.2, including "substring" match operations as per [RFC4790], Section 4.2, including
the "prefix" and "suffix" options for "substring" matching. CardDAV the "prefix" and "suffix" options for "substring" matching. CardDAV
uses these match options for "equals", "contains", "starts-with" and uses these match options for "equals", "contains", "starts-with", and
"ends-with" match operations. "ends-with" match operations.
CardDAV servers are REQUIRED to support the "i;ascii-casemap" CardDAV servers are REQUIRED to support the "i;ascii-casemap"
[RFC4790] and "i;unicode-casemap" [RFC5051] collations, and MAY [RFC4790] and "i;unicode-casemap" [RFC5051] collations and MAY
support other collations. support other collations.
Servers MUST advertise the set of collations that they support via Servers MUST advertise the set of collations that they support via
the CARDDAV:supported-collation-set property defined on any resource the CARDDAV:supported-collation-set property defined on any resource
that supports reports that use collations. that supports reports that use collations.
In the absence of a collation explicitly specified by the client, or In the absence of a collation explicitly specified by the client, or
if the client specifies the "default" collation identifier (as if the client specifies the "default" collation identifier (as
defined in [RFC4790] Section 3.1), the server MUST default to using defined in [RFC4790], Section 3.1), the server MUST default to using
"i;unicode-casemap" as the collation. "i;unicode-casemap" as the collation.
Wildcards (as defined in [RFC4790] Section 3.2) MUST NOT be used in Wildcards (as defined in [RFC4790], Section 3.2) MUST NOT be used in
the collation identifier. the collation identifier.
If the client chooses a collation not supported by the server, the If the client chooses a collation not supported by the server, the
server MUST respond with a CARDDAV:supported-collation precondition server MUST respond with a CARDDAV:supported-collation precondition
error response. error response.
8.3.1. CARDDAV:supported-collation-set Property 8.3.1. CARDDAV:supported-collation-set Property
Name: supported-collation-set Name: supported-collation-set
skipping to change at page 23, line 9 skipping to change at page 22, line 36
Protected: MUST be protected as it indicates support provided by the Protected: MUST be protected as it indicates support provided by the
server. server.
COPY/MOVE behavior: This property value MUST be preserved in COPY COPY/MOVE behavior: This property value MUST be preserved in COPY
and MOVE operations. and MOVE operations.
allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop allprop behavior: SHOULD NOT be returned by a PROPFIND DAV:allprop
request. request.
Description: The CARDDAV:supported-collation-set property contains Description: The CARDDAV:supported-collation-set property contains
two or more CARDDAV:supported-collation elements which specify the two or more CARDDAV:supported-collation elements that specify the
identifiers of the collations supported by the server. identifiers of the collations supported by the server.
Definition: Definition:
<!ELEMENT supported-collation-set ( <!ELEMENT supported-collation-set (
supported-collation supported-collation
supported-collation supported-collation
supported-collation*)> supported-collation*)>
<!-- Both "i;ascii-casemap" and "i;unicode-casemap" <!-- Both "i;ascii-casemap" and "i;unicode-casemap"
will be present --> will be present -->
skipping to change at page 23, line 45 skipping to change at page 23, line 27
retrieval of address object resources. A CardDAV client can specify retrieval of address object resources. A CardDAV client can specify
what information to return in the body of an address book REPORT what information to return in the body of an address book REPORT
request. request.
A CardDAV client can request particular WebDAV property values, all A CardDAV client can request particular WebDAV property values, all
WebDAV property values, or a list of the names of the resource's WebDAV property values, or a list of the names of the resource's
WebDAV properties. A CardDAV client can also request address data to WebDAV properties. A CardDAV client can also request address data to
be returned and whether all vCard properties should be returned or be returned and whether all vCard properties should be returned or
only particular ones. See CARDDAV:address-data in Section 10.4. only particular ones. See CARDDAV:address-data in Section 10.4.
8.5. Non-standard Properties and Parameters 8.5. Non-Standard Properties and Parameters
Servers MUST support the use of non-standard vCard property or Servers MUST support the use of non-standard vCard property or
parameter names in the CARDDAV:address-data XML element in address parameter names in the CARDDAV:address-data XML element in address
book REPORT requests to allow clients to request that non-standard book REPORT requests to allow clients to request that non-standard
properties and parameters be returned in the address data provided in properties and parameters be returned in the address data provided in
the response. the response.
Servers MAY support the use of non-standard vCard property or Servers MAY support the use of non-standard vCard property or
parameter names in the CARDDAV:prop-filter and CARDDAV:param-filter parameter names in the CARDDAV:prop-filter and CARDDAV:param-filter
XML elements specified in the CARDDAV:filter XML element of address XML elements specified in the CARDDAV:filter XML element of address
book REPORT requests. book REPORT requests.
Servers MUST fail with the CARDDAV:supported-filter precondition if Servers MUST fail with the CARDDAV:supported-filter precondition if
an address book REPORT request uses a CARDDAV:prop-filter or CARDDAV: an address book REPORT request uses a CARDDAV:prop-filter or
param-filter XML element that makes reference to a non-standard vCard CARDDAV:param-filter XML element that makes reference to a non-
property or parameter name which the server does not support queries standard vCard property or parameter name on which the server does
on. not support queries.
8.6. CARDDAV:addressbook-query Report 8.6. CARDDAV:addressbook-query Report
The CARDDAV:addressbook-query REPORT performs a search for all The CARDDAV:addressbook-query REPORT performs a search for all
address object resources that match a specified filter. The response address object resources that match a specified filter. The response
of this report will contain all the WebDAV properties and address of this report will contain all the WebDAV properties and address
object resource data specified in the request. In the case of the object resource data specified in the request. In the case of the
CARDDAV:address-data XML element, one can explicitly specify the CARDDAV:address-data XML element, one can explicitly specify the
vCard properties that should be returned in the address object vCard properties that should be returned in the address object
resource data that matches the filter. resource data that matches the filter.
The format of this report is modeled on the PROPFIND method. The The format of this report is modeled on the PROPFIND method. The
request and response bodies of the CARDDAV:addressbook-query report request and response bodies of the CARDDAV:addressbook-query report
use XML elements that are also used by PROPFIND. In particular the use XML elements that are also used by PROPFIND. In particular, the
request can include XML elements to request WebDAV properties to be request can include XML elements to request WebDAV properties to be
returned. When that occurs the response should follow the same returned. When that occurs, the response should follow the same
behavior as PROPFIND with respect to the DAV:multistatus response behavior as PROPFIND with respect to the DAV:multistatus response
elements used to return specific WebDAV property results. For elements used to return specific WebDAV property results. For
instance, a request to retrieve the value of a WebDAV property which instance, a request to retrieve the value of a WebDAV property that
does not exist is an error and MUST be noted with a response XML does not exist is an error and MUST be noted with a response XML
element which contains a 404 (Not Found) status value. element that contains a 404 (Not Found) status value.
Support for the CARDDAV:addressbook-query REPORT is REQUIRED. Support for the CARDDAV:addressbook-query REPORT is REQUIRED.
Marshalling: Marshalling:
The request body MUST be a CARDDAV:addressbook-query XML element The request body MUST be a CARDDAV:addressbook-query XML element
as defined in Section 10.3. as defined in Section 10.3.
The request MUST include a Depth header. The scope of the query The request MUST include a Depth header. The scope of the query
is determined by the value of the Depth header. e.g., to query all is determined by the value of the Depth header. For example, to
address object resources in an address book collection, the REPORT query all address object resources in an address book collection,
would use the address book collection as the request-URI and the REPORT would use the address book collection as the Request-
specify a Depth of 1 or infinity. URI and specify a Depth of 1 or infinity.
The response body for a successful request MUST be a DAV: The response body for a successful request MUST be a
multistatus XML element (i.e., the response uses the same format DAV:multistatus XML element (i.e., the response uses the same
as the response for PROPFIND). In the case where there are no format as the response for PROPFIND). In the case where there are
response elements, the returned DAV:multistatus XML element is no response elements, the returned DAV:multistatus XML element is
empty. empty.
The response body for a successful CARDDAV:addressbook-query The response body for a successful CARDDAV:addressbook-query
REPORT request MUST contain a DAV:response element for each REPORT request MUST contain a DAV:response element for each
address object that matched the search filter. address data is address object that matched the search filter. Address data is
returned in the CARDDAV:address-data XML element inside the DAV: returned in the CARDDAV:address-data XML element inside the
propstat XML element. DAV:propstat XML element.
Preconditions: Preconditions:
(CARDDAV:supported-address-data): The attributes "content-type" (CARDDAV:supported-address-data): The attributes "content-type"
and "version" of the CARDDAV:address-data XML element (see and "version" of the CARDDAV:address-data XML element (see
Section 10.4) specify a media type supported by the server for Section 10.4) specify a media type supported by the server for
address object resources. address object resources.
(CARDDAV:supported-filter): The CARDDAV:prop-filter (see (CARDDAV:supported-filter): The CARDDAV:prop-filter (see
Section 10.5.1) and CARDDAV:param-filter (see Section 10.5.2) XML Section 10.5.1) and CARDDAV:param-filter (see Section 10.5.2) XML
elements used in the CARDDAV:filter XML element (see Section 10.5) elements used in the CARDDAV:filter XML element (see Section 10.5)
in the REPORT request only make reference to vCard properties and in the REPORT request only make reference to vCard properties and
parameters for which queries are supported by the server. i.e., if parameters for which queries are supported by the server. That
the CARDDAV:filter element attempts to reference an unsupported is, if the CARDDAV:filter element attempts to reference an
vCard property or parameter, this precondition is violated. unsupported vCard property or parameter, this precondition is
Servers SHOULD report the CARDDAV:prop-filter or CARDDAV:param- violated. A server SHOULD report the CARDDAV:prop-filter or
filter for which it does not provide support. CARDDAV:param-filter for which it does not provide support.
<!ELEMENT supported-filter (prop-filter*, <!ELEMENT supported-filter (prop-filter*,
param-filter*)> param-filter*)>
(CARDDAV:supported-collation): Any XML attribute specifying a (CARDDAV:supported-collation): Any XML attribute specifying a
collation MUST specify a collation supported by the server as collation MUST specify a collation supported by the server as
described in Section 8.3. described in Section 8.3.
Postconditions: Postconditions:
(DAV:number-of-matches-within-limits): The number of matching (DAV:number-of-matches-within-limits): The number of matching
address object resources must fall within server-specific, address object resources must fall within server-specific,
predefined limits. For example, this condition might be triggered predefined limits. For example, this condition might be triggered
if a search specification would cause the return of an extremely if a search specification would cause the return of an extremely
large number of responses. large number of responses.
8.6.1. Limiting Results 8.6.1. Limiting Results
A client can limit the number of results returned by the server A client can limit the number of results returned by the server
through use of the CARDDAV:limit element in the request body. This through use of the CARDDAV:limit element in the request body. This
is useful when clients are only interested in a few matches, or only is useful when clients are only interested in a few matches or only
have limited space to display results to users and thus don't need have limited space to display results to users and thus don't need
the overhead of receiving more than that. When the results are the overhead of receiving more than that. When the results are
truncated by the server, the server MUST follow the rules below for truncated by the server, the server MUST follow the rules below for
indicating a result set truncation to the client. indicating a result set truncation to the client.
8.6.2. Truncation of Results 8.6.2. Truncation of Results
A server MAY limit the number of resources in a response, for A server MAY limit the number of resources in a response, for
example, to limit the amount of work expended in processing a query, example, to limit the amount of work expended in processing a query,
or as the result of an explicit limit set by the client. If the or as the result of an explicit limit set by the client. If the
result set is truncated because of such a limit, the response MUST result set is truncated because of such a limit, the response MUST
use status code 207, return a DAV:multistatus response body, and use status code 207 (Multi-Status), return a DAV:multistatus response
indicate a status of 507 (Insufficient Storage) for the request URI. body, and indicate a status of 507 (Insufficient Storage) for the
That DAV:response element SHOULD include a DAV:error element with the Request-URI. That DAV:response element SHOULD include a DAV:error
DAV:number-of-matches-within-limits precondition, as defined in element with the DAV:number-of-matches-within-limits precondition, as
[RFC3744] (Section 9.2). defined in [RFC3744], Section 9.2.
The server SHOULD also include the partial results in additional DAV: The server SHOULD also include the partial results in additional
response elements. If a client requested limit is being applied, the DAV:response elements. If a client-requested limit is being applied,
507 response for the request URI MUST NOT be included in calculating the 507 response for the Request-URI MUST NOT be included in
the limit (e.g., if the client requests that only a single result be calculating the limit (e.g., if the client requests that only a
returned, and multiple matches are present, then the DAV:multistatus single result be returned, and multiple matches are present, then the
response will include one DAV:response for the matching resource and DAV:multistatus response will include one DAV:response for the
one DAV:response for the 507 status on the request URI). matching resource and one DAV:response for the 507 status on the
Request-URI).
8.6.3. Example: Partial Retrieval of vCards Matching NICKNAME 8.6.3. Example: Partial Retrieval of vCards Matching NICKNAME
In this example, the client requests the server to search for address In this example, the client requests that the server search for
object resources that contain a NICKNAME property whose value equals address object resources that contain a NICKNAME property whose value
some specific text, and to return specific vCard properties for those equals some specific text and return specific vCard properties for
vCards found. In addition the DAV:getetag property is also requested those vCards found. In addition, the DAV:getetag property is also
and returned as part of the response. requested and returned as part of the response.
>> Request << >> Request <<
REPORT /home/bernard/addressbook/ HTTP/1.1 REPORT /home/bernard/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Depth: 1 Depth: 1
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
skipping to change at page 28, line 36 skipping to change at page 27, line 36
</C:address-data> </C:address-data>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
8.6.4. Example: Partial Retrieval of vCards Matching a Full Name or 8.6.4. Example: Partial Retrieval of vCards Matching a Full Name or
Email Address Email Address
In this example, the client requests the server to search for address In this example, the client requests that the server search for
object resources that contain a FN property whose value contains some address object resources that contain a FN property whose value
specific text or that contain an EMAIL property whose value contains contains some specific text or that contain an EMAIL property whose
other text, and to return specific vCard properties for those vCards value contains other text and return specific vCard properties for
found. In addition the DAV:getetag property is also requested and those vCards found. In addition, the DAV:getetag property is also
returned as part of the response. requested and returned as part of the response.
>> Request << >> Request <<
REPORT /home/bernard/addressbook/ HTTP/1.1 REPORT /home/bernard/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Depth: 1 Depth: 1
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<C:addressbook-query xmlns:D="DAV:" <C:addressbook-query xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:carddav"> xmlns:C="urn:ietf:params:xml:ns:carddav">
<D:prop> <D:prop>
<D:getetag/> <D:getetag/>
<C:address-data> <C:address-data>
<C:prop name="VERSION"/> <C:prop name="VERSION"/>
<C:prop name="UID"/> <C:prop name="UID"/>
<C:prop name="NICKNAME"/> <C:prop name="NICKNAME"/>
<C:prop name="EMAIL"/> <C:prop name="EMAIL"/>
skipping to change at page 31, line 7 skipping to change at page 29, line 31
END:VCARD END:VCARD
</C:address-data> </C:address-data>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
8.6.5. Example: Truncated Results 8.6.5. Example: Truncated Results
In this example, the client requests the server to search for address In this example, the client requests that the server search for
object resources that contain a FN property whose value contains some address object resources that contain a FN property whose value
specific text, and to return the DAV:getetag property for two results contains some specific text and return the DAV:getetag property for
only. The server response includes a 507 status for the request URI two results only. The server response includes a 507 status for the
indicating that there were more than two resources that matched the Request-URI indicating that there were more than two resources that
query, but that the server truncated the result set as requested by matched the query, but that the server truncated the result set as
the client. requested by the client.
>> Request << >> Request <<
REPORT /home/bernard/addressbook/ HTTP/1.1 REPORT /home/bernard/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Depth: 1 Depth: 1
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
skipping to change at page 32, line 16 skipping to change at page 30, line 32
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:" <D:multistatus xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:carddav"> xmlns:C="urn:ietf:params:xml:ns:carddav">
<D:response> <D:response>
<D:href>/home/bernard/addressbook/</D:href> <D:href>/home/bernard/addressbook/</D:href>
<D:status>HTTP/1.1 507 OK</D:status> <D:status>HTTP/1.1 507 Insufficient Storage</D:status>
<D:error><D:number-of-matches-within-limits/></D:error> <D:error><D:number-of-matches-within-limits/></D:error>
<D:responsedescription xml:lang="en"> <D:responsedescription xml:lang="en">
Only two matching records were returned Only two matching records were returned
</D:responsedescription> </D:responsedescription>
</D:response> </D:response>
<D:response> <D:response>
<D:href>/home/bernard/addressbook/v102.vcf</D:href> <D:href>/home/bernard/addressbook/v102.vcf</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:getetag>"23ba4d-ff11fb"</D:getetag> <D:getetag>"23ba4d-ff11fb"</D:getetag>
skipping to change at page 32, line 47 skipping to change at page 31, line 14
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
8.7. CARDDAV:addressbook-multiget Report 8.7. CARDDAV:addressbook-multiget Report
The CARDDAV:addressbook-multiget REPORT is used to retrieve specific The CARDDAV:addressbook-multiget REPORT is used to retrieve specific
address object resources from within a collection, if the Request-URI address object resources from within a collection, if the Request-URI
is a collection, or to retrieve a specific address object resource, is a collection, or to retrieve a specific address object resource,
if the Request-URI is a address object resource. This report is if the Request-URI is an address object resource. This report is
similar to the CARDDAV:addressbook-query REPORT (see Section 8.6), similar to the CARDDAV:addressbook-query REPORT (see Section 8.6),
except that it takes a list of DAV:href elements instead of a except that it takes a list of DAV:href elements instead of a
CARDDAV:filter element to determine which address object resources to CARDDAV:filter element to determine which address object resources to
return. return.
Support for the addressbook-multiget REPORT is REQUIRED. Support for the addressbook-multiget REPORT is REQUIRED.
Marshalling: Marshalling:
The request body MUST be a CARDDAV:addressbook-multiget XML The request body MUST be a CARDDAV:addressbook-multiget XML
element (see Section 10.7), which MUST contain at least one DAV: element (see Section 10.7), which MUST contain at least one
href XML element, and one optional CARDDAV:address-data element as DAV:href XML element and one optional CARDDAV:address-data element
defined in Section 10.4. If DAV:href elements are present, the as defined in Section 10.4. If DAV:href elements are present, the
scope of the request is the set of resources identified by these scope of the request is the set of resources identified by these
elements, which all need to be members (not necessarily internal elements, which all need to be members (not necessarily internal
members) of the resource identified by the Request-URI. members) of the resource identified by the Request-URI.
Otherwise, the scope is the resource identified by the Request-URI Otherwise, the scope is the resource identified by the Request-URI
itself. itself.
The request MUST include a Depth: 0 header, however the actual The request MUST include a Depth: 0 header; however, the actual
scope of the REPORT is determined as described above. scope of the REPORT is determined as described above.
The response body for a successful request MUST be a DAV: The response body for a successful request MUST be a
multistatus XML element. DAV:multistatus XML element.
The response body for a successful CARDDAV:addressbook-multiget The response body for a successful CARDDAV:addressbook-multiget
REPORT request MUST contain a DAV:response element for each REPORT request MUST contain a DAV:response element for each
address object resource referenced by the provided set of DAV:href address object resource referenced by the provided set of DAV:href
elements. Address data is returned in the CARDDAV:address-data elements. Address data is returned in the CARDDAV:address-data
element inside the DAV:prop element. element inside the DAV:prop element.
In the case of an error accessing any of the provided DAV:href In the case of an error accessing any of the provided DAV:href
resources, the server MUST return the appropriate error status resources, the server MUST return the appropriate error status
code in the DAV:status element of the corresponding DAV:response code in the DAV:status element of the corresponding DAV:response
skipping to change at page 34, line 9 skipping to change at page 32, line 20
address object resources. address object resources.
Postconditions: Postconditions:
None. None.
8.7.1. Example: CARDDAV:addressbook-multiget Report 8.7.1. Example: CARDDAV:addressbook-multiget Report
In this example, the client requests the server to return specific In this example, the client requests the server to return specific
vCard properties of the address components referenced by specific vCard properties of the address components referenced by specific
URIs. In addition the DAV:getetag property is also requested and URIs. In addition, the DAV:getetag property is also requested and
returned as part of the response. Note that in this example, the returned as part of the response. Note that, in this example, the
resource at resource at
http://addressbook.example.com/home/bernard/addressbook/vcf1.vcf does http://addressbook.example.com/home/bernard/addressbook/vcf1.vcf does
not exist, resulting in an error status response. not exist, resulting in an error status response.
>> Request << >> Request <<
REPORT /home/bernard/addressbook/ HTTP/1.1 REPORT /home/bernard/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Depth: 1 Depth: 1
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
skipping to change at page 35, line 41 skipping to change at page 33, line 41
<D:response> <D:response>
<D:href>/home/bernard/addressbook/vcf1.vcf</D:href> <D:href>/home/bernard/addressbook/vcf1.vcf</D:href>
<D:status>HTTP/1.1 404 Resource not found</D:status> <D:status>HTTP/1.1 404 Resource not found</D:status>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
8.7.2. Example: CARDDAV:addressbook-multiget Report 8.7.2. Example: CARDDAV:addressbook-multiget Report
In this example, the client requests the server to return vCard v4.0 In this example, the client requests the server to return vCard v4.0
data of the address components referenced by specific URIs. In data of the address components referenced by specific URIs. In
addition the DAV:getetag property is also requested and returned as addition, the DAV:getetag property is also requested and returned as
part of the response. Note that in this example, the resource at part of the response. Note that, in this example, the resource at
http://addressbook.example.com/home/bernard/addressbook/vcf3.vcf http://addressbook.example.com/home/bernard/addressbook/vcf3.vcf
exists but in a media type format that the server is unable to exists but in a media type format that the server is unable to
convert, resulting in an error status response. convert, resulting in an error status response.
>> Request << >> Request <<
REPORT /home/bernard/addressbook/ HTTP/1.1 REPORT /home/bernard/addressbook/ HTTP/1.1
Host: addressbook.example.com Host: addressbook.example.com
Depth: 1 Depth: 1
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<C:addressbook-multiget xmlns:D="DAV:" <C:addressbook-multiget xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:carddav"> xmlns:C="urn:ietf:params:xml:ns:carddav">
<D:prop> <D:prop>
<D:getetag/> <D:getetag/>
<C:address-data type='text/vcard' version='4.0'/> <C:address-data content-type='text/vcard' version='4.0'/>
</D:prop> </D:prop>
<D:href>/home/bernard/addressbook/vcf3.vcf</D:href> <D:href>/home/bernard/addressbook/vcf3.vcf</D:href>
</C:addressbook-multiget> </C:addressbook-multiget>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Date: Sat, 11 Nov 2006 09:32:12 GMT Date: Sat, 11 Nov 2006 09:32:12 GMT
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
skipping to change at page 37, line 5 skipping to change at page 34, line 49
</D:response> </D:response>
</D:multistatus> </D:multistatus>
9. Client Guidelines 9. Client Guidelines
9.1. Restrict the Properties Returned 9.1. Restrict the Properties Returned
Clients may not need all the properties in a vCard object when Clients may not need all the properties in a vCard object when
presenting information to the user, or looking up specific items for presenting information to the user, or looking up specific items for
their email address, for example. Since some property data can be their email address, for example. Since some property data can be
large (e.g., PHOTO or SOUND with inline content) clients can choose large (e.g., PHOTO or SOUND with in-line content) clients can choose
to ignore those by only requesting the specific items it knows it to ignore those by only requesting the specific items it knows it
will use, through use of the CARDDAV:address-data XML element in the will use, through use of the CARDDAV:address-data XML element in the
relevant reports. relevant reports.
However, if a client needs to make a change to a vCard, it can only However, if a client needs to make a change to a vCard, it can only
change the entire vCard data via a PUT request. There is no way to change the entire vCard data via a PUT request. There is no way to
incrementally make a change to a set of properties within a vCard incrementally make a change to a set of properties within a vCard
object resource. As a result the client will have to cache the object resource. As a result, the client will have to cache the
entire set of properties on a resource that is being changed. entire set of properties on a resource that is being changed.
9.2. Avoiding Lost Updates 9.2. Avoiding Lost Updates
When resources are accessed by multiple clients, the possibility of When resources are accessed by multiple clients, the possibility of
clients overwriting each other's changes exists. To alleviate that, clients overwriting each other's changes exists. To alleviate this,
clients SHOULD use the If-Match request header on PUT requests with clients SHOULD use the If-Match request header on PUT requests with
the ETag of the previously retrieved resource data to check whether the ETag of the previously retrieved resource data to check whether
the resource was modified since it was previously retrieved. If a the resource was modified since it was previously retrieved. If a
pre-condition failure occurs, clients need to reload the resource and precondition failure occurs, clients need to reload the resource and
go through their own merge or conflict resolution process before go through their own merge or conflict resolution process before
writing back the data (again using the If-Match check). writing back the data (again using the If-Match check).
9.3. Client Configuration 9.3. Client Configuration
When CardDAV clients need to be configured, the key piece of When CardDAV clients need to be configured, the key piece of
information that they require is the principal-URL of the user whose information that they require is the principal-URL of the user whose
address book information is desired. Servers SHOULD support the DAV: address book information is desired. Servers SHOULD support the
current-user-principal-URL property as defined in [RFC5397] to give DAV:current-user-principal-URL property as defined in [RFC5397] to
clients a fast way to locate user principals. give clients a fast way to locate user principals.
Given support for SRV records (Section 11) and DAV:current-user- Given support for SRV records (Section 11) and DAV:current-user-
principal-URL [RFC5397], users only need enter a user identifier, principal-URL [RFC5397], users only need enter a user identifier,
host name and password to configure their client. The client would host name, and password to configure their client. The client would
take the host name and do an SRV lookup to locate the CardDAV server, take the host name and do an SRV lookup to locate the CardDAV server,
then execute an authenticated PROPFIND on the root / resource looking then execute an authenticated PROPFIND on the root/resource looking
for the DAV:current-user-principal-URL property. The value returned for the DAV:current-user-principal-URL property. The value returned
gives the client direct access to the user's principal-URL and from gives the client direct access to the user's principal-URL and from
there all the related CardDAV properties needed to locate address there all the related CardDAV properties needed to locate address
books. books.
9.4. Finding Other Users' Address Books 9.4. Finding Other Users' Address Books
For address book sharing use cases, one might wish to find the For use cases of address book sharing, one might wish to find the
address book belonging to another user. To find other users' address address book belonging to another user. To find other users' address
books on the same server, the DAV:principal-property-search REPORT books on the same server, the DAV:principal-property-search REPORT
[RFC3744] can be used to filter on some properties and return others. [RFC3744] can be used to search principals for matching properties
and return specified properties for the matching principal resources.
To search for an address book owned by a user named "Laurie", the To search for an address book owned by a user named "Laurie", the
REPORT request body would look like this: REPORT request body would look like this:
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:principal-property-search xmlns:D="DAV:"> <D:principal-property-search xmlns:D="DAV:">
<D:property-search> <D:property-search>
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
<D:match>Laurie</D:match> <D:match>Laurie</D:match>
skipping to change at page 38, line 24 skipping to change at page 36, line 23
<D:prop> <D:prop>
<C:addressbook-home-set <C:addressbook-home-set
xmlns:C="urn:ietf:params:xml:ns:carddav"/> xmlns:C="urn:ietf:params:xml:ns:carddav"/>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
</D:principal-property-search> </D:principal-property-search>
The server performs a case-sensitive or caseless search for a The server performs a case-sensitive or caseless search for a
matching string subset of "Laurie" within the DAV:displayname matching string subset of "Laurie" within the DAV:displayname
property. Thus, the server might return "Laurie Dusseault", "Laurier property. Thus, the server might return "Laurie Dusseault", "Laurier
Desruisseaux" or "Wilfrid Laurier" all as matching DAV:displayname Desruisseaux", or "Wilfrid Laurier" all as matching DAV:displayname
values, and the address books for each of these. values, and the address books for each of these.
10. XML Element Definitions 10. XML Element Definitions
10.1. CARDDAV:addressbook XML Element 10.1. CARDDAV:addressbook XML Element
Name: addressbook Name: addressbook
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
skipping to change at page 39, line 39 skipping to change at page 37, line 34
DAV:prop)?, filter, limit?)> DAV:prop)?, filter, limit?)>
10.4. CARDDAV:address-data XML Element 10.4. CARDDAV:address-data XML Element
Name: address-data Name: address-data
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Specifies one of the following: Purpose: Specifies one of the following:
1. The parts of an address object resource which should be 1. The parts of an address object resource that should be
returned by a given address book REPORT request, and the media returned by a given address book REPORT request, and the media
type and version for the returned data; type and version for the returned data; or
2. The content of an address object resource in a response to an 2. The content of an address object resource in a response to an
address book REPORT request. address book REPORT request.
Description: When used in an address book REPORT request, the Description: When used in an address book REPORT request, the
CARDDAV:address-data XML element specifies which parts of address CARDDAV:address-data XML element specifies which parts of address
object resources need to be returned in the response. If the object resources need to be returned in the response. If the
CARDDAV:address-data XML element doesn't contain any CARDDAV:prop CARDDAV:address-data XML element doesn't contain any CARDDAV:prop
elements, address object resources will be returned in their elements, address object resources will be returned in their
entirety. Additionally a media type and version can be specified entirety. Additionally, a media type and version can be specified
to request that the server return the data in that format if to request that the server return the data in that format if
possible. possible.
Finally, when used in an address book REPORT response, the Finally, when used in an address book REPORT response, the
CARDDAV:address-data XML element specifies the content of a CARDDAV:address-data XML element specifies the content of an
address object resource. Given that XML parsers normalize the address object resource. Given that XML parsers normalize the
two-character sequence CRLF (US-ASCII decimal 13 and US-ASCII two-character sequence CRLF (US-ASCII decimal 13 and US-ASCII
decimal 10) to a single LF character (US-ASCII decimal 10), the CR decimal 10) to a single LF character (US-ASCII decimal 10), the CR
character (US-ASCII decimal 13) MAY be omitted in address object character (US-ASCII decimal 13) MAY be omitted in address object
resources specified in the CARDDAV:address-data XML element. resources specified in the CARDDAV:address-data XML element.
Furthermore, address object resources specified in the CARDDAV: Furthermore, address object resources specified in the
address-data XML element MAY be invalid per their media type CARDDAV:address-data XML element MAY be invalid per their media
specification if the CARDDAV:address-data XML element part of the type specification if the CARDDAV:address-data XML element part of
address book REPORT request did not specify required vCard the address book REPORT request did not specify required vCard
properties (e.g., UID, etc.) or specified a CARDDAV:prop XML properties (e.g., UID, etc.) or specified a CARDDAV:prop XML
element with the "novalue" attribute set to "yes". element with the "novalue" attribute set to "yes".
Note: The CARDDAV:address-data XML element is specified in requests Note: The CARDDAV:address-data XML element is specified in requests
and responses inside the DAV:prop XML element as if it were a and responses inside the DAV:prop XML element as if it were a
WebDAV property. However, the CARDDAV:address-data XML element is WebDAV property. However, the CARDDAV:address-data XML element is
not a WebDAV property and as such it is not returned in PROPFIND not a WebDAV property and as such it is not returned in PROPFIND
responses nor used in PROPPATCH requests. responses nor used in PROPPATCH requests.
Note: The address data embedded within the CARDDAV:address-data XML Note: The address data embedded within the CARDDAV:address-data XML
element MUST follow the standard XML character data encoding element MUST follow the standard XML character data encoding
rules, including use of &lt;, &gt;, &amp; etc entity encoding or rules, including use of &lt;, &gt;, &amp; etc., entity encoding or
the use of a <![CDATA[ ... ]]> construct. In the later case the the use of a <![CDATA[ ... ]]> construct. In the latter case, the
vCard data cannot contain the character sequence "]]>" which is vCard data cannot contain the character sequence "]]>", which is
the end delimiter for the CDATA section. the end delimiter for the CDATA section.
Definition: Definition:
<!ELEMENT address-data (allprop | prop*)> <!ELEMENT address-data (allprop | prop*)>
when nested in the DAV:prop XML element in an address book when nested in the DAV:prop XML element in an address book
REPORT request to specify which parts of address object REPORT request to specify which parts of address object
resources should be returned in the response; resources should be returned in the response;
skipping to change at page 41, line 41 skipping to change at page 39, line 20
Purpose: Specifies that all vCard properties shall be returned. Purpose: Specifies that all vCard properties shall be returned.
Description: This element can be used when the client wants all Description: This element can be used when the client wants all
vCard properties of components returned by a report. vCard properties of components returned by a report.
Definition: Definition:
<!ELEMENT allprop EMPTY> <!ELEMENT allprop EMPTY>
NOTE: The CARDDAV:allprop element defined here has the same name as Note: The CARDDAV:allprop element defined here has the same name as
the DAV:allprop element defined in WebDAV. However, the CARDDAV: the DAV:allprop element defined in WebDAV. However, the
allprop element defined here uses the CARDDAV:allprop element defined here uses the
"urn:ietf:params:xml:ns:carddav" namespace, as opposed to the "DAV:" "urn:ietf:params:xml:ns:carddav" namespace, as opposed to the "DAV:"
namespace used for the DAV:allprop element defined in WebDAV. namespace used for the DAV:allprop element defined in WebDAV.
10.4.2. CARDDAV:prop XML Element 10.4.2. CARDDAV:prop XML Element
Name: prop Name: prop
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Defines which vCard properties to return in the response. Purpose: Defines which vCard properties to return in the response.
Description: The "name" attribute specifies the name of the vCard Description: The "name" attribute specifies the name of the vCard
property to return (e.g., "NICKNAME"). The "novalue" attribute property to return (e.g., "NICKNAME"). The "novalue" attribute
can be used by clients to request that the actual value of the can be used by clients to request that the actual value of the
property not be returned (if the "novalue" attribute is set to property not be returned (if the "novalue" attribute is set to
skipping to change at page 42, line 14 skipping to change at page 39, line 38
Name: prop Name: prop
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Defines which vCard properties to return in the response. Purpose: Defines which vCard properties to return in the response.
Description: The "name" attribute specifies the name of the vCard Description: The "name" attribute specifies the name of the vCard
property to return (e.g., "NICKNAME"). The "novalue" attribute property to return (e.g., "NICKNAME"). The "novalue" attribute
can be used by clients to request that the actual value of the can be used by clients to request that the actual value of the
property not be returned (if the "novalue" attribute is set to property not be returned (if the "novalue" attribute is set to
"yes"). In that case the server will return just the vCard "yes"). In that case, the server will return just the vCard
property name and any vCard parameters and a trailing ":" without property name and any vCard parameters and a trailing ":" without
the subsequent value data. the subsequent value data.
vCard allows a "group" prefix to appear before a property name in vCard allows a "group" prefix to appear before a property name in
the vCard data. When the "name" attribute does not specify a the vCard data. When the "name" attribute does not specify a
group prefix, it MUST match properties in the vCard data without a group prefix, it MUST match properties in the vCard data without a
group prefix or with any group prefix. When the "name" attribute group prefix or with any group prefix. When the "name" attribute
includes a group prefix, it MUST match properties that have includes a group prefix, it MUST match properties that have
exactly the same group prefix and name. e.g.: a "name" set to exactly the same group prefix and name. For example, a "name" set
"TEL" will match "TEL", "X-ABC.TEL", "X-ABC-1.TEL" vCard to "TEL" will match "TEL", "X-ABC.TEL", and "X-ABC-1.TEL" vCard
properties. A "name" set to "X-ABC.TEL" will match an "X-ABC.TEL" properties. A "name" set to "X-ABC.TEL" will match an "X-ABC.TEL"
vCard property only, it will not match "TEL" or "X-ABC-1.TEL". vCard property only; it will not match "TEL" or "X-ABC-1.TEL".
Definition: Definition:
<!ELEMENT prop EMPTY> <!ELEMENT prop EMPTY>
<!ATTLIST prop name CDATA #REQUIRED <!ATTLIST prop name CDATA #REQUIRED
novalue (yes | no) "no"> novalue (yes | no) "no">
<!-- name value: a vCard property name --> <!-- name value: a vCard property name -->
<!-- novalue value: "yes" or "no" --> <!-- novalue value: "yes" or "no" -->
NOTE: The CARDDAV:prop element defined here has the same name as the Note: The CARDDAV:prop element defined here has the same name as the
DAV:prop element defined in WebDAV. However, the CARDDAV:prop DAV:prop element defined in WebDAV. However, the CARDDAV:prop
element defined here uses the "urn:ietf:params:xml:ns:carddav" element defined here uses the "urn:ietf:params:xml:ns:carddav"
namespace, as opposed to the "DAV:" namespace used for the DAV:prop namespace, as opposed to the "DAV:" namespace used for the DAV:prop
element defined in WebDAV. element defined in WebDAV.
10.5. CARDDAV:filter XML Element 10.5. CARDDAV:filter XML Element
Name: filter Name: filter
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
skipping to change at page 43, line 4 skipping to change at page 40, line 25
DAV:prop element defined in WebDAV. However, the CARDDAV:prop DAV:prop element defined in WebDAV. However, the CARDDAV:prop
element defined here uses the "urn:ietf:params:xml:ns:carddav" element defined here uses the "urn:ietf:params:xml:ns:carddav"
namespace, as opposed to the "DAV:" namespace used for the DAV:prop namespace, as opposed to the "DAV:" namespace used for the DAV:prop
element defined in WebDAV. element defined in WebDAV.
10.5. CARDDAV:filter XML Element 10.5. CARDDAV:filter XML Element
Name: filter Name: filter
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Determines which matching objects are returned. Purpose: Determines which matching objects are returned.
Description: The "filter" element specifies the search filter used Description: The "filter" element specifies the search filter used
to match address objects that should be returned by a report. The to match address objects that should be returned by a report. The
"test" attribute specifies whether any (logical OR) or all "test" attribute specifies whether any (logical OR) or all
(logical AND) of the prop-filter tests needs to match in order for (logical AND) of the prop-filter tests need to match in order for
the overall filter to match. the overall filter to match.
Definition: Definition:
<!ELEMENT filter (prop-filter*)> <!ELEMENT filter (prop-filter*)>
<!ATTLIST filter test (anyof | allof) "anyof"> <!ATTLIST filter test (anyof | allof) "anyof">
<!-- test value: <!-- test value:
anyof logical OR for prop-filter matches anyof logical OR for prop-filter matches
allof logical AND for prop-filter matches --> allof logical AND for prop-filter matches -->
10.5.1. CARDDAV:prop-filter XML Element 10.5.1. CARDDAV:prop-filter XML Element
Name: prop-filter Name: prop-filter
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Limits the search to specific vCard properties. Purpose: Limits the search to specific vCard properties.
Description: The CARDDAV:prop-filter XML element specifies a search Description: The CARDDAV:prop-filter XML element specifies search
criteria on a specific vCard property (e.g., NICKNAME). An criteria on a specific vCard property (e.g., "NICKNAME"). An
address object is said to match a CARDDAV:prop-filter if: address object is said to match a CARDDAV:prop-filter if:
* A vCard property of the type specified by the "name" attribute * A vCard property of the type specified by the "name" attribute
exists, and the CARDDAV:prop-filter is empty, or it matches any exists, and the CARDDAV:prop-filter is empty, or it matches any
specified CARDDAV:text-match or CARDDAV:param-filter specified CARDDAV:text-match or CARDDAV:param-filter
conditions. The "test" attribute specifies whether any conditions. The "test" attribute specifies whether any
(logical OR) or all (logical AND) of the text-filter and param- (logical OR) or all (logical AND) of the text-filter and param-
filter tests need to match in order for the overall filter to filter tests need to match in order for the overall filter to
match. match.
skipping to change at page 44, line 4 skipping to change at page 41, line 28
* A vCard property of the type specified by the "name" attribute * A vCard property of the type specified by the "name" attribute
does not exist, and the CARDDAV:is-not-defined element is does not exist, and the CARDDAV:is-not-defined element is
specified. specified.
vCard allows a "group" prefix to appear before a property name in vCard allows a "group" prefix to appear before a property name in
the vCard data. When the "name" attribute does not specify a the vCard data. When the "name" attribute does not specify a
group prefix, it MUST match properties in the vCard data without a group prefix, it MUST match properties in the vCard data without a
group prefix or with any group prefix. When the "name" attribute group prefix or with any group prefix. When the "name" attribute
includes a group prefix, it MUST match properties that have includes a group prefix, it MUST match properties that have
exactly the same group prefix and name. e.g.: a "name" set to exactly the same group prefix and name. For example, a "name" set
"TEL" will match "TEL", "X-ABC.TEL", "X-ABC-1.TEL" vCard to "TEL" will match "TEL", "X-ABC.TEL", "X-ABC-1.TEL" vCard
properties. A "name" set to "X-ABC.TEL" will match an "X-ABC.TEL" properties. A "name" set to "X-ABC.TEL" will match an "X-ABC.TEL"
vCard property only, it will not match "TEL" or "X-ABC-1.TEL". vCard property only, it will not match "TEL" or "X-ABC-1.TEL".
Definition: Definition:
<!ELEMENT prop-filter (is-not-defined | <!ELEMENT prop-filter (is-not-defined |
(text-match*, param-filter*))> (text-match*, param-filter*))>
<!ATTLIST prop-filter name CDATA #REQUIRED <!ATTLIST prop-filter name CDATA #REQUIRED
test (anyof | allof) "anyof"> test (anyof | allof) "anyof">
skipping to change at page 44, line 29 skipping to change at page 42, line 5
allof logical AND for text-match/param-filter matches --> allof logical AND for text-match/param-filter matches -->
10.5.2. CARDDAV:param-filter XML Element 10.5.2. CARDDAV:param-filter XML Element
Name: param-filter Name: param-filter
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Limits the search to specific parameter values. Purpose: Limits the search to specific parameter values.
Description: The CARDDAV:param-filter XML element specifies a search Description: The CARDDAV:param-filter XML element specifies search
criteria on a specific vCard property parameter (e.g., TYPE) in criteria on a specific vCard property parameter (e.g., TYPE) in
the scope of a given CARDDAV:prop-filter. A vCard property is the scope of a given CARDDAV:prop-filter. A vCard property is
said to match a CARDDAV:param-filter if: said to match a CARDDAV:param-filter if:
* A parameter of the type specified by the "name" attribute * A parameter of the type specified by the "name" attribute
exists, and the CARDDAV:param-filter is empty, or it matches exists, and the CARDDAV:param-filter is empty, or it matches
the CARDDAV:text-match conditions if specified. the CARDDAV:text-match conditions if specified.
or: or:
skipping to change at page 45, line 38 skipping to change at page 43, line 11
Purpose: Specifies a substring match on a vCard property or Purpose: Specifies a substring match on a vCard property or
parameter value. parameter value.
Description: The CARDDAV:text-match XML element specifies text used Description: The CARDDAV:text-match XML element specifies text used
for a substring match against the vCard property or parameter for a substring match against the vCard property or parameter
value specified in an address book REPORT request. value specified in an address book REPORT request.
The "collation" attribute is used to select the collation that the The "collation" attribute is used to select the collation that the
server MUST use for character string matching. In the absence of server MUST use for character string matching. In the absence of
this attribute the server MUST use the "i;unicode-casemap" this attribute, the server MUST use the "i;unicode-casemap"
collation. collation.
The "negate-condition" attribute is used to indicate that this The "negate-condition" attribute is used to indicate that this
test returns a match if the text matches, when the attribute value test returns a match if the text matches, when the attribute value
is set to "no", or return a match if the text does not match, if is set to "no", or return a match if the text does not match, if
the attribute value is set to "yes". For example, this can be the attribute value is set to "yes". For example, this can be
used to match components with a CATEGORIES property not set to used to match components with a CATEGORIES property not set to
PERSON. PERSON.
The "match-type" attribute is used to indicate the type of match The "match-type" attribute is used to indicate the type of match
skipping to change at page 46, line 37 skipping to change at page 44, line 7
Name: limit Name: limit
Namespace: urn:ietf:params:xml:ns:carddav Namespace: urn:ietf:params:xml:ns:carddav
Purpose: Specifies different types of limits that can be applied to Purpose: Specifies different types of limits that can be applied to
the results returned by the server. the results returned by the server.
Description: The CARDDAV:limit XML element can be used to specify Description: The CARDDAV:limit XML element can be used to specify
different types of limits that the client can request the server different types of limits that the client can request the server
to apply to the results returned by the server. Currently only to apply to the results returned by the server. Currently, only
the CARDDAV:nresults limit can be used, other types of limit could the CARDDAV:nresults limit can be used; other types of limit could
be defined in the future. be defined in the future.
Definition: Definition:
<!ELEMENT limit (nresults)> <!ELEMENT limit (nresults)>
10.6.1. CARDDAV:nresults XML Element 10.6.1. CARDDAV:nresults XML Element
Name: nresults Name: nresults
skipping to change at page 47, line 39 skipping to change at page 45, line 9
<!ELEMENT addressbook-multiget ((DAV:allprop | <!ELEMENT addressbook-multiget ((DAV:allprop |
DAV:propname | DAV:propname |
DAV:prop)?, DAV:prop)?,
DAV:href+)> DAV:href+)>
11. Service Discovery via SRV Records 11. Service Discovery via SRV Records
[RFC2782] defines a DNS-based service discovery protocol that has [RFC2782] defines a DNS-based service discovery protocol that has
been widely adopted as a means of locating particular services within been widely adopted as a means of locating particular services within
a local area network and beyond, using SRV RR records. a local area network and beyond, using SRV RRs.
This specification adds two service types for use with SRV records: This specification adds two service types for use with SRV records:
carddav: Identifies a CardDAV server that uses HTTP without TLS carddav: Identifies a CardDAV server that uses HTTP without TLS
[RFC2818]. [RFC2818].
carddavs: Identifies a CardDAV server that uses HTTP with TLS carddavs: Identifies a CardDAV server that uses HTTP with TLS
[RFC2818]. [RFC2818].
Example: non-TLS service record Example: non-TLS service record
skipping to change at page 48, line 29 skipping to change at page 45, line 43
searching option controlled by the CARDDAV:text-match element and searching option controlled by the CARDDAV:text-match element and
details of character handling are covered in the description of that details of character handling are covered in the description of that
element (see Section 10.5.4). element (see Section 10.5.4).
13. Security Considerations 13. Security Considerations
HTTP protocol transactions are sent in the clear over the network HTTP protocol transactions are sent in the clear over the network
unless protection from snooping is negotiated. This can be unless protection from snooping is negotiated. This can be
accomplished by use of TLS as defined in [RFC2818]. In particular, accomplished by use of TLS as defined in [RFC2818]. In particular,
if HTTP Basic authentication [RFC2617] is available, the server MUST if HTTP Basic authentication [RFC2617] is available, the server MUST
allow TLS to be used at the same time, and SHOULD prevent use of allow TLS to be used at the same time, and it SHOULD prevent use of
Basic authentication when TLS is not in use. Clients SHOULD use TLS Basic authentication when TLS is not in use. Clients SHOULD use TLS
whenever possible. whenever possible.
With the ACL extension [RFC3744] present, WebDAV allows control over With the ACL extension [RFC3744] present, WebDAV allows control over
who can access (read or write) any resource on the WebDAV server. In who can access (read or write) any resource on the WebDAV server. In
addition, WebDAV ACL provides for an "inheritance" mechanism, whereby addition, WebDAV ACL provides for an "inheritance" mechanism, whereby
resources may inherit access privileges from other resources. Often resources may inherit access privileges from other resources. Often,
the "other" resource is a parent collection of the resource itself. the "other" resource is a parent collection of the resource itself.
Servers are able to support address books that are "private" Servers are able to support address books that are "private"
(accessible only to the "owner"), "shared" (accessible to the owner (accessible only to the "owner"), "shared" (accessible to the owner
and other specified authenticated users), and "public" (accessible to and other specified authenticated users), and "public" (accessible to
any authenticated or unauthenticated users). When provisioning any authenticated or unauthenticated users). When provisioning
address books of a particular type, servers MUST ensure that the address books of a particular type, servers MUST ensure that the
correct privileges are applied on creation, and in particular private correct privileges are applied on creation. In particular, private
and shared address books MUST NOT be accessible by unauthenticated and shared address books MUST NOT be accessible by unauthenticated
users (to prevent data from being automatically searched or indexed users (to prevent data from being automatically searched or indexed
by web "crawlers"). by web "crawlers").
Clients SHOULD warn users in an appropriate fashion when they copy or Clients SHOULD warn users in an appropriate fashion when they copy or
move address data from a private address book to a shared address move address data from a private address book to a shared address
book or public address book. Clients SHOULD provide a clear book or public address book. Clients SHOULD provide a clear
indication as to which address books are private, shared or public. indication as to which address books are private, shared, or public.
Clients SHOULD provide an appropriate warning when changing access Clients SHOULD provide an appropriate warning when changing access
privileges for a private or shared address book with data so as to privileges for a private or shared address book with data so as to
allow unauthenticated users access. allow unauthenticated users access.
This specification currently relies on standard HTTP authentication This specification currently relies on standard HTTP authentication
mechanisms for identifying users. These comprise Basic and Digest mechanisms for identifying users. These comprise Basic and Digest
authentication [RFC2617] as well as TLS [RFC2818] using client-side authentication [RFC2617] as well as TLS [RFC2818] using client-side
certificates. certificates.
14. IANA Consideration 14. IANA Consideration
This document uses a URN to describe a new XML namespace conforming This document uses a URN to describe a new XML namespace conforming
to the registry mechanism described in [RFC3688]. to the registry mechanism described in [RFC3688].
14.1. Namespace Registration 14.1. Namespace Registration
Registration request for the carddav namespace: Registration request for the carddav namespace:
URI: urn:ietf:params:xml:ns:carddav URI: urn:ietf:params:xml:ns:carddav
Registrant Contact: See the "Author's Address" section of this Registrant Contact: The IESG <iesg@ietf.org>
document.
XML: None - not applicable for namespace registrations. XML: None - not applicable for namespace registrations.
15. Acknowledgments 15. Acknowledgments
Thanks go to Lisa Dusseault and Bernard Desruisseaux for their work Thanks go to Lisa Dusseault and Bernard Desruisseaux for their work
on CalDAV, on which CardDAV is heavily based. The following on CalDAV, on which CardDAV is heavily based. The following
individuals contributed their ideas and support for writing this individuals contributed their ideas and support for writing this
specification: Mike Douglass, Stefan Eissing, Helge Hess, Arnaud specification: Mike Douglass, Stefan Eissing, Helge Hess, Arnaud
Quillaud, Julian Reschke, Elias Sinderson, Greg Stein, Wilfredo Quillaud, Julian Reschke, Elias Sinderson, Greg Stein, Wilfredo
Sanchez, and Simon Vaillancourt. Sanchez, and Simon Vaillancourt.
16. References 16. References
16.1. Normative References 16.1. Normative References
[I-D.ietf-vcarddav-vcardrev]
Perreault, S. and P. Resnick, "vCard Format
Specification", draft-ietf-vcarddav-vcardrev-08 (work in
progress), July 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
RFC 2426, September 1998. RFC 2426, September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
skipping to change at page 51, line 12 skipping to change at page 48, line 19
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
[RFC5397] Sanchez, W. and C. Daboo, "WebDAV Current Principal [RFC5397] Sanchez, W. and C. Daboo, "WebDAV Current Principal
Extension", RFC 5397, December 2008. Extension", RFC 5397, December 2008.
[RFC5689] Daboo, C., "Extended MKCOL for Web Distributed Authoring [RFC5689] Daboo, C., "Extended MKCOL for Web Distributed Authoring
and Versioning (WebDAV)", RFC 5689, September 2009. and Versioning (WebDAV)", RFC 5689, September 2009.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Paoli, J., Yergeau, F., Bray, T., Sperberg-McQueen, C., Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
and E. Maler, "Extensible Markup Language (XML) 1.0 (Fifth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008, xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
16.2. Informative References 16.2. Informative References
[IMSP] Myers, J., "IMSP - Internet Message Support Protocol", [IMSP] Myers, J., "IMSP - Internet Message Support Protocol",
June 1995. Work in Progress, June 1995.
[RFC2244] Newman, C. and J. Myers, "ACAP -- Application [RFC2244] Newman, C. and J. Myers, "ACAP -- Application
Configuration Access Protocol", RFC 2244, November 1997. Configuration Access Protocol", RFC 2244, November 1997.
[RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol [RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Technical Specification Road Map", RFC 4510, (LDAP): Technical Specification Road Map", RFC 4510,
June 2006. June 2006.
Appendix A. Change History (to be removed prior to publication as an
RFC)
Changes in -10
1. Updated to MKColExt RFC reference.
2. GenART Review: changed to clients SHOULD support TLS.
3. GenART Review: changed security considerations in relation to
clients indicating which address books are private, shared or
public.
4. IESG Review: re-wrote section on locking to instead describe how
to avoid lost updates using ETags.
5. IESG Review: removed disadvantage describing stateless protocol
nature.
6. IESG Review: clarified that 507 is only returned when truncation
of the results set occurs.
7. IESG Review: added additional text in security considerations
about the handling private, shared and public address books.
8. Fixed typos.
9. Fixed some XML example errors.
Changes in -09
1. AD Review: support for vCard v4 is now a SHOULD.
2. As a result of the above, added a sub-section on content
conversion that defines a new precondition, and added an example
of a conversion failure when doing a multiget.
Changes in -08
1. AD Review: added references to list in section 1.
2. AD Review: added reference to RFC5280 for cert validation
procedures.
3. AD Review: added additional comment in addressbook-description
property relating to use of xml:lang attribute.
4. AD Review: max-resource-size now explicitly stated to be a
decimal integer.
5. AD Review: tweaked text for supported-collation-set to make it
clear two will always be present.
6. AD Review: section title change to "Client Guidelines".
7. AD Review: finding address books section re-worded and reference
added.
8. AD Review: re-worded prop-filter description to better explain
that text-match and param-filter can be specified independently
of each other.
9. AD Review: references added to security considerations.
10. AD Review: changed to RFC4510 reference.
Changes in -07
1. WGLC: changed all alprop behaviors to SHOULD NOT return in
allprop PROPFIND.
2. WGLC: Reworked XML conventions section to come into line with
text in extended MKCOL, and also updated W3C reference.
3. WGLC: Changed a couple of examples to use absolute path DAV:href
values.
4. WGLC: Simplified IANA Considerations section.
5. WGLC: Added new Client Configuration section and removed
reference to principal-match.
6. address-data element in supported-address-data changed to
address-data-type.
7. REPORTs now require Depth to be present and the scope of matching
resources is determined by the value of the Depth header.
8. Removed requirement that DAV:displayname should be unique at each
level.
Changes in -06
1. WGLC: addressbook-home-set changed to SHOULD NOT return in
allprop PROPFIND.
2. WGLC: principal-address description changed to note that the
resource pointed to could be in a regular collection too.
3. Added new section decribing how SRV and current-user-principal
are used to bootstrap client configuration.
4. Removed discussion of using principal-match report.
Changes in -05
1. Removed mailing list discussion note from abstract.
Changes in -04
1. Tweaked limit element text to not imply any formal ordering of
results.
2. Changed prop-filter element to allow zero or more text-match
elements rather than zero or one.
3. Updated to RFC5397 reference.
4. Updated TLS reference to latest version RFC5246.
5. Boiler plate update.
Changes in -03
1. Added limit element to addressbook-query.
2. Specified how a server signals that query results have been
truncated.
3. Minor stylistic changes.
Changes in -02
1. Added text to CARDDAV:prop and CARDDAV:prop-filter elements to
explain how vCard "group" prefix on property names is handled.
Changes in -01
1. Added section on SRV records.
Changes in -00
1. Removed text describing other protocols.
2. Added comment about a new vcard spec being developed.
3. Added SHOULD support for the DAV:current-user-principal-URL
property.
4. Added "anyof"/"allof" test attribute to query XML elements to
support simple or/and combinations of tests.
Changes in pre-04
1. Renamed addressbook-data to address-data for consistency.
2. Fixed address-data element definition.
Changes in pre-03
1. Replaced MKADDRESSBOOK with extended MKCOL.
2. Now require i;uncide-casemap as a supported collation and make it
the default.
3. No longer require i;octet as a supported collation.
4. Allow different types of match operations via the "match-type"
attribute on the "text-match" element.
5. Updated to 4918 reference and removed some text/sections
duplicating 4918.
6. WebDAV Level 3 now required.
7. TLS requirement text tweaked to match latest text approved by
IESG.
8. Added principal-address property to principal resources to allow
a vcard to be associated with a principal.
9. XML definition clean-up.
Changes in pre-02
1. Added commentary on SyncML.
2. Changed 'adbk' to 'addressbook'.
3. Support for MKADDRESSBOOK is now a SHOULD.
4. Updated to RFC4790 reference.
5. Removed synchronization report.
6. Removed BNF conventions section as we have no BNF.
7. Reworded and reformatted several items to match the final CalDAV
spec.
8. Added section on use of nonstandard properties and parameters
(as per CalDAV).
9. Added section of behavior of ETags (as per CalDAV).
10. Generalized the text so that vCard need not be the only format
supported by the server (i.e., allow xml version of vCard etc).
11. Renamed supported-addressbook-data to supported-address-data.
12. Renamed valid-addressbook-data to valid-address-data.
13. Now requires "i;unicasemao" collation.
Changes in pre-01
1. Fixed various incorrect references and typos.
2. Major changes to sync with latest CalDAV spec behaviors.
Author's Address Author's Address
Cyrus Daboo Cyrus Daboo
Apple Inc. Apple, Inc.
1 Infinite Loop 1 Infinite Loop
Cupertino, CA 95014 Cupertino, CA 95014
USA USA
Email: cyrus@daboo.name EMail: cyrus@daboo.name
URI: http://www.apple.com/ URI: http://www.apple.com/
 End of changes. 163 change blocks. 
563 lines changed or deleted 340 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/