| Network Working Group | C. Daboo |
| Internet-Draft | Apple Inc. |
| Intended status: Standards Track | October 18, 2012 |
| Expires: April 19, 2013 |
New Properties for iCalendar
draft-daboo-icalendar-extensions-00
This document defines a set of new properties for iCalendar data.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http:/⁠/⁠datatracker.ietf.org/⁠drafts/⁠current/⁠.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 19, 2013.
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http:/⁠/⁠trustee.ietf.org/⁠license-⁠info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The iCalendar [RFC5545] data format is used to represent calendar data and is used with iTIP [RFC5546] to handle scheduling operations between calendar users. iCalendar is in widespread use, and in accordance with provisions in that specification, extension elements have been added by various vendors to the data format in order to support and enhance capabilities. This specification collates a number of these ad-hoc extensions and uses the new IANA registry capability defined in [RFC5545] to register standard variants with clearly defined definitions and semantics. In addition, some new elements are introduced for features that vendors have been requesting recently.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
The notation used in this memo is the ABNF notation of [RFC5234] as used by iCalendar [RFC5545]. Any syntax elements shown below that are not explicitly defined in this specification come from iCalendar [RFC5545].
calprops /= *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
calname / caldescription /
caluid / calurl / caltzid /
calrefresh / calcolor /
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
calimg
;
)
eventprop /= *(
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
image
;
)
todoprop /= *(
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
image
;
)
jourprop /= *(
;
; The following are OPTIONAL,
; and MAY occur more than once.
;
image
;
)
The following changes to the syntax defined in iCalendar [RFC5545] are made here. New elements are defined in subsequent sections.
calname = "CALENDAR-NAME" calnameparam ":" text CRLF
calnameparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
CALENDAR-NAME:Company Vacation Days
caldesc = "CALENDAR-DESCRIPTION" caldescparam ":" text
CRLF
caldescparam = *(
;
; The following are OPTIONAL,
; but MUST NOT occur more than once.
;
(";" altrepparam) / (";" languageparam) /
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
CALENDAR-DESCRIPTION:This calendar contains all the \
official vacation days of our company.\nThese repre\
sent paid time-off - make sure you have fun, we'll \
be working you hard on the other days!
caluid = "CALENDAR-UID" caluidparam ":" text CRLF
caluidparam = *(";" other-param)
CALENDAR-UID:19960401T080045Z-4000F192713-0052@example.com
calurl = "CALENDAR-URL" calurlparam ":" url CRLF
calurlparam = *(";" other-param)
CALENDAR-URL:http://calendars.example.com/holidays/canada.ics
caltzid = "CALENDAR-TZID" caltzidparam ":" [tzidprefix]
text CRLF
caltzidparam = *(";" other-param)
CALENDAR-TZID:America/New_York
calrefesh = "CALENDAR-REFRESH-INTERVAL" calrefreshparam
":" dur-value CRLF
;consisting of a positive duration of time.
calrefeshparam = *(";" other-param)
CALENDAR-REFRESH-INTERVAL:P1W
calcolor = "CALENDAR-COLOR" calcolorparam ":"
calcolorvalue CRLF
calcolorparam = *(";" other-param)
calcolorvalue = integer ";" integer ";" integer
; Red, green, and blue values in the range
; 0 - 255.
CALENDAR-COLOR:255;0;255
calimg = "CALENDAR-IMAGE" calimgparam ( ":" uri ) /
(
";" "ENCODING" "=" "BASE64"
";" "VALUE" "=" "BINARY"
":" binary
)
CRLF
calimgparam = *(
;
; The following is OPTIONAL for a URI value,
; RECOMMENDED for a BINARY value,
; and MUST NOT occur more than once.
;
(";" fmttypeparam) /
;
; The following is OPTIONAL,
; and MOST NOT occur more than once.
;
(";" displayparam)
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
CALENDAR-IMAGE;DISPLAY=BADGE;FMTTYPE=image/png:http://ex
ample.com/images/holiday.png
image = "IMAGE" imageparam ( ":" uri ) /
(
";" "ENCODING" "=" "BASE64"
";" "VALUE" "=" "BINARY"
":" binary
)
CRLF
imageparam = *(
;
; The following is OPTIONAL for a URI value,
; RECOMMENDED for a BINARY value,
; and MUST NOT occur more than once.
;
(";" fmttypeparam) /
;
; The following is OPTIONAL,
; and MOST NOT occur more than once.
;
(";" displayparam)
;
; The following is OPTIONAL,
; and MAY occur more than once.
;
(";" other-param)
;
)
IMAGE;DISPLAY=BACKGROUND;FMTTYPE=image/png:htt
p://example.com/images/party.png
displayparam = "DISPLAY" "="
("BADGE" / ; A small "badge" image
"BACKGROUND" / ; Use as a background image
"OVERLAY" / ; Use as an overlay image
"BANNER" / ; Use as a "banner" across the top
x-name / ; Experimental type
iana-token) ; Other IANA registered type
;
; Default is BADGE
IMAGE;DISPLAY=BANNER;FMTTYPE=image/png:htt
p://example.com/images/weather-cloudy.png
TODO:Perhaps discuss issues with image processing related buffer overflows, accessing external URLs (privacy), etc.
This documents defines the following new iCalendar properties to be added to the registry defined in Section 8.2.3 of [RFC5545]:
| Property | Status | Reference |
|---|---|---|
| CALENDAR-NAME | Current | RFCXXXX, Section 4.1 |
| CALENDAR-DESCRIPTION | Current | RFCXXXX, Section 4.2 |
| CALENDAR-UID | Current | RFCXXXX, Section 4.3 |
| CALENDAR-URL | Current | RFCXXXX, Section 4.4 |
| CALENDAR-TZID | Current | RFCXXXX, Section 4.5 |
| CALENDAR-REFRESH-INTERVAL | Current | RFCXXXX, Section 4.6 |
| CALENDAR-COLOR | Current | RFCXXXX, Section 4.7 |
| CALENDAR-IMAGE | Current | RFCXXXX, Section 4.8 |
| IMAGE | Current | RFCXXXX, Section 5.1 |
This documents defines the following new iCalendar properties to be added to the registry defined in Section 8.2.3 of [RFC5545]:
| Property Parameter | Status | Reference |
|---|---|---|
| DISPLAY | Current | RFCXXXX, Section 6.1 |
This specification came about via discussions at the Calendaring and Scheduling Consortium.
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. |
| [RFC5234] | Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. |
| [RFC5545] | Desruisseaux, B., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 5545, September 2009. |
| [RFC5546] | Daboo, C., "iCalendar Transport-Independent Interoperability Protocol (iTIP)", RFC 5546, December 2009. |