Network Working GroupB Desruisseaux, Editor
Internet DraftOracle
<draft-ietf-calsify-rfc2445bis-07> July 2007
Obsoletes: 2445 (if approved)
Intended status: Standards Track
Expires: January 2008

Internet Calendaring and Scheduling Core Object Specification (iCalendar)
draft-ietf-calsify-rfc2445bis-07

Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

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”.

The list of current Internet-Drafts can be accessed at <http://www.ietf.org/ietf/1id-abstracts.txt>.

The list of Internet-Draft Shadow Directories can be accessed at <http://www.ietf.org/shadow.html>.

This Internet-Draft will expire in January 2008.

Copyright Notice

Copyright The Internet Society (2007). All Rights Reserved.

Abstract

 I  abstract   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-01-17 The abstract may not contain any references, and should be less than 20 lines.
Resolution: Rewrote a much shorter abstract.
Associated changes in this document: <#rfc.change.abstract.1>., Published in: draft-ietf-calsify-rfc2445bis-04
 I  

There is a clear need to provide and deploy interoperable calendaring and scheduling services for the Internet. Current group scheduling and Personal Information Management (PIM) products are being extended for use across the Internet, today, in proprietary ways. This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet.

This memo is formatted as a registration for a MIME media type per [RFC2048]. However, the format in this memo is equally applicable for use outside of a MIME message content type.

The proposed media type value is 'text/calendar'. This string would label a media type containing calendaring and scheduling information encoded as text characters formatted in a manner outlined below.

This MIME media type provides a standard content type for capturing calendar event, to-do and journal entry information. It also can be used to convey free/busy time information. The content type is suitable as a MIME message entity that can be transferred over MIME based email systems, using HTTP or some other Internet transport. In addition, the content type is useful as an object for interactions between desktop applications using the operating system clipboard, drag/drop or file systems capabilities.

This memo is based on the earlier work of the vCalendar specification for the exchange of personal calendaring and scheduling information. In order to avoid confusion with this referenced work, this memo is to be known as the iCalendar specification.

This memo defines the format for specifying iCalendar object methods. An iCalendar object method is a set of usage constraints for the iCalendar object. For example, these methods might define scheduling messages that request an event be scheduled, reply to an event request, send a cancellation notice for an event, modify or replace the definition of an event, provide a counter proposal for an original event request, delegate an event request to another individual, request free or busy time, reply to a free or busy time request, or provide similar scheduling messages for a to-do or journal entry calendar component. The iCalendar Transport-indendent Interoperability Protocol (iTIP) defined in [RFC2446] is one such scheduling protocol.

This document defines the iCalendar 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.

 I  

Editorial Note (To be removed by RFC Editor prior to publication)

This document is a product of the Calendaring and Scheduling Standards Simplification (Calsify) working group of the Internet Engineering Task Force. Comments on this draft are welcomed, and should be addressed to the ietf-calsify@osafoundation.org mailing list.


Table of Contents

Issues list

NameTypeStatusDateRaised ByResolved In
#issue01+4.1_line_foldingchangeclosed2006-05-24gsexton@mhsoftware.comdraft-ietf-calsify-rfc2445bis-02
#issue02+4.8.6.3_dtstart_typoeditclosed2006-05-25andrew_dowden@softdesign.net.nzdraft-ietf-calsify-rfc2445bis-02
#issue03+4.1_non-us-ascii_ordereditclosed2006-05-29lists@block-online.eudraft-ietf-calsify-rfc2445bis-02
#issue03+4.1.3_content_typoeditclosed2006-05-29lists@block-online.eudraft-ietf-calsify-rfc2445bis-06
#issue03+4.2.4_users_typoeditclosed2006-05-29lists@block-online.eudraft-ietf-calsify-rfc2445bis-01
#issue04+4.8.5.4_rrule_example1editclosed2006-05-29sroberts@uniserve.comdraft-ietf-calsify-rfc2445bis-02
#issue04+4.8.5.4_rrule_example2editclosed2006-09-12aki.niemi@nokia.comdraft-ietf-calsify-rfc2445bis-02
#issue08+4.3.6_nominal_durationchangeclosedreinhold@kainhofer.com
#issue10+end_date_not_inclusivechangeclosed2006-06-03reinhold@kainhofer.com
#issue13+dtstart_and_countchangeclosed2006-06-03reinhold@kainhofer.comdraft-ietf-calsify-rfc2445bis-06
#issue14+dtstart/dtend_meaningchangeclosed2006-06-03reinhold@kainhofer.com
#issue16+4.3.10_ignored_rule_partschangeclosed2006-06-03reinhold@kainhofer.comdraft-ietf-calsify-rfc2445bis-04
#issue19+iana_considerationschangeclosedlear@cisco.comdraft-ietf-calsify-rfc2445bis-06
#issue23+4.3.10_until_rule_partchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue24+multiple_ruleschangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-03
#issue25+exrule_and_dtstartchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-03
#issue26+byhour_byminute_bysecondchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue27+4.8.5.4_recur_instances_durationchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue28+4.8.5.4_rdate_requiredchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue29+dtstart_in_recur_vtodo_and_vjournalchangeclosed2006-07-12bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue31+charsetchangeclosed2006-08-11bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue32+icalendar_streamchangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue33+characters_vs_octetschangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue34+method_paramchangeclosed2006-08-21bernard.desruisseaux@oracle.com
#issue35+4.2.10_language_descchangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue36+4.1_x-name_usechangeclosed2006-06-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue37+4.6.1_eventprop_rulechangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue38+4.6.2_todoprop_rulechangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue39+4.6.3_jourprop_rulechangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue40+4.6.4_fbprop_rulechangeclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue41+4.6.4_freebusy_exampleeditclosed2006-09-15simon.pilette@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue42+4.8.6.1_valarm_action_restrictionchangeclosed2006-09-19bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue43+4.8.5.4_allowed_datetime_form_in_recur_compchangeclosed2006-09-19bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue44+4.8.8.1_param_on_x-propchangeclosed2006-09-19bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue45+ldap_urleditclosed2006-09-19bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
#issue46+simplify_abnfchangeclosed2006-09-22lists@block-online.eu draft-ietf-calsify-rfc2445bis-05
#issue47+4.8.6.3_trigger_relative_to_date_valuechangeclosed2006-09-25bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue48+deprecate_range_paramchangeclosed2006-10-02bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue51+4.6.1_implicit_dtend_of_day_eventschangeclosed2006-10-03bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue52+4.3.10_x-name_rule_partchangeclosed2006-10-12bernard.desruisseaux@oracle.com
#issue53+4.1_NON-US-ASCIIeditclosed2006-08-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue56+4.3.10_recur_rule_parts_orderchangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue57+duration_restrictionchangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue58+4.6.3_description_in_jourpropchangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
#issue59+4.6.1_default_duration_of_day_eventschangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue61+ianaparamchangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue62+4.8.4.4_recurrence_id_immutablechangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue64+4.8.8.2_request-statuschangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue65+6_recommended_practices_3changeclosed2006-11-05bernard.desruisseaux@oracle.com
#issue66+6_recommended_practices_rdatechangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue68+ambiguous_date_timechangeclosedlennox@cs.columbia.edu
#issue69+ambiguous_date_time_in_recurchangeclosedlennox@cs.columbia.edu
#issue71+leap_secondschangeclosedlennox@cs.columbia.edu
#issue72+4.6.5_vtimezone_required_with_rrulechangeclosed2006-11-05bernard.desruisseaux@oracle.com
#issue73+4.8.3.1_tzid_scopechangeclosed2006-11-05bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue74+deprecate_procedurechangeclosed2006-10-02bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue75+4.6.5_rdate_format_in_vtimezonechangeclosed2007-02-07bernard.desruisseaux@oracle.com
#issue76+4.8.2.2_dtend_dtstart_value_typechangeclosed2007-02-13bernard.desruisseaux@oracle.com
#issue77+4.8.2.3_due_dtstart_value_typechangeclosed2007-02-13bernard.desruisseaux@oracle.com
#issue78+4.6.5_dtstart_with_tzoffsetfromchangeclosed2007-02-15bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue79+4.6.5_dtstart_and_rdate_in_vtimezonechangeclosed2007-02-15bernard.desruisseaux@oracle.com
#issue80+security_considerationschangeclosed2006-03-06aki.niemi@nokia.com
#issue81+3.3.10_bysetpos_and_byxxxchangeclosed2006-11-05lennox@cs.columbia.edu
4.3.14_clarify_minuseditclosed2006-06-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-01
4.6.1_missing_value_parameditclosed2006-10-02bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
4.6.2_duration_without_dtstart_in_vtodochangeclosed2001-02-13jpr@ximian.comdraft-ietf-calsify-rfc2445bis-06
4.6.5_bad_dtstarteditclosed2006-06-21bernard.desruisseaux@oracle.com
4.6.5_bad_tzurleditclosed2006-06-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
4.8.1.1_attach_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.1.4_comment_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.1.4_redundant_type_infoeditclosed2006-06-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-01
4.8.2.1_completed_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.2.3_due_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.6.2_repeat_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.7.1_created_description_incompletechangeclosed2007-02-14bernard.desruisseaux@oracle.com
4.8.7.2_dtstampchangeclosed2007-02-14bernard.desruisseaux@oracle.com
abstracteditclosed2007-01-17bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
acknowledgementschangeclosed2006-09-25bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
cid_urleditclosed2006-09-28bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
diff_from_rfc2445editclosed2006-10-20bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
dtstamp_missing_secondseditclosed2006-06-09reinhold@kainhofer.comdraft-ietf-calsify-rfc2445bis-01
edit-01editclosed2006-06-09bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-01
edit-02editclosed2006-10-04bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-02
edit-03editclosed2006-10-11bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-03
edit-04editclosed2006-10-24bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-04
edit-05editclosed2007-01-15bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-05
edit-06editclosed2007-01-29bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
edit-07editclosed2007-03-03bernard.desruisseaux@oracle.com
i18n_considerationschangeclosed2006-06-21bernard.desruisseaux@oracle.com
invalid_media_typeeditclosed2006-06-21bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-01
iso8601editclosed2007-07-07bernard.desruisseaux@oracle.com
reserved_domain_nameeditclosed2006-09-28bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
tzid_and_date_valueschangeclosed2007-06-27bernard.desruisseaux@oracle.com
unrecognized_valuechangeclosed2007-07-07bernard.desruisseaux@oracle.com
vtimezone_exampleseditclosed2007-02-07bernard.desruisseaux@oracle.comdraft-ietf-calsify-rfc2445bis-06
#issue11+4.3.10_byxxx_rule_part_exampleschangeopen2006-06-03reinhold@kainhofer.com
#issue63+4.8.5.3_rdate_and_dtstartchangeopen2006-11-05bernard.desruisseaux@oracle.com
introductioneditopen2007-02-20bernard.desruisseaux@oracle.com
 I  edit-01   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-09 Umbrella issue for editorial changes done in draft -01.
Associated changes in this document: 1, 2, 2.1, 2.1, 2.1, 2.2, 2.2, 2.2, 2.2, 3.1, 3.2, 3.2, 3.3.3, 3.5, 3.6.5, 3.6.5, 3.6.5, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.7, 3.7.2, 3.8.1.9, 3.8.2.6, 3.8.2.7, 3.8.6.3, 3.8.7.2, 4, 7, 7, 7., Published in: draft-ietf-calsify-rfc2445bis-01
 I  edit-02   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-10-04 Umbrella issue for editorial changes done in draft -02.
Associated changes in this document: <#rfc.change.edit-02.1>, 1, 2, 2, 3.1, 3.1.4, 3.2, 3.2, 3.2.1, 3.2.1, 3.2.1, 3.2.4, 3.2.5, 3.2.6, 3.2.6, 3.2.6, 3.2.17, 3.2.17, 3.2.18, 3.3.3, 3.3.3, 3.3.5, 3.3.5, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.11, 3.3.11, 3.3.12, 3.3.12, 3.5, 3.6, 3.6, 3.6, 3.6, 3.6.2, 3.6.3, 3.6.3, 3.8.1.5, 3.8.1.5, 3.8.1.7, 3.8.1.7, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.11, 3.8.2.2, 3.8.2.3, del-16, 3.8.2.6, 3.8.2.7, 3.8.2.7, 3.8.3.5, 3.8.4.1, 3.8.4.2, 3.8.4.3, 3.8.4.5, 3.8.4.5, 3.8.4.5, 3.8.4.7, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.7.4, 3.8.7.4, 3.8.8.2, 4, 4, 4, 4, 4, 4, 4, del-24, 7, 7, 7, 7, 7, 7, 7, 7, <#rfc.change.edit-02.94>., Published in: draft-ietf-calsify-rfc2445bis-02
 I  edit-03   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-10-11 Umbrella issue for editorial changes done in draft -03.
Associated changes in this document: 3.1.3, 3.2.7, 3.2.14, 3.3.1, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.6.5, 3.6.5, 3.8.1.1, 3.8.1.1, 3.8.1.1, 3.8.1.7, 3.8.2.6, 3.8.4.1, 3.8.4.1, 3.8.4.4, 3.8.5.1, 3.8.5.1, 3.8.5.1, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.6.2, 3.8.8.3, 7., Published in: draft-ietf-calsify-rfc2445bis-03
 I  edit-04   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-10-24 Umbrella issue for editorial changes done in draft -04.
Associated changes in this document: 1, 2, 2, 2, 2.1, 2.1, 2.2, 3.1, 3.1.1, 3.1.1, 3.1.1, 3.1.1, 3.2, 3.2.1, 3.2.1, 3.2.2, 3.2.2, 3.2.3, 3.2.3, 3.2.3, 3.2.4, 3.2.4, 3.2.4, 3.2.4, 3.2.4, 3.2.5, 3.2.5, 3.2.5, 3.2.5, 3.2.5, 3.2.6, 3.2.6, 3.2.7, 3.2.7, 3.2.8, 3.2.8, 3.2.8, 3.2.8, 3.2.9, 3.2.9, 3.2.9, 3.2.9, 3.2.9, 3.2.9, 3.2.10, 3.2.10, 3.2.10, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.12, 3.2.12, del-16, del-16, del-16, 3.2.13, 3.2.13, 3.2.13, 3.2.13, 3.2.14, 3.2.15, 3.2.15, 3.2.16, 3.2.16, 3.2.17, 3.2.17, 3.2.17, 3.2.17, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.18, 3.2.19, 3.2.19, 3.2.19, 3.2.19, 3.2.19, 3.2.19, 3.3.1, 3.3.1, 3.3.2, 3.3.2, 3.3.3, 3.3.3, 3.3.3, 3.3.3, 3.3.4, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, 3.3.5, del-16, 3.3.6, 3.3.7, 3.3.8, 3.3.9, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.11, 3.3.11, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.12, 3.3.13, 3.3.13, 3.3.14, 3.3.14, 3.3.14, 3.6, 3.6.1, 3.6.1, 3.6.1, 3.6.1, 3.6.1, 3.6.1, 3.6.2, 3.6.2, 3.6.2, 3.6.3, 3.6.3, 3.6.3, 3.6.3, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.7.1, 3.7.2, 3.7.2, 3.7.2, 3.7.2, 3.7.2, 3.7.3, 3.7.4, 3.8.1.1, 3.8.1.1, 3.8.1.1, 3.8.1.1, 3.8.1.1, 3.8.1.2, 3.8.1.2, 3.8.1.2, 3.8.1.3, 3.8.1.4, 3.8.1.4, 3.8.1.4, 3.8.1.5, 3.8.1.5, 3.8.1.5, 3.8.1.5, 3.8.1.6, 3.8.1.6, 3.8.1.6, 3.8.1.6, 3.8.1.7, 3.8.1.7, 3.8.1.7, 3.8.1.7, 3.8.1.8, 3.8.1.8, 3.8.1.8, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.10, 3.8.1.10, 3.8.1.10, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.12, 3.8.1.12, 3.8.2.1, 3.8.2.2, 3.8.2.2, 3.8.2.2, 3.8.2.3, 3.8.2.3, 3.8.2.3, 3.8.2.3, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.5, 3.8.2.5, 3.8.2.5, 3.8.2.6, 3.8.2.6, 3.8.2.6, 3.8.2.6, 3.8.2.6, 3.8.2.7, 3.8.3.1, 3.8.3.1, 3.8.3.1, 3.8.3.1, 3.8.3.2, 3.8.3.2, 3.8.3.3, 3.8.3.4, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.3.5, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.4, 3.8.4.4, 3.8.4.4, 3.8.4.5, 3.8.4.5, 3.8.4.5, 3.8.4.5, 3.8.4.5, 3.8.4.6, 3.8.4.7, 3.8.4.7, 3.8.4.7, 3.8.5.1, 3.8.5.1, 3.8.5.1, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.6.1, 3.8.6.2, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.7.1, 3.8.7.2, 3.8.7.3, 3.8.7.3, 3.8.7.3, 3.8.8.2, 3.8.8.2, 3.8.8.2, 3.8.8.2, 3.8.8.3, 3.8.8.3, 3.8.8.3, 3.8.8.3, 3.8.8.3, del-17, 4, 4, 4, 4, 4, 4, 4, 4, 4, 5, 5, 5, 5, 5, 5, 5, 7., Published in: draft-ietf-calsify-rfc2445bis-04
 I  edit-05   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-01-15 Umbrella issue for editorial changes done in draft -05.
Associated changes in this document: 1, 2.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.1, 3.2.10, 3.2.12, 3.2.12, 3.2.12, 3.3.1, 3.3.6, 3.3.11, 3.6, 3.6, 3.6.5, 3.8.1.5, 3.8.1.7, 3.8.1.7, 3.8.2.6., Published in: draft-ietf-calsify-rfc2445bis-05
 I  edit-06   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-01-29 Umbrella issue for editorial changes done in draft -06.
Associated changes in this document: 3.2, 3.2.10, 3.3.5, 3.3.5, 3.3.5, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.13, 3.3.13, 3.3.13, 3.6, 3.6, 3.6.1, 3.6.4, 3.6.4, 3.6.4, 3.6.5, 3.6.5, 3.6.6, 3.7.1, 3.7.1, 3.7.2, 3.7.4, 3.7.4, 3.8.1.4, 3.8.1.4, 3.8.1.5, 3.8.1.6, 3.8.1.6, 3.8.1.8, 3.8.1.9, 3.8.1.9, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.1.11, 3.8.2.1, 3.8.2.2, 3.8.2.2, 3.8.2.3, 3.8.2.3, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.4, 3.8.2.6, 3.8.3.2, 3.8.3.3, 3.8.3.4, 3.8.3.5, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.4, 3.8.4.5, 3.8.4.5, 3.8.5.1, del-17, del-17, 3.8.6.1, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.7.3, 3.8.7.3, 3.8.7.4, 3.8.7.4, 3.8.7.4, 3.8.8.2, 3.8.8.2, 4, 4, 4, 5, 5., Published in: draft-ietf-calsify-rfc2445bis-06
 I  edit-07   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-03-03 Umbrella issue for editorial changes done in draft -07.
Associated changes in this document: 3.3.4, 3.3.5, 3.3.6, 3.3.9, 3.3.9, 3.3.9, 3.3.9, 3.3.9, 3.3.10, 3.3.10, 3.3.12, 3.4, 3.6.2, 3.6.2, 3.6.2, 3.6.2, 3.6.2, 3.6.2, 3.6.2, 3.8.1.1, 3.8.1.1, 3.8.1.1, 3.8.1.4, 7.
 I  iso8601   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-07-07 Need to clarify differences with ISO 8601.
Resolution: Done.
Associated changes in this document: 3.3.4, 3.3.6, 3.3.6, 3.3.6, 3.3.6, 3.3.9, 3.3.9.
 I  invalid_media_type   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 Examples are making use of invalid media type.
Resolution: Fixed.
Associated changes in this document: 3.2.8, 3.6.6., Published in: draft-ietf-calsify-rfc2445bis-01
 I  reserved_domain_name   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-09-28 The examples in this specification should use the reserved domain names specified in RFC 2606.
Resolution: Changed domain names in examples.
Associated changes in this document: 3.1.1, 3.1.3, 3.2, 3.2.1, 3.2.1, 3.2.2, 3.2.4, 3.2.4, 3.2.5, 3.2.5, 3.2.5, 3.2.6, 3.2.6, 3.2.8, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.11, 3.2.12, 3.2.14, 3.2.15, 3.2.16, 3.2.17, 3.2.17, 3.3.3, 3.3.13, 3.6.1, 3.6.1, 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.4, 3.6.6, 3.6.6, 3.6.6, del-16, del-16, 3.8.1.1, 3.8.1.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.5, 3.8.4.5, 3.8.4.6, 3.8.4.7, 3.8.8.3, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4., Published in: draft-ietf-calsify-rfc2445bis-06
 I  dtstamp_missing_seconds   (type: edit, status: closed)
reinhold@kainhofer.com2006-06-09 The seconds in the DTSTAMP are missing
2006-06-21Resolution: Added seconds.
Associated changes in this document: 3.6.1, 3.6.1, 3.6.1, 3.6.2, 3.6.3, 4., Published in: draft-ietf-calsify-rfc2445bis-01
 I  cid_url   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-09-28 The Content-ID URL specified in the examples should not contain angle bracket pair (i.e, '<' and '>').
Resolution: Removed the angle bracket pair in the examples.
Associated changes in this document: 3.2.1, 3.2.1, 3.2.14, 3.2.14, 3.8.4.2, 3.8.4.2, 3.8.4.5, 3.8.4.5, 3.8.4.5, 3.8.4.5., Published in: draft-ietf-calsify-rfc2445bis-02
 I  vtimezone_examples   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2007-02-07 The time zone information for US/Eastern needs to be updated.
Resolution: Done.
Associated changes in this document: 3.2.18, 3.2.18, 3.3.5, 3.3.5, 3.3.10, 3.3.12, 3.5, 3.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.8.3.1, 3.8.3.1, 3.8.3.1, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 4, 4, 4., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue34+method_param   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 Clarify what should be done with the "method" parameter when the iCalendar stream is a sequence of iCalendar objects.
Resolution: See issue #issue19+iana_considerations.
 I  #issue45+ldap_url   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-09-19 The LDAP URLs specified in the examples of section 4.2.6, 4.8.4.1, 4.8.4.2, and 4.8.4.3 are all broken. They are missing a '?' character and they partially escape the '=' character in quoted-printable...
Resolution: Fixed.
Associated changes in this document: 3.2.6, 3.2.6, 3.2.6, 3.2.6, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.1, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.2, 3.8.4.3, 3.8.4.3, 3.8.4.3, 3.8.4.3., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue46+simplify_abnf   (type: change, status: closed)
lists@block-online.eu 2006-09-22 The ABNF rules tzprop, audioprop, dispprop, emailprop, and procprop should be simplified by removing the number of required properties in front of the "*" as this was found confusing by most.
Resolution: Done.
Associated changes in this document: 3.6, 3.6.5, 3.6.5, 3.6.6, 3.6.6, 3.6.6, 3.8.6.3., Published in: draft-ietf-calsify-rfc2445bis-05
 I  #issue48+deprecate_range_param   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-10-02 The RANGE parameter should be deprecated.
Resolution: Done.
Associated changes in this document: 3.2, 3.2, 3.8.4.4, 3.8.4.4, 3.8.4.4, 3.8.4.4, 3.8.4.4., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue57+duration_restriction   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 The text should specify that the DURATION property MUST be specified as a "dur-day" or "dur-week" value when the DTSTART is a DATE.
Resolution: Add restriction.
Associated changes in this document: 3.6.1, 3.8.2.5., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue71+leap_seconds   (type: change, status: closed)
lennox@cs.columbia.edu Need to clarify whether leap seconds must be considered when computing exact durations.
Resolution: Leap seconds MUST NOT be considered.
Associated changes in this document: 3.3.5, 3.3.5, 3.3.6.
 I  #issue74+deprecate_procedure   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-10-02 The PROCEDURE ACTION should be deprecated.
Resolution: Done.
Associated changes in this document: 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.6.6, 3.8.1.5, 3.8.1.5, 3.8.6.1, 3.8.6.1., Published in: draft-ietf-calsify-rfc2445bis-06

1. Introduction

 I  introduction   (type: edit, status: open)
bernard.desruisseaux@oracle.com2007-02-20 The Introduction section should be updated.

The use of calendaring and scheduling has grown considerably in the last decade. Enterprise and inter-enterprise business has become dependent on rapid scheduling of events and actions using this information technology. However, the longer term growth of calendaring and scheduling  I , is currently limited by the lack of Internet standards for the message content types that are central to these knowledgeware applications. This memo is intended to progress the level of interoperability possible between dissimilar calendaring and scheduling applications. This memo defines a MIME content type for exchanging electronic calendaring and scheduling information. The Internet Calendaring and Scheduling Core Object Specification, or iCalendar, allows for the capture and exchange of information normally stored within a calendaring and scheduling application; such as a Personal Information Manager (PIM) or a Group Scheduling product.

The iCalendar format is suitable as an exchange format between applications or systems. The format is defined in terms of a MIME content type. This will enable the object to be exchanged using several transports, including but not limited to SMTP, HTTP, a file system, desktop interactive protocols such as the use of a memory- based clipboard or drag/drop interactions, point-to-point asynchronous communication, wired-network transport, or some form of unwired transport such as infrared might also be used.

The memo also provides for the definition of iCalendar object methods that will map this content type to a set of messages for supporting calendaring and scheduling operations such as requesting, replying to, modifying, and canceling meetings or appointments, to-dos and journal entries. The iCalendar object methods can be used to define other calendaring and scheduling operations such a requesting for and replying with free/busy time data. Such a scheduling protocol is defined in the iCalendar Transport-independent Interoperability Protocol (iTIP) defined in  I [RFC2446][I-D.ietf-calsify-2446bis].

The memo also includes a formal grammar for the content type based on the Internet ABNF defined in  I [RFC2234].[RFC4234]. This ABNF is required for the implementation of parsers and to serve as the definitive reference when ambiguities or questions arise in interpreting the descriptive prose definition of the memo.  I Additional restrictions that could not easily be expressed with the ABNF syntax are specified as comments in the ABNF. Comments with normative statements should be treated as such.


2. Basic Grammar and Conventions

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  I interoperatedinterpreted as described in [RFC2119].

This memo makes use of both a descriptive prose and a more formal notation for defining the calendaring and scheduling format.

The notation used in this memo is the ABNF notation of  I [RFC2234].[RFC4234]. Readers intending on implementing  I thisthe format defined in this memo should be familiar with this notation in order to properly interpret the specifications of this memo.

All numeric  I and hexadecimal values used in this memo are given in decimal notation.

All names of properties, property parameters, enumerated property values and property parameter values are case-insensitive. However, all other property values are case-sensitive, unless otherwise stated.

Note: All indented editorial notes, such as this one, are intended to provide the reader with additional information. The information is not essential to the building of an implementation conformant with this memo. The information is provided to highlight a particular feature or characteristic of the memo.

The format for the iCalendar object is based on the syntax of the  I [RFC2425] content type.text/directory media type [RFC2425]. While the iCalendar object is not a profile of the  I [RFC2425] content type,text/directory media type [RFC2425], it does reuse a number of the elements from the [RFC2425] specification.

2.1. Formatting Conventions

The  I mechanismselements defined in this memo are defined in prose. Many of the terms used to describe these have common usage that is different than the standards usage of this memo. In order to reference within this memo elements of the calendaring and scheduling model, core object (this memo) or interoperability protocol  I [RFC2446][I-D.ietf-calsify-2446bis] some formatting conventions have been used. Calendaring and scheduling roles are referred to in quoted-strings of text with the first character of each word in upper case. For example, "Organizer" refers to a role of a "Calendar User" within the scheduling protocol defined by  I [RFC2446][I-D.ietf-calsify-2446bis]. Calendar components defined by this memo are referred to with capitalized, quoted-strings of text. All calendar components start with the letter "V". For example, "VEVENT" refers to the event calendar component, "VTODO" refers to the to-do calendar component and "VJOURNAL" refers to the daily journal calendar component. Scheduling methods defined by  I [RFC2446]iTIP are referred to with capitalized, quoted-strings of text. For example, "REQUEST" refers to the method for requesting a scheduling calendar component be created or modified, "REPLY" refers to the method a recipient of a request uses to update their status with the "Organizer" of the calendar component.

The properties defined by this memo are referred to with capitalized, quoted-strings of text, followed by the word "property". For example, "ATTENDEE" property refers to the iCalendar property used to convey the calendar address of a calendar user. Property parameters defined by this memo are referred to with lowercase, quoted-strings of text, followed by the word "parameter". For example, "value" parameter refers to the iCalendar property parameter used to override the default  I datavalue type for a property value. Enumerated values defined by this memo are referred to with capitalized text, either alone or followed by the word "value". For example, the "MINUTELY" value can be used with the "FREQ" component of the "RECUR"  I datavalue type to specify repeating components based on an interval of one minute or more.

 I  

In this document, descriptions of characters are of the form "character name (codepoint)", where "codepoint" is from the US-ASCII character set. The "character name" is the authoritative description; (codepoint) is a reference to that character in US-ASCII.

2.2. Related Memos

Implementers will need to be familiar with several other memos that, along with this memo, form a framework for Internet calendaring and scheduling standards. This memo  I , [ICAL], specifies a core specification of objects,  I datavalue types, properties and property parameters.

This memo does not attempt to repeat the specification of concepts or definitions from these other memos. Where possible, references are made to the memo that provides for the specification of these concepts or definitions.

 I  

del-1. International Considerations

In the rest of this document, descriptions of characters are of the form "character name (codepoint)", where "codepoint" is from the US-ASCII character set. The "character name" is the authoritative description; (codepoint) is a reference to that character in US-ASCII  I or US-ASCII compatible sets (for example the ISO-8859-x family, UTF-8, ISO-2022-xx, KOI8-R). If a non-US-ASCII compatible character set is used, appropriate code-point from that character set MUST be chosen instead. Use of non-US-ASCII-compatible character sets is NOT recommended.

 I  

del-2. Registration Information

The Calendaring and Scheduling Core Object Specification is intended for use as a MIME content type. However, the implementation of the memo is in no way limited solely as a MIME content type.

del-3. Content Type

The following text is intended to register this memo as the MIME content type "text/calendar".

To: ietf-types@uninett.no

Subject: Registration of MIME content type text/calendar.

MIME media type name: text

MIME subtype name: calendar

del-4. Parameters

Required parameters:
none
Optional parameters:
charset, method, component and optinfo
The "charset" parameter is defined in [RFC2046] for other body parts. It is used to identify the default character set used within the body part.
The "method" parameter is used to convey the iCalendar object method or transaction semantics for the calendaring and scheduling information. It also is an identifier for the restricted set of properties and values that the iCalendar object consists of. The parameter is to be used as a guide for applications interpreting the information contained within the body part. It SHOULD NOT be used to exclude or require particular pieces of information unless the identified method definition specifically calls for this behavior. Unless specifically forbidden by a particular method definition, a text/calendar content type can contain any set of properties permitted by the Calendaring and Scheduling Core Object Specification. The "method" parameter MUST be the same value as that specified in the "METHOD" component property in the iCalendar object. If one is present, the other MUST also be present.
The value for the "method" parameter is defined as follows:
   method  = 1*(ALPHA / DIGIT / "-")
   ; IANA registered iCalendar object method
The "component" parameter conveys the type of iCalendar calendar component within the body part. If the iCalendar object contains more than one calendar component type, then multiple component parameters MUST be specified.
The value for the "component" parameter is defined as follows:
   component = ("VEVENT" / "VTODO" / "VJOURNAL" / "VFREEBUSY"
               / "VTIMEZONE" / x-name / iana-token)
