2009-04-29 2012-05-01 A Standards Track RFC is required for registration of iCalendar elements that modify elements previously documented in a Standards Track RFC. Expert Review with RFC Required VCALENDAR Current Section 3.4 VEVENT Current Section 3.6.1 VTODO Current Section 3.6.2 VJOURNAL Current Section 3.6.3 VFREEBUSY Current Section 3.6.4 VTIMEZONE Current Section 3.6.5 VALARM Current Section 3.6.6 STANDARD Current Section 3.6.5 DAYLIGHT Current Section 3.6.5 Expert Review with RFC Required CALSCALE Current Section 3.7.1 METHOD Current Section 3.7.2 PRODID Current Section 3.7.3 VERSION Current Section 3.7.4 ATTACH Current Section 3.8.1.1 CATEGORIES Current Section 3.8.1.2 CLASS Current Section 3.8.1.3 COMMENT Current Section 3.8.1.4 DESCRIPTION Current Section 3.8.1.5 GEO Current Section 3.8.1.6 LOCATION Current Section 3.8.1.7 PERCENT-COMPLETE Current Section 3.8.1.8 PRIORITY Current Section 3.8.1.9 RESOURCES Current Section 3.8.1.10 STATUS Current Section 3.8.1.11 SUMMARY Current Section 3.8.1.12 COMPLETED Current Section 3.8.2.1 DTEND Current Section 3.8.2.2 DUE Current Section 3.8.2.3 DTSTART Current Section 3.8.2.4 DURATION Current Section 3.8.2.5 FREEBUSY Current Section 3.8.2.6 TRANSP Current Section 3.8.2.7 TZID Current Section 3.8.3.1 TZNAME Current Section 3.8.3.2 TZOFFSETFROM Current Section 3.8.3.3 TZOFFSETTO Current Section 3.8.3.4 TZURL Current Section 3.8.3.5 ATTENDEE Current Section 3.8.4.1 CONTACT Current Section 3.8.4.2 ORGANIZER Current Section 3.8.4.3 RECURRENCE-ID Current Section 3.8.4.4 RELATED-TO Current Section 3.8.4.5 URL Current Section 3.8.4.6 UID Current Section 3.8.4.7 EXDATE Current Section 3.8.5.1 EXRULE Deprecated Section 4.8.5.2 RDATE Current Section 3.8.5.2 RRULE Current Section 3.8.5.3 ACTION Current Section 3.8.6.1 REPEAT Current Section 3.8.6.2 TRIGGER Current Section 3.8.6.3 CREATED Current Section 3.8.7.1 DTSTAMP Current Section 3.8.7.2 LAST-MODIFIED Current Section 3.8.7.3 SEQUENCE Current Section 3.8.7.4 REQUEST-STATUS Current Section 3.8.8.3 XML Current Section 4.2 Expert Review with RFC Required ALTREP Current Section 3.2.1 CN Current Section 3.2.2 CUTYPE Current Section 3.2.3 DELEGATED-FROM Current Section 3.2.4 DELEGATED-TO Current Section 3.2.5 DIR Current Section 3.2.6 ENCODING Current Section 3.2.7 FMTTYPE Current Section 3.2.8 FBTYPE Current Section 3.2.9 LANGUAGE Current Section 3.2.10 MEMBER Current Section 3.2.11 PARTSTAT Current Section 3.2.12 RANGE Current Section 3.2.13 RELATED Current Section 3.2.14 RELTYPE Current Section 3.2.15 ROLE Current Section 3.2.16 RSVP Current Section 3.2.17 SCHEDULE-AGENT Current Section 7.1 SCHEDULE-FORCE-SEND Current Section 7.2 SCHEDULE-STATUS Current Section 7.3 SENT-BY Current Section 3.2.18 TZID Current Section 3.2.19 VALUE Current Section 3.2.20 Expert Review with RFC Required A Standards Track RFC is REQUIRED for the registration of new Value Data Types that modify existing properties. BINARY Current Section 3.3.1 BOOLEAN Current Section 3.3.2 CAL-ADDRESS Current Section 3.3.3 DATE Current Section 3.3.4 DATE-TIME Current Section 3.3.5 DURATION Current Section 3.3.6 FLOAT Current Section 3.3.7 INTEGER Current Section 3.3.8 PERIOD Current Section 3.3.9 RECUR Current Section 3.3.10 TEXT Current Section 3.3.11 TIME Current Section 3.3.12 URI Current Section 3.3.13 UTC-OFFSET Current Section 3.3.14 Expert Review with RFC Required INDIVIDUAL Current Section 3.2.3 GROUP Current Section 3.2.3 RESOURCE Current Section 3.2.3 ROOM Current Section 3.2.3 UNKNOWN Current Section 3.2.3 Expert Review with RFC Required FREE Current Section 3.2.9 BUSY Current Section 3.2.9 BUSY-UNAVAILABLE Current Section 3.2.9 BUSY-TENTATIVE Current Section 3.2.9 Expert Review with RFC Required A Standards Track RFC is REQUIRED for the registration of Participation Status values to be used in "VEVENT" calendar components. NEEDS-ACTION Current Section 3.2.12 ACCEPTED Current Section 3.2.12 DECLINED Current Section 3.2.12 TENTATIVE Current Section 3.2.12 DELEGATED Current Section 3.2.12 COMPLETED Current Section 3.2.12 IN-PROCESS Current Section 3.2.12 Expert Review with RFC Required CHILD Current Section 3.2.15 PARENT Current Section 3.2.15 SIBLING Current Section 3.2.15 Expert Review with RFC Required CHAIR Current Section 3.2.16 REQ-PARTICIPANT Current Section 3.2.16 OPT-PARTICIPANT Current Section 3.2.16 NON-PARTICIPANT Current Section 3.2.16 Expert Review with RFC Required AUDIO Current Section 3.8.6.1 DISPLAY Current Section 3.8.6.1 EMAIL Current Section 3.8.6.1 PROCEDURE Deprecated Section 4.8.6.1 Expert Review with RFC Required PUBLIC Current Section 3.8.1.3 PRIVATE Current Section 3.8.1.3 CONFIDENTIAL Current Section 3.8.1.3 Expert Review with RFC Required PUBLISH Current REQUEST Current REPLY Current ADD Current CANCEL Current REFRESH Current COUNTER Current DECLINECOUNTER Current Expert Review with RFC Required 1.0 Current , Section 3.2.9.1 1.1 Current , Section 3.2.9.2 1.2 Current , Section 3.2.9.3 2.0 Current , Section 3.6.1 2.1 Current , Section 3.6.2 2.2 Current , Section 3.6.3 2.3 Current , Section 3.6.4 2.4 Current , Section 3.6.5 2.5 Current , Section 3.6.6 2.6 Current , Section 3.6.7 2.7 Current , Section 3.6.8 2.8 Current , Section 3.6.9 2.9 Current , Section 3.6.10 2.10 Current , Section 3.6.11 2.11 Current , Section 3.6.12 3.0 Current , Section 3.6.13 3.1 Current , Section 3.6.14 3.2 Current , Section 3.6.15 3.3 Current , Section 3.6.16 3.4 Current , Section 3.6.17 3.5 Current , Section 3.6.18 3.6 Current , Section 3.6.19 3.7 Current , Section 3.6.20 3.8 Current , Section 3.6.21 3.9 Current , Section 3.6.22 3.10 Current , Section 3.6.23 3.11 Current , Section 3.6.24 3.12 Current , Section 3.6.25 3.13 Current , Section 3.6.26 3.14 Current , Section 3.6.27 4.0 Current , Section 3.6.28 5.0 Current , Section 3.6.29 5.1 Current , Section 3.6.30 5.2 Current , Section 3.6.31 5.3 Current , Section 3.6.32 Expert Review with RFC Required SERVER Current Section 7.1 CLIENT Current Section 7.1 NONE Current Section 7.1 Expert Review with RFC Required REQUEST Current Section 7.2 REPLY Current Section 7.2