RFC 4324: Calendar Access Protocol (CAP)
In plain English — editorial summary, not part of the RFC
The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4324
- Published
- December 2005
- Authors
- D. Royer; G. Babics; S. Mansour
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 131
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4791Calendaring Extensions to WebDAV (CalDAV)Updated
March 2007
- RFC 5333IANA Registration of Enumservices for Internet CalendaringUpdated
October 2009
- RFC 5545Internet Calendaring and Scheduling Core Object Specification (iCalendar)Updated
September 2009
- RFC 6638Scheduling Extensions to CalDAVUpdated
June 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?