The "optinfo" parameter conveys optional information about the iCalendar object within the body part. This parameter can only specify semantics already specified by the iCalendar object and that can be otherwise determined by parsing the body part. In addition, the optional information specified by this parameter MUST be consistent with that information specified by the iCalendar object. For example, it can be used to convey the "Attendee" response status to a meeting request. The parameter value consists of a string value.
The parameter can be specified multiple times.
This parameter MAY only specify semantics already specified by the iCalendar object and that can be otherwise determined by parsing the body part.
The value for the "optinfo" parameter is defined as follows:
   optinfo = infovalue / qinfovalue

   infovalue       = iana-token / x-name

   qinfovalue      = DQUOTE (infovalue) DQUOTE

del-5. Content Header Fields

Optional content header fields: Any header fields defined by [RFC2045].

del-6. Encoding Considerations

This MIME content type can contain 8bit characters, so the use of quoted-printable or BASE64 MIME content-transfer-encodings might be necessary when iCalendar objects are transferred across protocols restricted to the 7bit repertoire. Note that a text valued property in the content entity can also have content encoding of special characters using a BACKSLASH character (US-ASCII decimal 92) escapement technique. This means that content values can end up encoded twice.

del-7. Security Considerations

SPOOFING:
In this memo, the "Organizer" is the only person authorized to make changes to an existing "VEVENT", "VTODO", "VJOURNAL" calendar component and redistribute the updates to the "Attendees". An iCalendar object that maliciously changes or cancels an existing "VEVENT", "VTODO" or "VJOURNAL" or "VFREEBUSY" calendar component might be constructed by someone other than the "Organizer" and sent to the "Attendees". In addition in this memo, other than the "Organizer", an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL" calendar component is the only other person authorized to update any parameter associated with their "ATTENDEE" property and send it to the "Organizer". An iCalendar object that maliciously changes the "ATTENDEE" parameters can be constructed by someone other than the real "Attendee" and sent to the "Organizer".
PROCEDURAL ALARMS:
An iCalendar object can be created that contains a "VEVENT" and "VTODO" calendar component with "VALARM" calendar components. The "VALARM" calendar component can be of type PROCEDURE and can have an attachment containing some sort of executable program. Implementations that incorporate these types of alarms are subject to any virus or malicious attack that might occur as a result of executing the attachment.
ATTACHMENTS:
An iCalendar object can include references to Uniform Resource Locators that can be programmed resources.
Implementers and users of this memo should be aware of the network security implications of accepting and parsing such information. In addition, the security considerations observed by implementations of electronic mail systems should be followed for this memo.

del-8. Interoperability Considerations

This MIME content type is intended to define a common format for conveying calendaring and scheduling information between different systems. It is heavily based on the earlier [VCAL] industry specification.

del-9. Applications Which Use This Media Type

This content-type is designed for widespread use by Internet calendaring and scheduling applications. In addition, applications in the workflow and document management area might find this content-type applicable. The [RFC2446] and [RFC2447] Internet protocols directly use this content-type also. Future work on an Internet calendar access protocol will utilize this content-type too.

del-10. Additional Information

This memo defines this content-type.

del-11. Magic Numbers

None.

del-12. File Extensions

The file extension of "ics" is to be used to designate a file containing (an arbitrary set of) calendaring and scheduling information consistent with this MIME content type.

The file extension of "ifb" is to be used to designate a file containing free or busy time information consistent with this MIME content type.

Macintosh file type codes: The file type code of "iCal" is to be used in Apple MacIntosh operating system environments to designate a file containing calendaring and scheduling information consistent with this MIME media type.

The file type code of "iFBf" is to be used in Apple MacIntosh operating system environments to designate a file containing free or busy time information consistent with this MIME media type.

del-13. Contact for Further Information

   Frank Dawson
   6544 Battleford Drive
   Raleigh, NC 27613-3502
   919-676-9515 (Telephone)
   919-676-9564 (Data/Facsimile)
   Frank_Dawson@Lotus.com (Internet Mail)

   Derik Stenerson
   One Microsoft Way
   Redmond, WA  98052-6399
   425-936-5522 (Telephone)
   425-936-7329 (Facsimile)
   deriks@microsoft.com (Internet Mail)

del-14. Intended Usage

COMMON

del-15. Authors/Change Controllers

   Frank Dawson
   6544 Battleford Drive
   Raleigh, NC 27613-3502
   919-676-9515 (Telephone)
   919-676-9564 (Data/Facsimile)
   Frank_Dawson@Lotus.com (Internet Mail)

   Derik Stenerson
   One Microsoft Way
   Redmond, WA  98052-6399
   425-936-5522 (Telephone)
   425-936-7329 (Facsimile)
   deriks@microsoft.com (Internet Mail)

3. iCalendar Object Specification

The following sections define the details of a Calendaring and Scheduling Core Object Specification. This information is intended to be an integral part of the MIME content type registration. In addition, this information can be used independent of such content registration. In particular, this memo has direct applicability for use as a calendaring and scheduling exchange format in file-, memory- or network-based transport mechanisms.

3.1. Content Lines

 I  #issue01+4.1_line_folding   (type: change, status: closed)
gsexton@mhsoftware.com2006-05-24 Relax or clarify line folding requirement.
Resolution: Deleted the second sentence in the 2nd paragraph after the example in 4.1 as redundant (it says the exact same thing in the first paragraph). Added a Note.
Associated changes in this document: 3.1, 3.1., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue03+4.1_non-us-ascii_order   (type: edit, status: closed)
lists@block-online.eu2006-05-29 NON-US-ASCII should appear after VALUE-CHAR.
Resolution: Fixed.
Associated changes in this document: 3.1., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue36+4.1_x-name_use   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 The comment for x-name specifies that x-name are not intended for use in released products which is in contradiction with the text in section 4.8.8.1 Non-standard Properties as well as the text in section 7.2 Registration of New Properties.
Resolution: Deleted text.
Associated changes in this document: 3.1., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue53+4.1_NON-US-ASCII   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 ABNF for NON-US-ASCII should be updated for UTF-8.
Resolution: Done.
Associated changes in this document: 3.1., Published in: draft-ietf-calsify-rfc2445bis-04

The iCalendar object is organized into individual lines of text, called content lines. Content lines are delimited by a line break, which is a CRLF sequence (US-ASCII decimal 13, followed by US-ASCII decimal 10).

Lines of text SHOULD NOT be longer than 75 octets, excluding the line break. Long content lines SHOULD be split into a multiple line representations using a line "folding" technique. That is, a long line can be split between any two characters by inserting a CRLF immediately followed by a single linear white space character (i.e., SPACE, US-ASCII decimal 32 or HTAB, US-ASCII decimal 9). Any sequence of CRLF followed immediately by a single linear white space character is ignored (i.e., removed) when processing the content type.

For example the line:

   DESCRIPTION:This is a long description that exists on a long line.

Can be represented as:

   DESCRIPTION:This is a lo
    ng description
     that exists on a long line.

The process of moving from this folded multiple line representation to its single line representation is called "unfolding". Unfolding is accomplished by removing the CRLF character and the linear white space character that immediately follows.

When parsing a content line, folded lines MUST first be unfolded according to the unfolding procedure described above. I When generating a content line, lines longer than 75 octets SHOULD be folded according to the folding procedure described above.  I 

Note: It is possible for very simple implementations to generate improperly folded lines in the middle of a UTF-8 multi-octet sequence. For this reason, implementations need to unfold lines in such a way to properly restore the original sequence.

The content information associated with an iCalendar object is formatted using a syntax similar to that defined by [RFC2425]. That is, the content information consists of CRLF-separated content lines.

The following notation defines the lines of content in an iCalendar object:

   contentline   = name *(";" param ) ":" value CRLF
   ; This ABNF is just a general definition for an initial parsing
   ; of the content line into its property name, parameter list,
   ; and value string

   ; When parsing a content line, folded lines MUST first
   ; be unfolded according to the unfolding procedure
   ; described above. When generating a content line, lines
   ; longer than 75 octets SHOULD be folded according to
   ; the folding procedure described above.

   name          =  I x-name / iana-tokeniana-token / x-name

   iana-token    = 1*(ALPHA / DIGIT / "-")
   ; iCalendar identifier registered with IANA

   x-name        = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
   ;  I ReserveredReserved for experimental use. I  Not intended for use in
   ; released products.

   vendorid      = 3*(ALPHA / DIGIT)
   ; Vendor identification

   param         = param-name "=" param-value *("," param-value)
   ; Each property defines the specific ABNF for the parameters
   ; allowed on the property. Refer to specific properties for
   ; precise parameter ABNF.

   param-name    = iana-token /  I x-tokenx-name

   param-value   = paramtext / quoted-string

   paramtext     = *SAFE-CHAR

   value         = *VALUE-CHAR

   quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
    I    NON-US-ASCII       = %x80-F8
   ; Use restricted by charset parameter
   ; on outer MIME object (UTF-8 preferred)

   QSAFE-CHAR    = WSP / %x21 / %x23-7E / NON-US-ASCII
   ; Any character except  I CTLCONTROL and DQUOTE

   SAFE-CHAR     = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
                 / NON-US-ASCII
   ; Any character except  I CTLCONTROL, DQUOTE, ";", ":", ","

   VALUE-CHAR    = WSP / %x21-7E / NON-US-ASCII
   ; Any textual character

    I NON-US-ASCII  = UTF8-2 / UTF8-3 / UTF8-4
   ; UTF8-2, UTF8-3, and UTF8-4 are defined in [RFC3629]
 I 

   CR            = %x0D
   ; carriage return

   LF            = %x0A
   ; line feed

   CRLF          = CR LF
   ; Internet standard newline
 
    I CTLCONTROL       = %x00-08 / %x0A-1F / %x7F
   ;  I ControlsAll the controls except HTAB I 

   ALPHA         = %x41-5A / %x61-7A   ; A-Z / a-z

   DIGIT         = %x30-39
   ; 0-9

   DQUOTE        = %x22
   ; Quotation Mark

   WSP           = SPACE / HTAB

   SPACE         = %x20

   HTAB          = %x09
 

The property value component of a content line has a format that is property specific. Refer to the section describing each property for a definition of this format.

All names of properties, property parameters, enumerated property values and property parameter values are case-insensitive. However, all other property values are case-sensitive, unless otherwise stated.

3.1.1. List and Field Separators

Some properties and parameters allow a list of values. Values in a list of values MUST be separated by a COMMA character (US-ASCII decimal 44). There is no significance to the order of values in a list. For those parameter values (such as those that specify URI values) that are specified in quoted-strings, the individual quoted- strings are separated by a COMMA character (US-ASCII decimal 44).

Some property values are defined in terms of multiple parts. These structured property values MUST have their value parts separated by a SEMICOLON character (US-ASCII decimal 59).

Some properties allow a list of parameters. Each property parameter in a list of property parameters MUST be separated by a SEMICOLON character (US-ASCII decimal 59).

Property parameters with values containing a COLON  I character (US-ASCII decimal 58), a SEMICOLON  I character (US-ASCII decimal 59) or a COMMA character  I (US-ASCII decimal 44) MUST be placed in quoted text.

For example, in the following properties a SEMICOLON is used to separate property parameters from each other, and a COMMA is used to separate property values in a value list.

   ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT: I MAILTOmailto:
    jsmith@ I host.comexample.com

   RDATE;VALUE=DATE:19970304,19970504,19970704,19970904

3.1.2. Multiple Values

Some properties defined in the iCalendar object can have multiple values. The general rule for encoding multi-valued items is to simply create a new content line for each value, including the property name. However, it should be noted that some properties support encoding multiple values in a single property by separating the values with a COMMA character (US-ASCII decimal 44). Individual property definitions should be consulted for determining whether a specific property allows multiple values and in which of these two forms.

3.1.3. Binary Content

 I  #issue03+4.1.3_content_typo   (type: edit, status: closed)
lists@block-online.eu2006-05-29 "contact" should be changed to "content".
Resolution: Fixed.
Associated changes in this document: 3.1.3, 3.1.3., Published in: draft-ietf-calsify-rfc2445bis-06

Binary content information in an iCalendar object SHOULD be referenced using a URI within a property value. That is the binary content information SHOULD be placed in an external MIME entity that can be referenced by a URI from within the iCalendar object. In applications where this is not feasible, binary  I contactcontent information can be included within an iCalendar object, but only after first encoding it into text using the "BASE64" encoding method defined in  I [RFC2045][RFC4648]. Inline binary  I contactcontent SHOULD only be used in applications whose special circumstances demand that an iCalendar object be expressed as a single entity. A property containing inline binary content information MUST specify the "ENCODING" property parameter. Binary content information placed external to the iCalendar object MUST be referenced by a uniform resource identifier (URI).

The following example specifies an "ATTACH" property that references an attachment external to the iCalendar object with a URI reference:

   ATTACH:http:// I xyz.comexample.com/public/quarterly-report.doc

The following example specifies an "ATTACH" property with inline binary encoded content information:

   ATTACH;FMTTYPE=image/basic;ENCODING=BASE64;VALUE=BINARY:
    MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1U
    EBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIE
      <...remainder of "BASE64" encoded binary data...>

3.1.4. Character Set

 I  #issue31+charset   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-11 Need to clarify which charsets are supported by iCalendar.
Resolution: Specified UTF-8 as the only charset supported by iCalendar. Compliant applications are REQUIRED to accept UTF-8 and US-ASCII. Support for other charset is deprecated.
Associated changes in this document: del-1, 3.1.4, 3.1.4, 3.1.4, 3.1.4, 3.1.4, 3.3.11., Published in: draft-ietf-calsify-rfc2445bis-02

There is not a property parameter to declare the  I character setcharset used in a property value. The default  I character setcharset for an iCalendar  I objectstream is UTF-8 as defined in  I [RFC2279].[RFC3629].

The "charset" Content-Type parameter  I canMUST be used in MIME transports to specify  I any other IANA registered character set.the charset being used.

3.2. Property Parameters

 I  #issue61+ianaparam   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 All properties should allow ianaparam the same way they allow xparam. All components should allow iana-prop the same way they allow x-prop.
Resolution: Changed all ABNF accordingly.
Associated changes in this document: 3.2, 3.2, 3.2, 3.2, 3.2, 3.6, 3.6, 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.6.5, 3.6.5, 3.6.5, 3.6.6, 3.6.6, 3.6.6, 3.7.1, 3.7.1, 3.7.2, 3.7.2, 3.7.3, 3.7.3, 3.7.4, 3.7.4, 3.8.1.1, 3.8.1.1, 3.8.1.2, 3.8.1.2, 3.8.1.3, 3.8.1.3, 3.8.1.4, 3.8.1.4, 3.8.1.5, 3.8.1.5, 3.8.1.6, 3.8.1.6, 3.8.1.7, 3.8.1.7, 3.8.1.8, 3.8.1.8, 3.8.1.9, 3.8.1.9, 3.8.1.10, 3.8.1.10, 3.8.1.11, 3.8.1.11, 3.8.1.12, 3.8.1.12, 3.8.2.1, 3.8.2.1, 3.8.2.2, 3.8.2.2, 3.8.2.3, 3.8.2.3, 3.8.2.4, 3.8.2.4, 3.8.2.5, 3.8.2.5, 3.8.2.6, 3.8.2.6, 3.8.2.7, 3.8.2.7, 3.8.3.1, 3.8.3.1, 3.8.3.2, 3.8.3.2, 3.8.3.3, 3.8.3.3, 3.8.3.4, 3.8.3.4, 3.8.3.5, 3.8.3.5, 3.8.4.1, 3.8.4.1, 3.8.4.2, 3.8.4.2, 3.8.4.3, 3.8.4.3, 3.8.4.4, 3.8.4.4, 3.8.4.5, 3.8.4.5, 3.8.4.6, 3.8.4.6, 3.8.4.7, 3.8.4.7, 3.8.5.1, 3.8.5.1, 3.8.5.2, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.6.1, 3.8.6.1, 3.8.6.2, 3.8.6.2, 3.8.6.3, 3.8.6.3, 3.8.6.3, 3.8.7.1, 3.8.7.1, 3.8.7.2, 3.8.7.2, 3.8.7.3, 3.8.7.3, 3.8.7.4, 3.8.7.4, 3.8.8, 3.8.8.2, 3.8.8.3, 3.8.8.3., Published in: draft-ietf-calsify-rfc2445bis-06

A property can have attributes associated with it. These "property parameters" contain meta-information about the property or the property value. Property parameters are provided to specify such information as the location of an alternate text representation for a property value, the language of a text property value, the  I datavalue type of the property value and other attributes.

Property parameter values that contain the COLON (US-ASCII decimal 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) character separators MUST be specified as quoted-string text values. Property parameter values MUST NOT contain the  I DOUBLE-QUOTEDQUOTE (US-ASCII decimal 22) character. The  I DOUBLE-QUOTEDQUOTE (US-ASCII decimal 22) character is used as a delimiter for parameter values that contain restricted characters or URI text. For example:

   DESCRIPTION;ALTREP="http://www. I wiz.orgexample.org":The Fall'98 Wild
     Wizards Conference - - Las Vegas I \, NV I \, USA

Property parameter values that are not in quoted strings are case insensitive.

The general property parameters defined by this memo are defined by the following notation:

    I icalparameter = altrepparam       ; Alternate text representation
                 / cnparam           ; Common name
                 / cutypeparam       ; Calendar user type
                 / delfromparam      ; Delegator
                 / deltoparam        ; Delegatee
                 / dirparam          ; Directory entry
                 / encodingparam     ; Inline encoding
                 / fmttypeparam      ; Format type
                 / fbtypeparam       ; Free/busy time type
                 / languageparam     ; Language for text
                 / memberparam       ; Group or list membership
                 / partstatparam     ; Participation status I 
                 / rangeparam        ; Recurrence identifier range
                 / trigrelparam      ; Alarm trigger relationship
                 / reltypeparam      ; Relationship type
                 / roleparam         ; Participation role
                 / rsvpparam         ; RSVP expectation
                 / sentbyparam       ; Sent by
                 / tzidparam         ; Reference to time zone object
                 / valuetypeparam    ; Property value data type I 
                 / ianaparam
                 ; Some other IANA registered iCalendar parameter.
                 / xparam
                 ; A non-standard, experimental parameter.
                 / other-param
              
   other-param   = (iana-param / x-param)

   iana I -param  = iana-token "=" param-value *("," param-value)
    I ; Some other IANA registered iCalendar parameter.

   x I -param     = x-name "=" param-value *("," param-value)
    I ; A non-standard, experimental parameter.

 I Applications MUST ignore x-param and iana-param value they don't recognized.

3.2.1. Alternate Text Representation

Parameter Name:
ALTREP
Purpose:
To specify an alternate text representation for the property value.
Format Definition:
 I TheThis property parameter is defined by the following notation:
   altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
Description:
 I TheThis parameter specifies a URI that points to an alternate representation for a textual property value. A property specifying this parameter MUST also include a value that reflects the default representation of the text value. The individual URI parameter values MUST each be specified in a quoted-string.
Example:
     DESCRIPTION;ALTREP="CID: I <part3.msg.970415T083000@ I host.comexample.com I >":
      Project XYZ Review Meeting will include the following agenda
       items: (a) Market Overview I \, (b) Finances I \, (c) Project Man
      agement
The "ALTREP" property parameter value might point to a "text/html" content portion.
     Content-Type:text/html
     Content-Id:<part3.msg.970415T083000@ I host.comexample.com>
      I <html><body>
     <p><b>Project XYZ Review Meeting</b> will include the following
     agenda items:<ol><li>Market
     Overview</li><li>Finances</li><li>Project Management</li></ol></p>
     </body></html>
     <html>
       <head>
        <title></title>
       </head>
       <body>
         <p>
           <b>Project XYZ Review Meeting</b> will include
           the following agenda items:
           <ol>
             <li>Market Overview</li>
             <li>Finances</li>
             <li>Project Management</li>
           </ol>
         </p>
       </body>
     </html>

3.2.2. Common Name

Parameter Name:
CN
Purpose:
To specify the common name to be associated with the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
   cnparam    = "CN" "=" param-value
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the common name to be associated with the calendar user specified by the property. The parameter value is text. The parameter value can be used for display text to be associated with the calendar address specified by the property.
Example:
     ORGANIZER;CN="John Smith": I MAILTOmailto:jsmith@ I host.comexample.com

3.2.3. Calendar User Type

Parameter Name:
CUTYPE
Purpose:
To specify the type of calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     cutypeparam        = "CUTYPE" "="
                        ("INDIVIDUAL"   ; An individual
                       / "GROUP"        ; A group of individuals
                       / "RESOURCE"     ; A physical resource
                       / "ROOM"         ; A room resource
                       / "UNKNOWN"      ; Otherwise not known
                       / x-name         ; Experimental type
                       / iana-token)    ; Other IANA registered
                                        ; type
     ; Default is INDIVIDUAL
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the type of calendar user specified by the property. If not specified on a property that allows this parameter, the default is INDIVIDUAL.  I Applications MUST treat x-name and iana-token value they don't recognized the same way as the INDIVIDUAL value.
Example:
     ATTENDEE;CUTYPE=GROUP: I MAILTOmailto:ietf-calsch@ I imc.orgexample.org

3.2.4. Delegators

Parameter Name:
DELEGATED-FROM
Purpose:
To specify the calendar users that have delegated their participation to the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     delfromparam       = "DELEGATED-FROM" "=" DQUOTE cal-address
                           DQUOTE *("," DQUOTE cal-address DQUOTE)
 I  #issue03+4.2.4_users_typo   (type: edit, status: closed)
lists@block-online.eu2006-05-29 "uses" should be changed to "users".
Resolution: Fixed.
Associated changes in this document: 3.2.4., Published in: draft-ietf-calsify-rfc2445bis-01
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type.  I This parameter can be specified on a property that has a value type of calendar address. This parameter specifies those calendar  I usesusers that have delegated their participation in a group scheduled event or to-do to the calendar user specified by the property. The value MUST be a  I MAILTOmailto URI as defined in  I [RFC1738][RFC2368]. The individual calendar address parameter values MUST each be specified in a quoted-string.
Example:
     ATTENDEE;DELEGATED-FROM=" I MAILTOmailto:jsmith@ I host.comexample.com": I MAILTOmailto:
      jdoe@ I host.comexample.com

3.2.5. Delegatees

Parameter Name:
DELEGATED-TO
Purpose:
To specify the calendar users to whom the calendar user specified by the property has delegated participation.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE
                  *("," DQUOTE cal-address DQUOTE)
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. This parameter specifies those calendar users whom have been delegated participation in a group scheduled event or to-do by the calendar user specified by the property. The value MUST be a  I MAILTOmailto URI as defined in  I [RFC1738][RFC2368]. The individual calendar address parameter values MUST each be specified in a quoted-string.
Example:
     ATTENDEE;DELEGATED-TO=" I MAILTOmailto:jdoe@ I host.comexample.com"," I MAILTOmailto:jqpublic
      @ I host.comexample.com": I MAILTOmailto:jsmith@ I host.comexample.com

3.2.6. Directory Entry Reference

Parameter Name:
DIR
Purpose:
To specify reference to a directory entry associated with the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     dirparam   = "DIR" "=" DQUOTE uri DQUOTE
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies a reference to the directory entry associated with the calendar user specified by the property. The parameter value is a URI. The  I individual URI parameter  I valuesvalue MUST  I each be specified in a quoted-string.
Example:
     ORGANIZER;DIR="ldap:// I host.comexample.com:6666/o= I eDABC%20Industries,
      c= I 3DUS I ???(cn= I 3DBJim%20Dolittle)": I MAILTOmailto:jimdo@ I host1.comexample.com

3.2.7. Inline Encoding

Parameter Name:
ENCODING
Purpose:
To specify an alternate inline encoding for the property value.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     encodingparam      = "ENCODING" "="
                        ( "8BIT"
        ; "8bit" text encoding is defined in [RFC2045]
                        / "BASE64"
        ; "BASE64" binary encoding format is defined in  I [RFC2045][RFC4648] I 
                        / iana-token
        ; Some other IANA registered iCalendar encoding type
                        / x-name)
        ; A non-standard, experimental encoding type
                        )
Description:
 I TheThis property parameter identifies the inline encoding used in a property value. The default encoding is "8BIT", corresponding to a property value consisting of text. The "BASE64" encoding type corresponds to a property value encoded using the "BASE64" encoding defined in [RFC2045].
If the value type parameter is ";VALUE=BINARY", then the inline encoding parameter MUST be specified with the value ";ENCODING=BASE64".
Example:
     ATTACH;FMTYPE=IMAGE/JPEG;ENCODING=BASE64;VALUE=BINARY:MIICajC
      CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
      qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw
      <...remainder of "BASE64" encoded binary data...>

3.2.8. Format Type

Parameter Name:
FMTTYPE
Purpose:
To specify the content type of a referenced object.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     fmttypeparam = "FMTTYPE" "="  I iana-token
                                        ; A IANA registered content type
                                     / x-name
                                     ; A non-standard content typetype "/" subtype *(";" parameter)
                     ; Where "type", "subtype", and "parameter"
                     ; are defined in section 5.1 of [RFC2045]
Description:
This parameter can be specified on properties that are used to reference an object. The parameter specifies the content type of the referenced object. For example, on the "ATTACH" property, a FTP type URI value does not, by itself, necessarily convey the type of content associated with the resource. The parameter value MUST be the  I TEXTtext for either an IANA registered  I contentmedia type or a non-standard  I contentmedia type.
Example:
     ATTACH;FMTTYPE= I application/binaryapplication/msword:ftp:// I domain.comexample.com/pub/docs/
      agenda.doc

3.2.9. Free/Busy Time Type

Parameter Name:
FBTYPE
Purpose:
To specify the free or busy time type.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     fbtypeparam        = "FBTYPE" "=" ("FREE" / "BUSY"
                        / "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
                        / x-name
              ; Some experimental iCalendar  I datafree busy type.
                        / iana-token)
              ; Some other IANA registered iCalendar  I datafree busy type.
Description:
 I TheThis parameter specifies the free or busy time type. The value FREE indicates that the time interval is free for scheduling. The value BUSY indicates that the time interval is busy because one or more events have been scheduled for that interval. The value BUSY-UNAVAILABLE indicates that the time interval is busy and that the interval can not be scheduled. The value BUSY-TENTATIVE indicates that the time interval is busy because one or more events have been tentatively scheduled for that interval. If not specified on a property that allows this parameter, the default is BUSY.  I Applications MUST treat x-name and iana-token value they don't recognized the same way as the BUSY value.
Example:
The following is an example of this parameter on a  I "FREEBUSY I " property.
     FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z

3.2.10. Language

 I  #issue35+4.2.10_language_desc   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 The text should not specify that the LANGUAGE parameter can be specified on properties with a TEXT value type. The "ATTENDEE" and "ORGANIZER" properties which have a "CAL-ADDRESS" value type both allow the "LANGUAGE" parameter.
Resolution: Removed the first sentence of the Description.
Associated changes in this document: 3.2.10, 3.2.10, 3.2.10, 3.2.10., Published in: draft-ietf-calsify-rfc2445bis-06

Parameter Name:
LANGUAGE
Purpose:
To specify the language for text values in a property or property parameter.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     languageparam = "LANGUAGE" "=" language

     language =  I <Text identifying a language, as defined in [RFC1766]>Language-Tag
                ; As defined in [RFC4646]
Description:
 I This parameter can be specified on properties with a text value type. TheThis parameter identifies the language of the text in the property  I orvalue and of all property parameter value I s of the property. The value of the  I "language""LANGUAGE" property parameter is that defined in  I [RFC1766][RFC4646].
For transport in a MIME entity, the Content-Language header field can be used to set the default language for the entire body part. Otherwise, no default language is assumed.
Example:
 I The following are examples of this parameter on the "SUMMARY" and "LOCATION" properties:
     SUMMARY;LANGUAGE=us-EN:Company Holiday Party

     LOCATION;LANGUAGE=en:Germany

     LOCATION;LANGUAGE=no:Tyskland
 I The following example makes use of the Quoted-Printable encoding in order to represent non-ASCII characters.
     LOCATION;LANGUAGE=da:K=F8benhavn
     LOCATION;LANGUAGE=en:Copenhagen

3.2.11. Group or List Membership

Parameter Name:
MEMBER
Purpose:
To specify the group or list membership of the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     memberparam        = "MEMBER" "=" DQUOTE cal-address DQUOTE
                          *("," DQUOTE cal-address DQUOTE)
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the groups or list membership for the calendar user specified by the property. The parameter value  I is either a single calendar address in a quoted-string or a COMMA character (US-ASCII decimal 44)  I separated list of calendar addresses, each in a quoted-string. The individual calendar address parameter values MUST each be specified in a quoted-string.
Example:
     ATTENDEE;MEMBER=" I MAILTOmailto:ietf-calsch@ I imc.orgexample.org": I MAILTOmailto:
      jsmith@ I host.comexample.com

     ATTENDEE;MEMBER=" I MAILTOmailto:projectA@ I host.comexample.com"," I MAILTOmailto:pr
      ojectB@ I host.comexample.com": I MAILTOmailto:janedoe@ I host.comexample.com

3.2.12. Participation Status

Parameter Name:
PARTSTAT
Purpose:
To specify the participation status for the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     partstatparam    = "PARTSTAT" "="  I 
                       (partstat-event
                      / partstat-todo
                      / partstat-jour)

     partstat-event   = ("NEEDS-ACTION"    ; Event needs action
                      / "ACCEPTED"         ; Event accepted
                      / "DECLINED"         ; Event declined
                      / "TENTATIVE"        ; Event tentatively
                                           ; accepted
                      / "DELEGATED"        ; Event delegated
                      / x-name             ; Experimental status
                      / iana-token)        ; Other IANA registered
                                           ; status
     ; These are the participation statuses for a "VEVENT".
     ; Default is NEEDS-ACTION.

      I partstatparam      /= "PARTSTAT" "="partstat-todo    = ("NEEDS-ACTION"    ; To-do needs action
                      / "ACCEPTED"         ; To-do accepted
                      / "DECLINED"         ; To-do declined
                      / "TENTATIVE"        ; To-do tentatively
                                           ; accepted
                      / "DELEGATED"        ; To-do delegated
                      / "COMPLETED"        ; To-do completed.
                                           ; COMPLETED property has
                                           ; date/time completed.
                      / "IN-PROCESS"       ; To-do in process of
                                           ; being completed
                      / x-name             ; Experimental status
                      / iana-token)        ; Other IANA registered
                                           ; status
     ; These are the participation statuses for a "VTODO".
     ; Default is NEEDS-ACTION.

      I partstatparam      /= "PARTSTAT" "="partstat-jour    = ("NEEDS-ACTION"    ; Journal needs action
                      / "ACCEPTED"         ; Journal accepted
                      / "DECLINED"         ; Journal declined
                      / x-name             ; Experimental status
                      / iana-token)        ; Other IANA registered
                                           ; status
     ; These are the participation statuses for a "VJOURNAL".
     ; Default is NEEDS-ACTION.
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the participation status for the calendar user specified by the property value. The parameter values differ depending on whether they are associated with a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST match one of the values allowed for the given calendar component. If not specified on a property that allows this parameter, the default value is NEEDS-ACTION.  I Applications MUST treat x-name and iana-token value they don't recognized the same way as the NEEDS-ACTION value.
Example:
     ATTENDEE;PARTSTAT=DECLINED: I MAILTOmailto:jsmith@ I host.comexample.com
 I  

del-16. Recurrence Identifier Range

Parameter Name:
RANGE
Purpose:
To specify the effective range of recurrence instances from the instance specified by the recurrence identifier specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
         rangeparam = "RANGE" "=" ("THISANDPRIOR"
         ; To specify all instances prior to the recurrence identifier
                                 / "THISANDFUTURE")
         ; To specify the instance specified by the recurrence identifier
         ; and all subsequent recurrence instances
