Facts about CardDAV
- 08
CardDAV servers require HTTP authentication mechanisms like Basic Auth or Digest Auth to secure contact access, making TLS encryption essential for protecting sensitive address book data during transmission.
- 07
Approximately 40 percent of CardDAV implementations support delegation, enabling users to grant other people permission to manage their contacts on shared servers without exposing login credentials.
- 06
Exchange ActiveSync, Microsoft's proprietary protocol, initially competed with CardDAV for mobile contact synchronization until Apple iOS 8 in 2014 added native CardDAV support, significantly expanding the standard's adoption.
- 05
The CalDAV protocol, CardDAV's sibling standard published in RFC 4791 in 2008, predates CardDAV by three years and handles calendar data using the same WebDAV infrastructure foundation.
- 04
Open-source CardDAV servers like Nextcloud and Radicale reduced deployment barriers by allowing organizations to self-host contact synchronization infrastructure without relying on proprietary cloud services.
- 03
Most CardDAV implementations use the vCard 3.0 and 4.0 formats to store contact data, with vCard 4.0 introduced in 2011 adding support for extended properties like photographs and phonetic names.
- 02
Apple's Contacts app and Google Contacts both implement CardDAV synchronization, allowing millions of users to automatically sync address books across iPhone, Android, and web platforms without manual intervention.
- 01
RFC 6352, published in 2011, standardized CardDAV as an HTTP-based protocol for managing contact information across multiple devices and servers.