Calendaring Extensions to WebDAV , or CalDAV , is an Internet standard allowing a client to access and manage calendar data along with the ability to schedule meetings with users on the same or on remote servers . It lets multiple users in different locations share, search and synchronize calendar data. It extends the WebDAV ( HTTP -based protocol for data manipulation) specification and uses the iCalendar format for the calendar data. The access protocol is defined by RFC 4791 . Extensions to CalDAV for scheduling are standardized as RFC 6638 . The protocol is used by many important open-source applications.
8-699: The CalDAV specification was first published in 2003 as an Internet Draft submitted to the Internet Engineering Task Force ( IETF ) by Lisa Dusseault. In March 2007, the CalDAV specification was finished and published by the IETF as RFC 4791, authored by Cyrus Daboo ( Apple ), Bernard Desruissaux ( Oracle ), and Lisa Dusseault ( CommerceNet ). CalDAV is designed for implementation by any collaborative software , client or server, that needs to maintain, access or share collections of events. It
16-417: A number of calendaring-specific operations such as doing free-busy time reports and expansion of recurring events. With this functionality, a user may synchronize their own calendar to a CalDAV server, and share it among multiple devices or with other users. The protocol also supports non-personal calendars, such as calendars for sites or organizations. Internet Draft An Internet Draft ( I-D )
24-485: Is a document published by the Internet Engineering Task Force (IETF) containing preliminary technical specifications, results of networking-related research, or other technical information. Often, Internet Drafts are intended to be work-in-progress documents for work that is eventually to be published as a Request for Comments (RFC) and potentially leading to an Internet Standard . It
32-455: Is considered inappropriate to rely on Internet Drafts for reference purposes. I-D citations should indicate the I-D is a work in progress . An Internet Draft is expected to adhere to the basic requirements imposed on any RFC. An Internet Draft is only valid for six months unless it is replaced by an updated version. An otherwise expired draft remains valid while it is under official review by
40-500: Is developed as an open standard to foster interoperability between software from different vendors. The architecture of CalDAV (partially inherited from the underlying specifications) organizes the data (events, tasks, free-busy info, notes) in directories (collections), where multiple items (resources) reside. The resources and collections can be accessed by one or more users, using standard HTTP and DAV semantics to detect conflicting changes, or to provide locking. For access control
48-504: The Internet Engineering Steering Group (IESG) when a request to publish it as an RFC has been submitted. Expired drafts are replaced with a "tombstone" version and remain available for reference. Internet Drafts produced by the IETF working groups follow the naming convention: draft-ietf-<wg>-<name>-<version number>.txt . Internet Drafts produced by IRTF research groups following
56-414: The concept of ACLs are used, so each operation (view, edit, delete etc.) can be denied or granted per user. Therefore, the specification requires that CalDAV servers must support "WebDAV Access Control Protocol" ( RFC 3744 ). The calendar resources must use iCalendar format, which allows the server to understand and process the data. Parsing the iCalendar items is necessary, because the server has to support
64-462: The naming convention: draft-irtf-<rg>-<name>-<version number>.txt . Drafts produced by individuals following the naming convention: draft-<individual>-<name>-<version number>.txt The IAB , RFC Editor, and other organizations associated with the IETF may also produce Internet Drafts. They follow the naming convention: draft-<org>-<name>-<version number>.txt . The initial version number
#506493