Description:
 I TheThis parameter can be specified on a property that specifies a recurrence identifier. The parameter specifies the effective range of recurrence instances that is specified by the property. The effective range is from the recurrence  I identifiedidentifier specified by the property. If this parameter is not specified an allowed property, then the default range is the single instance specified by the recurrence identifier value of the property. The parameter value can be "THISANDPRIOR" to indicate a range defined by the recurrence identified value of the property and all prior instances. The parameter value can also be "THISANDFUTURE" to indicate a range defined by the recurrence identifier and all subsequent instances.
Example:
         RECURRENCE-ID;RANGE=THISANDPRIOR:19980401T133000Z
    

3.2.13. Alarm Trigger Relationship

Parameter Name:
RELATED
Purpose:
To specify the relationship of the alarm trigger with respect to the start or end of the calendar component.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     trigrelparam       = "RELATED" "="
                         ("START"       ; Trigger off of start
                        / "END")        ; Trigger off of end
Description:
 I TheThis parameter can be specified on properties that specify an alarm trigger with a  I "DURATION I " value type. The parameter specifies whether the alarm will trigger relative to the start or end of the calendar component. The parameter value START will set the alarm to trigger off the start of the calendar component; the parameter value END will set the alarm to trigger off the end of the calendar component. If the parameter is not specified on an allowable property, then the default is START.
Example:
     TRIGGER;RELATED=END:PT5M

3.2.14. Relationship Type

Parameter Name:
RELTYPE
Purpose:
To specify the type of hierarchical relationship associated with the calendar component specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     reltypeparam       = "RELTYPE" "="
                         ("PARENT"    ; Parent relationship. Default.
                        / "CHILD"     ; Child relationship
                        / "SIBLING I "   ; Sibling relationship
                        / iana-token  ; Some other IANA registered
                                      ; iCalendar relationship type
                        / x-name)     ; A non-standard, experimental
                                      ; relationship type
Description:
This parameter can be specified on a property that references another related calendar. The parameter specifies the hierarchical relationship type of the calendar component referenced by the property. The parameter value can be PARENT, to indicate that the referenced calendar component is a superior of calendar component; CHILD to indicate that the referenced calendar component is a subordinate of the calendar component; SIBLING to indicate that the referenced calendar component is a peer of the calendar component. If this parameter is not specified on an allowable property, the default relationship type is PARENT.  I Applications MUST treat x-name and iana-token value they don't recognized the same way as the PARENT value.
Example:
     RELATED-TO;RELTYPE=SIBLING: I <19960401-080045-4000F192713@
       I host.comexample.com I >

3.2.15. Participation Role

Parameter Name:
ROLE
Purpose:
To specify the participation role for the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     roleparam  = "ROLE" "="
                 ("CHAIR"             ; Indicates chair of the
                                      ; calendar entity
                / "REQ-PARTICIPANT"   ; Indicates a participant whose
                                      ; participation is required
                / "OPT-PARTICIPANT"   ; Indicates a participant whose
                                      ; participation is optional
                / "NON-PARTICIPANT"   ; Indicates a participant who
                                      ; is copied for information
                                      ; purposes only
                / x-name              ; Experimental role
                / iana-token)         ; Other IANA role
     ; Default is REQ-PARTICIPANT
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the participation role for the calendar user specified by the property in the group schedule calendar component. If not specified on a property that allows this parameter, the default value is REQ-PARTICIPANT.  I Applications MUST treat x-name and iana-token value they don't recognized the same way as the REQ-PARTICIPANT value.
Example:
     ATTENDEE;ROLE=CHAIR: I MAILTOmailto:mrbig@ I host.comexample.com

3.2.16. RSVP Expectation

Parameter Name:
RSVP
Purpose:
To specify whether there is an expectation of a favor of a reply from the calendar user specified by the property value.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
     ; Default is FALSE
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the expectation of a reply from the calendar user specified by the property value. This parameter is used by the "Organizer" to request a participation status reply from an "Attendee" of a group scheduled event or to-do. If not specified on a property that allows this parameter, the default value is FALSE.
Example:
     ATTENDEE;RSVP=TRUE: I MAILTOmailto:jsmith@ I host.comexample.com

3.2.17. Sent By

Parameter Name:
SENT-BY
Purpose:
To specify the calendar user that is acting on behalf of the calendar user specified by the property.
Format Definition:
 I TheThis property parameter is defined by the following notation:
     sentbyparam        = "SENT-BY" "=" DQUOTE cal-address DQUOTE
Description:
This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter specifies the calendar user that is acting on behalf of the calendar user specified by the property. The parameter value MUST be a  I MAILTOmailto URI as defined in  I [RFC1738][RFC2368]. The individual calendar address parameter values MUST each be specified in a quoted-string.
Example:
     ORGANIZER;SENT-BY I :=" I MAILTOmailto:sray@ I host.comexample.com": I MAILTOmailto:
      jsmith@ I host.comexample.com

3.2.18. Time Zone Identifier

 I  tzid_and_date_values   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-06-27 We need to clarify that the TZID property parameter MUST NOT be applied to DATE properties.
2007-07-04Resolution: Done.
Associated changes in this document: 3.2.18.

Parameter Name:
TZID
Purpose:
To specify the identifier for the time zone definition for a time component in the property value.
Format Definition:
This property parameter is defined by the following notation:
     tzidparam  = "TZID" "=" [tzidprefix] paramtext I  CRLF

     tzidprefix = "/"
Description:
 I TheThis parameter MUST be specified on the "DTSTART", "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE-TIME or TIME value type is specified and when the value is not either a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type definition for a description of UTC and "floating time" formats. This property parameter specifies a text value which uniquely identifies the "VTIMEZONE" calendar component to be used when evaluating the time portion of the property. The value of the  I "TZID I " property parameter will be equal to the value of the  I "TZID I " property for the matching time zone definition. An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object.
The parameter MUST be specified on properties with a DATE-TIME value if the DATE-TIME is not either a UTC or a "floating" time.
The presence of the SOLIDUS character (US-ASCII decimal 47) as a prefix, indicates that this  I "TZID I " represents a unique ID in a globally defined time zone registry (when such registry is defined).
Note: This document does not define a naming convention for time zone identifiers. Implementers may want to use the naming conventions defined in existing time zone specifications such as the public-domain  I Olson databaseTZ database [TZDB]. The specification of globally unique time zone identifiers is not addressed by this document and is left for future study.
The following are examples of this property parameter:
     DTSTART;TZID= I US-EasternAmerica/New_York:19980119T020000

     DTEND;TZID= I US-EasternAmerica/New_York:19980119T030000
The  I "TZID I " property parameter MUST NOT be applied to  I DATE properties, and DATE-TIME or TIME properties whose time values are specified in UTC.
The use of local time in a DATE-TIME or TIME value without the  I "TZID I " property parameter is to be interpreted as a local time value, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
For more information see the sections on the  I datavalue types DATE-TIME and TIME.

3.2.19. Value Data Types

 I  unrecognized_value   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-07-07 Should specify that unrecognized VALUE MUST (instead of SHOULD) be treated like TEXT.
Associated changes in this document: 3.2, 3.2.3, 3.2.9, 3.2.12, 3.2.14, 3.2.15, 3.2.19, 3.6, 3.8.1.3, 3.8.6.1, 5.

Parameter Name:
VALUE
Purpose:
To explicitly specify the  I datavalue type format for a property value.
Format Definition:
 I The "VALUE"This property parameter is defined by the following notation:
     valuetypeparam = "VALUE" "=" valuetype

     valuetype  = ("BINARY"
                / "BOOLEAN"
                / "CAL-ADDRESS"
                / "DATE"
                / "DATE-TIME"
                / "DURATION"
                / "FLOAT"
                / "INTEGER"
                / "PERIOD"
                / "RECUR"
                / "TEXT"
                / "TIME"
                / "URI"
                / "UTC-OFFSET"
                / x-name
                ; Some experimental iCalendar  I datavalue type.
                / iana-token)
                ; Some other IANA registered iCalendar  I datavalue type.
Description:
 I The "VALUE"This parameter specifies the  I datavalue type and format of the property value. The property values MUST be of a single value type. For example, a "RDATE" property cannot have a combination of DATE-TIME and TIME value types.
If the property's value is the default value type, then this parameter need not be specified. However, if the property's default value type is overridden by some other allowable value type, then this parameter MUST be specified.
 I Applications MUST treat x-name and iana-token value they don't recognized the same way as the TEXT value.

3.3. Property Value Data Types

The properties in an iCalendar object are strongly typed. The definition of each property restricts the value to be one of the value data types, or simply value types, defined in this section. The value type for a property will either be specified implicitly as the default value type or will be explicitly specified with the "VALUE" parameter. If the value type of a property is one of the alternate valid types, then it MUST be explicitly specified with the "VALUE" parameter.

3.3.1. Binary

Value Name:
BINARY
Purpose:
This value type is used to identify properties that contain a character encoding of inline binary data. For example, an inline attachment of  I an object codea document might be included in an iCalendar object.
Format Definition:
 I TheThis value type is defined by the following notation:
     binary     = *(4b-char) [b-end]
     ; A "BASE64" encoded character string, as defined by  I [RFC2045][RFC4648].

     b-end      = (2b-char "==") / (3b-char "=")

     b-char = ALPHA / DIGIT / "+" / "/"
Description:
Property values with this value type MUST also include the inline encoding parameter sequence of ";ENCODING=BASE64". That is, all inline binary data MUST first be character encoded using the "BASE64" encoding method defined in [RFC2045]. No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following is an abridged example of a "BASE64" encoded binary value data.
      I ATTACH;VALUE=BINARY;ENCODING=BASE64:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlI
      ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv
        <...remainder of "BASE64" encoded binary data...>

3.3.2. Boolean

Value Name:
BOOLEAN
Purpose:
This value type is used to identify properties that contain either a "TRUE" or "FALSE" Boolean value.
Format Definition:
 I TheThis value type is defined by the following notation:
     boolean    = "TRUE" / "FALSE"
Description:
These values are case insensitive text. No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following is an example of a hypothetical property that has a BOOLEAN value type:
      I GIBBERISH:TRUE

3.3.3. Calendar User Address

Value Name:
CAL-ADDRESS
Purpose:
This value type is used to identify properties that contain a calendar user address.
Format Definition:
 I TheThis value type is  I as defined by the following notation:
     cal-address        = uri
Description:
The value is a URI as defined by  I [RFC1738][RFC3986] or any other IANA registered form for a URI. When used to address an Internet email transport address for a calendar user, the value MUST be a  I MAILTOmailto URI, as defined by  I [RFC1738][RFC2368]. No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
   I ATTENDEE: I MAILTOmailto:jane_doe@ I host.comexample.com

3.3.4. Date

Value Name:
DATE
Purpose:
This value type is used to identify values that contain a calendar date.
Format Definition:
 I TheThis value type is defined by the following notation:
     date               = date-value

     date-value         = date-fullyear date-month date-mday
     date-fullyear      = 4DIGIT
     date-month         = 2DIGIT        ;01-12
     date-mday          = 2DIGIT        ;01-28, 01-29, 01-30, 01-31
                                        ;based on month/year
Description:
If the property permits, multiple "date" values are specified as a COMMA character (US-ASCII decimal 44) separated list of values. The format for the value type is  I expressed asbased on the  I [ISO.8601.1988][ISO.8601.2004] complete representation, basic format for a calendar date. The textual format specifies a four-digit year, two-digit month, and two-digit day of the month. There are no separator characters between the year, month and day component text.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following represents July 14, 1997:
     19970714

3.3.5. Date-Time

 I  #issue68+ambiguous_date_time   (type: change, status: closed)
lennox@cs.columbia.edu Need to clarify handling of ambiguous DATE-TIME values.
Associated changes in this document: 3.3.5.

Value Name:
DATE-TIME
Purpose:
This value type is used to identify values that specify a precise calendar date and time of day.
Format Definition:
 I TheThis value type is defined by the following notation:
     date-time  = date "T" time ;As specified in the date and time
                                ;value definitions
Description:
If the property permits, multiple "date-time" values are specified as a COMMA character (US-ASCII decimal 44) separated list of values. No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
The "DATE-TIME"  I datavalue type is used to identify values that contain a precise calendar date and time of day. The format is based on the  I [ISO.8601.1988][ISO.8601.2004] complete representation, basic format for a calendar date and time of day. The text format is a concatenation of the "date", followed by the LATIN CAPITAL LETTER T character (US-ASCII decimal 84) time designator, followed by the "time" format.
The "DATE-TIME"  I datavalue type expresses time values in three forms:
The form of date and time with UTC offset MUST NOT be used. For example, the following is not valid for a date-time value:
      I DTSTART:19980119T230000-0800       ;Invalid time format
FORM #1: DATE WITH LOCAL TIME
The date with local time form is simply a date-time value that does not contain the UTC designator nor does it reference a time zone. For example, the following represents  I JanuraryJanuary 18, 1998, at 11 PM:
      I DTSTART:19980118T230000
Date-time values of this type are said to be "floating" and are not bound to any time zone in particular. They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from 11:00 AM to 1:00 PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. The recipient of an iCalendar object with a property value consisting of a local time, without any relative time zone information, SHOULD interpret the value as being fixed to whatever time zone the  I "ATTENDEE I " is in at any given moment. This means that two  I ATTENDEEs,"Attendees", in different time zones, receiving the same event definition as a floating time, may be participating in the event at different actual times. Floating time SHOULD only be used where that is the reasonable behavior.
In most cases, a fixed time is desired. To properly communicate a fixed time in a property value, either UTC time or local time with time zone reference MUST be specified.
The use of local time in a DATE-TIME value without the  I "TZID I " property parameter is to be interpreted as floating time, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
FORM #2: DATE WITH UTC TIME
The date with UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z suffix character (US-ASCII decimal 90), the UTC designator, appended to the time value. For example, the following represents January 19, 1998, at 0700 UTC:
      I DTSTART:19980119T070000Z
The  I "TZID I " property parameter MUST NOT be applied to DATE-TIME properties whose time values are specified in UTC.
FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE
The date and local time with reference to time zone information is identified by the use the  I "TZID I " property parameter to reference the appropriate time zone definition.  I "TZID I " is discussed in detail in  I the section on Time ZoneSection 3.2.18. For example, the following represents 2 I :00 A I .M I . in New York on Janurary 19, 1998:
      I DTSTART:TZID= I US-EasternAmerica/New_York:19980119T020000
 I If, based on the definition of the referenced time zone, the local time described occurs more than once (when changing from daylight to standard time), the DATE-TIME value refers to the first occurence of the referenced time. Thus, TZID=America/New_York:20071104T013000 indicates November 4, 2007 at 1:30 A.M. EDT (UTC-04:00). If the local time described does not occur (when changing from standard to daylight time), the DATE-TIME value is interpreted using the UTC offset before the gap in local times. Thus, TZID=America/New_York:20070311T023000 indicates March 11, 2007 at 3:30 A.M. EDT (UTC-04:00), one hour after 1:30 A.M. EST (UTC-05:00).
 I A time value MUST only specify the second 60 when specifying a positive leap second. For example:
     19970630T235960Z
Implementations which do not support leap seconds SHOULD interpret the second 60 as equivalent to the second 59.
Example:
The following represents July 14, 1997, at 1:30 PM in New York City in each of the three time formats, using the "DTSTART" property.
     DTSTART:19970714T133000                   ; Local time
     DTSTART:19970714T173000Z                  ; UTC time
     DTSTART;TZID= I US-EasternAmerica/New_York:19970714T133000
                                               ; Local time and time
                                               ; zone reference
 I A time value MUST ONLY specify 60 seconds when specifying the periodic "leap second" in the time value. For example:
      I COMPLETED:19970630T235960Z

3.3.6. Duration

 I  #issue08+4.3.6_nominal_duration   (type: change, status: closed)
reinhold@kainhofer.com Need to clarify how to compute the exact duration of a nominal duration.
Resolution: Time discontinuities must be taken into account. Greatest order time component must be added first.
Associated changes in this document: 3.3.6, 3.3.6, 3.3.6.

Value Name:
DURATION
Purpose:
This value type is used to identify properties that contain a duration of time.
Format Definition:
 I TheThis value type is defined by the following notation:
     dur-value  = (["+"] / "-") "P" (dur-date / dur-time / dur-week)

     dur-date   = dur-day [dur-time]
     dur-time   = "T" (dur-hour / dur-minute / dur-second)
     dur-week   = 1*DIGIT "W"
     dur-hour   = 1*DIGIT "H" [dur-minute]
     dur-minute = 1*DIGIT "M" [dur-second]
     dur-second = 1*DIGIT "S"
     dur-day    = 1*DIGIT "D"
Description:
If the property permits, multiple "duration" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values. The format is  I expressed asbased on the  I [ISO.8601.1988][ISO.8601.2004]  I complete representation basic format  I with designators for the duration of time. The format can represent  I durations in terms of weeks, days, hours, minutes, and seconds.nominal durations (weeks and days) and accurate durations (hours, minutes, and seconds).  I Note that unlike [ISO.8601.2004] this value type doesn't support the "Y" and "M" designators to specify durations in terms of years and months.
 I The duration of a week or a day depends on its position in the calendar. In the case of discontinuities in the time scale, such as the change from standard time to daylight time and back, the computation of the exact duration requires the substraction or addition of the change of duration of the discontinuity.  I Leap seconds MUST NOT be considered when computing an exact duration.  I When computing an exact duration, the greatest order time components MUST be added first, that is, the number of weeks MUST be added first, followed by the number of days, number of hours, number of minutes, and number of seconds.
Negative durations are typically used to schedule an alarm to trigger before an associated time (see Section 3.8.6.3).
No additional content value encoding (i.e., BACKSLASH character encoding) are defined for this value type.
Example:
A duration of 15 days, 5 hours and 20 seconds would be:
     P15DT5H0M20S
A duration of 7 weeks would be:
     P7W

3.3.7. Float

Value Name:
FLOAT
Purpose:
This value type is used to identify properties that contain a real number value.
Format Definition:
 I TheThis value type is defined by the following notation:
     float      = (["+"] / "-") 1*DIGIT ["." 1*DIGIT]
Description:
If the property permits, multiple "float" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
     1000000.0000001
     1.333
     -3.14

3.3.8. Integer

Value Name:
INTEGER
Purpose:
This value type is used to identify properties that contain a signed integer value.
Format Definition:
 I TheThis value type is defined by the following notation:
     integer    = (["+"] / "-") 1*DIGIT
Description:
If the property permits, multiple "integer" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values. The valid range for "integer" is -2147483648 to 2147483647. If the sign is not specified, then the value is assumed to be positive.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
     1234567890
     -1234567890
     +1234567890
     432109876

3.3.9. Period of Time

Value Name:
PERIOD
Purpose:
This value type is used to identify values that contain a precise period of time.
Format Definition:
 I The dataThis value type is defined by the following notation:
     period     = period-explicit / period-start

     period-explicit = date-time "/" date-time
     ;  I [ISO.8601.1988][ISO.8601.2004] complete representation basic format for a
     ; period of time consisting of a start and end. The start MUST
     ; be before the end.

     period-start = date-time "/" dur-value
     ;  I [ISO.8601.1988][ISO.8601.2004] complete representation basic format for a
     ; period of time consisting of a start and positive duration
     ; of time.
Description:
If the property permits, multiple "period" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values. There are two forms of a period of time. First, a period of time is identified by its start and its end. This format is  I expressed asbased on the  I [ISO.8601.1988][ISO.8601.2004] complete representation, basic format for "DATE-TIME" start of the period, followed by a SOLIDUS character (US-ASCII decimal 47), followed by the "DATE-TIME" of the end of the period. The start of the period MUST be before the end of the period. Second, a period of time can also be defined by a start and a positive duration of time. The format is  I expressed asbased on the  I [ISO.8601.1988][ISO.8601.2004] complete representation, basic format for the "DATE-TIME" start of the period, followed by a SOLIDUS character (US-ASCII decimal 47), followed by the  I [ISO.8601.1988][ISO.8601.2004] basic format for "DURATION" of the period.
Example:
The period starting at 18:00:00 UTC, on January 1, 1997 and ending at 07:00:00 UTC on January 2, 1997 would be:
     19970101T180000Z/19970102T070000Z
The period start at 18:00:00 on January 1, 1997 and lasting 5 hours and 30 minutes would be:
     19970101T180000Z/PT5H30M
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.

3.3.10. Recurrence Rule

 I  #issue13+dtstart_and_count   (type: change, status: closed)
reinhold@kainhofer.com2006-06-03 Is the first instance defined by DTSTART always considered as part of the COUNT of a recurrence rule?
2006-10-20Resolution: Specify that in a recurring component, the value of the DTSTART property SHOULD match the pattern of the recurrence rule.
Associated changes in this document: 3.3.10, 3.8.5.1, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue14+dtstart/dtend_meaning   (type: change, status: closed)
reinhold@kainhofer.com2006-06-03 Meaning of DTSTART/DTEND in recurring component.
2006-10-22Resolution: See issue 13 and issue 25.
 I  #issue11+4.3.10_byxxx_rule_part_examples   (type: change, status: open)
reinhold@kainhofer.com2006-06-03 We should add more BYXXX rule parts examples.
Resolution:
Associated changes in this document: 3.3.10, 3.3.10, 3.3.10, 3.3.10, 3.3.10.
 I  #issue16+4.3.10_ignored_rule_parts   (type: change, status: closed)
reinhold@kainhofer.com2006-06-03 Clarify what it means to ignore BYxxx rule part values which are beyond the available scope and provide an example.
Resolution: Done.
Associated changes in this document: 3.3.10, 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue24+multiple_rules   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 Need to clarify number of recurrence instances generated when multiple recurrence rules are specified.
2006-10-22Resolution: Recurring components SHOULD only have one "RRULE" property.
Associated changes in this document: 3.3.10, 3.6.1, 3.6.1, 3.6.2, 3.6.2, 3.6.3, 3.6.3, 3.6.5, 3.6.5, 3.8.5.1, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-03
 I  #issue23+4.3.10_until_rule_part   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 We need to clarify that the UNTIL rule part MUST specify a value of the same type as the value specified by DTSTART.
Resolution: Done.
Associated changes in this document: 3.3.10, 3.3.10, 3.3.10, 3.3.10., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue25+exrule_and_dtstart   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 Is the first instance defined by DTSTART always excluded by EXRULE?
2006-10-22Resolution: Deprecate the EXRULE property.
Associated changes in this document: 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.8.5.1, 3.8.5.1, 3.8.5.1, 3.8.5.1, 3.8.5, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.2, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.5.3, 3.8.7.4., Published in: draft-ietf-calsify-rfc2445bis-03
 I  #issue26+byhour_byminute_bysecond   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 How should the BYHOUR, BYMINUTE and BYSECOND rule parts be handled when DTSTART is a DATE value?
2006-10-23Resolution: Specified that these rule part MUST NOT be specified when "DTSTART" is a DATE, and that they MUST be ignored when present.
Associated changes in this document: 3.3.10., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue52+4.3.10_x-name_rule_part   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-10-12 "x-name" should be removed from the "recur" rule part definition. It should be sufficient to allow xparam on properties of RECUR value type.
Resolution: See text change for #issue56+4.3.10_recur_rule_parts_order.
 I  #issue56+4.3.10_recur_rule_parts_order   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 In section 4.3.10 Recurrence Rule of RFC 2445 it says: "The rule parts are not ordered in any particular sequence." On the other hand, the way the ABNF of the "recur" rule is written, the "FREQ" rule should always appear first.
Resolution: Changed ABNF to allow rule part in any order.
Associated changes in this document: 3.3.10, 3.3.10., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue69+ambiguous_date_time_in_recur   (type: change, status: closed)
lennox@cs.columbia.edu Need to clarify handling of ambiguous DATE-TIME values.
Associated changes in this document: 3.3.10.
 I  #issue81+3.3.10_bysetpos_and_byxxx   (type: change, status: closed)
lennox@cs.columbia.edu2006-11-05 The meaning of "the set of events specified by the rule" is very unclear.
Resolution: Added text that was proposed by Eric Busboom back in 2001.
Associated changes in this document: 3.3.10.

Value Name:
RECUR
Purpose:
This value type is used to identify properties that contain a recurrence rule specification.
Format Definition:
 I TheThis value type is defined by the following notation:
 I 
     recur      = "FREQ"=freq *(

                ; either UNTIL or COUNT may appear in a 'recur',
                ; but UNTIL and COUNT MUST NOT occur in the same 'recur'

                ( ";" "UNTIL" "=" enddate ) /
                ( ";" "COUNT" "=" 1*DIGIT ) /

                ; the rest of these keywords are optional,
                ; but MUST NOT occur more than once

                ( ";" "INTERVAL" "=" 1*DIGIT )          /
                ( ";" "BYSECOND" "=" byseclist )        /
                ( ";" "BYMINUTE" "=" byminlist )        /
                ( ";" "BYHOUR" "=" byhrlist )           /
                ( ";" "BYDAY" "=" bywdaylist )          /
                ( ";" "BYMONTHDAY" "=" bymodaylist )    /
                ( ";" "BYYEARDAY" "=" byyrdaylist )     /
                ( ";" "BYWEEKNO" "=" bywknolist )       /
                ( ";" "BYMONTH" "=" bymolist )          /
                ( ";" "BYSETPOS" "=" bysplist )         /
                ( ";" "WKST" "=" weekday )              /
                ( ";" x-name "=" text )
                )

     recur           = recur-rule-part *( ";" recur-rule-part )
                     ;
                     ; The rule parts are not ordered in any
                     ; particular sequence
                     ;
                     ; The FREQ rule part is REQUIRED,
                     ; but MUST NOT occur more than once
                     ;
                     ; The UNTIL or COUNT rule parts are OPTIONAL,
                     ; but they MUST NOT occur in the same 'recur'
                     ;
                     ; The other rule parts are OPTIONAL,
                     ; but MUST NOT occur more than once

     recur-rule-part = ( "FREQ" "=" freq )
                     / ( "UNTIL" "=" enddate )
                     / ( "COUNT" "=" 1*DIGIT )
                     / ( "INTERVAL" "=" 1*DIGIT )
                     / ( "BYSECOND" "=" byseclist )
                     / ( "BYMINUTE" "=" byminlist )
                     / ( "BYHOUR" "=" byhrlist )
                     / ( "BYDAY" "=" bywdaylist )
                     / ( "BYMONTHDAY" "=" bymodaylist )
                     / ( "BYYEARDAY" "=" byyrdaylist )
                     / ( "BYWEEKNO" "=" bywknolist )
                     / ( "BYMONTH" "=" bymolist )
                     / ( "BYSETPOS" "=" bysplist )
                     / ( "WKST" "=" weekday ) 
     freq        = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
                 / "WEEKLY" / "MONTHLY" / "YEARLY"

     enddate     = date  I 
     enddate     =/ date-time     ;A I n UTC value

     byseclist   =  I seconds / ( seconds *("," seconds) )

     seconds     =  I 1 I DIGIT / 1*2DIGIT       ;0 to  I 5960

     byminlist   =  I minutes / ( minutes *("," minutes) )

     minutes     =  I 1 I DIGIT / 1*2DIGIT       ;0 to 59

     byhrlist    =  I hour / ( hour *("," hour) )

     hour        =  I 1 I DIGIT / 1*2DIGIT       ;0 to 23

     bywdaylist  =  I weekdaynum / ( weekdaynum *("," weekdaynum) )

     weekdaynum  = [ I ([plus I  / minus] ordwk I  / minus ordwk)] weekday

     plus        = "+"

     minus       = "-"

     ordwk       =  I 1 I DIGIT / 1*2DIGIT       ;1 to 53

     weekday     = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA"
     ;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
     ;FRIDAY,  I and SATURDAY  I and SUNDAYdays of the week.

     bymodaylist =  I monthdaynum / ( monthdaynum *("," monthdaynum) )

     monthdaynum =  I ([plus I  / minus] ordmoday I ) / (minus ordmoday)

     ordmoday    =  I 1 I DIGIT / 1*2DIGIT       ;1 to 31

     byyrdaylist =  I yeardaynum / ( yeardaynum *("," yeardaynum) )

     yeardaynum  =  I ([plus I  / minus] ordyrday I ) / (minus ordyrday)

     ordyrday    =  I 1 I DIGIT / 2DIGIT / 1*3DIGIT      ;1 to 366

     bywknolist  =  I weeknum / ( weeknum *("," weeknum) )

     weeknum     =  I ([plus I  / minus] ordwk I ) / (minus ordwk)

     bymolist    =  I monthnum / ( monthnum *("," monthnum) )

     monthnum    =  I 1 I DIGIT / 1*2DIGIT       ;1 to 12

     bysplist    =  I setposday / ( setposday *("," setposday) )

     setposday   = yeardaynum
Description:
 I If the property permits, multiple "recur" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values.  I TheThis value type is a structured value consisting of a list of one or more recurrence grammar parts. Each rule part is defined by a NAME=VALUE pair. The rule parts are separated from each other by the SEMICOLON character (US-ASCII decimal 59). The rule parts are not ordered in any particular sequence. Individual rule parts MUST only be specified once.  I 
