draft-ietf-vcarddav-carddav-00.txt   draft-ietf-vcarddav-carddav-01.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Internet-Draft Apple
Intended status: Standards Track May 28, 2008 Intended status: Standards Track July 12, 2008
Expires: November 29, 2008 Expires: January 13, 2009
vCard Extensions to WebDAV (CardDAV) vCard Extensions to WebDAV (CardDAV)
draft-ietf-vcarddav-carddav-00 draft-ietf-vcarddav-carddav-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 29, 2008. This Internet-Draft will expire on January 13, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines extensions to the Web Distributed Authoring and This document defines extensions to the Web Distributed Authoring and
Versioning (WebDAV) protocol to specify a standard way of accessing, Versioning (WebDAV) protocol to specify a standard way of accessing,
managing, and sharing contact information based on the vCard format. managing, and sharing contact information based on the vCard format.
Discussion of this Internet-Draft is taking place on the mailing list Discussion of this Internet-Draft is taking place on the mailing list
<http://lists.osafoundation.org/mailman/listinfo/ietf-carddav>. <http://lists.osafoundation.org/mailman/listinfo/ietf-carddav>.
skipping to change at page 3, line 18 skipping to change at page 3, line 18
10.3. CARDDAV:addressbook-query XML Element . . . . . . . . . . 34 10.3. CARDDAV:addressbook-query XML Element . . . . . . . . . . 34
10.4. CARDDAV:address-data XML Element . . . . . . . . . . . . . 35 10.4. CARDDAV:address-data XML Element . . . . . . . . . . . . . 35
10.4.1. CARDDAV:allprop XML Element . . . . . . . . . . . . . 36 10.4.1. CARDDAV:allprop XML Element . . . . . . . . . . . . . 36
10.4.2. CARDDAV:prop XML Element . . . . . . . . . . . . . . . 37 10.4.2. CARDDAV:prop XML Element . . . . . . . . . . . . . . . 37
10.5. CARDDAV:filter XML Element . . . . . . . . . . . . . . . . 38 10.5. CARDDAV:filter XML Element . . . . . . . . . . . . . . . . 38
10.5.1. CARDDAV:prop-filter XML Element . . . . . . . . . . . 38 10.5.1. CARDDAV:prop-filter XML Element . . . . . . . . . . . 38
10.5.2. CARDDAV:param-filter XML Element . . . . . . . . . . . 39 10.5.2. CARDDAV:param-filter XML Element . . . . . . . . . . . 39
10.5.3. CARDDAV:is-not-defined XML Element . . . . . . . . . . 40 10.5.3. CARDDAV:is-not-defined XML Element . . . . . . . . . . 40
10.5.4. CARDDAV:text-match XML Element . . . . . . . . . . . . 40 10.5.4. CARDDAV:text-match XML Element . . . . . . . . . . . . 40
10.6. CARDDAV:addressbook-multiget XML Element . . . . . . . . . 41 10.6. CARDDAV:addressbook-multiget XML Element . . . . . . . . . 41
11. Internationalization Considerations . . . . . . . . . . . . . 41 11. Service Discovery via SRV records . . . . . . . . . . . . . . 41
12. Security Considerations . . . . . . . . . . . . . . . . . . . 42 12. Internationalization Considerations . . . . . . . . . . . . . 42
13. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 42 13. Security Considerations . . . . . . . . . . . . . . . . . . . 42
13.1. Namespace Registration . . . . . . . . . . . . . . . . . . 42 14. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 43
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43 14.1. Namespace Registration . . . . . . . . . . . . . . . . . . 43
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43
15.1. Normative References . . . . . . . . . . . . . . . . . . . 43 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43
15.2. Informative References . . . . . . . . . . . . . . . . . . 44 16.1. Normative References . . . . . . . . . . . . . . . . . . . 43
16.2. Informative References . . . . . . . . . . . . . . . . . . 45
Appendix A. Change History (to be removed prior to Appendix A. Change History (to be removed prior to
publication as an RFC) . . . . . . . . . . . . . . . 44 publication as an RFC) . . . . . . . . . . . . . . . 45
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 46 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 47
Intellectual Property and Copyright Statements . . . . . . . . . . 47 Intellectual Property and Copyright Statements . . . . . . . . . . 48
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
Lightweight Directory Access Protocol LDAP [RFC4511], Internet Lightweight Directory Access Protocol LDAP [RFC4511], Internet
Message Support Protocol IMSP [IMSP] and Application Configuration Message Support Protocol IMSP [IMSP] and Application Configuration
Access Protocol ACAP [RFC2244], together with SyncML used for Access Protocol ACAP [RFC2244], together with SyncML used for
skipping to change at page 41, line 44 skipping to change at page 41, line 44
Description: See Section 8.7. Description: See Section 8.7.
Definition: Definition:
<!ELEMENT addressbook-multiget ((DAV:allprop | <!ELEMENT addressbook-multiget ((DAV:allprop |
DAV:propname | DAV:propname |
DAV:prop)?, DAV:prop)?,
DAV:href+)> DAV:href+)>
11. Internationalization Considerations 11. Service Discovery via SRV records
[RFC2782] defines a DNS-based service discovery protocol that has
been widely adopted as a means of locating particular services within
a local area network and beyond, using SRV RR records.
This specification adds two service types for use with SRV records:
carddav: Identifies a CardDAV server that uses HTTP without SSL.
carddavs: Identifies a CardDAV server that uses HTTP with SSL.
Example: non-SSL service record
_carddav._tcp SRV 0 1 80 addressbook.example.com.
Example: SSL service
_carddavs._tcp SRV 0 1 443 addressbook.example.com.
12. Internationalization Considerations
CardDAV allows internationalized strings to be stored and retrieved CardDAV allows internationalized strings to be stored and retrieved
for the description of address book collections (see Section 6.2.1). for the description of address book collections (see Section 6.2.1).
The CARDDAV:addressbook-query report (Section 8.6) includes a text The CARDDAV:addressbook-query report (Section 8.6) includes a text
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).
12. 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 is available, the server MUST allow TLS if HTTP Basic authentication is available, the server MUST allow TLS
to be used at the same time, and SHOULD prevent use of Basic to be used at the same time, and SHOULD prevent use of Basic
authentication when TLS is not in use. authentication when TLS is not in use.
With the ACL extension present, WebDAV allows control over who can With the ACL extension present, WebDAV allows control over who can
access (read or write) any resource on the WebDAV server. In access (read or write) any resource on the WebDAV server. In
skipping to change at page 42, line 37 skipping to change at page 43, line 11
unauthenticated access to any address book or address object data. unauthenticated access to any address book or address object data.
Clients MAY choose to warn users when they create address data in a Clients MAY choose to warn users when they create address data in a
public address book, copy or move address data into public address public address book, copy or move address data into public address
books, or change access privileges in such a way as to expose address books, or change access privileges in such a way as to expose address
data to unauthenticated users. data to unauthenticated users.
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 as well as SSL using client-side certificates. authentication as well as SSL using client-side certificates.
13. IANA Consideration 14. IANA Consideration
In addition to the namespaces defined by RFC4918 [RFC4918] for XML In addition to the namespaces defined by RFC4918 [RFC4918] for XML
elements, this document uses a URN to describe a new XML namespace elements, this document uses a URN to describe a new XML namespace
conforming to a registry mechanism described in RFC3688 [RFC3688]. conforming to a registry mechanism described in RFC3688 [RFC3688].
All other IANA considerations mentioned in RFC4918 [RFC4918] also All other IANA considerations mentioned in RFC4918 [RFC4918] also
apply to this document. apply to this document.
13.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: See the "Author's Address" section of this
document. document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
14. 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: Stefan Eissing, Arnaud Quillaud, Julian Reschke, Elias specification: Stefan Eissing, Arnaud Quillaud, Julian Reschke, Elias
Sinderson, Greg Stein, Wilfredo Sanchez. Sinderson, Greg Stein, Wilfredo Sanchez.
15. References 16. References
15.1. Normative References 16.1. Normative References
[I-D.ietf-vcarddav-vcardrev] [I-D.ietf-vcarddav-vcardrev]
Resnick, P. and S. Perreault, "vCard Format Resnick, P. and S. Perreault, "vCard Format
Specification", draft-ietf-vcarddav-vcardrev-01 (work in Specification", draft-ietf-vcarddav-vcardrev-01 (work in
progress), April 2008. progress), April 2008.
[I-D.ietf-vcarddav-webdav-mkcol] [I-D.ietf-vcarddav-webdav-mkcol]
Daboo, C., "Extended MKCOL for WebDAV", May 2008. Daboo, C., "Extended MKCOL for WebDAV", May 2008.
[I-D.sanchez-webdav-current-principal] [I-D.sanchez-webdav-current-principal]
skipping to change at page 43, line 47 skipping to change at page 44, line 23
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
RFC 2246, January 1999. RFC 2246, January 1999.
[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.
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", RFC 2782,
February 2000.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
Whitehead, "Versioning Extensions to WebDAV Whitehead, "Versioning Extensions to WebDAV
(Web Distributed Authoring and Versioning)", RFC 3253, (Web Distributed Authoring and Versioning)", RFC 3253,
March 2002. March 2002.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
Distributed Authoring and Versioning (WebDAV) Distributed Authoring and Versioning (WebDAV)
Access Control Protocol", RFC 3744, May 2004. Access Control Protocol", RFC 3744, May 2004.
skipping to change at page 44, line 33 skipping to change at page 45, line 9
[RFC5051] Crispin, M., "i;unicode-casemap - Simple Unicode Collation [RFC5051] Crispin, M., "i;unicode-casemap - Simple Unicode Collation
Algorithm", RFC 5051, October 2007. Algorithm", RFC 5051, October 2007.
[W3C.REC-xml-20060816] [W3C.REC-xml-20060816]
Bray, T., Paoli, J., Sperberg-McQueen, C., Yergeau, F., Bray, T., Paoli, J., Sperberg-McQueen, C., Yergeau, F.,
and E. Maler, "Extensible Markup Language (XML) 1.0 and E. Maler, "Extensible Markup Language (XML) 1.0
(Fourth Edition)", World Wide Web Consortium (Fourth Edition)", World Wide Web Consortium
Recommendation REC-xml-20060816, August 2006, Recommendation REC-xml-20060816, August 2006,
<http://www.w3.org/TR/2006/REC-xml-20060816>. <http://www.w3.org/TR/2006/REC-xml-20060816>.
15.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. 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.
[RFC4511] Sermersheim, J., "Lightweight Directory Access Protocol [RFC4511] Sermersheim, J., "Lightweight Directory Access Protocol
(LDAP): The Protocol", RFC 4511, June 2006. (LDAP): The Protocol", RFC 4511, June 2006.
Appendix A. Change History (to be removed prior to publication as an Appendix A. Change History (to be removed prior to publication as an
RFC) RFC)
Changes from -01
1. Added section on SRV records.
Changes from draft-daboo-carddav-04 Changes from draft-daboo-carddav-04
1. Removed text describing other protocols. 1. Removed text describing other protocols.
2. Added comment about a new vcard spec being developed. 2. Added comment about a new vcard spec being developed.
3. Added SHOULD support for the DAV:current-user-principal-URL 3. Added SHOULD support for the DAV:current-user-principal-URL
property. property.
4. Added "anyof"/"allof" test attribute to query XML elements to 4. Added "anyof"/"allof" test attribute to query XML elements to
skipping to change at page 47, line 44 skipping to change at line 2105
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 18 change blocks. 
28 lines changed or deleted 53 lines changed or added

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