RFC 6638: Scheduling Extensions to CalDAV
In plain English — editorial summary, not part of the RFC
This document defines extensions to the Calendaring Extensions to WebDAV (CalDAV) "calendar-access" feature to specify a standard way of performing scheduling operations with iCalendar-based calendar components. This document defines the "calendar-auto-schedule" feature of CalDAV. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6638
- Published
- June 2012
- Authors
- C. Daboo; B. Desruisseaux
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 78
- Also known as
- —
- Updated by:
- RFC 7953
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5545Internet Calendaring and Scheduling Core Object Specification (iCalendar)Updated
September 2009
- RFC 7529Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)Current
May 2015
- RFC 6047iCalendar Message-Based Interoperability Protocol (iMIP)Current
December 2010
- RFC 7809Calendaring Extensions to WebDAV (CalDAV): Time Zones by ReferenceCurrent
March 2016
- RFC 5333IANA Registration of Enumservices for Internet CalendaringUpdated
October 2009
- RFC 7986New Properties for iCalendarCurrent
October 2016
- RFC 8984JSCalendar: A JSON Representation of Calendar DataCurrent
July 2021
- RFC 9074"VALARM" Extensions for iCalendarCurrent
August 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?