Note: Compliant applications MUST accept rule parts ordered in any sequence, but to ensure backward compatibility with applications that pre-date this revision of iCalendar the FREQ rule part MUST be the first rule part specified in a RECUR value.
The FREQ rule part identifies the type of recurrence rule. This rule part MUST be specified in the recurrence rule. Valid values include SECONDLY, to specify repeating events based on an interval of a second or more; MINUTELY, to specify repeating events based on an interval of a minute or more; HOURLY, to specify repeating events based on an interval of an hour or more; DAILY, to specify repeating events based on an interval of a day or more; WEEKLY, to specify repeating events based on an interval of a week or more; MONTHLY, to specify repeating events based on an interval of a month or more; and YEARLY, to specify repeating events based on an interval of a year or more.
The INTERVAL rule part contains a positive integer representing how often the recurrence rule repeats. The default value is "1", meaning every second for a SECONDLY rule, or every minute for a MINUTELY rule, every hour for an HOURLY rule, every day for a DAILY rule, every week for a WEEKLY rule, every month for a MONTHLY rule and every year for a YEARLY rule.
The UNTIL rule part defines a  I date-timeDATE or DATE-TIME value which bounds the recurrence rule in an inclusive manner. If the value specified by UNTIL is synchronized with the specified recurrence, this  I date or date-timeDATE or DATE-TIME becomes the last instance of the recurrence.  I The value of the UNTIL rule part MUST have the same value type as the "DTSTART" property. Furthermore, if the "DTSTART" property is specified as a date with local time, then the UNTIL rule part MUST also be specified as a date with local time. Else, if the "DTSTART" property is specified as a date with UTC time or a date with local time and time zone reference, then the UNTIL rule part MUST be specified as a date with UTC time. In the case of the "STANDARD" and "DAYLIGHT" sub-components the UNTIL rule part MUST always be specified as a date with UTC time. If specified as a  I date-timeDATE-TIME value, then it MUST be specified in  I ana UTC time format. If not present, and the COUNT rule part is also not present, the  I "RRULE I " is considered to repeat forever.
The COUNT rule part defines the number of occurrences at which to range-bound the recurrence. The "DTSTART" property value I , if specified,always counts as the first occurrence.
The BYSECOND rule part specifies a COMMA character (US-ASCII decimal 44) separated list of seconds within a minute. Valid values are 0 to  I 5960. The BYMINUTE rule part specifies a COMMA character (US-ASCII decimal 44) separated list of minutes within an hour. Valid values are 0 to 59. The BYHOUR rule part specifies a COMMA character (US-ASCII decimal 44) separated list of hours of the day. Valid values are 0 to 23.  I The BYSECOND, BYMINUTE and BYHOUR rule parts MUST NOT be specified when the associated "DTSTART" property has a DATE value type. These rule parts MUST be ignored in RECUR value that violate the above requirement (e.g., generated by applications that pre-date this revision of iCalendar).
The BYDAY rule part specifies a COMMA character (US-ASCII decimal 44) separated list of days of the week;  I SU indicates Sunday; MO indicates Monday; TU indicates Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates Friday; SA indicates Saturday I ; SU indicates Sunday.
Each BYDAY value can also be preceded by a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific day within the MONTHLY or YEARLY  I "RRULE I ". For example, within a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday within the month, whereas -1MO represents the last Monday of the month. If an integer modifier is not present, it means all days of this type within the specified frequency. For example, within a MONTHLY rule, MO represents all Mondays within the month.  I The BYDAY rule part MUST NOT be specified with a numeric value when the FREQ rule part is not set to MONTHLY or YEARLY. Furthermore, the BYDAY rule part MUST NOT be specified with a numeric value with the FREQ rule part set to YEARLY when the BYWEEKNO rule part is specified. The numeric value in a BYDAY rule part with the FREQ rule part set to YEARLY corresponds to an offset within the month when the BYMONTH rule part is present, and corresponds to an offset within the year when the BYWEEKNO or BYMONTH rule parts are present.
The BYMONTHDAY rule part specifies a COMMA character ( I US-ASCII decimal 44) separated list of days of the month. Valid values are 1 to 31 or -31 to -1. For example, -10 represents the tenth to the last day of the month.  I The BYMONTHDAY rule part MUST NOT be specified when the FREQ rule part is set to WEEKLY.
The BYYEARDAY rule part specifies a COMMA character (US-ASCII decimal 44) separated list of days of the year. Valid values are 1 to 366 or -366 to -1. For example, -1 represents the last day of the year (December 31st) and -306 represents the 306th to the last day of the year (March 1st).  I The BYYEARDAY rule part MUST NOT be specified when the FREQ rule part is set to DAILY, WEEKLY, and MONTHLY.
The BYWEEKNO rule part specifies a COMMA character (US-ASCII decimal 44) separated list of ordinals specifying weeks of the year. Valid values are 1 to 53 or -53 to -1. This corresponds to weeks according to week numbering as defined in  I [ISO.8601.1988][ISO.8601.2004]. A week is defined as a seven day period, starting on the day of the week defined to be the week start (see WKST). Week number one of the calendar year is the first week which contains at least four (4) days in that calendar year. This rule part  I is only valid for YEARLY rules.MUST NOT be used when the FREQ rule part is not set to YEARLY. For example, 3 represents the third week of the year.
Note: Assuming a Monday week start, week 53 can only occur when Thursday is January 1 or if it is a leap year and Wednesday is January 1.
The BYMONTH rule part specifies a COMMA character (US-ASCII decimal 44) separated list of months of the year. Valid values are 1 to 12.
The WKST rule part specifies the day on which the workweek starts. Valid values are MO, TU, WE, TH, FR, SA and SU. This is significant when a WEEKLY  I "RRULE I " has an interval greater than 1, and a BYDAY rule part is specified. This is also significant when in a YEARLY  I "RRULE I " when a BYWEEKNO rule part is specified. The default value is MO.
The BYSETPOS rule part specifies a COMMA character (US-ASCII decimal 44) separated list of values which corresponds to the nth occurrence within the set of  I eventsrecurrence instances specified by the rule.  I BYSETPOS operates on a set of recurrence instances in one interval of the recurrence rule. For a WEEKLY rule, the interval is one week, for a MONTHLY rule, one month, and for a YEARLY rule, one year. Valid values are 1 to 366 or -366 to -1. It MUST only be used in conjunction with another BYxxx rule part. For example "the last work day of the month" could be represented as:
      I RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-1
Each BYSETPOS value can include a positive (+n) or negative (-n) integer. If present, this indicates the nth occurrence of the specific occurrence within the set of  I eventsoccurences specified by the rule.
 I If BYxxx rule part values are found which are beyond the available scope (ie, BYMONTHDAY=30 in February), they are simply ignored.Recurrence rules may generate recurrence instances with invalid date (e.g., February 30) or nonexistent local time (e.g., 1:30 AM on a day where the local time is moved forward by an hour at 1:00 AM). Such recurrence instances MUST be ignored and MUST NOT be counted as part of the recurrence set.
Information, not contained in the rule, necessary to determine the various recurrence instance start time and dates are derived from the Start Time ( I "DTSTART I ")  I entrycomponent attribute. For example, "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the month or a time. This information would be the same as what is specified for  I "DTSTART I ".
BYxxx rule parts modify the recurrence in some manner. BYxxx rule parts for a period of time which is the same or greater than the frequency generally reduce or limit the number of occurrences of the recurrence generated. For example, "FREQ=DAILY;BYMONTH=1" reduces the number of recurrence instances from all days (if BYMONTH  I tagrule part is not present) to all days in January. BYxxx rule parts for a period of time less than the frequency generally increase or expand the number of occurrences of the recurrence. For example, "FREQ=YEARLY;BYMONTH=1,2" increases the number of days within the yearly recurrence set from 1 (if BYMONTH  I tagrule part is not present) to 2.
If multiple BYxxx rule parts are specified, then after evaluating the specified FREQ and INTERVAL rule parts, the BYxxx rule parts are applied to the current set of evaluated occurrences in the following order: BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY, BYHOUR, BYMINUTE, BYSECOND and BYSETPOS; then COUNT and UNTIL are evaluated.
The table below summarizes the dependency of BYxxx rule part expand or limit behaviour on the FREQ rule part value.
The term "N/A" means that the corresponding BYxxx rule part MUST NOT be used with the corresponding FREQ value.
BYDAY has some special behaviour depending on the FREQ value and this is described in separate notes below the table.
+----------+--------+--------+-------+-------+------+-------+------+
|          |SECONDLY|MINUTELY|HOURLY |DAILY  |WEEKLY|MONTHLY|YEARLY|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTH   |Limit   |Limit   |Limit  |Limit  |Limit |Limit  |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYWEEKNO  |N/A     |N/A     |N/A    |N/A    |N/A   |N/A    |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYYEARDAY |Limit   |Limit   |Limit  |N/A    |N/A   |N/A    |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMONTHDAY|Limit   |Limit   |Limit  |Limit  |N/A   |Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYDAY     |Limit   |Limit   |Limit  |Limit  |Expand|Note 1 |Note 2|
+----------+--------+--------+-------+-------+------+-------+------+
|BYHOUR    |Limit   |Limit   |Limit  |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYMINUTE  |Limit   |Limit   |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSECOND  |Limit   |Expand  |Expand |Expand |Expand|Expand |Expand|
+----------+--------+--------+-------+-------+------+-------+------+
|BYSETPOS  |Limit   |Limit   |Limit  |Limit  |Limit |Limit  |Limit |
+----------+--------+--------+-------+-------+------+-------+------+
Note 1:
Limit if BYMONTHDAY is present, otherwise special expand for MONTHLY.
Note 2:
Limit if BYYEARDAY or BYMONTHDAY is present, otherwise special expand for WEEKLY if BYWEEKNO present, otherwise special expand for MONTHLY if BYMONTH present, otherwise special expand for YEARLY.
Here is an example of evaluating multiple BYxxx rule parts.
     DTSTART;TZID= I US-EasternAmerica/New_York:19970105T083000
     RRULE:FREQ=YEARLY;INTERVAL=2;BYMONTH=1;BYDAY=SU;BYHOUR=8,9;
      BYMINUTE=30
First, the "INTERVAL=2" would be applied to "FREQ=YEARLY" to arrive at "every other year". Then, "BYMONTH=1" would be applied to arrive at "every January, every other year". Then, "BYDAY=SU" would be applied to arrive at "every Sunday in January, every other year". Then, "BYHOUR=8,9" would be applied to arrive at "every Sunday in January at 8 AM and 9 AM, every other year". Then, "BYMINUTE=30" would be applied to arrive at "every Sunday in January at 8:30 AM and 9:30 AM, every other year". Then, lacking information from  I "RRULE I ", the second is derived from  I "DTSTART I ", to end up in "every Sunday in January at 8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the BYMINUTE, BYHOUR, BYDAY, BYMONTHDAY or BYMONTH rule part were missing, the appropriate minute, hour, day or month would have been retrieved from the "DTSTART" property.
 I If the computed local start time of a recurrence instance does not exist, or occurs more than once, for the specified time zone, the time of the recurrence instance is interpreted in the same manner as an explicit DATE-TIME value describing that date and time, as specified in Section 3.3.5.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following is a rule which specifies 10  I meetingsoccurences which occur every other day:
     FREQ=DAILY;COUNT=10;INTERVAL=2
There are other examples specified in  I the "RRULE" specification.Section 3.8.5.3.

3.3.11. Text

Value Name:
TEXT
Purpose:
This value type is used to identify values that contain human readable text.
Format Definition:
 I The character sets supported by this revision of iCalendar are UTF-8 and US ASCII thereof. The applicability to other character sets is for future work.  I TheThis value type is defined by the following notation.
     text       = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
        ; Folded according to description above

     ESCAPED-CHAR =  I ("\\" / "\;" / "\," / "\N" / "\n")
        ; \\ encodes \, \N or \n encodes newline
        ; \; encodes ;, \, encodes ,

     TSAFE-CHAR = %x20-21 / %x23-2B / %x2D-39 / %x3C-5B I  /
                  %x5D-7E / NON-US-ASCII
        ; Any character except CTLs not needed by the current
        ; character set, DQUOTE, ";", ":", "\", ","
 I 
Note: Certain other character sets may require modification of the above definitions, but this is beyond the scope of this document.
Description:
If the property permits, multiple  I "text"TEXT values are specified by a COMMA character (US-ASCII decimal 44) separated list of values.
The language in which the text is represented can be controlled by the "LANGUAGE" property parameter.
An intentional formatted text line break MUST only be included in a "TEXT" property value by representing the line break with the character sequence of BACKSLASH (US-ASCII decimal 92), followed by a LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL LETTER N (US-ASCII decimal 78), that is "\n" or "\N".
The "TEXT" property values may also contain special characters that are used to signify delimiters, such as a COMMA character for lists of values or a SEMICOLON character for structured values. In order to support the inclusion of these special characters in "TEXT" property values, they MUST be escaped with a BACKSLASH character. A BACKSLASH character (US-ASCII decimal 92) in a "TEXT" property value MUST be escaped with another BACKSLASH character. A COMMA character in a "TEXT" property value MUST be escaped with a BACKSLASH character (US-ASCII decimal 92). A SEMICOLON character in a "TEXT" property value MUST be escaped with a BACKSLASH character (US-ASCII decimal 92). However, a COLON character in a "TEXT" property value SHALL NOT be escaped with a BACKSLASH character.
Example:
A multiple line value of:
     Project XYZ Final Review
     Conference Room - 3B
     Come Prepared.
would be represented as:
     Project XYZ Final Review\nConference Room - 3B\nCome Prepared.

3.3.12. Time

Value Name:
TIME
Purpose:
This value type is used to identify values that contain a time of day.
Format Definition:
 I TheThis  I datavalue type is defined by the following notation:
     time         = time-hour time-minute time-second [time-utc]

     time-hour    = 2DIGIT        ;00-23
     time-minute  = 2DIGIT        ;00-59
     time-second  = 2DIGIT        ;00-60
     ;The "60" value is used to account for  I positive "leap" seconds.

     time-utc     = "Z"
Description:
If the property permits, multiple "time" values are specified by a COMMA character (US-ASCII decimal 44) separated list of values. No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
The "TIME"  I datavalue type is used to identify values that contain a time of day. The format is based on the  I [ISO.8601.1988][ISO.8601.2004] complete representation, basic format for a time of day. The text format consists of a two-digit 24-hour of the day (i.e., values  I 00-23), two-digit minute in the hour (i.e., values  I 00-59), and two-digit seconds in the minute (i.e., values  I 00-60). The seconds value of 60 MUST only  I tobe used to account for  I positive "leap" seconds. Fractions of a second are not supported by this format.
In parallel to the "DATE-TIME" definition above, the "TIME"  I datavalue type expresses time values in three forms:
The form of time with UTC offset MUST NOT be used. For example, the following is  I NOT VALIDnot valid for a time value:
     230000-0800        ;Invalid time format
FORM #1 LOCAL TIME
The local time form is simply a time value that does not contain the UTC designator nor does it reference a time zone. For example, 11:00 PM:
     230000
Time values of this type are said to be "floating" and are not bound to any time zone in particular. They are used to represent the same hour, minute, and second value regardless of which time zone is currently being observed. For example, an event can be defined that indicates that an individual will be busy from 11:00 AM to 1:00 PM every day, no matter which time zone the person is in. In these cases, a local time can be specified. The recipient of an iCalendar object with a property value consisting of a local time, without any relative time zone information, SHOULD interpret the value as being fixed to whatever time zone the  I "ATTENDEE I " is in at any given moment. This means that two  I ATTENDEEs,"Attendees", may participate in the same event at different UTC times; floating time SHOULD only be used where that is reasonable behavior.
In most cases, a fixed time is desired. To properly communicate a fixed time in a property value, either UTC time or local time with time zone reference MUST be specified.
The use of local time in a TIME value without the  I "TZID I " property parameter is to be interpreted as a local time value, regardless of the existence of "VTIMEZONE" calendar components in the iCalendar object.
FORM #2: UTC TIME
UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z suffix character (US-ASCII decimal 90), the UTC designator, appended to the time value. For example, the following represents 07:00 AM UTC:
     070000Z
The  I "TZID I " property parameter MUST NOT be applied to TIME properties whose time values are specified in UTC.
FORM #3: LOCAL TIME AND TIME ZONE REFERENCE
The local time with reference to time zone information form is identified by the use the  I "TZID I " property parameter to reference the appropriate time zone definition.  I "TZID I " is discussed in detail in  I the section on Time ZoneSection 3.2.18.
Example:
The following represents 8:30 AM in New York in Winter, five hours behind UTC, in each of the three formats I using the "X-TIMEOFDAY" non-standard property:
      I X-TIMEOFDAY:083000
      I X-TIMEOFDAY:133000Z

      I X-TIMEOFDAY;TZID= I US-EasternAmerica/New_York:083000

3.3.13. URI

Value Name:
URI
Purpose:
This value type is used to identify values that contain a uniform resource identifier (URI) type of reference to the property value.
Format Definition:
 I The dataThis value type is defined by the following notation:
     uri = <As defined  I by any IETF RFCin section 3 of [RFC3986]>
Description:
This  I datavalue type might be used to reference binary information, for values that are large, or otherwise undesirable to include directly in the iCalendar object.
 I The URI value formats in [RFC1738], RFC 2111 and any other IETF registered value format can be specified.Property values with this value type MUST follow the generic URI syntax defined in [RFC3986].
 I Any IANA registered URI format can be used. These include, but are not limited to, those defined in [RFC1738] and RFC 2111.
When a property parameter value is a URI value type, the URI MUST be specified as a quoted-string value.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following is a URI for a network file:
     http:// I host1.comexample.com/my-report.txt

3.3.14. UTC Offset

Value Name:
UTC-OFFSET
Purpose:
This value type is used to identify properties that contain an offset from UTC to local time.
Format Definition:
 I The dataThis value type is defined by the following notation:
     utc-offset = time-numzone I   ;As defined above in time data type

     time-numzone = ("+" / "-") time-hour time-minute [time-second]
 I  4.3.14_clarify_minus   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 Add MUST requirement for HYPHEN-MINUS character.
Resolution: Done.
Associated changes in this document: 3.3.14., Published in: draft-ietf-calsify-rfc2445bis-01
Description:
The PLUS SIGN (US-ASCII decimal 43) character MUST be specified for positive UTC offsets (i.e., ahead of UTC).  I The HYPHEN-MINUS character (US-ASCII decimal 45) MUST be specified for negative UTC offsets (i.e., behind of UTC). The value of "-0000" and "-000000" are not allowed. The time-second, if present,  I may notMUST NOT be 60; if absent, it defaults to zero.
No additional content value encoding (i.e., BACKSLASH character encoding) is defined for this value type.
Example:
The following UTC offsets are given for standard time for New York (five hours behind UTC) and Geneva (one hour ahead of UTC):
     -0500

     +0100

3.4. iCalendar Object

 I  #issue32+icalendar_stream   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 Introduce the notion of an "iCalendar stream" to make it explicit when we are refering to a "single iCalendar object" or a "sequence of iCalendar objects".
Resolution: Done.
Associated changes in this document: 3.4, 3.4, 3.4, 3.4., Published in: draft-ietf-calsify-rfc2445bis-04

The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of  I an iCalendar stream with a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together I .in an iCalendar stream. The first line and last line of the iCalendar object MUST contain a pair of iCalendar object delimiter strings. The syntax for an iCalendar  I objectstream is as follows:

 I 
     icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF
                  icalbody
                  "END" ":" "VCALENDAR" CRLF)

     icalstream = 1*icalobject

     icalobject = "BEGIN" ":" "VCALENDAR" CRLF
                  icalbody
                  "END" ":" "VCALENDAR" CRLF

The following is a simple example of an iCalendar object:

     BEGIN:VCALENDAR
     VERSION:2.0
     PRODID:-//hacksw/handcal//NONSGML v1.0//EN
     BEGIN:VEVENT I 
     UID:19970610T172345Z-AF23B2@example.com
     DTSTAMP:19970610T172345Z
     DTSTART:19970714T170000Z
     DTEND:19970715T0 I 3595940000Z
     SUMMARY:Bastille Day Party
     END:VEVENT
     END:VCALENDAR

3.5. Property

A property is the definition of an individual attribute describing a calendar  I object or a calendar component. A property takes the form defined by the "contentline" notation defined in  I section 4.1.1Section 3.1.

The following is an example of a property:

     DTSTART:19960415T133000Z

This memo imposes no ordering of properties within an iCalendar object.

Property names, parameter names and enumerated parameter values are case insensitive. For example, the property name "DUE" is the same as "due" and "Due", DTSTART;TZID= I US-EasternAmerica/New_York:19980714T120000 is the same as DtStart;TzID= I US-EasternAmerica/New_York:19980714T120000.

3.6. Calendar Components

The body of the iCalendar object consists of a sequence of calendar properties and one or more calendar components. The calendar properties are attributes that apply to the calendar  I object as a whole. The calendar components are collections of properties that express a particular calendar semantic. For example, the calendar component can specify an event, a to-do, a journal entry, time zone information,  I or free/busy time information, or an alarm.

The body of the iCalendar object is defined by the following notation:

     icalbody   = calprops component

     calprops   =  I 2*(

                ;  I 'prodid' and 'version' are boththe following are REQUIRED,
                ; but MUST NOT occur more than once

                prodid / version /

                ;  I 'calscale' and 'method'the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                calscale / method /
    I 
                ;  I 'x-prop' isthe following are OPTIONAL,
                ; and MAY occur more than once
   
                x-prop I  / iana-prop
                )

     component  = 1*(eventc / todoc / journalc / freebusyc /
                   I / timezonec / iana-comp / x-comp)

     iana-comp  = "BEGIN" ":" iana-token CRLF
                  1*contentline
                  "END" ":" iana-token CRLF

     x-comp     = "BEGIN" ":" x-name CRLF
                  1*contentline
                  "END" ":" x-name CRLF

An iCalendar object MUST include the "PRODID" and "VERSION" calendar properties. In addition, it MUST include at least one calendar component. Special forms of iCalendar objects are possible to publish just busy time (i.e., only a "VFREEBUSY" calendar component) or time zone (i.e., only a "VTIMEZONE" calendar component) information. In addition, a complex iCalendar object  I is possible that is used to capture a complete snapshot of the contents of a calendar  I is possible (e.g., composite of many different calendar components). More commonly, an iCalendar object will consist of just a single "VEVENT", "VTODO" or "VJOURNAL" calendar component.  I Applications MUST ignore x-comp and iana-comp they don't recognized.

3.6.1. Event Component

 I  4.6.1_missing_value_param   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-10-02 The DTSTART property is missing the VALUE=DATE parameter in the last example of section 4.6.1.
2006-10-02Resolution: Fixed.
Associated changes in this document: 3.6.1., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue10+end_date_not_inclusive   (type: change, status: closed)
reinhold@kainhofer.com2006-06-03 We need to clarify that the "DTEND" property specifies the non-inclusive end of a "VEVENT" even when specified as a DATE, and that the "DUE" property also specifies the non-inclusive end of a "VTODO" even when specified as a DATE.
Resolution: Added examples.
Associated changes in this document: 3.6.1, 3.6.2.
 I  #issue37+4.6.1_eventprop_rule   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 The rule eventprop specifies that DTSTAMP, DTSTART and UID are OPTIONAL which is in contradiction with section 4.8.7.2 Date/Time Stamp, section 4.8.2.4 Date/Time Start, and section 4.8.4.7 Unique Identifier which all specify that those three properties are REQUIRED in VEVENT components.
2006-09-28Resolution: Changed ABNF to specify that DTSTAMP, DTSTART and UID are REQUIRED.
Associated changes in this document: 3.4, 3.6.1, 3.6.1, 3.6.1, 3.6.1., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue51+4.6.1_implicit_dtend_of_day_events   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-10-03 Clarify implicit duration of day events with no DTEND nor DURATION property.
Resolution: Done.
Associated changes in this document: 3.6.1, 3.6.1., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue59+4.6.1_default_duration_of_day_events   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 Clarify that for cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE data type but no "DTEND" or "DURATION" property, the events non-inclusive end is the end of the calendar date specified by the "DTSTART" property. We should further specify that such event should appear as opaque in a search for busy time, unless the "TRANSP" property is set to TRANSPARENT.
Resolution: Clarified text.
Associated changes in this document: 3.6.1, 3.6.1, 3.8.2.4, 5., Published in: draft-ietf-calsify-rfc2445bis-06

Component Name:
VEVENT
Purpose:
Provide a grouping of component properties that describe an event.
Format Definition:
A "VEVENT" calendar component is defined by the following notation:
     eventc     = "BEGIN" ":" "VEVENT" CRLF
                  eventprop *alarmc
                  "END" ":" "VEVENT" CRLF

     eventprop  = *(
      I 
                ; the following are REQUIRED,
                ; but MUST NOT occur more than once

                dtstamp / dtstart / uid /

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once
                
                class / created / description /  I dtstart / geo /
                last-mod / location / organizer / priority /
                 I dtstamp / seq / status / summary / transp /
                 I uid / url / recurid / I 

                ; the following is OPTIONAL,
                ; but SHOULD NOT occur more than once

                rrule /

                ; either 'dtend' or 'duration'  I mayMAY appear in
                ; a 'eventprop', but 'dtend' and 'duration'
                ; MUST NOT occur in the same 'eventprop'

                dtend / duration /

                ; the following are  I optionalOPTIONAL,
                ; and MAY occur more than once

                attach / attendee / categories / comment /
                contact / exdate /  I exrule / rstatus / related /
                resources / rdate /  I rrule / x-prop I  / iana-prop

                )
Description:
A "VEVENT" calendar component is a grouping of component properties, and possibly including "VALARM" calendar components, that represents a scheduled amount of time on a calendar. For example, it can be an activity; such as a one-hour long, department meeting from 8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time on an individual calendar. Hence, the event will appear as an opaque interval in a search for busy time. Alternately, the event can have its Time Transparency set to "TRANSPARENT" in order to prevent blocking of the event in searches for busy time.
The "VEVENT" is also the calendar component used to specify an anniversary or daily reminder within a calendar. These events have a DATE value type for the "DTSTART" property instead of the default  I datavalue type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it MUST be specified as a DATE value also. The anniversary type of "VEVENT" can span more than one date (i.e I ., "DTEND" property value is set to a calendar date after the "DTSTART" property value).  I If such a "VEVENT" has a "DURATION" property, it MUST be specified as a "dur-day" or "dur-week" value.
The "DTSTART" property for a "VEVENT" specifies the inclusive start of the event. For recurring events, it also specifies the very first instance in the recurrence set. The "DTEND" property for a "VEVENT" calendar component specifies the non-inclusive end of the event. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE  I datavalue type but no "DTEND"  I nor DURATION property, the  I events non-inclusive end is the end of the calendar date specified by the "DTSTART" property.event's duration is taken to be one day. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE-TIME  I datavalue type but no "DTEND" property, the event ends on the same calendar date and time of day specified by the "DTSTART" property.
The "VEVENT" calendar component cannot be nested within another calendar component. However, "VEVENT" calendar components can be related to each other or to a "VTODO" or to a "VJOURNAL" calendar component with the "RELATED-TO" property.
Example:
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:
     BEGIN:VEVENT
     UID:19970901T130000Z-123401@ I host.comexample.com  I 
     DTSTAMP:19970901T1300Z 
     DTSTAMP:19970901T130000Z 
     DTSTART:19970903T163000Z
     DTEND:19970903T190000Z
     SUMMARY:Annual Employee Review
     CLASS:PRIVATE
     CATEGORIES:BUSINESS,HUMAN RESOURCES
     END:VEVENT
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:
     BEGIN:VEVENT
     UID:19970901T130000Z-123402@ I host.comexample.com  I 
     DTSTAMP:19970901T1300Z 
     DTSTAMP:19970901T130000Z 
     DTSTART:19970401T163000Z
     DTEND:19970402T010000Z
     SUMMARY:Laurel is in sensitivity awareness class.
     CLASS:PUBLIC
     CATEGORIES:BUSINESS,HUMAN RESOURCES
     TRANSP:TRANSPARENT
     END:VEVENT
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually.  I Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:
     BEGIN:VEVENT
     UID:19970901T130000Z-123403@ I host.comexample.com  I 
     DTSTAMP:19970901T1300Z 
     DTSTAMP:19970901T130000Z 
     DTSTART I ;VALUE=DATE:19971102
     SUMMARY:Our Blissful Anniversary I 
     TRANSP:TRANSPARENT
     CLASS:CONFIDENTIAL
     CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
     RRULE:FREQ=YEARLY
     END:VEVENT
 I The following is an example of the "VEVENT" calendar component used to represent a multi-day event scheduled from June 28th, 2007 to July 8th, 2007 inclusively. Note that the "DTEND" property is set to July 9th, 2007, since the "DTEND" property specifies the non-inclusive end of the event.
     BEGIN:VEVENT
     UID:20070423T123432Z-541111@example.com
     DTSTAMP:20070423T123432Z
     DTSTART;VALUE=DATE:20070628
     DTEND;VALUE=DATE:20070709
     SUMMARY:Festival International de Jazz de Montreal
     TRANSP:TRANSPARENT
     END:VEVENT

3.6.2. To-do Component

 I  #issue38+4.6.2_todoprop_rule   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 The rule todoprop specifies that DTSTAMP, and UID are OPTIONAL which is in contradiction with section 4.8.7.2 Date/Time Stamp, and section 4.8.4.7 Unique Identifier which all specify that those two properties are REQUIRED in VTODO components.
2006-09-28Resolution: Changed ABNF to specify that DTSTAMP and UID are REQUIRED.
Associated changes in this document: 3.6.2, 3.6.2, 3.6.2., Published in: draft-ietf-calsify-rfc2445bis-02
 I  4.6.2_duration_without_dtstart_in_vtodo   (type: change, status: closed)
jpr@ximian.com2001-02-13 Both DTSTART and DURATION are optional in VTODO, so one could specify DURATION without DTSTART.
Resolution: Added a comment in the ABFN to clarify that DTSTART is required when DURATION is specified.
Associated changes in this document: 3.6.2., Published in: draft-ietf-calsify-rfc2445bis-06

Component Name:
VTODO
Purpose:
Provide a grouping of calendar properties that describe a to-do.
Format Definition:
A "VTODO" calendar component is defined by the following notation:
     todoc      = "BEGIN" ":" "VTODO" CRLF
                  todoprop *alarmc
                  "END" ":" "VTODO" CRLF

     todoprop   = *(
      I 
                ; the following are REQUIRED,
                ; but MUST NOT occur more than once

                dtstamp / uid /

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                class / completed / created / description /  I dtstamp / 
                dtstart / geo / last-mod / location / organizer /
                percent / priority / recurid / seq / status /
                summary /  I uid / url / I 

                ; the following is OPTIONAL,
                ; but SHOULD NOT occur more than once

                rrule /

                ; either 'due' or 'duration'  I mayMAY appear in
                ; a 'todoprop', but 'due' and 'duration'
                ; MUST NOT occur in the same 'todoprop' I .
                ; If 'duration' appear in a 'todoprop',
                ; then 'dtstart' MUST also appear in
                ' the same 'todoprop'.

                due / duration /

                ; the following are  I optionalOPTIONAL,
                ; and MAY occur more than once

                attach / attendee / categories / comment / contact /
                exdate /  I exrule / rstatus / related / resources /
                rdate /  I rrule / x-prop I  / iana-prop

                )
Description:
A "VTODO" calendar component is a grouping of component properties and possibly "VALARM" calendar components that represent an action-item or assignment. For example, it can be used to represent an item of work assigned to an individual; such as "turn in travel expense today".
The "VTODO" calendar component cannot be nested within another calendar component. However, "VTODO" calendar components can be related to each other or to a  I "VTODO""VEVENT" or to a "VJOURNAL" calendar component with the "RELATED-TO" property.
A "VTODO" calendar component without the "DTSTART" and "DUE" (or "DURATION") properties specifies a to-do that will be associated with each successive calendar date, until it is completed.
Examples:
 I The following is an example of a "VTODO" calendar component that needs to be completed before May 1st, 2007. On midnight May 1st, 2007 this to-do would be considered overdue.
     BEGIN:VTODO
     UID:20070313T123432Z-456553@example.com
     DTSTAMP:20070313T123432Z
     DUE;VALUE=DATE:20070501
     SUMMARY:Submit Quebec Income Tax Return for 2006
     CLASS:CONFIDENTIAL
     CATEGORIES:FAMILY,FINANCE
     STATUS:NEEDS-ACTION
     END:VTODO
The following is an example of a "VTODO" calendar component I :that was due before 1:00 P.M. UTC on July 9th, 2007 and was completed on July 7th, 2007 at 10:00 A.M. UTC.
     BEGIN:VTODO
     UID: I 19970901T130000Z20070514T103211Z-123404@ I host.comexample.com
     DTSTAMP: I 19970901T1300Z20070514T103211Z
     DTSTART: I 19970415T133000Z20070514T110000Z
     DUE: I 19970416T045959Z20070709T130000Z I 
     COMPLETED:20070707T100000Z
     SUMMARY: I 1996 Income Tax PreparationSubmit Revised Internet-Draft I 
     CLASS:CONFIDENTIAL
     CATEGORIES:FAMILY,FINANCE
     PRIORITY:1
     STATUS:NEEDS-ACTION
     END:VTODO

3.6.3. Journal Component

 I  #issue39+4.6.3_jourprop_rule   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 The rule jourprop specifies that DTSTAMP, and UID are OPTIONAL which is in contradiction with section 4.8.7.2 Date/Time Stamp, and section 4.8.4.7 Unique Identifier which all specify that those two properties are REQUIRED in VJOURNAL components.
2006-09-28Resolution: Changed ABNF to specify that DTSTAMP and UID are REQUIRED.
Associated changes in this document: 3.6.3, 3.6.3, 3.6.3., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue58+4.6.3_description_in_jourprop   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 According to section 4.8.1.5 Description, the "DESCRIPTION" property can be specified multiple times within a "VJOURNAL" calendar component, but the ABNF of jourprop doesn't allow "DESCRIPTION" to occure more than once.
Resolution: Fix ABNF.
Associated changes in this document: 3.6.3, 3.6.3., Published in: draft-ietf-calsify-rfc2445bis-04

