RFC 8607: Calendaring Extensions to WebDAV (CalDAV): Managed Attachments
In plain English — editorial summary, not part of the RFC
This specification adds an extension to the Calendaring Extensions to WebDAV (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server. This specification documents existing code deployed by multiple vendors. It is published as an Informational specification rather than Standards Track due to its noncompliance with multiple best current practices of HTTP.
Document record
- Document ID
- RFC8607
- Published
- June 2019
- Authors
- C. Daboo; A. Quillaud; K. Murchison
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9074"VALARM" Extensions for iCalendarCurrent
August 2021
- RFC 7953Calendar AvailabilityCurrent
August 2016
- 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 5545Internet Calendaring and Scheduling Core Object Specification (iCalendar)Updated
September 2009
- RFC 7986New Properties for iCalendarCurrent
October 2016
- RFC 7808Time Zone Data Distribution ServiceCurrent
March 2016
- RFC 8144Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)Current
April 2017
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?