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

8.3.3. Parameters Registry

The following table has been used to initialize the parameters registry.

    +----------------+---------+--------------------------+
    | Parameter      | Status  | Reference                |
    +----------------+---------+--------------------------+
    | ALTREP         | Current | RFC 5545, Section 3.2.1  |
    |                |         |                          |
    | CN             | Current | RFC 5545, Section 3.2.2  |
    |                |         |                          |
    | CUTYPE         | Current | RFC 5545, Section 3.2.3  |
    |                |         |                          |
    | DELEGATED-FROM | Current | RFC 5545, Section 3.2.4  |
    |                |         |                          |
    | DELEGATED-TO   | Current | RFC 5545, Section 3.2.5  |
    |                |         |                          |
    | DIR            | Current | RFC 5545, Section 3.2.6  |
    |                |         |                          |
    | ENCODING       | Current | RFC 5545, Section 3.2.7  |
    |                |         |                          |
    | FMTTYPE        | Current | RFC 5545, Section 3.2.8  |
    |                |         |                          |
    | FBTYPE         | Current | RFC 5545, Section 3.2.9  |
    |                |         |                          |
    | LANGUAGE       | Current | RFC 5545, Section 3.2.10 |
    |                |         |                          |
    | MEMBER         | Current | RFC 5545, Section 3.2.11 |
    |                |         |                          |
    | PARTSTAT       | Current | RFC 5545, Section 3.2.12 |
    |                |         |                          |
    | RANGE          | Current | RFC 5545, Section 3.2.13 |
    |                |         |                          |
    | RELATED        | Current | RFC 5545, Section 3.2.14 |
    |                |         |                          |
    | RELTYPE        | Current | RFC 5545, Section 3.2.15 |
    |                |         |                          |
    | ROLE           | Current | RFC 5545, Section 3.2.16 |
    |                |         |                          |
    | RSVP           | Current | RFC 5545, Section 3.2.17 |
    |                |         |                          |
    | SENT-BY        | Current | RFC 5545, Section 3.2.18 |
    |                |         |                          |
    | TZID           | Current | RFC 5545, Section 3.2.19 |
    |                |         |                          |
    | VALUE          | Current | RFC 5545, Section 3.2.20 |
    +----------------+---------+--------------------------+

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 ietf.org .  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.