Component Name:
VJOURNAL
Purpose:
Provide a grouping of component properties that describe a journal entry.
Format Definition:
A "VJOURNAL" calendar component is defined by the following notation:
     journalc   = "BEGIN" ":" "VJOURNAL" CRLF
                  jourprop
                  "END" ":" "VJOURNAL" CRLF

     jourprop   = *(
      I 
                ; the following are REQUIRED,
                ; but MUST NOT occur more than once

                dtstamp / uid /

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                class / created /  I description / dtstart /  I dtstamp / 
                last-mod / organizer / recurid / seq /
                status / summary /  I uid / url / I 

                ; the following is OPTIONAL,
                ; but SHOULD NOT occur more than once

                rrule /

                ; the following are  I optionalOPTIONAL,
                ; and MAY occur more than once

                attach / attendee / categories / comment /
                contact /  I description / exdate /  I exrule / related / rdate /
                 I rrule / rstatus / x-prop I  / iana-prop
                )
Description:
A "VJOURNAL" calendar component is a grouping of component properties that represent one or more descriptive text notes associated with a particular calendar date. The "DTSTART" property is used to specify the calendar date that the journal entry is associated with. Generally, it will have a DATE value data type, but it can also be used to specify a DATE-TIME value data type. Examples of a journal entry include a daily record of a legislative body or a journal entry of individual telephone contacts for the day or an ordered list of accomplishments for the day. The "VJOURNAL" calendar component can also be used to associate a document with a calendar date.
The "VJOURNAL" calendar component does not take up time on a calendar. Hence, it does not play a role in free or busy time searches  I - --- it is as though it has a time transparency value of TRANSPARENT. It is transparent to any such searches.
The "VJOURNAL" calendar component cannot be nested within another calendar component. However, "VJOURNAL" calendar components can be related to each other or to a "VEVENT" or to a "VTODO" calendar component, with the "RELATED-TO" property.
Example:
The following is an example of the "VJOURNAL" calendar component:
     BEGIN:VJOURNAL
     UID:19970901T130000Z-123405@ I host.comexample.com  I 
     DTSTAMP:19970901T1300Z 
     DTSTAMP:19970901T130000Z 
     DTSTART;VALUE=DATE:19970317
     SUMMARY:Staff meeting minutes
     DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa
       and Bob. Aurora project plans were reviewed. There is currentl
      y no budget reserves for this project. Lisa will escalate to
       management. Next meeting on Tuesday.\n
        I  2. Telephone Conference: ABC Corp. sales representative called
       to discuss new printer. Promised to get us a demo by Friday.\n
        I  3. Henry Miller (Handsoff Insurance): Car was totaled by tree.
       Is looking into a loaner car.  I 654555-2323 (tel).
     END:VJOURNAL

3.6.4. Free/Busy Component

 I  #issue41+4.6.4_freebusy_example   (type: edit, status: closed)
simon.pilette@oracle.com2006-09-15 The FREEBUSY property does not allow the VALUE parameter.
2006-09-28Resolution: Change the example to not use the VALUE parameter.
Associated changes in this document: 3.6.4., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue40+4.6.4_fbprop_rule   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 The rule jourprop specifies that DTSTAMP, and UID are OPTIONAL which is in contradiction with section 4.8.7.2 Date/Time Stamp, and section 4.8.4.7 Unique Identifier which all specify that those two properties are REQUIRED in VJOURNAL components.
2006-09-28Resolution: Changed ABNF to specify that DTSTAMP and UID are REQUIRED.
Associated changes in this document: 3.6.4., Published in: draft-ietf-calsify-rfc2445bis-04

Component Name:
VFREEBUSY
Purpose:
Provide a grouping of component properties that describe either a request for free/busy time, describe a response to a request for free/busy time or describe a published set of busy time.
Format Definition:
A "VFREEBUSY" calendar component is defined by the following notation:
     freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
                  fbprop
                  "END" ":" "VFREEBUSY" CRLF

     fbprop     = *(
      I 
                ; the following are REQUIRED,
                ; but MUST NOT occur more than once

                dtstamp / uid /

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                contact / dtstart / dtend / duration / dtstamp /
                organizer / uid / url /

                ; the following are  I optionalOPTIONAL,
                ; and MAY occur more than once

                attendee / comment / freebusy / rstatus / x-prop I  /
                iana-prop
                )
Description:
A "VFREEBUSY" calendar component is a grouping of component properties that represents either a request for, a reply to a request for free or busy time information or a published set of busy time information.
When used to request free/busy time information, the "ATTENDEE" property specifies the calendar users whose free/busy time is being requested; the "ORGANIZER" property specifies the calendar user who is requesting the free/busy time; the "DTSTART" and "DTEND" properties specify the window of time for which the free/busy time is being requested; the "UID" and "DTSTAMP" properties are specified to assist in proper sequencing of multiple free/busy time requests.
When used to reply to a request for free/busy time, the "ATTENDEE" property specifies the calendar user responding to the free/busy time request; the "ORGANIZER" property specifies the calendar user that originally requested the free/busy time; the "FREEBUSY" property specifies the free/busy time information (if it exists); and the "UID" and "DTSTAMP" properties are specified to assist in proper sequencing of multiple free/busy time replies.
When used to publish busy time, the "ORGANIZER" property specifies the calendar user associated with the published busy time; the "DTSTART" and "DTEND" properties specify an inclusive time window that surrounds the busy time information; the "FREEBUSY" property specifies the published busy time information; and the "DTSTAMP" property specifies the date/time that iCalendar object was created.
The "VFREEBUSY" calendar component cannot be nested within another calendar component. Multiple "VFREEBUSY" calendar components can be specified within an iCalendar object. This permits the grouping of Free/Busy information into logical collections, such as monthly groups of busy time information.
The "VFREEBUSY" calendar component is intended for use in iCalendar object methods involving requests for free time, requests for busy time, requests for both free and busy, and the associated replies.
Free/Busy information is represented with the "FREEBUSY" property. This property provides a terse representation of time periods. One or more "FREEBUSY" properties can be specified in the "VFREEBUSY" calendar component.
When present in a "VFREEBUSY" calendar component, the "DTSTART" and "DTEND" properties SHOULD be specified prior to any "FREEBUSY" properties. In a free time request, these properties can be used in combination with the "DURATION" property to represent a request for a duration of free time within a specified window of time.
The recurrence properties ("RRULE",  I "EXRULE", "RDATE", "EXDATE") are not permitted within a "VFREEBUSY" calendar component. Any recurring events are resolved into their individual busy time periods using the "FREEBUSY" property.
Example:
The following is an example of a "VFREEBUSY" calendar component used to request free or busy time information:
     BEGIN:VFREEBUSY I 
     UID:19970901T082949Z-FA43EF@example.com 
     ORGANIZER: I MAILTOmailto:jane_doe@ I host1.comexample.com
     ATTENDEE: I MAILTOmailto:john_public@ I host2.comexample.com
     DTSTART:19971015T050000Z
     DTEND:19971016T050000Z
     DTSTAMP:19970901T083000Z
     END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component used to reply to the request with busy time information:
     BEGIN:VFREEBUSY I 
     UID:19970901T095957Z-76A912@example.com 
     ORGANIZER: I MAILTOmailto:jane_doe@ I host1.comexample.com
     ATTENDEE: I MAILTOmailto:john_public@ I host2.comexample.com
     DTSTAMP:19970901T100000Z
     FREEBUSY I ;VALUE=PERIOD:19971015T050000Z/PT8H30M,
      19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
     URL:http:// I host2.comexample.com/pub/busy/jpublic-01.ifb
     COMMENT:This iCalendar file contains busy time information for
       the next three months.
     END:VFREEBUSY
The following is an example of a "VFREEBUSY" calendar component used to publish busy time information.
     BEGIN:VFREEBUSY I 
     UID:19970901T115957Z-76A912@example.com
     DTSTAMP:19970901T120000Z 
     ORGANIZER:jsmith@ I host.comexample.com
     DTSTART:19980313T141711Z
     DTEND:19980410T141711Z
     FREEBUSY:19980314T233000Z/19980315T003000Z
     FREEBUSY:19980316T153000Z/19980316T163000Z
     FREEBUSY:19980318T030000Z/19980318T040000Z
     URL:http://www. I host.comexample.com/calendar/busytime/jsmith.ifb
     END:VFREEBUSY

3.6.5. Time Zone Component

 I  #issue72+4.6.5_vtimezone_required_with_rrule   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 Clarified whether the "VTIMEZONE" calendar component MUST be present if the iCalendar object contains an RRULE that generates dates on both sides of a time zone shift. (See also issue 43)
Resolution: This requirement has been removed.
 I  #issue75+4.6.5_rdate_format_in_vtimezone   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-07 We need to clarify the DATE-TIME format required for the "RDATE" property in "VTIMEZONE" components.
Resolution: The "RDATE" property MUST be specified as a local DATE-TIME value.
Associated changes in this document: 3.6.5.
 I  #issue78+4.6.5_dtstart_with_tzoffsetfrom   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-15 The text erronously specify that the "DTSTART" and the "TZOFFSETTO" properties MUST be used when generating the onset date-time values (instances) from the RRULE. The text should have mentionned "TZOFFSETFROM".
Resolution: Changed "TZOFFSETTO" to "TZOFFSETFROM".
Associated changes in this document: 3.6.5., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue79+4.6.5_dtstart_and_rdate_in_vtimezone   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-15 We need to clarify that "DTSTART" always specify a onset date-time of an observance and that its value does not need to be repeated in an "RDATE" property.
Resolution:
Associated changes in this document: 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 3.6.5, 4, 4.
 I  4.6.5_bad_dtstart   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 The "DAYLIGHT" sub-component in the "VTIMEZONE" example is using the wrong "DTSTART" value.
Resolution: Fixed.
Associated changes in this document: 3.6.5.
 I  4.6.5_bad_tzurl   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 TZURL should use example.com domain and specify the ".ics" file extension.
Resolution: Fixed.
Associated changes in this document: 3.6.5., Published in: draft-ietf-calsify-rfc2445bis-06

Component Name:
VTIMEZONE
Purpose:
Provide a grouping of component properties that defines a time zone.
Format Definition:
A "VTIMEZONE" calendar component is defined by the following notation:
     timezonec  = "BEGIN" ":" "VTIMEZONE" CRLF
                   I 2*(

                  ; 'tzid' is  I requiredREQUIRED, but MUST NOT occur more
                  ; than once

                  tzid /

                  ; 'last-mod' and 'tzurl' are  I optionalOPTIONAL,
                   I ; but MUST NOT occur more than once

                  last-mod / tzurl /

                  ; one of 'standardc' or 'daylightc' MUST occur
                   I ..; and each MAY occur more than once.

                  standardc / daylightc /

                  ; the following  I is optionalare OPTIONAL,
                  ; and MAY occur more than once

                  x-prop I  / iana-prop

                  )

                  "END" ":" "VTIMEZONE" CRLF

     standardc  = "BEGIN" ":" "STANDARD" CRLF
                  tzprop
                  "END" ":" "STANDARD" CRLF

     daylightc  = "BEGIN" ":" "DAYLIGHT" CRLF
                  tzprop
                  "END" ":" "DAYLIGHT" CRLF

     tzprop     =  I 3*(

                  ; the following are  I each REQUIRED,
                  ; but MUST NOT occur more than once

                  dtstart / tzoffsetto / tzoffsetfrom / I 

                  ; the following is OPTIONAL,
                  ; but SHOULD NOT occur more than once

                  rrule /
                
                  ; the following are  I optionalOPTIONAL,
                  ; and MAY occur more than once

                  comment / rdate /  I rrule / tzname / x-prop I  / iana-prop

                  )
Description:
A time zone is unambiguously defined by the set of time measurement rules determined by the governing body for a given geographic area. These rules describe at a minimum the base offset from UTC for the time zone, often referred to as the Standard Time offset. Many locations adjust their Standard Time forward or backward by one hour, in order to accommodate seasonal changes in number of daylight hours, often referred to as Daylight Saving Time. Some locations adjust their time by a fraction of an hour. Standard Time is also known as Winter Time. Daylight Saving Time is also known as Advanced Time, Summer Time, or Legal Time in certain countries. The following table shows the changes in time zone rules in effect for New York City starting from 1967. Each line represents a description or rule for a particular observance.

Effective Observance Rule

Date(Date/Time)OffsetAbbreviation
1967-*1973last Sun in OctApr, 02:00-05400ESDT
1967-19732006last Sun in AprOct, 02:00-04500EDST
1974-1974Jan 6, 02:00-0400EDT
1975-1975Feb 23, 02:00-0400EDT
1976-1986last Sun in Apr, 02:00-0400EDT
1987-*2006first Sun in Apr, 02:00-0400EDT
2007-* second Sun in Mar, 02:00 -0400 EDT
2007-* first Sun in Nov, 02:00 -0500 EST

Note: The specification of a global time zone registry is not addressed by this document and is left for future study. However, implementers may find the  I Olson time zone databaseTZ database [TZDB] a useful reference. It is an informal, public-domain collection of time zone information, which is currently being maintained by volunteer Internet participants, and is used in several operating systems. This database contains current and historical time zone information for a wide variety of locations around the globe; it provides a time zone identifier for every unique time zone rule set in actual use since 1970, with historical data going back to the introduction of standard time.

Interoperability between two calendaring and scheduling applications, especially for recurring events, to-dos or journal entries, is dependent on the ability to capture and convey date and time information in an unambiguous format. The specification of current time zone information is integral to this behavior.
If present, the "VTIMEZONE" calendar component defines the set of Standard Time and Daylight Saving Time observances (or rules) for a particular time zone for a given interval of time. The "VTIMEZONE" calendar component cannot be nested within other calendar components. Multiple "VTIMEZONE" calendar components can exist in an iCalendar object. In this situation, each "VTIMEZONE" MUST represent a unique time zone definition. This is necessary for some classes of events, such as airline flights, that start in one time zone and end in another.
 I The "VTIMEZONE" calendar component MUST be present if the iCalendar object contains an RRULE that generates dates on both sides of a time zone shift (e.g. both in Standard Time and Daylight Saving Time) unless the iCalendar object intends to convey a floating time (See the section "4.1.10.11 Time" for proper interpretation of floating time). It can be present if the iCalendar object does not contain such a RRULE. In addition, if a RRULE is present, there MUST be valid time zone information for all recurrence instances.
The "VTIMEZONE" calendar component MUST include the "TZID" property and at least one definition of a  I standard"STANDARD" or  I daylight"DAYLIGHT"  I sub-component. The  I standard"STANDARD" or  I daylight"DAYLIGHT"  I subcomponent MUST include the "DTSTART", "TZOFFSETFROM" and "TZOFFSETTO" properties.
An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object.  I In addition, a "VTIMEZONE" calendar component, referred to by a recurring calendar component, MUST provide valid time zone information for all recurrence instances.
Each "VTIMEZONE" calendar component consists of a collection of one or more sub-components that describe the rule for a particular observance (either a Standard Time or a Daylight Saving Time observance). The "STANDARD" sub-component consists of a collection of properties that describe Standard Time. The "DAYLIGHT" sub-component consists of a collection of properties that describe Daylight Saving Time. In general this collection of properties consists of:
For a given time zone, there may be multiple unique definitions of the observances over a period of time. Each observance is described using either a "STANDARD" or "DAYLIGHT" sub-component. The collection of these sub-components is used to describe the time zone for a given period of time. The offset to apply at any given time is found by locating the observance that has the last onset date and time before the time in question, and using the offset value from that observance.
The top-level properties in a "VTIMEZONE" calendar component are:
The mandatory "TZID" property is a text value that uniquely identifies the  I VTIMZONE"VTIMEZONE" calendar component within the scope of an iCalendar object.
The optional "LAST-MODIFIED" property is a UTC value that specifies the date and time that this time zone definition was last updated.
The optional "TZURL" property is  I a url value that points to a published  I "VTIMEZONE I " definition.  I "TZURL I " SHOULD refer to a resource that is accessible by anyone who might need to interpret the object. This SHOULD NOT normally be a  I file:"file" URL or other URL that is not widely-accessible.
The collection of properties that are used to define the  I "STANDARD I " and  I "DAYLIGHT I " sub-components include:
The mandatory "DTSTART" property gives the effective onset date and local time for the time zone sub-component definition. "DTSTART" in this usage MUST be specified as a local DATE-TIME value.
The mandatory "TZOFFSETFROM" property gives the UTC offset which is in use when the onset of this time zone observance begins. "TZOFFSETFROM" is combined with "DTSTART" to define the effective onset for the time zone sub-component definition. For example, the following represents the time at which the observance of Standard Time took effect in Fall 1967 for New York City:
     DTSTART:19671029T020000

     TZOFFSETFROM:-0400
The mandatory "TZOFFSETTO I " property gives the UTC offset for the time zone sub-component (Standard Time or Daylight Saving Time) when this observance is in use.
The optional "TZNAME" property is the customary name for the time zone. It may be specified multiple times, to allow for specifying multiple language variants of the time zone names. This could be used for displaying dates.
 I If specified,theThe onset  I date-times for the observance defined by the time zone sub-component is defined by  I either the  I "DTSTART", "RRULE" I or, and "RDATE"  I property.If neither is specified, only one sub-component can be specified in the "VTIMEZONE" calendar component and it is assumed that the single observance specified is always in effect.properties.
The "RRULE" property defines the recurrence rule for the onset of the observance defined by this time zone sub-component. Some specific requirements for the usage of  I "RRULE I " for this purpose include:
Alternatively, the "RDATE" property can be used to define the onset of the observance by giving the individual onset date and times. "RDATE" in this usage MUST be specified as a local DATE-TIME value I in UTC time, relative to the UTC offset specified in the "TZOFFSETFROM" property.
The optional "COMMENT" property is also allowed for descriptive explanatory text.
Example:
The following are examples of the "VTIMEZONE" calendar component:
This is an example showing all the time zone rules for New York City since April 30, 1967 at 03:00:00 EDT.
     BEGIN:VTIMEZONE
     TZID:America/New_York
     LAST-MODIFIED:20050809T050000Z
     BEGIN:DAYLIGHT
     DTSTART:19670430T020000
     RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19730429T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU;UNTIL=20061029T060000Z
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19740106T020000
     RDATE:19750223T020000
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:DAYLIGHT
     DTSTART:19760425T020000
     RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=-1SU;UNTIL=19860427T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU;UNTIL=20060402T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:DAYLIGHT
     DTSTART:20070311T020000
     RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:STANDARD
     DTSTART:20071104T020000
     RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     END:VTIMEZONE
This is an example showing time zone information for  I the Eastern United StatesNew York City using "RDATE" property. Note that this is only suitable for a recurring event that starts on or later than  I April 6, 1997March 11, 2007 at 03:00:00 EDT (i.e., the earliest effective transition date and time) and ends no later than  I April 7, 1998 02:00:00 ESTMarch 9, 2008 at 01:59:59 EST (i.e., latest valid date and time for EST in this scenario). For example, this can be used for a recurring event that occurs every Friday,  I 8am8:00 A.M.-9:00 A.M., starting June 1,  I 19972007, ending December 31,  I 19972007,
     BEGIN:VTIMEZONE
     TZID: I US-EasternAmerica/New_York
     LAST-MODIFIED: I 119870101T000000Z20050809T050000Z
     BEGIN:STANDARD
     DTSTART: I 19971026T02000020071104T020000 I 
     RDATE:19971026T020000
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART: I 19971026T02000020070311T020000 I 
     RDATE:19970406T020000
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE
This is a simple example showing the current time zone rules for  I the Eastern United StatesNew York City using a  I "RRULE I " recurrence pattern. Note that there is no effective end date to either of the Standard Time or Daylight Time rules. This information would be valid for a recurring event starting today and continuing indefinitely.
     BEGIN:VTIMEZONE
     TZID: I US-EasternAmerica/New_York
     LAST-MODIFIED: I 119870101T000000Z20050809T050000Z
  I 
     TZURL:http://zones.stds_r_us.net/tz/US-Eastern 
     TZURL:http://zones.example.com/tz/America-New_York.ics 
     BEGIN:STANDARD
     DTSTART: I 19671029T02000020071104T020000
     RRULE:FREQ=YEARLY; I BYDAY=-1SU;BYMONTH=10BYMONTH=11;BYDAY=1SU
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART: I 19870405T02000020070311T020000
     RRULE:FREQ=YEARLY; I BYDAY=1SU;BYMONTH=4BYMONTH=3;BYDAY=2SU
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE
This is an example showing a  I fictitious set of rules for the Eastern United States,set of rules for a fictitious time zone where the Daylight Time rule has an effective end date (i.e., after that date, Daylight Time is no longer observed).
     BEGIN:VTIMEZONE
     TZID: I US--Fictitious-EasternFictitious
     LAST-MODIFIED:19870101T000000Z
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE
This is an example showing a  I fictitious set of rules for the Eastern United States,set of rules for a fictitious time zone where the first Daylight Time rule has an effective end date. There is a second Daylight Time rule that picks up where the other left off.
     BEGIN:VTIMEZONE
     TZID: I US--Fictitious-EasternFictitious
     LAST-MODIFIED:19870101T000000Z
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:DAYLIGHT
     DTSTART:19990424T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE

3.6.6. Alarm Component

 I  #issue42+4.8.6.1_valarm_action_restriction   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-09-19 One should be allowed to specify an ACTION property with a "iana-token" or "x-name" value in a VALARM component.
Resolution: Removed the restriction on the allowed values for the ACTION property when used in VALARM components.
Associated changes in this document: 3.6.6., Published in: draft-ietf-calsify-rfc2445bis-06

Component Name:
VALARM
Purpose:
Provide a grouping of component properties that define an alarm.
Format Definition:
A "VALARM" calendar component is defined by the following notation:
     alarmc     = "BEGIN" ":" "VALARM" CRLF
                  (audioprop / dispprop / emailprop I  / procprop)
                  "END" ":" "VALARM" CRLF

     audioprop  =  I 2*(

                ; 'action' and 'trigger' are both REQUIRED,
                ; but MUST NOT occur more than once

                action / trigger /

                ; 'duration' and 'repeat' are both  I optionalOPTIONAL,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                attach /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                x-prop I  / iana-prop

                )

     dispprop   =  I 3*(

                ; the following are  I all REQUIRED,
                ; but MUST NOT occur more than once

                action / description / trigger /

                ; 'duration' and 'repeat' are both  I optionalOPTIONAL,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                 I *x-prop I  / iana-prop

                )

     emailprop  =  I 5*(

                ; the following are all REQUIRED,
                ; but MUST NOT occur more than once

                action / description / trigger / summary I  /

                ; the following is REQUIRED,
                ; and MAY occur more than once

                attendee /

                ; 'duration' and 'repeat' are both  I optionalOPTIONAL,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following are  I optionalOPTIONAL,
                ; and MAY occur more than once

                attach / x-prop I  / iana-prop

                )
 I 
     procprop   = 3*(

                ; the following are all REQUIRED,
                ; but MUST NOT occur more than once

                action / attach / trigger /

                ; 'duration' and 'repeat' are both optional,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; 'description' is optional,
                ; and MUST NOT occur more than once

                description /

                ; the following is optional,
                ; and MAY occur more than once

                x-prop

                )

Description:
A "VALARM" calendar component is a grouping of component properties that is a reminder or alarm for an event or a to-do. For example, it may be used to define a reminder for a pending event or an overdue to-do.
The "VALARM" calendar component MUST include the "ACTION" and "TRIGGER" properties. The "ACTION" property further constrains the "VALARM" calendar component in the following ways:
When the action is "AUDIO", the alarm can also include one and only one "ATTACH" property, which MUST point to a sound resource, which is rendered when the alarm is triggered.
When the action is "DISPLAY", the alarm MUST also include a "DESCRIPTION" property, which contains the text to be displayed when the alarm is triggered.
When the action is "EMAIL", the alarm MUST include a "DESCRIPTION" property, which contains the text to be used as the message body, a "SUMMARY" property, which contains the text to be used as the message subject, and one or more "ATTENDEE" properties, which contain the email address of attendees to receive the message. It can also include one or more "ATTACH" properties, which are intended to be sent as message attachments. When the alarm is triggered, the email message is sent.
When the action is "PROCEDURE", the alarm MUST include one and only one "ATTACH" property, which MUST point to a procedure resource, which is invoked when the alarm is triggered.
The "VALARM" calendar component MUST only appear within either a "VEVENT" or "VTODO" calendar component. "VALARM" calendar components cannot be nested. Multiple mutually independent "VALARM" calendar components can be specified for a single "VEVENT" or "VTODO" calendar component.
The "TRIGGER" property specifies when the alarm will be triggered. The "TRIGGER" property specifies a duration prior to the start of an event or a to-do. The "TRIGGER" edge may be explicitly set to be relative to the "START" or "END" of the event or to-do with the "RELATED" parameter of the "TRIGGER" property. The "TRIGGER" property value type can alternatively be set to an absolute calendar date  I and time of day value.with UTC time.
In an alarm set to trigger on the "START" of an event or to-do, the "DTSTART" property MUST be present in the associated event or to-do. In an alarm in a "VEVENT" calendar component set to trigger on the "END" of the event, either the "DTEND" property MUST be present, or the "DTSTART" and "DURATION" properties MUST both be present. In an alarm in a "VTODO" calendar component set to trigger on the "END" of the to-do, either the "DUE" property MUST be present, or the "DTSTART" and "DURATION" properties MUST both be present.
The alarm can be defined such that it triggers repeatedly. A definition of an alarm with a repeating trigger MUST include both the "DURATION" and "REPEAT" properties. The "DURATION" property specifies the delay period, after which the alarm will repeat. The "REPEAT" property specifies the number of additional repetitions that the alarm will  I be triggered. This  I repititionrepetition count is in addition to the initial triggering of the alarm. Both of these properties MUST be present in order to specify a repeating alarm. If one of these two properties is absent, then the alarm will not repeat beyond the initial trigger.
The "ACTION" property is used within the "VALARM" calendar component to specify the type of action invoked when the alarm is triggered. The "VALARM" properties provide enough information for a specific action to be invoked. It is typically the responsibility of a "Calendar User Agent" (CUA) to deliver the alarm in the specified fashion. An "ACTION" property value of AUDIO specifies an alarm that causes a sound to be played to alert the user; DISPLAY specifies an alarm that causes a text message to be displayed to the user;  I and EMAIL specifies an alarm that causes an electronic email message to be delivered to one or more email addresses I ; and PROCEDURE specifies an alarm that causes a procedure to be executed.  I The "ACTION" property MUST specify one and only one of these values.
In an AUDIO alarm, if the optional "ATTACH" property is included, it MUST specify an audio sound resource. The intention is that the sound will be played as the alarm effect. If an "ATTACH" property is specified that does not refer to a sound resource, or if the specified sound resource cannot be rendered (because its format is unsupported, or because it cannot be retrieved), then the CUA or other entity responsible for playing the sound may choose a fallback action, such as playing a built-in default sound, or playing no sound at all.
In a DISPLAY alarm, the intended alarm effect is for the text value of the "DESCRIPTION" property to be displayed to the user.
In an EMAIL alarm, the intended alarm effect is for an email message to be composed and delivered to all the addresses specified by the "ATTENDEE" properties in the "VALARM" calendar component. The "DESCRIPTION" property of the "VALARM" calendar component MUST be used as the body text of the message, and the "SUMMARY" property MUST be used as the subject text. Any "ATTACH" properties in the "VALARM" calendar component SHOULD be sent as attachments to the message.
In a PROCEDURE alarm, the "ATTACH" property in the "VALARM" calendar component MUST specify a procedure or program that is intended to be invoked as the alarm effect. If the procedure or program is in a format that cannot be rendered, then no procedure alarm will be invoked. If the "DESCRIPTION" property is present, its value specifies the argument string to be passed to the procedure or program. "Calendar User Agents" that receive an iCalendar object with this category of alarm, can disable or allow the "Calendar User" to disable, or otherwise ignore this type of alarm. While a very useful alarm capability, the PROCEDURE type of alarm SHOULD be treated by the "Calendar User Agent" as a potential security risk.
Example:
The following example is for a "VALARM" calendar component that specifies an audio alarm that will sound at a precise time and repeat 4 more times at 15 minute intervals:
     BEGIN:VALARM
     TRIGGER;VALUE=DATE-TIME:19970317T133000Z
     REPEAT:4
     DURATION:PT15M
     ACTION:AUDIO
     ATTACH;FMTTYPE=audio/basic:ftp:// I host.comexample.com/pub/
      sounds/bell-01.aud
     END:VALARM
The following example is for a "VALARM" calendar component that specifies a display alarm that will trigger 30 minutes before the scheduled start of the event or  I the due date/time of the to-do it is associated with and will repeat 2 more times at 15 minute intervals:
     BEGIN:VALARM
     TRIGGER:-PT30M
     REPEAT:2
     DURATION:PT15M
     ACTION:DISPLAY
     DESCRIPTION:Breakfast meeting with executive\n
      team at 8:30 AM EST.
     END:VALARM
The following example is for a "VALARM" calendar component that specifies an email alarm that will trigger 2 days before the scheduled due date/time of a to-do it is associated with. It does not repeat. The email has a subject, body and attachment link.
     BEGIN:VALARM
     TRIGGER;RELATED=END:-P2D
     ACTION:EMAIL
     ATTENDEE: I MAILTOmailto:john_doe@ I host.comexample.com
     SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING ***
     DESCRIPTION:A draft agenda needs to be sent out to the attendees
       to the weekly managers meeting (MGR-LIST). Attached is a
       pointer the document template for the agenda file.
     ATTACH;FMTTYPE= I application/binaryapplication/msword:http:// I host.comexample.com/
      templates/agenda.doc
     END:VALARM
The following example is for a "VALARM" calendar component that specifies a procedural alarm that will trigger at a precise date/time and will repeat 23 more times at one hour intervals. The alarm will invoke a procedure file.
     BEGIN:VALARM
     TRIGGER;VALUE=DATE-TIME:19980101T050000Z
     REPEAT:23
     DURATION:PT1H
     ACTION:PROCEDURE  I 
     ATTACH;FMTTYPE=application/binary:ftp:// I host.comexample.com/novo- 
     ATTACH;FMTTYPE=application/octet-stream:ftp:// I host.comexample.com/novo- 
      procs/felizano.exe
     END:VALARM

3.7. Calendar Properties

The Calendar Properties are attributes that apply to the iCalendar object, as a whole. These properties do not appear within a calendar component. They SHOULD be specified after the "BEGIN:VCALENDAR"  I propertydelimiter string and prior to any calendar component.

3.7.1. Calendar Scale

Property Name:
CALSCALE
Purpose:
This property defines the calendar scale used for the calendar information specified in the iCalendar object.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
 I PropertyThis property can be specified  I once in an iCalendar object. The default value is "GREGORIAN".
Description:
This memo is based on the Gregorian calendar scale. The Gregorian calendar scale is assumed if this property is not specified in the iCalendar object. It is expected that other calendar scales will be defined in other specifications or by future versions of this memo.
Format Definition:
 I TheThis property is defined by the following notation:
     calscale   = "CALSCALE" calparam ":" calvalue CRLF

     calparam   = *(";"  I xparamother-param)

     calvalue   = "GREGORIAN" I  / iana-token
Example:
The following is an example of this property:
     CALSCALE:GREGORIAN

3.7.2. Method

