[ISO.8601.2004] International Organization for Standardization, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", 2004. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Zawinski, "The mailto URL scheme", RFC 2368, July 1998. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, September 2009. The editor would also like to thank the Calendaring and Scheduling Consortium for advice with this specification, and for organizing interoperability testing events to help refine it. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996. A special thanks to the working group chairs Aki Niemi and Eliot Lear for their support and guidance.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. Author's Address Bernard Desruisseaux (editor) Oracle Corporation 600 blvd.
Berners- Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Howes, "Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator", RFC 4516, June 2006. Dusseault, "Calendaring Extensions to Web DAV (Cal DAV)", RFC 4791, March 2007. x-param can be used on RECUR value type properties instead.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, August 1998. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. The "DTSTART" property SHOULD be synchronized with the recurrence rule, if specified. The "RRULE" property SHOULD NOT occur more than once in a component. The BYHOUR, BYMINUTE, and BYSECOND rule parts MUST NOT be specified in the "RRULE" property when the "DTSTART" property is specified as a DATE value. The value type of the "DTEND" or "DUE" properties MUST match the value type of "DTSTART" property. The "DURATION" property can no longer appear in "VFREEBUSY" components. The "EXRULE" property can no longer be specified in a component. The "THISANDPRIOR" value can no longer be used with the "RANGE" parameter. The "PROCEDURE" value can no longer be used with the "ACTION" property. The value type RECUR no longer allows multiple values to be specified by a COMMA-separated list of values. x-name rule parts can no longer be specified in properties of RECUR value type (e.g., "RRULE").
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, August 1998. Howes, "v Card MIME Directory Profile", RFC 2426, September 1998. and Stenerson, D., "Internet Calendaring and Scheduling Core Object Specification (i Calendar)", RFC 2445, November 1998. Olson, "Sources for Time Zone and Daylight Saving Time Data", July 2009, 1.
[ANSI INCITS 61-1986] International Committee for Information Technology, "Representation of Geographic Point Locations for Information Interchange (formerly ANSI X3.61-1986 (R1997))", ANSI INCITS 61-1986 (R2007), 2007. Mc Cahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[2447bis] Melnikov, A., "i Calendar Message-Based Interoperability Protocol (i MIP)", Work in Progress, June 2008.
[2446bis] Daboo, C., "i Calendar Transport-Independent Interoperability Protocol (i TIP)", Work in Progress, April 2009.
[ISO.9070.1991] International Organization for Standardization, "Information Technology_SGML Support Facilities -- Registration Procedures for Public Text Owner Identifiers, Second Edition", April 1991. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006. [US-ASCII] American National Standards Institute, "Coded Character Set - 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986.
Abstract This document defines the i Calendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.
Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Copyright and License Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document.