Calendar Access Protocol (CAP)
RFC 4324
Document | Type |
RFC - Experimental
(December 2005; No errata)
Was draft-royer-calsch-cap (individual in gen area)
|
|
---|---|---|---|
Authors | George Babics , Steve Mansour , Doug Royer | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4324 (Experimental) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | phb@mit.edu |
Network Working Group D. Royer Request for Comments: 4324 IntelliCal, LLC Category: Experimental G. Babics Oracle S. Mansour eBay December 2005 Calendar Access Protocol (CAP) Status of This Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract 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. Royer, et al. Experimental [Page 1] RFC 4324 Calendar Access Protocol December 2005 Table of Contents 1. Introduction ....................................................5 1.1. Formatting Conventions .....................................5 1.2. Related Documents ..........................................6 1.3. Definitions ................................................7 2. Additions to iCalendar .........................................11 2.1. New Value Types (Summary) ................................14 2.1.1. New Parameters (summary) .............................14 2.1.2. New or Updated Properties (summary) ..................14 2.1.3. New Components (summary) .............................17 2.2. Relationship of RFC-2446 (ITIP) to CAP ...................18 3. CAP Design .....................................................20 3.1. System Model ..............................................20 3.2. Calendar Store Object Model ...............................20 3.3. Protocol Model ............................................21 3.3.1. Use of BEEP, MIME, and iCalendar .....................22 4. Security Model .................................................23 4.1. Calendar User and UPNs ....................................23 4.1.1. UPNs and Certificates ................................24 4.1.2. Anonymous Users and Authentication ...................25 4.1.3. User Groups ..........................................25 4.2. Access Rights .............................................26 4.2.1. Access Control and NOCONFLICT ........................26 4.2.2. Predefined VCARs .....................................26 4.2.3. Decreed VCARs ........................................28 4.3. CAP Session Identity ......................................28 5. CAP URL and Calendar Address ...................................29 6. New Value Types ................................................30 6.1. Property Value Data Types .................................30 6.1.1. CAL-QUERY Value Type .................................30 6.1.1.1. [NOT] CAL-OWNERS() ..............................36 6.1.1.2. CURRENT-TARGET() ................................37 6.1.1.3. PARAM() .........................................37 6.1.1.4. SELF() ..........................................38 6.1.1.5. STATE() .........................................38 6.1.1.6. Use of Single Quote .............................38 6.1.1.7. Comparing DATE and DATE-TIME Values .............39 6.1.1.8. DTEND and DURATION ..............................40 6.1.1.9. [NOT] LIKE ......................................40 6.1.1.10. Empty vs. NULL .................................41 6.1.1.11. [NOT] IN .......................................41 6.1.1.12. DATE-TIME and TIME Values in a WHERE Clause ....42 6.1.1.13. Multiple Contained Components ..................43 6.1.1.14. Example, Query by UID ..........................43 6.1.1.15. Query by Date-Time Range .......................43 6.1.1.16. Query for All Unprocessed Entries ..............44 6.1.1.17. Query with Subset of Properties by Date/Time ...44Show full document text