Try out our new RRULE tool for creating RRULE compatible strings.






Specifies the time zone component to use when determining the results of a report.


The CALDAV given calendaring REPORT request, the server MUST rely on the specified VTIMEZONE component instead of the CALDAV:calendar- timezone property of the calendar collection, in which the calendar object resource is contained to resolve "date" values and "date with local time" values (i.e., floating time) to "date with UTC time" values. The server will require this information to determine if a calendar component scheduled with "date" values or "date with local time" values intersects a CALDAV:time-range specified in a CALDAV:calendar-query REPORT.


The iCalendar data embedded within the CALDAV element MUST follow the standard XML character data encoding rules, including use of <, >, & etc. entity encoding or the use of a construct. In the later case, the iCalendar data cannot contain the character sequence "]]>", which is the end delimiter for the CDATA section.


   PCDATA value: an iCalendar object with exactly one VTIMEZONE

This document was automatically converted to XHTML using an RFC to HTML converter with the original text document at the Internet Engineering Task Force web site at .  The original text document should be referred to if there are any errors or discrepancies found in this document.

Need to test your iCalendar feeds?

The iCalendar Validator provides developers and testers a method to validate their iCalendar feeds, which can take data from either a URL, file or text snippet and compare it against the RFC 5545 specification.  We believe we have one of the best iCalendar validation tools available on the internet. More information about the validator can be found here.