Property Name:
METHOD
Purpose:
This property defines the iCalendar object method associated with the calendar object.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified  I once in an iCalendar object.
Description:
When used in a MIME message entity, the value of this property MUST be the same as the Content-Type "method" parameter value.  I This property can only appear once within the iCalendar object. If either the "METHOD" property or the Content-Type "method" parameter is specified, then the other MUST also be specified.
No methods are defined by this specification. This is the subject of other specifications, such as the iCalendar Transport-independent Interoperability Protocol (iTIP) defined by  I [RFC2446][I-D.ietf-calsify-2446bis].
If this property is not present in the iCalendar object, then a scheduling transaction MUST NOT be assumed. In such cases, the iCalendar object is merely being used to transport a snapshot of some calendar information; without the intention of conveying a scheduling semantic.
Format Definition:
 I TheThis property is defined by the following notation:
     method     = "METHOD" metparam ":" metvalue CRLF

     metparam   = *(";"  I xparamother-param)

     metvalue   = iana-token
Example:
The following is a hypothetical example of this property to convey that the iCalendar object is a  I scheduling request I for a meeting:
     METHOD:REQUEST

3.7.3. Product Identifier

Property Name:
PRODID
Purpose:
This property specifies the identifier for the product that created the iCalendar object.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property MUST be specified once in an iCalendar object.
Description:
The vendor of the implementation SHOULD assure that this is a globally unique identifier; using some technique such as an FPI value, as defined in [ISO.9070.1991].
This property SHOULD not be used to alter the interpretation of an iCalendar object beyond the semantics specified in this memo. For example, it is not to be used to further the understanding of non-standard properties.
Format Definition:
 I TheThis property is defined by the following notation:
     prodid     = "PRODID" pidparam ":" pidvalue CRLF

     pidparam   = *(";"  I xparamother-param)

     pidvalue   = text
     ;Any text that describes the product and version
     ;and that is generally assured of being unique.
Example:
The following is an example of this property. It does not imply that English is the default language.
     PRODID:-//ABC Corporation//NONSGML My Product//EN

3.7.4. Version

Property Name:
VERSION
Purpose:
This property specifies the identifier corresponding to the highest version number or the minimum and maximum range of the iCalendar specification that is required in order to interpret the iCalendar object.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be specified  I byonce in an iCalendar object I , but MUST only be specified once
Description:
A value of "2.0" corresponds to this memo.
Format Definition:
 I TheThis property is defined by the following notation:
     version    = "VERSION" verparam ":" vervalue CRLF

     verparam   = *(";"  I xparamother-param)

     vervalue   = "2.0"         ;This memo
                / maxver
                / (minver ";" maxver)

     minver     = <A IANA registered iCalendar version identifier>
     ;Minimum iCalendar version needed to parse the iCalendar object

     maxver     = <A IANA registered iCalendar version identifier>
     ;Maximum iCalendar version needed to parse the iCalendar object
Example:
The following is an example of this property:
     VERSION:2.0

3.8. Component Properties

The following properties can appear within calendar components, as specified by each component property definition.

3.8.1. Descriptive Component Properties

The following properties specify descriptive information about calendar components.

3.8.1.1. Attachment

 I  4.8.1.1_attach_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "ATTACH" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.1.1, 3.8.1.1.

Property Name:
ATTACH
Purpose:
 I TheThis property provides the capability to associate a document object with a calendar component.
Value Type:
The default value type for this property is URI. The value type can also be set to BINARY to indicate inline binary encoded content information.
Property Parameters:
 I Non-standardIANA, non-standard, inline encoding, format type and value data type property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified  I multiple times in a "VEVENT", "VTODO", "VJOURNAL" or "VALARM" calendar component I s  I with the exception of AUDIO alarm which only allow this property to occur once.
Description:
 I The property can be specified within "VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components. This property can be specified multiple times within an iCalendar object.This property is used in "VEVENT", "VTODO", and "VJOURNAL" calendar components to associate a resource (e.g., document) with the calendar component. This property is used in "VALARM" calendar components to specify an audio sound resource or an email message attachment. This property can be specified as a URI pointing to a resource or as inline binary encoded content.
Format Definition:
 I TheThis property is defined by the following notation:
     attach      = "ATTACH"  I attparamattachparam ":" uri  CRLF

      I attach     =            / "ATTACH"  I attparamattachparam ";" "ENCODING" "=" "BASE64"
                   ";" "VALUE" "=" "BINARY" ":" binary

      I attparamattachparam = *(

                 ; the following is  I optionalOPTIONAL,
                 ; but MUST NOT occur more than once

                 (";" fmttypeparam) /

                 ; the following is  I optionalOPTIONAL,
                 ; and MAY occur more than once

                 (";"  I xparamother-param)

                 )
Example:
The following are examples of this property:
     ATTACH:CID:jsmith.part3.960817T083000.xyzMail@ I host1.comexample.com

     ATTACH;FMTTYPE=application/postscript:ftp:// I xyzCorp.comexample.com/pub/
      reports/r-960812.ps

3.8.1.2. Categories

Property Name:
CATEGORIES
Purpose:
This property defines the categories for a calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, and language property parameters can be specified on this property.
Conformance:
The property can be specified within "VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description:
This property is used to specify categories or subtypes of the calendar component. The categories are useful in searching for a calendar component of a particular type and category. Within the "VEVENT", "VTODO" or "VJOURNAL" calendar components, more than one category can be specified as a list of categories separated by the COMMA character (US-ASCII decimal 44).
Format Definition:
 I TheThis property is defined by the following notation:
     categories = "CATEGORIES" catparam ":" text *("," text)
                  CRLF

     catparam   = *(

                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" languageparam ) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following are examples of this property:
     CATEGORIES:APPOINTMENT,EDUCATION

     CATEGORIES:MEETING

3.8.1.3. Classification

Property Name:
CLASS
Purpose:
This property defines the access classification for a calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property can be specified once in a "VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description:
An access classification is only one component of the general security system within a calendar application. It provides a method of capturing the scope of the access the calendar owner intends for information within an individual calendar entry. The access classification of an individual iCalendar component is useful when measured along with the other security components of a calendar system (e.g., calendar user authentication, authorization, access rights, access role, etc.). Hence, the semantics of the individual access classifications cannot be completely defined by this memo alone. Additionally, due to the "blind" nature of most exchange processes using this memo, these access classifications cannot serve as an enforcement statement for a system receiving an iCalendar object. Rather, they provide a method for capturing the intention of the calendar owner for the access to the calendar component.  I If not specified in a component that allows this property, the default value is PUBLIC. Applications MUST treat x-name and iana-token value they don't recognized the same way as the PRIVATE value.
Format Definition:
 I TheThis property is defined by the following notation:
     class      = "CLASS" classparam ":" classvalue CRLF

     classparam = *(";"  I xparamother-param)

     classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token
                / x-name
     ;Default is PUBLIC
Example:
The following is an example of this property:
     CLASS:PUBLIC

3.8.1.4. Comment

 I  4.8.1.4_comment_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "COMMENT" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.1.4.

Property Name:
COMMENT
Purpose:
This property specifies non-processing information intended to provide a comment to the calendar user.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
This property can be specified  I multiple times in "VEVENT", "VTODO", "VJOURNAL",  I "VTIMEZONE" orand "VFREEBUSY" calendar components  I as well as in the "STANDARD" and "DAYLIGHT" sub-components.
Description:
 I The property can be specified multiple times.This property is used to specify a comment to the calendar user.
Format Definition:
 I TheThis property is defined by the following notation:
     comment    = "COMMENT" commparam ":" text CRLF

     commparam  = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of this property:
     COMMENT:The meeting really needs to include both ourselves
       and the customer. We can't hold this meeting without them.
       As a matter of fact\, the venue for the meeting ought to be at
       their site. - - John
 I  4.8.1.4_redundant_type_info   (type: edit, status: closed)
bernard.desruisseaux@oracle.com2006-06-21 Redundant info.
Resolution: Removed text.
Associated changes in this document: 3.8.1.4., Published in: draft-ietf-calsify-rfc2445bis-01
The data type for this property is TEXT.

3.8.1.5. Description

Property Name:
DESCRIPTION
Purpose:
This property provides a more complete description of the calendar component, than that provided by the "SUMMARY" property.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
The property can be specified in the "VEVENT", "VTODO", "VJOURNAL" or "VALARM" calendar components. The property can be specified multiple times only within a "VJOURNAL" calendar component.
Description:
This property is used in the "VEVENT" and "VTODO" to capture lengthy textual decriptions associated with the activity.
This property is used in the "VJOURNAL" calendar component to capture one  I or more textual journal entries.
This property is used in the "VALARM" calendar component to capture the display text for a DISPLAY category of alarm,  I and to capture the body text for an EMAIL category of alarm I and to capture the argument string for a PROCEDURE category of alarm.
Format Definition:
 I TheThis property is defined by the following notation:
     description        = "DESCRIPTION" descparam ":" text CRLF

     descparam  = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of  I thethis property with formatted line breaks in the property value:
     DESCRIPTION:Meeting to provide technical review for "Phoenix"
       design.\n I  Happy Face Conference Room. Phoenix design team
       MUST attend this meeting.\n I  RSVP to team leader.
The following is an example of the property with folding of long lines:
         DESCRIPTION:Last draft of the new novel is to be completed
           for the editor's proof today.
    

3.8.1.6. Geographic Position

Property Name:
GEO
Purpose:
This property specifies information related to the global position for the activity specified by a calendar component.
Value Type:
FLOAT. The value MUST be two SEMICOLON separated FLOAT values.
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified in "VEVENT" or "VTODO" calendar components.
Description:
 I TheThis property value specifies latitude and longitude, in that order (i.e., "LAT LON" ordering). The longitude represents the location  I eastEast or  I westWest of the prime meridian as a positive or negative real number, respectively. The longitude and latitude values MAY be specified up to six decimal places, which will allow for accuracy to within one meter of geographical position. Receiving applications MUST accept values of this precision and MAY truncate values of greater precision.
Values for latitude and longitude shall be expressed as decimal fractions of degrees. Whole degrees of latitude shall be represented by a two-digit decimal number ranging from 0 through 90. Whole degrees of longitude shall be represented by a decimal number ranging from 0 through 180. When a decimal fraction of a degree is specified, it shall be separated from the whole number of degrees by a decimal point.
Latitudes  I nNorth of the equator shall be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the digits designating degrees. Latitudes  I sSouth of the Equator shall be designated by a minus sign (-) preceding the digits designating degrees. A point on the Equator shall be assigned to the Northern Hemisphere.
Longitudes east of the prime meridian shall be specified by a plus sign (+), or by the absence of a minus sign (-), preceding the digits designating degrees. Longitudes west of the meridian shall be designated by minus sign (-) preceding the digits designating degrees. A point on the prime meridian shall be assigned to the Eastern Hemisphere. A point on the 180th meridian shall be assigned to the Western Hemisphere. One exception to this last convention is permitted. For the special condition of describing a band of latitude around the earth, the East Bounding Coordinate data element shall be assigned the value +180 (180) degrees.
Any spatial address with a latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively. The component for longitude may have any legal value.
With the exception of the special condition described above, this form is specified in Department of Commerce, 1986, Representation of geographic point locations for information interchange (Federal Information Processing Standard 70-1): Washington, Department of Commerce, National Institute of Standards and Technology.
The simple formula for converting degrees-minutes-seconds into decimal degrees is:
decimal = degrees + minutes/60 + seconds/3600.
Format Definition:
 I TheThis property is defined by the following notation:
     geo        = "GEO" geoparam ":" geovalue CRLF

     geoparam   = *(";"  I xparamother-param)

     geovalue   = float ";" float
     ;Latitude and Longitude components
Example:
The following is an example of this property:
     GEO:37.386013;-122.082932

3.8.1.7. Location

Property Name:
LOCATION
Purpose:
 I TheThis property defines the intended venue for the activity defined by a calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
This property can be specified in "VEVENT" or "VTODO" calendar component.
Description:
Specific venues such as conference or meeting rooms may be explicitly specified using this property. An alternate representation may be specified that is a URI that points to directory information with more structured specification of the location. For example, the alternate representation may specify either an LDAP  I URIURL [RFC4516] pointing to an LDAP server entry or a CID  I URIURL [RFC2392] pointing to a MIME body part containing a vCard [RFC2426] for the location.
Format Definition:
 I TheThis property is defined by the following notation:
     location   = "LOCATION I "  locparam ":" text CRLF

     locparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following are some examples of this property:
     LOCATION:Conference Room - F123 I \, Bldg. 002

     LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
      Conference Room - F123 I \, Bldg. 002

3.8.1.8. Percent Complete

Property Name:
PERCENT-COMPLETE
Purpose:
This property is used by an assignee or delegatee of a to-do to convey the percent completion of a to-do to the  I "Organizer I ".
Value Type:
INTEGER
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified  I once in a "VTODO" calendar component.
Description:
The property value is a positive integer between zero and one hundred. A value of "0" indicates the to-do has not yet been started. A value of "100" indicates that the to-do has been completed. Integer values in between indicate the percent partially complete.
When a to-do is assigned to multiple individuals, the property value indicates the percent complete for that portion of the to-do assigned to the assignee or delegatee. For example, if a to-do is assigned to both individuals "A" and "B". A reply from "A" with a percent complete of "70" indicates that "A" has completed 70% of the to-do assigned to them. A reply from "B" with a percent complete of "50" indicates "B" has completed 50% of the to-do assigned to them.
Format Definition:
 I TheThis property is defined by the following notation:
     percent = "PERCENT-COMPLETE" pctparam ":" integer CRLF

     pctparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property to show 39% completion:
     PERCENT-COMPLETE:39

3.8.1.9. Priority

Property Name:
PRIORITY
Purpose:
 I TheThis property defines the relative priority for a calendar component.
Value Type:
INTEGER
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified in  I a "VEVENT"  I orand "VTODO" calendar component I s.
Description:
 I TheThis priority is specified as an integer in the range zero to nine. A value of zero (US-ASCII decimal 48) specifies an undefined priority. A value of one (US-ASCII decimal 49) is the highest priority. A value of two (US-ASCII decimal 50) is the second highest priority. Subsequent numbers specify a decreasing ordinal priority. A value of nine (US-ASCII decimal  I 5857) is the lowest priority.
A CUA with a three-level priority scheme of "HIGH", "MEDIUM" and "LOW" is mapped into this property such that a property value in the range of one (US-ASCII decimal 49) to four (US-ASCII decimal 52) specifies "HIGH" priority. A value of five (US-ASCII decimal 53) is the normal or "MEDIUM" priority. A value in the range of six (US-ASCII decimal 54) to nine (US-ASCII decimal  I 5857) is "LOW" priority.
A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ..., "C3" is mapped into this property such that a property value of one (US-ASCII decimal 49) specifies "A1", a property value of two (US-ASCII decimal 50) specifies "A2", a property value of three (US-ASCII decimal 51) specifies "A3", and so forth up to a property value of 9 (US-ASCII decimal  I 5857) specifies "C3".
Other integer values are reserved for future use.
Within a "VEVENT" calendar component, this property specifies a priority for the event. This property may be useful when more than one event is scheduled for a given time period.
Within a "VTODO" calendar component, this property specified a priority for the to-do. This property is useful in prioritizing multiple action items for a given time period.
Format Definition:
 I TheThis property is  I specifieddefined by the following notation:
     priority   = "PRIORITY" prioparam ":" pri I ovalue CRLF
     ;Default is zero  I (i.e., undefined)

     prioparam  = *(";"  I xparamother-param)

     pri I ovalue   = integer       ;Must be in the range [0..9]
        ; All other values are reserved for future use
The following is an example of a property with the highest priority:
     PRIORITY:1
 I Example:
The following is an example of a property with the highest priority:
     PRIORITY:1
The following is an example of a property with a next highest priority:
     PRIORITY:2
 I Example:The following is an example of a property with no priority. This is equivalent to not specifying the "PRIORITY" property:
     PRIORITY:0

3.8.1.10. Resources

Property Name:
RESOURCES
Purpose:
This property defines the equipment or resources anticipated for an activity specified by a calendar  I entity..component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
This property can be specified  I once in "VEVENT" or "VTODO" calendar component.
Description:
The property value is an arbitrary text. More than one resource can be specified as a list of resources separated by the COMMA character (US-ASCII decimal 44).
Format Definition:
 I TheThis property is defined by the following notation:
     resources  = "RESOURCES" resrcparam ":" text *("," text) CRLF

     resrcparam = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of this property:
     RESOURCES:EASEL,PROJECTOR,VCR

     RESOURCES;LANGUAGE=fr:1 raton-laveur

3.8.1.11. Status

Property Name:
STATUS
Purpose:
This property defines the overall status or confirmation for the calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified  I once in "VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description:
In a group scheduled calendar component, the property is used by the "Organizer" to provide a confirmation of the event to the "Attendees". For example in a "VEVENT" calendar component, the "Organizer" can indicate that a meeting is tentative, confirmed or cancelled. In a "VTODO" calendar component, the "Organizer" can indicate that an action item needs action, is completed, is in process or being worked on, or has been cancelled. In a "VJOURNAL" calendar component, the "Organizer" can indicate that a journal entry is draft, final or has been cancelled or removed.
Format Definition:
 I TheThis property is defined by the following notation:
     status          = "STATUS" statparam I ]  ":" statvalue CRLF

     statparam       = *(";"  I xparamother-param)

      I statvalue       = (statvalue-event
                     /  statvalue-todo
                     /  statvalue-jour) 

     statvalue I -event = "TENTATIVE"    ;Indicates event is tentative.
                     / "CONFIRMED"    ;Indicates event is definite.
                     / "CANCELLED"    ;Indicates event was cancelled.
     ;Status values for a "VEVENT"

     statvalue I -todo  = I / "NEEDS-ACTION" ;Indicates to-do needs action.
                     / "COMPLETED"    ;Indicates to-do completed.
                     / "IN-PROCESS"   ;Indicates to-do in process of I .
                     / "CANCELLED"    ;Indicates to-do was cancelled.
     ;Status values for "VTODO".

     statvalue I -jour  = I / "DRAFT"        ;Indicates journal is draft.
                     / "FINAL"        ;Indicates journal is final.
                     / "CANCELLED"    ;Indicates journal is removed.
    ;Status values for "VJOURNAL".
Example:
The following is an example of this property for a "VEVENT" calendar component:
     STATUS:TENTATIVE
The following is an example of this property for a "VTODO" calendar component:
     STATUS:NEEDS-ACTION
The following is an example of this property for a "VJOURNAL" calendar component:
     STATUS:DRAFT

3.8.1.12. Summary

Property Name:
SUMMARY
Purpose:
This property defines a short summary or subject for the calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
The property can be specified in "VEVENT", "VTODO", "VJOURNAL" or "VALARM" calendar components.
Description:
This property is used in the "VEVENT", "VTODO" and "VJOURNAL" calendar components to capture a short, one line summary about the activity or journal entry.
This property is used in the "VALARM" calendar component to capture the subject of an EMAIL category of alarm.
Format Definition:
 I TheThis property is defined by the following notation:
     summary    = "SUMMARY" summparam ":" text CRLF

     summparam  = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of this property:
     SUMMARY:Department Party

3.8.2. Date and Time Component Properties

The following properties specify date and time related information in calendar components.

3.8.2.1. Date/Time Completed

 I  4.8.2.1_completed_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "COMPLETED" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.2.1, 3.8.2.1.

Property Name:
COMPLETED
Purpose:
This property defines the date and time that a to-do was actually completed.
Value Type:
DATE-TIME
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property can be specified in a "VTODO" calendar component.  I The value MUST be specified as a date with UTC time.
Description:
 I The date and time MUST be in a UTC format.This property defines the date and time that a to-do was actually completed.
Format Definition:
 I TheThis property is defined by the following notation:
     completed  = "COMPLETED" compparam ":" date-time CRLF

     compparam  = *(";"  I xparamother-param)
Example:
The following is an example of this property:
  COMPLETED:19960401T I 235959150000Z

3.8.2.2. Date/Time End

 I  #issue76+4.8.2.2_dtend_dtstart_value_type   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-13 We should clarify that the value type of the "DTEND" property MUST be the same as the "DTSTART" property
Resolution: Done.
Associated changes in this document: 3.8.2.2.

Property Name:
DTEND
Purpose:
This property specifies the date and time that a calendar component ends.
Value Type:
The default value type is DATE-TIME. The value type can be set to a DATE value type.
Property Parameters:
 I Non-standardIANA, non-standard, value data type,  I and time zone identifier property parameters can be specified on this property.
Conformance:
This property can be specified in "VEVENT" or "VFREEBUSY" calendar components.
Description:
Within the "VEVENT" calendar component, this property defines the date and time by which the event ends. The  I value type of this property MUST be the same as the "DTSTART" property, and its value MUST be later in time than the value of the "DTSTART" property.  I Furthermore, this property MUST be specified as a date with local time if and only if the "DTSTART" property is also specified as a date with local time.
Within the "VFREEBUSY" calendar component, this property defines the end date and time for the free or busy time information. The time MUST be specified in the UTC time format. The value MUST be later in time than the value of the "DTSTART" property.
Format Definition:
 I TheThis property is defined by the following notation:
     dtend      = "DTEND" dtendparam I  ":" dtendval CRLF

     dtendparam = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once


                (";"  I xparamother-param)

                )

     dtendval   = date-time / date
     ;Value MUST match value type
Example:
The following is an example of this property:
     DTEND:19960401T I 235959150000Z

     DTEND;VALUE=DATE:19980704

3.8.2.3. Date/Time Due

 I  #issue77+4.8.2.3_due_dtstart_value_type   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-13 We should clarify that the value type of the "DUE" property MUST be the same as the "DTSTART" property
Resolution: Done.
Associated changes in this document: 3.8.2.3.
 I  4.8.2.3_due_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "DUE" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.2.3.

Property Name:
DUE
Purpose:
This property defines the date and time that a to-do is expected to be completed.
Value Type:
The default value type is DATE-TIME. The value type can be set to a DATE value type.
Property Parameters:
 I Non-standardIANA, non-standard, value data type,  I and time zone identifier property parameters can be specified on this property.
Conformance:
The property can be specified once in a "VTODO" calendar component.
Description:
 I This property defines the date and time that a to-do is expected to be completed.  I The value MUST be a date/time equal to or after the DTSTART value, if specified.For cases where this property is specified in a "VTODO" calendar component that also specifies a "DTSTART" property, the value type of this property MUST be the same as the "DTSTART" property, and the value of this property MUST be later in time than the value of the "DTSTART" property.  I Furthermore, this property MUST be specified as a date with local time if and only if the "DTSTART" property is also specified as a date with local time.
Format Definition:
 I TheThis property is defined by the following notation:
     due        = "DUE" dueparam I  ":" dueval CRLF

     dueparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                 I *(";"  I xparamother-param)

                )

     dueval     = date-time / date
     ;Value MUST match value type
Example:
The following is an example of this property:
     DUE:19980430T I 235959000000Z

3.8.2.4. Date/Time Start

 I  #issue29+dtstart_in_recur_vtodo_and_vjournal   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 Clarify that the DTSTART property is required in recurring VTODO and VJOURNAL components.
Resolution: Done.
Associated changes in this document: 3.8.2.4, 3.8.2.4., Published in: draft-ietf-calsify-rfc2445bis-04

Property Name:
DTSTART
Purpose:
This property specifies when the calendar component begins.
Value Type:
The default value type is DATE-TIME. The time value MUST be one of the forms defined for the DATE-TIME value type. The value type can be set to a DATE value type.
Property Parameters:
 I Non-standardIANA, non-standard, value data type,  I and time zone identifier property parameters can be specified on this property.
Conformance:
This property can be specified  I once in the "VEVENT", "VTODO",  I or "VFREEBUSY" I , or "VTIMEZONE" calendar components  I as well as in the "STANDARD" and "DAYLIGHT" sub-components.  I This property is REQUIRED in "VEVENT" calendar components and in all types of recurring calendar components.
Description:
Within the "VEVENT" calendar component, this property defines the start date and time for the event.  I The property is REQUIRED in "VEVENT" calendar components.  I Events can have a start date/time but no end date/time. In that case, the event does not take up any time.
Within the "VFREEBUSY" calendar component, this property defines the start date and time for the free or busy time information. The time MUST be specified in UTC time.
Within the  I "VTIMEZONE" calendar component"STANDARD" and "DAYLIGHT" sub-components, this property defines the effective start date and time for a time zone specification. This property is REQUIRED within each  I "STANDARD I " and  I "DAYLIGHT I "  I partsub-components included in "VTIMEZONE" calendar components and MUST be specified as a local DATE-TIME without the "TZID" property parameter.
Format Definition:
 I TheThis property is defined by the following notation:
     dtstart    = "DTSTART" dtstparam ":" dtstval CRLF

     dtstparam  = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                 I *(";"  I xparamother-param)

                )

     dtstval    = date-time / date
     ;Value MUST match value type
Example:
The following is an example of this property:
     DTSTART:19980118T073000Z

3.8.2.5. Duration

Property Name:
DURATION
Purpose:
 I TheThis property specifies a positive duration of time.
Value Type:
DURATION
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified in "VEVENT", "VTODO", "VFREEBUSY" or "VALARM" calendar components.
Description:
In a "VEVENT" calendar component the property may be used to specify a duration of the event, instead of an explicit end date/time. In a "VTODO" calendar component the property may be used to specify a duration for the to-do, instead of an explicit due date/time. In a "VFREEBUSY" calendar component the property may be used to specify the interval of free time being requested. In a "VALARM" calendar component the property may be used to specify the delay period prior to repeating an alarm.  I When the "DURATION" property relates to a "DTSTART" property that is specified as a DATE value, then the "DURATION" property MUST be specified as a "dur-day" or "dur-week" value.
Format Definition:
 I TheThis property is defined by the following notation:
     duration   = "DURATION" durparam ":" dur-value CRLF
                  ;consisting of a positive duration of time.

                  durparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property that specifies an interval of time of 1 hour and zero minutes and zero seconds:
     DURATION:PT1H0M0S
The following is an example of this property that specifies an interval of time of 15 minutes.
     DURATION:PT15M

3.8.2.6. Free/Busy Time

Property Name:
FREEBUSY
Purpose:
 I TheThis property defines one or more free or busy time intervals.
Value Type:
PERIOD I . The date and time values MUST be in  I ana UTC time format.
Property Parameters:
 I Non-standardIANA, non-standard I or, and free/busy time type property parameters can be specified on this property.
Conformance:
The property can be specified in a "VFREEBUSY" calendar component.
 I Property Parameter:
"FBTYPE" and non-standard parameters can be specified on this property.
Description:
These time periods can be specified as either a start and end date-time or a start date-time and duration. The date and time MUST be a UTC time format.
"FREEBUSY" properties within the "VFREEBUSY" calendar component SHOULD be sorted in ascending order, based on start time and then end time, with the earliest periods first.
The "FREEBUSY" property can specify more than one value, separated by the COMMA character (US-ASCII decimal 44). In such cases, the "FREEBUSY" property values  I SHOULDMUST all be of the same "FBTYPE" property parameter type (e.g., all values of a particular "FBTYPE" listed together in a single property).
Format Definition:
 I TheThis property is defined by the following notation:
     freebusy   = "FREEBUSY" fbparam ":" fbvalue CRLF

     fbparam    = *(
                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" fbtypeparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )

     fbvalue    = period * I [("," period I ])
     ;Time value MUST be in the UTC time format.
Example:
The following are some examples of this property:
     FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M

     FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H

     FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H
      ,19970308T230000Z/19970309T000000Z

3.8.2.7. Time Transparency

Property Name:
TRANSP
Purpose:
This property defines whether an event is transparent or not to busy time searches.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified once in a "VEVENT" calendar component.
Description:
Time Transparency is the characteristic of an event that determines whether it appears to consume time on a calendar. Events that consume actual time for the individual or resource associated with the calendar SHOULD be recorded as OPAQUE, allowing them to be detected by free-busy time searches. Other events, which do not take up the individual's (or resource's) time SHOULD be recorded as TRANSPARENT, making them invisible to free-busy time searches.
Format Definition:
 I TheThis property is  I specifieddefined by the following notation:
     transp     = "TRANSP"  I tranparamtransparam ":" transvalue CRLF

      I tranparam transparam = *(";"  I xparamother-param)

     transvalue = "OPAQUE"
                 ;Blocks or opaque on busy time searches.
                 / "TRANSPARENT"
                 ;Transparent on busy time searches.
     ;Default value is OPAQUE
Example:
The following is an example of this property for an event that is transparent or does not block on free/busy time searches:
     TRANSP:TRANSPARENT
The following is an example of this property for an event that is opaque or blocks on free/busy time searches:
     TRANSP:OPAQUE

3.8.3. Time Zone Component Properties

The following properties specify time zone information in calendar components.

3.8.3.1. Time Zone Identifier

 I  #issue73+4.8.3.1_tzid_scope   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 We need to clarify the "scope" in which a TZID MUST be unique.
Resolution: Clarified that the TZID must be unique in the scope of an iCalendar object only.
Associated changes in this document: 3.8.3.1., Published in: draft-ietf-calsify-rfc2445bis-06

Property Name:
TZID
Purpose:
This property specifies the text value that uniquely identifies the "VTIMEZONE" calendar component  I in the scope of an iCalendar object.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be specified in a "VTIMEZONE" calendar component.
Description:
This is the label by which a time zone calendar component is referenced by any iCalendar properties whose  I datavalue type is either DATE-TIME or TIME and not intended to specify a UTC or a "floating" time. The presence of the SOLIDUS character (US-ASCII decimal 47) as a prefix, indicates that this  I "TZID I " represents an unique ID in a globally defined time zone registry (when such registry is defined).
Note: This document does not define a naming convention for time zone identifiers. Implementers may want to use the naming conventions defined in existing time zone specifications such as the public-domain  I Olson databaseTZ database [TZDB]. The specification of globally unique time zone identifiers is not addressed by this document and is left for future study.
Format Definition:
This property is defined by the following notation:
     tzid       = "TZID" tzidpropparam ":" [tzidprefix] text CRLF

     tzidpropparam      = *(";"  I xparamother-param)

     ;tzidprefix        = "/"
     ; Defined previously. Just listed here for reader convenience.
Example:
The following are examples of non-globally unique time zone identifiers:
     TZID: I US-EasternAmerica/New_York

     TZID: I California-Los_AngelesAmerica/Los_Angeles
The following is an example of a fictitious globally unique time zone identifier:
     TZID: I /US-New_York-New_York/example.org/America/New_York

3.8.3.2. Time Zone Name

