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






Forces the server to expand recurring components into individual recurrence instances.


The CALDAV given calendaring REPORT request, the server MUST expand the recurrence set into calendar components that define exactly one

recurrence instance, and MUST return only those whose scheduled time intersect a specified time range.

The "start" attribute specifies the inclusive start of the time range, and the "end" attribute specifies the non-inclusive end of the time range. Both attributes are specified as date with UTC time value. The value of the "end" attribute MUST be greater than the value of the "start" attribute.

The server MUST use the same logic as defined for CALDAV:time- range to determine if a recurrence instance intersects the specified time range.

Recurring components, other than the initial instance, MUST include a RECURRENCE-ID property indicating which instance they refer to.

The returned calendar components MUST NOT use recurrence properties (i.e., EXDATE, EXRULE, RDATE, and RRULE) and MUST NOT have reference to or include VTIMEZONE components. Date and local time with reference to time zone information MUST be converted into date with UTC time.



   start value: an iCalendar "date with UTC time"
   end value: an iCalendar "date with UTC time"

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.