RFC 7953: Calendar Availability
In plain English — editorial summary, not part of the RFC
This document specifies a new iCalendar (RFC 5545) component that allows the publication of available and unavailable time periods associated with a calendar user. This component can be used in standard iCalendar free-busy lookups, including the iCalendar Transport-independent Interoperability Protocol (iTIP; RFC 5546) free-busy requests, to generate repeating blocks of available or busy time with exceptions as needed. This document also defines extensions to the Calendaring Extensions to WebDAV (CalDAV) calendar access protocol (RFC 4791) and the associated scheduling protocol (RFC 6638) to specify how this new calendar component can be used when evaluating free-busy time.
Document record
- Document ID
- RFC7953
- Published
- August 2016
- Authors
- C. Daboo; M. Douglass
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7809Calendaring Extensions to WebDAV (CalDAV): Time Zones by ReferenceCurrent
March 2016
- RFC 7529Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)Current
May 2015
- RFC 9074"VALARM" Extensions for iCalendarCurrent
August 2021
- RFC 7986New Properties for iCalendarCurrent
October 2016
- RFC 8607Calendaring Extensions to WebDAV (CalDAV): Managed AttachmentsCurrent
June 2019
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7808Time Zone Data Distribution ServiceCurrent
March 2016
- RFC 8984JSCalendar: A JSON Representation of Calendar DataCurrent
July 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?