Property Name:
TZNAME
Purpose:
This property specifies the customary designation for a time zone description.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, and language property parameters can be specified on this property.
Conformance:
This property can be specified in  I a "VTIMEZONE" calendar component."STANDARD" and "DAYLIGHT" sub-components.
Description:
This property may be specified in multiple languages; in order to provide for different language requirements.
Format Definition:
This property is defined by the following notation:
     tzname     = "TZNAME" tznparam ":" text CRLF

     tznparam   = *(

                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following are example of this property:
     TZNAME:EST
The following is an example of this property when two different languages for the time zone name are specified:
     TZNAME;LANGUAGE=en:EST
     TZNAME;LANGUAGE=fr-CA:HNE

3.8.3.3. Time Zone Offset From

Property Name:
TZOFFSETFROM
Purpose:
This property specifies the offset which is in use prior to this time zone observance.
Value Type:
UTC-OFFSET
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be specified in  I a "VTIMEZONE" calendar component."STANDARD" and "DAYLIGHT" sub-components.
Description:
This property specifies the offset which is in use prior to this time observance. It is used to calculate the absolute time at which the transition to a given observance takes place. This property MUST only be specified in a "VTIMEZONE" calendar component. A "VTIMEZONE" calendar component MUST include this property. The property value is a signed numeric indicating the number of hours and possibly minutes from UTC. Positive numbers represent time zones east of the prime meridian, or ahead of UTC. Negative numbers represent time zones west of the prime meridian, or behind UTC.
Format Definition:
 I TheThis property is defined by the following notation:
     tzoffsetfrom       = "TZOFFSETFROM" frmparam ":" utc-offset
                          CRLF

     frmparam   = *(";"  I xparamother-param)
Example:
The following are examples of this property:
     TZOFFSETFROM:-0500

     TZOFFSETFROM:+1345

3.8.3.4. Time Zone Offset To

Property Name:
TZOFFSETTO
Purpose:
This property specifies the offset which is in use in this time zone observance.
Value Type:
UTC-OFFSET
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be specified in  I a "VTIMEZONE" calendar component."STANDARD" and "DAYLIGHT" sub-components.
Description:
This property specifies the offset which is in use in this time zone observance. It is used to calculate the absolute time for the new observance. The property value is a signed numeric indicating the number of hours and possibly minutes from UTC. Positive numbers represent time zones east of the prime meridian, or ahead of UTC. Negative numbers represent time zones west of the prime meridian, or behind UTC.
Format Definition:
 I TheThis property is defined by the following notation:
     tzoffsetto = "TZOFFSETTO" toparam ":" utc-offset CRLF

     toparam    = *(";"  I xparamother-param)
Example:
The following are examples of this property:
     TZOFFSETTO:-0400

     TZOFFSETTO:+1245

3.8.3.5. Time Zone URL

Property Name:
TZURL
Purpose:
 I The TZURLThis property provides a means for a  I "VTIMEZONE I " component to point to a network location that can be used to retrieve an up-to-date version of itself.
Value Type:
URI
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified in a "VTIMEZONE" calendar component.
Description:
 I The TZURLThis property provides a means for a  I "VTIMEZONE I " component to point to a network location that can be used to retrieve an up-to-date version of itself. This provides a hook to handle changes government bodies impose upon time zone definitions. Retrieval of this resource results in an iCalendar object containing a single  I "VTIMEZONE I " component and a  I "METHOD I " property set to PUBLISH.
Format Definition:
 I TheThis property is defined by the following notation:
     tzurl      = "TZURL" tzurlparam ":" uri CRLF

     tzurlparam = *(";"  I xparamother-param)
Example:
The following is an example of this property:
  TZURL:http://timezones. I r.us.netexample.org/tz/ I US-CaliforniaAmerica-Los_Angeles I .ics

3.8.4. Relationship Component Properties

The following properties specify relationship information in calendar components.

3.8.4.1. Attendee

Property Name:
ATTENDEE
Purpose:
 I TheThis property defines an "Attendee" within a calendar component.
Value Type:
CAL-ADDRESS
Property Parameters:
 I Non-standardIANA, non-standard, language, calendar user type, group or list membership, participation role, participation status, RSVP expectation, delegatee, delegator, sent by, common name or directory entry reference property parameters can be specified on this property.
Conformance:
This property MUST be specified in an iCalendar object that specifies a group scheduled calendar entity. This property MUST NOT be specified in an iCalendar object when publishing the calendar information (e.g., NOT in an iCalendar object that specifies the publication of a calendar user's busy time, event, to-do or journal). This property is not specified in an iCalendar object that specifies only a time zone definition or that defines calendar  I entitiescomponents that are not group scheduled  I entities,components, but are  I entitiescomponents only on a single user's calendar.
Description:
 I TheThis property MUST only be specified within calendar components to specify participants, non-participants and the chair of a group scheduled calendar entity. The property is specified within an "EMAIL" category of the "VALARM" calendar component to specify an email address that is to receive the email type of iCalendar alarm.
The property parameter  I "CN I " is for the common or displayable name associated with the calendar address;  I "ROLE I ", for the intended role that the attendee will have in the calendar component;  I "PARTSTAT I ", for the status of the attendee's participation;  I "RSVP I ", for indicating whether the favor of a reply is requested;  I "CUTYPE I ", to indicate the type of calendar user;  I "MEMBER I ", to indicate the groups that the attendee belongs to;  I "DELEGATED-TO I ", to indicate the calendar users that the original request was delegated to; and  I "DELEGATED-FROM I ", to indicate whom the request was delegated from;  I "SENT-BY I ", to indicate whom is acting on behalf of the  I "ATTENDEE I "; and  I "DIR I ", to indicate the URI that points to the directory information corresponding to the attendee. These property parameters can be specified on an "ATTENDEE" property in either a "VEVENT", "VTODO" or "VJOURNAL" calendar component. They MUST  I notNOT be specified in an "ATTENDEE" property in a "VFREEBUSY" or "VALARM" calendar component. If the  I "LANGUAGE I " property parameter is specified, the identified language applies to the  I "CN I " parameter.
A recipient delegated a request MUST inherit the  I "RSVP I " and  I "ROLE I " values from the attendee that delegated the request to them.
Multiple attendees can be specified by including multiple "ATTENDEE" properties within the calendar component.
Format Definition:
 I TheThis property is defined by the following notation:
     attendee   = "ATTENDEE" attparam ":" cal-address CRLF

     attparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" cutypeparam) / (";" I  memberparam) /
                (";" roleparam) / (";" partstatparam) /
                (";" rsvpparam) / (";" deltoparam) /
                (";" delfromparam) / (";" sentbyparam) /
                (";" I  cnparam) / (";" dirparam) /
                (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following are examples of this property's use for a to-do:
 I      ORGANIZER:MAILTO:jsmith@host1.com
     ATTENDEE;MEMBER=" I MAILTOmailto:DEV-GROUP@ I host2.comexample.com":
       I MAILTOmailto:joecool@ I host2.comexample.com
     ATTENDEE;DELEGATED-FROM=" I MAILTOmailto:immud@ I host3.comexample.com":
       I MAILTOmailto:ildoit@ I host1.comexample.com
The following is an example of this property used for specifying multiple attendees to an event:
 I      ORGANIZER:MAILTO:jsmith@host1.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry
      Cabot: I MAILTOmailto:hcabot@ I host2.comexample.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM=" I MAILTOmailto:bob@
       I host.comexample.com";PARTSTAT=ACCEPTED;CN=Jane Doe: I MAILTOmailto:jdoe@
       I host1.comexample.com
The following is an example of this property with a URI to the directory information associated with the attendee:
     ATTENDEE;CN=John Smith;DIR="ldap:// I host.comexample.com:6666/o= I eDABC%
      20Industries,c= I 3DUS I ???(cn= I 3DBJim%20Dolittle)": I MAILTOmailto:jimdo@
       I host1.comexample.com
The following is an example of this property with "delegatee" and "delegator" information for an event:
 I      ORGANIZER;CN=John Smith:MAILTO:jsmith@host.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
      " I MAILTOmailto:iamboss@ I host2.comexample.com";CN=Henry Cabot: I MAILTOmailto:hcabot@
       I host2.comexample.com
     ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
      " I MAILTOmailto:hcabot@ I host2.comexample.com";CN=The Big Cheese: I MAILTOmailto:iamboss
      @ I host2.comexample.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
      : I MAILTOmailto:jdoe@ I host1.comexample.com
Example:
The following is an example of this property's use when another calendar user is acting on behalf of the "Attendee":
     ATTENDEE;SENT-BY= I MAILTOmailto:jan_doe@ I host1.comexample.com;CN=John Smith:
       I MAILTOmailto:jsmith@ I host1.comexample.com

3.8.4.2. Contact

Property Name:
CONTACT
Purpose:
 I TheThis property is used to represent contact information or alternately a reference to contact information associated with the calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, alternate text representation and language property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified in a "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar component.
Description:
The property value consists of textual contact information. An alternative representation for the property value can also be specified that refers to a URI pointing to an alternate form, such as a vCard [RFC2426], for the contact information.
Format Definition:
 I TheThis property is defined by the following notation:
     contact    = "CONTACT" contparam ":" text CRLF

     contparam  = *(
                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of this property referencing textual contact information:
     CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234
The following is an example of this property with an alternate representation of a LDAP URI to a directory entry containing the contact information:
     CONTACT;ALTREP="ldap:// I host.comexample.com:6666/o= I 3DABC%20Industries\,
      c= I 3DUS I ???(cn= I 3DBJim%20Dolittle)":Jim Dolittle\, ABC Industries\,
      +1-919-555-1234
The following is an example of this property with an alternate representation of a MIME body part containing the contact information, such as a vCard [RFC2426] embedded in a  I [MIME-DIR] content-type:text/directory media type [RFC2425]:
     CONTACT;ALTREP="CID I =<:part3.msg970930T083000SILVER@ I host.comexample.com I >":
      Jim Dolittle\, ABC Industries\, +1-919-555-1234
The following is an example of this property referencing a network resource, such as a vCard [RFC2426] object containing the contact information:
     CONTACT;ALTREP="http:// I host.comexample.com/pdi/jdoe.vcf":Jim
       Dolittle\, ABC Industries\, +1-919-555-1234

3.8.4.3. Organizer

Property Name:
ORGANIZER
Purpose:
 I TheThis property defines the organizer for a calendar component.
Value Type:
CAL-ADDRESS
Property Parameters:
 I Non-standardIANA, non-standard, language, common name, directory entry reference, sent by property parameters can be specified on this property.
Conformance:
This property MUST be specified in an iCalendar object that specifies a group scheduled calendar entity. This property MUST be specified in an iCalendar object that specifies the publication of a calendar user's busy time. This property MUST NOT be specified in an iCalendar object that specifies only a time zone definition or that defines calendar  I entitiescomponents that are not group scheduled  I entities,components, but are  I entitiescomponents only on a single user's calendar.
Description:
 I TheThis property is specified within the "VEVENT", "VTODO", "VJOURNAL I " calendar components to specify the organizer of a group scheduled calendar entity. The property is specified within the "VFREEBUSY" calendar component to specify the calendar user requesting the free or busy time. When publishing a "VFREEBUSY" calendar component, the property is used to specify the calendar that the published busy time came from.
The property has the property parameters  I "CN I ", for specifying the common or display name associated with the "Organizer",  I "DIR I ", for specifying a pointer to the directory information associated with the "Organizer",  I "SENT-BY I ", for specifying another calendar user that is acting on behalf of the "Organizer". The non-standard parameters may also be specified on this property. If the  I "LANGUAGE I " property parameter is specified, the identified language applies to the  I "CN I " parameter value.
Format Definition:
 I TheThis property is defined by the following notation:
     organizer  = "ORGANIZER" orgparam ":"
                  cal-address CRLF

     orgparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" cnparam) / (";" dirparam) / (";" sentbyparam) /
                (";" languageparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )
Example:
The following is an example of this property:
     ORGANIZER;CN=John Smith: I MAILTOmailto:jsmith@ I host1.comexample.com
The following is an example of this property with a pointer to the directory information associated with the organizer:
     ORGANIZER;CN=JohnSmith;DIR="ldap:// I host.comexample.com:6666/o= I 3DDC%20Ass
      ociates,c= I 3DUS I ???(cn= I 3DJohn%20Smith)": I MAILTOmailto:jsmith@ I host1.comexample.com
The following is an example of this property used by another calendar user who is acting on behalf of the organizer, with responses intended to be sent back to the organizer, not the other calendar user:
     ORGANIZER;SENT-BY=" I MAILTOmailto:jane_doe@ I host.comexample.com":
       I MAILTOmailto:jsmith@ I host1.comexample.com

3.8.4.4. Recurrence ID

 I  #issue62+4.8.4.4_recurrence_id_immutable   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 The text that says that the "RECURRENCE-ID" for a given recurrence instance might change should be removed.
Resolution: Text removed.
Associated changes in this document: 3.8.4.4., Published in: draft-ietf-calsify-rfc2445bis-06

Property Name:
RECURRENCE-ID
Purpose:
This property is used in conjunction with the "UID" and "SEQUENCE" property to identify a specific instance of a recurring "VEVENT", "VTODO" or "VJOURNAL" calendar component. The property value is the  I effectiveoriginal value of the "DTSTART" property of the recurrence instance.
Value Type:
The default value type for this property is DATE-TIME. The time format can be any of the valid forms defined for a DATE-TIME value type. See DATE-TIME value type definition for specific interpretations of the various forms. The value type can be set to DATE.
Property Parameters:
 I Non-standard propertyIANA, non-standard, value data type,  I and time zone identifier  I and recurrence identifier range parameters can be specified on this property.
Conformance:
This property can be specified in an iCalendar object containing a recurring calendar component.
Description:
The full range of calendar components specified by a recurrence set is referenced by referring to just the "UID" property value corresponding to the calendar component. The "RECURRENCE-ID" property allows the reference to an individual instance within the recurrence set.
If the value of the "DTSTART" property is a DATE type value, then the value MUST be the calendar date for the recurrence instance.
The date/time value is set to the time when the original recurrence instance would occur; meaning that if the intent is to change a Friday meeting to Thursday, the date/time is still set to the original Friday meeting.
The "RECURRENCE-ID" property is used in conjunction with the "UID" and "SEQUENCE" property to identify a particular instance of a recurring event, to-do or journal. For a given pair of "UID" and "SEQUENCE" property values, the "RECURRENCE-ID" value for a recurrence instance is fixed.  I When the definition of the recurrence set for a calendar component changes, and hence the "SEQUENCE" property value changes, the "RECURRENCE-ID" for a given recurrence instance might also change.  I The "RANGE" parameter is used to specify the effective range of recurrence instances from the instance specified by the "RECURRENCE-ID" property value. The default value for the range parameter is the single recurrence instance only. The value can also be "THISANDPRIOR" to indicate a range defined by the given recurrence instance and all prior instances or the value can be "THISANDFUTURE" to indicate a range defined by the given recurrence instance and all subsequent instances.
Format Definition:
 I TheThis property is defined by the following notation:
     recurid    = "RECURRENCE-ID" ridparam ":" ridval CRLF

     ridparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE I ")) /
                (";" tzidparam) /  I (";" rangeparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )

     ridval     = date-time / date
     ;Value MUST match value type
Example:
The following are examples of this property:
     RECURRENCE-ID;VALUE=DATE:19960401
     
     RECURRENCE-ID I ;RANGE=THISANDFUTURE:19960120T120000Z

3.8.4.5. Related To

Property Name:
RELATED-TO
Purpose:
 I TheThis property is used to represent a relationship or reference between one calendar component and another.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard, and relationship type property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified  I one or more times in the "VEVENT", "VTODO"  I orand "VJOURNAL" calendar components.
Description:
The property value consists of the persistent, globally unique identifier of another calendar component. This value would be represented in a calendar component by the "UID" property.
By default, the property value points to another calendar component that has a PARENT relationship to the referencing object. The "RELTYPE" property parameter is used to either explicitly state the default PARENT relationship type to the referenced calendar component or to override the default PARENT relationship type and specify either a CHILD or SIBLING relationship. The PARENT relationship indicates that the calendar component is a subordinate of the referenced calendar component. The CHILD relationship indicates that the calendar component is a superior of the referenced calendar component. The SIBLING relationship indicates that the calendar component is a peer of the referenced calendar component.
Changes to a calendar component referenced by this property can have an implicit impact on the related calendar component. For example, if a group event changes its start or end date or time, then the related, dependent events will need to have their start and end dates changed in a corresponding way. Similarly, if a PARENT calendar component is  I canceledcancelled or deleted, then there is an implied impact to the related CHILD calendar components. This property is intended only to provide information on the relationship of calendar components. It is up to the target calendar system to maintain any property implications of this relationship.
Format Definition:
 I TheThis property is defined by the following notation:
     related    = "RELATED-TO"  I [relparam I ] ":" text CRLF

     relparam   = *(

                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" reltypeparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparmother-param)

                )
The following is an example of this property:
     RELATED-TO: I <jsmith.part7.19960817T083000.xyzMail@ I host3.comexample.com I >

     RELATED-TO: I <19960401-080045-4000F192713-0052@ I host1.comexample.com I >

3.8.4.6. Uniform Resource Locator

Property Name:
URL
Purpose:
This property defines a Uniform Resource Locator (URL) associated with the iCalendar object.
Value Type:
URI
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified once in the "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description:
This property may be used in a calendar component to convey a location where a more dynamic rendition of the calendar information associated with the calendar component can be found. This memo does not attempt to standardize the form of the URI, nor the format of the resource pointed to by the property value. If the URL property and Content-Location MIME header are both specified, they MUST point to the same resource.
Format Definition:
 I TheThis property is defined by the following notation:
     url        = "URL" urlparam ":" uri CRLF

     urlparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property:
     URL:http:// I abcexample.com/pub/calendars/jsmith/mytime.ics
 I  #issue33+characters_vs_octets   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-08-21 "255 characters" should be changed to "255 octets".
2006-08-21Resolution: Done.
Associated changes in this document: 3.8.4.7, 3.8.4.7, 5., Published in: draft-ietf-calsify-rfc2445bis-02

3.8.4.7. Unique Identifier

Property Name:
UID
Purpose:
This property defines the persistent, globally unique identifier for the calendar component.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property MUST be specified in the "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description:
The  I "UID I " itself MUST be a globally unique identifier. The generator of the identifier MUST guarantee that the identifier is unique. There are several algorithms that can be used to accomplish this. The identifier is RECOMMENDED to be the identical syntax to the  I [RFC0822][RFC2822] addr-spec. A good method to assure uniqueness is to put the domain name or a domain literal IP address of the host on which the identifier was created on the right hand side of the "@", and on the left hand side, put a combination of the current calendar date and time of day (i.e., formatted in as a DATE-TIME value) along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number). Using a date/time value on the left hand side and a domain name or domain literal on the right hand side makes it possible to guarantee uniqueness since no two hosts should be using the same domain name or IP address at the same time. Though other algorithms will work, it is RECOMMENDED that the right hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left hand side within the scope of that domain.
This is the method for correlating scheduling messages with the referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component.
The full range of calendar components specified by a recurrence set is referenced by referring to just the "UID" property value corresponding to the calendar component. The "RECURRENCE-ID" property allows the reference to an individual instance within the recurrence set.
This property is an important method for group scheduling applications to match requests with later replies, modifications or deletion requests. Calendaring and scheduling applications MUST generate this property in "VEVENT", "VTODO" and "VJOURNAL" calendar components to assure interoperability with other group scheduling applications. This identifier is created by the calendar system that generates an iCalendar object.
Implementations MUST be able to receive and persist values of at least 255  I charactersoctets for this property  I but MUST NOT truncate values in the middle of a UTF-8 multi-octet sequence.
Format Definition:
 I TheThis property is defined by the following notation:
     uid        = "UID" uidparam ":" text CRLF

     uidparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property:
     UID:19960401T080045Z-4000F192713-0052@ I host1.comexample.com

3.8.5. Recurrence Component Properties

The following properties specify recurrence information in calendar components.

3.8.5.1. Exception Date/Times

Property Name:
EXDATE
Purpose:
This property defines the list of date/time exceptions for  I a recurring calendar component.recurring events, to-dos, journal entries or time zone definitions.
Value Type:
The default value type for this property is DATE-TIME. The value type can be set to DATE.
Property Parameters:
 I Non-standardIANA, non-standard, value data type and time zone identifier property parameters can be specified on this property.
Conformance:
This property can be specified in  I an iCalendar object that includes a recurring calendar component.recurring "VEVENT", "VTODO", and "VJOURNAL" calendar components as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component.
Description:
The exception dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE",  I and "EXDATE"  I and "EXRULE" properties contained within the  I iCalendar object.recurring component. The "DTSTART" property defines the first instance in the recurrence set.  I The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined.  I Multiple instances of the "RRULE" and "EXRULE" properties can also be specified to define more sophisticated recurrence sets. The final recurrence set is generated by gathering all of the start date-times generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start date and times  I which fall within the union of start date and times generated by any specified "EXRULE" and "EXDATE" properties.specified by "EXDATE" properties. This implies that start date and times  I within exclusion related properties (i.e., "EXDATE" and "EXRULE")specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE").  I WhereWhen duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
The "EXDATE" property can be used to exclude the value specified in "DTSTART". However, in such cases the original "DTSTART" date MUST still be maintained by the calendaring and scheduling system because the original "DTSTART" value has inherent usage dependencies by other properties such as the "RECURRENCE-ID".
Format Definition:
 I TheThis property is defined by the following notation:
     exdate     = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF

     exdtparam  = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /

                (";" tzidparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )

     exdtval    = date-time / date
     ;Value MUST match value type
Example:
The following is an example of this property:
     EXDATE:19960402T010000Z,19960403T010000Z,19960404T010000Z
 I  

del-17. Exception Rule

Property Name:
EXRULE
Purpose:
This property defines a rule or repeating pattern for an exception to a recurrence set.
Value Type:
RECUR
Property Parameters:
Non-standard property parameters can be specified on this property.
Conformance:
This property can be specified in "VEVENT", "VTODO" or "VJOURNAL" calendar components.
Description:
The exception rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained within the iCalendar object. The "DTSTART" defines the first instance in the recurrence set. Multiple instances of the "RRULE" and "EXRULE" properties can also be specified to define more sophisticated recurrence sets. The final recurrence set is generated by gathering all of the start date-times generated by any of the specified "RRULE" and "RDATE" properties, and excluding any start date and times which fall within the union of start date and times generated by any specified "EXRULE" and "EXDATE" properties. This implies that start date and times within exclusion related properties (i.e., "EXDATE" and "EXRULE") take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence  I instance is considered. Duplicate  I recurrence instances are ignored.
The "EXRULE" property can be used to exclude the value specified in "DTSTART". However, in such cases the original "DTSTART" date MUST still be maintained by the calendaring and scheduling system because the original "DTSTART" value has inherent usage dependencies by other properties such as the "RECURRENCE-ID".
Format Definition:
The property is defined by the following notation:
     exrule     = "EXRULE" exrparam ":" recur CRLF

     exrparam   = *(";" xparam)
Example:
The following are examples of this property. Except every other week, on Tuesday and Thursday for 4 occurrences:
     EXRULE:FREQ=WEEKLY;COUNT=4;INTERVAL=2;BYDAY=TU,TH
Except daily for 10 occurrences:
     EXRULE:FREQ=DAILY;COUNT=10
Except yearly in June and July for 8 occurrences:
     EXRULE:FREQ=YEARLY;COUNT=8;BYMONTH=6,7

3.8.5.2. Recurrence Date/Times

 I  #issue63+4.8.5.3_rdate_and_dtstart   (type: change, status: open)
bernard.desruisseaux@oracle.com2006-11-05 We need to clarify whether RDATE can specify a value earlier in time than DTSTART.
Resolution:

Property Name:
RDATE
Purpose:
This property defines the list of date/times for  I a recurrence set.recurring events, to-dos, journal entries or time zone definitions.
Value Type:
The default value type for this property is DATE-TIME. The value type can be set to DATE or PERIOD.
Property Parameters:
 I Non-standardIANA, non-standard, value data type and time zone identifier property parameters can be specified on this property.
Conformance:
 I TheThis property can be specified in  I recurring "VEVENT", "VTODO",  I and "VJOURNAL"  I calendar components  I or "VTIMEZONE" calendar components.as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component.
Description:
This property can appear along with the "RRULE" property to define an aggregate set of repeating occurrences. When they both appear in  I an iCalendar object,a recurring component, the  I recurring eventsrecurrence instances are defined by the union of occurrences defined by both the "RDATE" and "RRULE".
The recurrence dates, if specified, are used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE",  I and "EXDATE"  I and "EXRULE" properties contained within the  I iCalendar object.recurring component. The "DTSTART" property defines the first instance in the recurrence set.  I The "DTSTART" property value SHOULD match the pattern of the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined.  I Multiple instances of the "RRULE" and "EXRULE" properties can also be specified to define more sophisticated recurrence sets. The final recurrence set is generated by gathering all of the start date-times generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start date and times  I which fall within the union of start date and times generated by any specified "EXRULE" and "EXDATE" properties.specified by "EXDATE" properties. This implies that start date/times  I within exclusion related properties (i.e., "EXDATE" and "EXRULE")specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
Format Definition:
 I TheThis property is defined by the following notation:
     rdate      = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF

     rdtparam   = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE" / "PERIOD")) /
                (";" tzidparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )

     rdtval     = date-time / date / period
     ;Value MUST match value type
Example:
The following are examples of this property:
     RDATE:19970714T123000Z
     RDATE;TZID= I US-EASTERNAmerica/New_York:19970714T083000

     RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
      19960404T010000Z/PT3H

     RDATE;VALUE=DATE:19970101,19970120,19970217,19970421
      19970526,19970704,19970901,19971014,19971128,19971129,19971225

3.8.5.3. Recurrence Rule

 I  #issue27+4.8.5.4_recur_instances_duration   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 We need to clarify how the duration of generated recurrence instances is determined.
Resolution: If the master component specifies the DTEND property, the duration of the generated recurrence instances will be the "computed duration" of the first instance defined in the master component (i.e., DTEND-DTSTART). Else, if the master component specifies the DURATION property, the duration of the generated recurrence instances will be the "nominal duration" of the first instance defined in the master component. The exact duration of a nominal duration depends on its position in the calendar.
Associated changes in this document: 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-06
 I  #issue28+4.8.5.4_rdate_required   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-07-12 Need to clarify whether RDATE is REQUIRED even when the recurrence instance is redefined in an exception component.
Resolution: Relax requirement.
Associated changes in this document: 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-04
 I  #issue43+4.8.5.4_allowed_datetime_form_in_recur_comp   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-09-19 Clarify the DATE-TIME forms allowed for DTSTART and DTEND/DUE in recurring components. (See also issue 72)
Resolution: Relax requirement to allow all forms of DATE-TIME (i.e., also DATE WITH UTC TIME)
Associated changes in this document: 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-04

Property Name:
RRULE
Purpose:
This property defines a rule or repeating pattern for recurring events, to-dos,  I journal entries or time zone definitions.
Value Type:
RECUR
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified  I one or more times in recurring "VEVENT", "VTODO" and "VJOURNAL" calendar components I . It can also be specified once in each STANDARD or DAYLIGHT sub-component of the "VTIMEZONE" calendar component.as well as in the "STANDARD" and "DAYLIGHT" sub-components of the "VTIMEZONE" calendar component, but it SHOULD NOT be specified more than once. The recurrence set generated with multiple  I "RRULE I " properties is undefined.
Description:
The recurrence rule, if specified, is used in computing the recurrence set. The recurrence set is the complete set of recurrence instances for a calendar component. The recurrence set is generated by considering the initial "DTSTART" property along with the "RRULE", "RDATE",  I and "EXDATE"  I and "EXRULE" properties contained within the  I iCalendar object.recurring component. The "DTSTART" property defines the first instance in the recurrence set.  I The "DTSTART" property value SHOULD be synchronized with the recurrence rule, if specified. The recurrence set generated with a "DTSTART" property value not synchronized with the recurrence rule is undefined.  I Multiple instances of the "RRULE" and "EXRULE" properties can also be specified to define more sophisticated recurrence sets. The final recurrence set is generated by gathering all of the start date/times generated by any of the specified "RRULE" and "RDATE" properties, and then excluding any start date/times  I which fall within the union of start date/times generated by any specified "EXRULE" and "EXDATE" properties.specified by "EXDATE" properties. This implies that start date/times  I within exclusion related properties (i.e., "EXDATE" and "EXRULE")specified by "EXDATE" properties take precedence over those specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are generated by the "RRULE" and "RDATE" properties, only one recurrence is considered. Duplicate instances are ignored.
The "DTSTART"  I and "DTEND" property pair or "DTSTART" and "DURATION" property pair,property specified within the iCalendar object defines the first instance of the recurrence.  I When used with a recurrence rule, the "DTSTART" and "DTEND" properties MUST be specified in local time and the appropriate set of "VTIMEZONE" calendar components MUST be included. For detail on the usage of the "VTIMEZONE" calendar component, see the "VTIMEZONE" calendar component definition.In most cases, a "DTSTART" property of DATE-TIME value type used with a recurrence rule, should be specified as a date with local time and time zone reference to make sure all the recurrence instances start at the same local time regardless of time zone changes.
 I Any duration associated with the iCalendar object applies to all members of the generated recurrence set.If the duration of the recurring component is specified with the "DTEND" or "DUE" property, then the same exact duration will apply to all the members of the generated recurrence set. Else, if the duration of the recurring component is specified with the "DURATION" property, then the same nominal duration will apply to all the members of the generated recurrence set and the exact duration of each recurrence instance will depend on its specific start time. For example, recurrence instances of a nominal duration of one day will have an exact duration of more or less than 24 hours on a day where a time zone shift occurs.  I Any modified duration for specific recurrences MUST be explicitly specified using the "RDATE" property.The duration of a specific recurrence may be modified in an exception component or simply by using an "RDATE" property of PERIOD value type.
Format Definition:
This property is defined by the following notation:
     rrule      = "RRULE" rrulparam ":" recur CRLF

     rrulparam  = *(";"  I xparamother-param)
Example:
All examples assume the Eastern United States time zone.
Daily for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=DAILY;COUNT=10

     ==> (1997 9:00 AM EDT) September 2-11
Daily until December 24, 1997:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=DAILY;UNTIL=19971224T000000Z

     ==> (1997 9:00 AM EDT) September 2-30;October 1-25
         (1997 9:00 AM EST) October 26-31;November 1-30;December 1-23
Every other day - forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=DAILY;INTERVAL=2

     ==> (1997 9:00 AM EDT) September I  2,4,6,8...24,26,28,30;
                            October 2,4,6...20,22,24
         (1997 9:00 AM EST) October 26,28,30;
                            November 1,3,5,7...25,27,29;
                            Dec I ember 1,3,...
Every 10 days, 5 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5

     ==> (1997 9:00 AM EDT) September 2,12,22;
                            October 2,12
 I  #issue04+4.8.5.4_rrule_example1   (type: edit, status: closed)
sroberts@uniserve.com2006-05-29 (2000 9:00 AM EDT) January 31 is AFTER the until day (2000 9:00 am UTC) January 31.
2006-09-28Resolution: Changed UNTIL value to 20000131T140000Z.
Associated changes in this document: 3.8.5.3, 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue04+4.8.5.4_rrule_example2   (type: edit, status: closed)
aki.niemi@nokia.com2006-09-12 Example should specify "EST" instead of "EDT".
2006-09-28Resolution: Changed "EDT" to "EST".
Associated changes in this document: 3.8.5.3, 3.8.5.3, 3.8.5.3., Published in: draft-ietf-calsify-rfc2445bis-02
Everyday in January, for 3 years:
     DTSTART;TZID= I US-EasternAmerica/New_York:19980101T090000
     
     RRULE:FREQ=YEARLY;UNTIL=20000131T I 09140000Z;
      BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA
     or
     RRULE:FREQ=DAILY;UNTIL=20000131T I 09140000Z;BYMONTH=1
     
     ==> (1998 9:00 AM  I EDTEST)January 1-31
         (1999 9:00 AM  I EDTEST)January 1-31
         (2000 9:00 AM  I EDTEST)January 1-31
Weekly for 10 occurrences
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=WEEKLY;COUNT=10

     ==> (1997 9:00 AM EDT) September 2,9,16,23,30;October 7,14,21
         (1997 9:00 AM EST) October 28;November 4
Weekly until December 24, 1997
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z

     ==> (1997 9:00 AM EDT) September 2,9,16,23,30;
                            October 7,14,21
         (1997 9:00 AM EST) October 28;
                            November 4,11,18,25;
                            December 2,9,16,23
Every other week - forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;WKST=SU

     ==> (1997 9:00 AM EDT) September 2,16,30;
                            October 14
         (1997 9:00 AM EST) October 28;
                            November 11,25;
                            December 9,23
         (1998 9:00 AM EST) January 6,20;
                            February  I 3, 17
         ...
Weekly on Tuesday and Thursday for 5 weeks:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=WEEKLY;UNTIL=19971007T000000Z;WKST=SU;BYDAY=TU,TH

     or

     RRULE:FREQ=WEEKLY;COUNT=10;WKST=SU;BYDAY=TU,TH

     ==> (1997 9:00 AM EDT) September 2,4,9,11,16,18,23,25,30;
                            October 2
Every other week on Monday, Wednesday and Friday until December 24, 1997,  I but starting on  I TuesdayMonday, September  I 21, 1997:
     DTSTART;TZID= I US-EasternAmerica/New_York:1997090 I 21T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;UNTIL=19971224T000000Z;WKST=SU;
      BYDAY=MO,WE,FR

     ==> (1997 9:00 AM EDT) September  I 21,3,5,15,17,19,29;
                            October 1,3,13,15,17
         (1997 9:00 AM EST) October 27,29,31;
                            November 10,12,14,24,26,28;
                            December 8,10,12,22
Every other week on Tuesday and Thursday, for 8 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=8;WKST=SU;BYDAY=TU,TH

     ==> (1997 9:00 AM EDT) September 2,4,16,18,30;
                            October 2,14,16
Monthly on the 1st Friday for ten occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970905T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR

     ==> (1997 9:00 AM EDT) September 5;October 3
         (1997 9:00 AM EST) November 7;Dec I ember 5
         (1998 9:00 AM EST) January 2;February 6;March 6;April 3
         (1998 9:00 AM EDT) May 1;June 5
Monthly on the 1st Friday until December 24, 1997:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970905T090000
     RRULE:FREQ=MONTHLY;UNTIL=19971224T000000Z;BYDAY=1FR

     ==> (1997 9:00 AM EDT) September 5; October 3
         (1997 9:00 AM EST) November 7; December 5
Every other month on the 1st and last Sunday of the month for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970907T090000
     RRULE:FREQ=MONTHLY;INTERVAL=2;COUNT=10;BYDAY=1SU,-1SU

     ==> (1997 9:00 AM EDT) September 7,28
         (1997 9:00 AM EST) November 2,30
         (1998 9:00 AM EST) January 4,25;March 1,29
         (1998 9:00 AM EDT) May 3,31
Monthly on the second to last Monday of the month for 6 months:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970922T090000
     RRULE:FREQ=MONTHLY;COUNT=6;BYDAY=-2MO

     ==> (1997 9:00 AM EDT) September 22;October 20
         (1997 9:00 AM EST) November 17;December 22
         (1998 9:00 AM EST) January 19;February 16
Monthly on the third to the last day of the month, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970928T090000
     RRULE:FREQ=MONTHLY;BYMONTHDAY=-3

     ==> (1997 9:00 AM EDT) September 28
         (1997 9:00 AM EST) October 29;November 28;December 29
         (1998 9:00 AM EST) January 29;February 26
         ...
Monthly on the 2nd and 15th of the month for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=2,15

     ==> (1997 9:00 AM EDT) September 2,15;October 2,15
         (1997 9:00 AM EST) November 2,15;December 2,15
         (1998 9:00 AM EST) January 2,15
Monthly on the first and last day of the month for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970930T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=1,-1

     ==> (1997 9:00 AM EDT) September 30;October 1
         (1997 9:00 AM EST) October 31;November 1,30;December 1,31
         (1998 9:00 AM EST) January 1,31;February 1
Every 18 months on the 10th thru 15th of the month for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970910T090000
     RRULE:FREQ=MONTHLY;INTERVAL=18;COUNT=10;BYMONTHDAY=10,11,12,
      13,14,15

     ==> (1997 9:00 AM EDT) September 10,11,12,13,14,15
         (1999 9:00 AM EST) March 10,11,12,13
Every Tuesday, every other month:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=MONTHLY;INTERVAL=2;BYDAY=TU

     ==> (1997 9:00 AM EDT) September 2,9,16,23,30
         (1997 9:00 AM EST) November 4,11,18,25
         (1998 9:00 AM EST) January 6,13,20,27;March 3,10,17,24,31
         ...
Yearly in June and July for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970610T090000
     RRULE:FREQ=YEARLY;COUNT=10;BYMONTH=6,7
     
     ==> (1997 9:00 AM EDT) June 10;July 10
         (1998 9:00 AM EDT) June 10;July 10
         (1999 9:00 AM EDT) June 10;July 10
         (2000 9:00 AM EDT) June 10;July 10
         (2001 9:00 AM EDT) June 10;July 10
Note: Since none of the BYDAY, BYMONTHDAY or BYYEARDAY components are specified, the day is gotten from  I "DTSTART I "
Every other year on January, February, and March for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970310T090000
     RRULE:FREQ=YEARLY;INTERVAL=2;COUNT=10;BYMONTH=1,2,3

     ==> (1997 9:00 AM EST) March 10
         (1999 9:00 AM EST) January 10;February 10;March 10
         (2001 9:00 AM EST) January 10;February 10;March 10
         (2003 9:00 AM EST) January 10;February 10;March 10
Every 3rd year on the 1st, 100th and 200th day for 10 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970101T090000
     RRULE:FREQ=YEARLY;INTERVAL=3;COUNT=10;BYYEARDAY=1,100,200

     ==> (1997 9:00 AM EST) January 1
         (1997 9:00 AM EDT) April 10;July 19
         (2000 9:00 AM EST) January 1
         (2000 9:00 AM EDT) April 9;July 18
         (2003 9:00 AM EST) January 1
         (2003 9:00 AM EDT) April 10;July 19
         (2006 9:00 AM EST) January 1
Every 20th Monday of the year, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970519T090000
     RRULE:FREQ=YEARLY;BYDAY=20MO

     ==> (1997 9:00 AM EDT) May 19
         (1998 9:00 AM EDT) May 18
         (1999 9:00 AM EDT) May 17
         ...
Monday of week number 20 (where the default start of the week is Monday), forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970512T090000
     RRULE:FREQ=YEARLY;BYWEEKNO=20;BYDAY=MO

     ==> (1997 9:00 AM EDT) May 12
         (1998 9:00 AM EDT) May 11
         (1999 9:00 AM EDT) May 17
         ...
Every Thursday in March, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970313T090000
     RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=TH

     ==> (1997 9:00 AM EST) March 13,20,27
         (1998 9:00 AM EST) March 5,12,19,26
         (1999 9:00 AM EST) March 4,11,18,25
         ...
Every Thursday, but only during June, July, and August, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970605T090000
     RRULE:FREQ=YEARLY;BYDAY=TH;BYMONTH=6,7,8

     ==> (1997 9:00 AM EDT) June 5,12,19,26;July 3,10,17,24,31;
                            August 7,14,21,28
         (1998 9:00 AM EDT) June 4,11,18,25;July 2,9,16,23,30;
                            August 6,13,20,27
         (1999 9:00 AM EDT) June 3,10,17,24;July 1,8,15,22,29;
                            August 5,12,19,26
         ...
Every Friday the 13th, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     EXDATE;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13

     ==> (1998 9:00 AM EST) February 13;March 13;November 13
         (1999 9:00 AM EDT) August 13
         (2000 9:00 AM EDT) October 13
         ...
The first Saturday that follows the first Sunday of the month, forever:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970913T090000
     RRULE:FREQ=MONTHLY;BYDAY=SA;BYMONTHDAY=7,8,9,10,11,12,13

     ==> (1997 9:00 AM EDT) September 13;October 11
         (1997 9:00 AM EST) November 8;December 13
         (1998 9:00 AM EST) January 10;February 7;March 7
         (1998 9:00 AM EDT) April 11;May 9;June 13...
         ...
Every four years, the first Tuesday after a Monday in November, forever (U.S. Presidential Election day):
     DTSTART;TZID= I US-EasternAmerica/New_York:19961105T090000
     RRULE:FREQ=YEARLY;INTERVAL=4;BYMONTH=11;BYDAY=TU;
      BYMONTHDAY=2,3,4,5,6,7,8

      ==> (1996 9:00 AM EST) November 5
          (2000 9:00 AM EST) November 7
          (2004 9:00 AM EST) November 2
          ...
The 3rd instance into the month of one of Tuesday, Wednesday or Thursday, for the next 3 months:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970904T090000
     RRULE:FREQ=MONTHLY;COUNT=3;BYDAY=TU,WE,TH;BYSETPOS=3

     ==> (1997 9:00 AM EDT) September 4;October 7
         (1997 9:00 AM EST) November 6
The 2nd to last weekday of the month:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970929T090000
     RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-2

     ==> (1997 9:00 AM EDT) September 29
         (1997 9:00 AM EST) October 30;November 27;December 30
         (1998 9:00 AM EST) January 29;February 26;March 30
         ...
Every 3 hours from 9:00 AM to 5:00 PM on a specific day:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=HOURLY;INTERVAL=3;UNTIL=19970902T170000Z

     ==> (September 2, 1997 EDT) 09:00,12:00,15:00
Every 15 minutes for 6 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=MINUTELY;INTERVAL=15;COUNT=6

     ==> (September 2, 1997 EDT) 09:00,09:15,09:30,09:45,10:00,10:15
Every hour and a half for 4 occurrences:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=MINUTELY;INTERVAL=90;COUNT=4

     ==> (September 2, 1997 EDT) 09:00,10:30;12:00;13:30
Every 20 minutes from 9:00 AM to 4:40 PM every day:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970902T090000
     RRULE:FREQ=DAILY;BYHOUR=9,10,11,12,13,14,15,16;BYMINUTE=0,20,40
     or
     RRULE:FREQ=MINUTELY;INTERVAL=20;BYHOUR=9,10,11,12,13,14,15,16

     ==> (September 2, 1997 EDT) 9:00,9:20,9:40,10:00,10:20,
                                 ... 16:00,16:20,16:40
         (September 3, 1997 EDT) 9:00,9:20,9:40,10:00,10:20,
                                 ...16:00,16:20,16:40
         ...
An example where the days generated makes a difference because of WKST:
     DTSTART;TZID= I US-EasternAmerica/New_York:19970805T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=MO

     ==> (1997 EDT) Aug I ust 5,10,19,24
changing only WKST from MO to SU, yields different results...
     DTSTART;TZID= I US-EasternAmerica/New_York:19970805T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=SU

     ==> (1997 EDT) August 5,17,19,31
 I An example where an invalid date (i.e., February 30) is ignored.
     DTSTART;TZID=America/New_York:20070115T090000
     RRULE:FREQ=MONTHLY;BYMONTHDAY=15,30;COUNT=5

     ==> (2007 EST) January 15,30
         (2007 EST) February 15
         (2007 EDT) March 15,30

3.8.6. Alarm Component Properties

The following properties specify alarm information in calendar components.

3.8.6.1. Action

Property Name:
ACTION
Purpose:
This property defines the action to be invoked when an alarm is triggered.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be specified once in a "VALARM" calendar component.
Description:
Each "VALARM" calendar component has a particular type of action associated with it. This property specifies the type of action I .  I Applications MUST ignore alarms with x-name and iana-token value they don't recognized.
Format Definition:
 I TheThis property is defined by the following notation:
     action      = "ACTION" actionparam ":" actionvalue CRLF

     actionparam = *(";"  I xparamother-param)


     actionvalue = "AUDIO" / "DISPLAY" / "EMAIL" I  / "PROCEDURE"
                 / iana-token / x-name
Example:
The following are examples of this property in a "VALARM" calendar component:
     ACTION:AUDIO

     ACTION:DISPLAY I 

     ACTION:PROCEDURE

3.8.6.2. Repeat Count

 I  4.8.6.2_repeat_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "REPEAT" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.6.2.

Property Name:
REPEAT
Purpose:
This property defines the number of time the alarm should be repeated, after the initial trigger.
Value Type:
INTEGER
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified in a "VALARM" calendar component.
Description:
 I This property defines the number of time an alarm should be repeated after its initial trigger. If the alarm triggers more than once, then this property MUST be specified along with the "DURATION" property.
Format Definition:
 I TheThis property is defined by the following notation:
     repeat I cnt  = "REPEAT" repparam ":" integer CRLF
     ;Default is "0", zero.

     repparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property for an alarm that repeats 4 additional times with a 5 minute delay after the initial triggering of the alarm:
     REPEAT:4
     DURATION:PT5M

3.8.6.3. Trigger

 I  #issue02+4.8.6.3_dtstart_typo   (type: edit, status: closed)
andrew_dowden@softdesign.net.nz2006-05-25 Typo in DTSTART.
2006-09-25Resolution: Fixed.
Associated changes in this document: 3.8.6.3, 3.8.6.3., Published in: draft-ietf-calsify-rfc2445bis-02
 I  #issue47+4.8.6.3_trigger_relative_to_date_value   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-09-25 Need to clarify if alarms specified in calendar components defined in terms of a DATE value type needs to be triggered relative to 00:00:00 UTC on the specified date, or whether they can be triggered relative to midnight of some other time zone.
Resolution: Changed the text to specify that applications should trigger the alarm relative to 00:00:00 of the user's configured time zone, or relative to 00:00:00 UTC if no configured time zone can be found for the user.
Associated changes in this document: 3.8.6.3, 3.8.6.3, 3.8.6.3., Published in: draft-ietf-calsify-rfc2445bis-06

Property Name:
TRIGGER
Purpose:
This property specifies when an alarm will trigger.
Value Type:
The default value type is DURATION. The value type can be set to a DATE-TIME value type, in which case the value MUST specify a UTC formatted DATE-TIME value.
Property Parameters:
 I Non-standardIANA, non-standard, value data type, time zone identifier or trigger relationship property parameters can be specified on this property. The trigger relationship property parameter MUST only be specified when the value type is  I "DURATION I ".
Conformance:
This property MUST be specified in the "VALARM" calendar component.
Description:
 I Within the "VALARM" calendar component, thisThis property defines when  I thean alarm will trigger. The default value type is DURATION, specifying a relative time for the trigger of the alarm. The default duration is relative to the start of an event or to-do that the alarm is associated with. The duration can be explicitly set to trigger from either the end or the start of the associated event or to-do with the "RELATED" parameter. A value of START will set the alarm to trigger off the start of the associated event or to-do. A value of END will set the alarm to trigger off the end of the associated event or to-do.
Either a positive or negative duration may be specified for the "TRIGGER" property. An alarm with a positive duration is triggered after the associated start or end of the event or to-do. An alarm with a negative duration is triggered before the associated start or end of the event or to-do.
The "RELATED" property parameter is not valid if the value type of the property is set to DATE-TIME (i.e., for an absolute date and time alarm trigger). If a value type of DATE-TIME is specified, then the property value MUST be specified in the UTC time format. If an absolute trigger is specified on an alarm for a recurring event or to-do, then the alarm will only trigger for the specified absolute date/time, along with any specified repeating instances.
If the trigger is set relative to START, then the "DTSTART" property MUST be present in the associated "VEVENT" or "VTODO" calendar component. If an alarm is specified for an event with the trigger set relative to the END, then the "DTEND" property or the  I "DSTART""DTSTART" and "DURATION I '" properties MUST be present in the associated "VEVENT" calendar component. If the alarm is specified for a to-do with a trigger set relative to the END, then either the "DUE" property or the  I "DSTART""DTSTART" and "DURATION I '" properties MUST be present in the associated "VTODO" calendar component.
Alarms specified in an event or to-do which is defined in terms of a DATE value type will be triggered  I relative to 00:00:00 of the user's configured time zone on the specified date, or relative to 00:00:00 UTC on the specified date  I if no configured time zone can be found for the user. For example, if  I "DTSTART:19980205,"DTSTART" is a DATE value set to 19980205 then the duration trigger will be relative to I 19980205T000000  I ZAmerica/New_York for a user configured with the America/New_York time zone.
Format Definition:
 I TheThis property is defined by the following notation:
     trigger    = "TRIGGER" (trigrel / trigabs) I  CRLF

     trigrel    = *(

                ; the following are  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                  (";" "VALUE" "=" "DURATION") /
                  (";" trigrelparam) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                  (";"  I xparamother-param)
                ) ":"  dur-value

     trigabs    =  I 1*(

                ; the following is REQUIRED,
                ; but MUST NOT occur more than once

                  (";" "VALUE" "=" "DATE-TIME") /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                  ) ":" date-time
Example:
A trigger set 15 minutes prior to the start of the event or to-do.
     TRIGGER:-P I T15M
A trigger set 5 minutes after the end of  I thean event or  I the due date of a to-do.
     TRIGGER;RELATED=END:P I T5M
A trigger set to an absolute date/time.
     TRIGGER;VALUE=DATE-TIME:19980101T050000Z

3.8.7. Change Management Component Properties

The following properties specify change management information in calendar components.

3.8.7.1. Date/Time Created

 I  4.8.7.1_created_description_incomplete   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 The description of the "CREATED" property is incomplete.
Resolution: Provided a complete description.
Associated changes in this document: 3.8.7.1, 3.8.7.1.

Property Name:
CREATED
Purpose:
This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store.
Note: This is analogous to the creation date and time for a file in the file system.
Value Type:
DATE-TIME
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property can be specified once in "VEVENT", "VTODO" or "VJOURNAL" calendar components.  I The value MUST be specified as a date with UTC time.
Description:
 I The date and time is a UTC value.This property specifies the date and time that the calendar information was created by the calendar user agent in the calendar store.
Format Definition:
 I TheThis property is defined by the following notation:
     created    = "CREATED" creaparam ":" date-time CRLF

     creaparam  = *(";"  I xparamother-param)
Example:
The following is an example of this property:
     CREATED:19960329T133000Z

3.8.7.2. Date/Time Stamp

 I  4.8.7.2_dtstamp   (type: change, status: closed)
bernard.desruisseaux@oracle.com2007-02-14 We need to clarify the purpose of the "DTSTAMP" property.
Resolution:
Associated changes in this document: 3.8.7.2, 3.8.7.2, 3.8.7.2.

Property Name:
DTSTAMP
Purpose:
 I The property indicates the date/time that the instance of the iCalendar object was created.In the case of an iCalendar object that specifies a "METHOD" property, this property specifies the date and time that the instance of the iCalendar object was created. In the case of an iCalendar object that doesn't specify a "METHOD" property, this property specifies the date and time that the information associated with the calendar component was last revised in the calendar store.
Value Type:
DATE-TIME
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property MUST be included in the "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
Description:
The value MUST be specified in the UTC time format.
This property is also useful to protocols such as  I [RFC2447][I-D.ietf-calsify-rfc2447bis] that have inherent latency issues with the delivery of content. This property will assist in the proper sequencing of messages containing iCalendar objects.
 I ThisIn the case of an iCalendar object that specifies a "METHOD" property, this property is different than the "CREATED" and "LAST-MODIFIED" properties. These two properties are used to specify when the particular calendar data in the calendar store was created and last modified. This is different than when the iCalendar object representation of the calendar service information was created or last modified.
 I In the case of an iCalendar object that doesn't specify a "METHOD" property, this property is equivalent to the "LAST-MODIFIED" property.
Format Definition:
 I TheThis property is defined by the following notation:
     dtstamp    = "DTSTAMP" stmparam ":" date-time CRLF

     stmparam   = *(";"  I xparamother-param)
Example:
     DTSTAMP:19971210T080000Z

3.8.7.3. Last Modified

Property Name:
LAST-MODIFIED
Purpose:
 I TheThis property specifies the date and time that the information associated with the calendar component was last revised in the calendar store.
Note: This is analogous to the modification date and time for a file in the file system.
Value Type:
DATE-TIME
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
This property can be specified in the " I VEVENT", "VTODO", "VJOURNAL" or "VTIMEZONE" calendar components.
Description:
The property value MUST be specified in the UTC time format.
Format Definition:
 I TheThis property is defined by the following notation:
     last-mod   = "LAST-MODIFIED" lstparam ":" date-time CRLF

     lstparam   = *(";"  I xparamother-param)
Example:
The following is  I arean example I s of this property:
     LAST-MODIFIED:19960817T133000Z

3.8.7.4. Sequence Number

Property Name:
SEQUENCE
Purpose:
This property defines the revision sequence number of the calendar component within a sequence of revisions.
Value Type:
 I integerINTEGER
Property Parameters:
 I Non-standardIANA and non-standard property parameters can be specified on this property.
Conformance:
The property can be specified in "VEVENT", "VTODO" or "VJOURNAL" calendar component.
Description:
When a calendar component is created, its sequence number is zero (US-ASCII decimal 48). It is monotonically incremented by the "Organizer's" CUA each time the "Organizer" makes a significant revision to the calendar component. When the "Organizer" makes changes to one of the following properties, the sequence number MUST be incremented:
In addition, changes made by the "Organizer" to other properties can also force the sequence number to be incremented. The "Organizer" CUA MUST increment the sequence number when I ever it makes changes to properties in the calendar component that the "Organizer" deems will jeopardize the validity of the participation status of the "Attendees". For example, changing the location of a meeting from one locale to another distant locale could effectively impact the participation status of the "Attendees".
The "Organizer" includes this property in an iCalendar object that it sends to an "Attendee" to specify the current version of the calendar component.
The "Attendee" includes this property in an iCalendar object that it sends to the "Organizer" to specify the version of the calendar component that the "Attendee" is referring to.
A change to the sequence number is not the mechanism that an "Organizer" uses to request a response from the "Attendees". The "RSVP" parameter on the "ATTENDEE" property is used by the "Organizer" to indicate that a response from the "Attendees" is requested.
Format Definition:
This property is defined by the following notation:
     seq = "SEQUENCE" seqparam ":" integer CRLF
     ; Default is "0"

     seqparam   = *(";"  I xparamother-param)
Example:
The following is an example of this property for a calendar component that was just created by the "Organizer" I .:
     SEQUENCE:0
The following is an example of this property for a calendar component that has been revised two different times by the "Organizer" I .:
     SEQUENCE:2

3.8.8. Miscellaneous Component Properties

The following properties specify information about a number of miscellaneous features of calendar components.

 I  

3.8.8.1. IANA Properties

Property Name:
An IANA registered property name
Value Type:
The default value type is TEXT. The value type can be set to any value type.
Property Parameters:
Any parameter can be specified on this property.
Description:
This specification allows other properties registered with IANA to be specified in any calendar components. Compliant applications are expected to be able to parse these other IANA registered properties but can ignore them.
Format Definition:
This property is defined by the following notation:
     iana-prop = iana-token *(";" icalparameter) ":" value CRLF
Example:
The following are examples of properties that might be registered to IANA:
     DRESSCODE:CASUAL

     NON-SMOKING;VALUE=BOOLEAN:TRUE

3.8.8.2. Non-standard Properties

 I  #issue44+4.8.8.1_param_on_x-prop   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-09-19 x-prop should allow any parameter defined by iCalendar as well as any iana-param.
Resolution: Fixed ABNF.
Associated changes in this document: 3.8.8.2, 3.8.8.2, 3.8.8.2, 3.8.8.2., Published in: draft-ietf-calsify-rfc2445bis-06

Property Name:
Any property name with a "X-" prefix
Purpose:
This class of property provides a framework for defining non-standard properties.
Value Type:
 I TEXTThe default value type is TEXT. The value type can be set to any value type.
Property Parameters:
 I Non-standardIANA, non-standard and language property parameters can be specified on this property.
Conformance:
This property can be specified in any calendar component.
Description:
The MIME Calendaring and Scheduling Content Type provides a "standard mechanism for doing non-standard things". This extension support is provided for implementers to "push the envelope" on the existing version of the memo. Extension properties are specified by property and/or property parameter names that have the prefix text of "X-" (the two character sequence: LATIN CAPITAL LETTER X character followed by the  I HYPEN-MINUSHYPHEN-MINUS character). It is recommended that vendors concatenate onto this sentinel another short prefix text to identify the vendor. This will facilitate readability of the extensions and minimize possible collision of names between different vendors. User agents that support this content type are expected to be able to parse the extension properties and property parameters but can ignore them.
At present, there is no registration authority for names of extension properties and property parameters. The  I datavalue type for this property is TEXT. Optionally, the  I datavalue type can be any of the other valid  I datavalue types.
Format Definition:
 I TheThis property is defined by the following notation:
     x-prop = x-name *(";"  I xparamicalparameter) I [";" languageparam] ":"  I textvalue CRLF I 
        ; Lines longer than 75 octets should be folded
 
Example:
The following might be the ABC vendor's extension for an audio-clip form of subject property:
 I 
     X-ABC-MMSUBJ;X-ABC-MMSUBJTYPE=wave:http://load.noise.org/mysubj.wav

     X-ABC-MMSUBJ;VALUE=URI;FMTTYPE=audio/basic:http://www.example.
      org/mysubj.au

3.8.8.3. Request Status

 I  #issue64+4.8.8.2_request-status   (type: change, status: closed)
bernard.desruisseaux@oracle.com2006-11-05 We need to clarify that REQUEST-STATUS only allows pairs (1.1) and 3-tuples (1.1.1).
Resolution:
Associated changes in this document: 3.8.8.3, 3.8.8.3, 3.8.8.3, 3.8.8.3., Published in: draft-ietf-calsify-rfc2445bis-06

Property Name:
REQUEST-STATUS
Purpose:
This property defines the status code returned for a scheduling request.
Value Type:
TEXT
Property Parameters:
 I Non-standardIANA, non-standard and language property parameters can be specified on this property.
Conformance:
The property can be specified in "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar component.
Description:
This property is used to return status code information related to the processing of an associated iCalendar object. The  I datavalue type for this property is TEXT.
The value consists of a short return status component, a longer return status description component, and optionally a status-specific data component. The components of the value are separated by the SEMICOLON character (US-ASCII decimal 59).
The short return status is a PERIOD character (US-ASCII decimal 46) separated  I pair or 3-tuple of integers. For example,  I "3.1" or "3.1.1". The successive levels of integers provide for a successive level of status code granularity.
The following are initial classes for the return status code. Individual iCalendar object methods will define specific return status codes for these classes. In addition, other classes for the return status code may be defined using the registration process defined later in this memo.
     |==============+===============================================|
     | Short Return | Longer Return Status Description              |
     | Status Code  |                                               |
     |==============+===============================================|
     |    1.xx      | Preliminary success. This class of status     |
     |              | of status code indicates that the request has |
     |              | request has been initially processed but that |
     |              | completion is pending.                        |
     |==============+===============================================|
     |    2.xx      | Successful. This class of status code         |
     |              | indicates that the request was completed      |
     |              | successfuly. However, the exact status code   |
     |              | can indicate that a fallback has been taken.  |
     |==============+===============================================|
     |    3.xx      | Client Error. This class of status code       |
     |              | indicates that the request was not successful.|
     |              | The error is the result of either a syntax or |
     |              | a semantic error in the client formatted      |
     |              | request. Request should not be retried until  |
     |              | the condition in the request is corrected.    |
     |==============+===============================================|
     |    4.xx      | Scheduling Error. This class of status code   |
     |              | indicates that the request was not successful.|
     |              | Some sort of error occurred within the        |
     |              | calendaring and scheduling service, not       |
     |              | directly related to the request itself.       |
     |==============+===============================================|
Format Definition:
 I TheThis property is defined by the following notation:
     rstatus    = "REQUEST-STATUS" rstatparam ":"
                  statcode ";" statdesc [";" extdata]

     rstatparam = *(

                ; the following is  I optionalOPTIONAL,
                ; but MUST NOT occur more than once

                (";" languagepar I am) /

                ; the following is  I optionalOPTIONAL,
                ; and MAY occur more than once

                (";"  I xparamother-param)

                )

     statcode   = 1*DIGIT  I 1* I 2("." 1*DIGIT)
     ;Hierarchical, numeric return status code

     statdesc   = text
     ;Textual status description

     extdata    = text
     ;Textual exception data. For example, the offending property
     ;name and value or complete property line.
Example:
The following are some possible examples of this property.
The COMMA and SEMICOLON separator characters in the property value are BACKSLASH character escaped because they appear in a text value.
     REQUEST-STATUS:2.0;Success

     REQUEST-STATUS:3.1;Invalid property value;DTSTART:96-Apr-01

     REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduled
      as a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2

     REQUEST-STATUS:4.1;Event conflict. Date/time is busy.

     REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:
       I MAILTOmailto:jsmith@ I host.comexample.com

4. iCalendar Object Examples

The following examples are provided as an informational source of illustrative iCalendar objects consistent with this content type.

The following example specifies a three-day conference that begins at  I 8:00 AM EDT,2:30 P.M. UTC, September 18, 1996 and end at  I 6:00 PM EDT,10:00 P.M. UTC, September 20, 1996.

      I BEGIN:VCALENDAR PRODID:-//xyz Corp//NONSGML PDA Calendar Verson
     1.0//EN VERSION:2.0 BEGIN:VEVENT DTSTAMP:19960704T120000Z
     UID:uid1@host.com ORGANIZER: I MAILTOmailto:jsmith@host.com
     DTSTART:19960918T143000Z DTEND:19960920T220000Z STATUS:CONFIRMED
     CATEGORIES:CONFERENCE SUMMARY:Networld+Interop Conference
     DESCRIPTION:Networld+Interop Conference
       and Exhibit\nAtlanta World Congress Center\n
      Atlanta, Georgia END:VEVENT END:VCALENDAR BEGIN:VCALENDAR
     PRODID:-//xyz Corp//NONSGML PDA Calendar Version 1.0//EN
     VERSION:2.0
     BEGIN:VEVENT
     DTSTAMP:19960704T120000Z
     UID:uid1@example.com
     ORGANIZER: I MAILTOmailto:jsmith@example.com
     DTSTART:19960918T143000Z
     DTEND:19960920T220000Z
     STATUS:CONFIRMED
     CATEGORIES:CONFERENCE
     SUMMARY:Networld+Interop Conference
     DESCRIPTION:Networld+Interop Conference
       and Exhibit\nAtlanta World Congress Center\n
      Atlanta\, Georgia
     END:VEVENT
     END:VCALENDAR 

The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.

     BEGIN:VCALENDAR
     PRODID:-//RDU Software//NONSGML HandCal//EN
     VERSION:2.0
     BEGIN:VTIMEZONE
     TZID: I US-EasternAmerica/New_York
     BEGIN:STANDARD
     DTSTART:19981025T020000 I 
     RDATE:19981025T020000
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19990404T020000 I 
     RDATE:19990404T020000
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE
     BEGIN:VEVENT
     DTSTAMP:19980309T231000Z
     UID:guid-1. I host1.comexample.com
     ORGANIZER;ROLE=CHAIR: I MAILTOmailto:mrbig@ I host.comexample.com
     ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:
       I MAILTOmailto:employee-A@ I host.comexample.com
     DESCRIPTION:Project XYZ Review Meeting
     CATEGORIES:MEETING
     CLASS:PUBLIC
     CREATED:19980309T130000Z
     SUMMARY:XYZ Project Review
     DTSTART;TZID= I US-EasternAmerica/New_York:19980312T083000
     DTEND;TZID= I US-EasternAmerica/New_York:19980312T093000
     LOCATION:1CP Conference Room 4350
     END:VEVENT
     END:VCALENDAR

The following is an example of an iCalendar object passed in a MIME message with a single body part consisting of a "text/calendar" Content Type.

     TO:jsmith@ I host1.comexample.com
     FROM:jdoe@ I host1.comexample.com
     MIME-VERSION:1.0
     MESSAGE-ID:<id3@ I host1.comexample.com>
     CONTENT-TYPE:text/calendar I ; method="xyz"; component="VEVENT"

     BEGIN:VCALENDAR
     METHOD:xyz
     VERSION:2.0
     PRODID:-//ABC Corporation//NONSGML My Product//EN
     BEGIN:VEVENT  I 
     DTSTAMP:19970324T1200Z 
     DTSTAMP:19970324T120000Z 
     SEQUENCE:0
     UID:uid3@ I host1.comexample.com
     ORGANIZER: I MAILTOmailto:jdoe@ I host1.comexample.com
     ATTENDEE;RSVP=TRUE: I MAILTOmailto:jsmith@ I host1.comexample.com