Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 168
- Abstract
- This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK]
- Publication Date
- 2009-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5545- Link
- https://doi.org/10.17487/RFC5545
- Author(s)
- Bernard Desruisseaux
- Keyword(s)
- Calendaring, CalDAV, Schedule, Scheduling, iCalendar, ITIP, IMIP, xCalendar
Latest version of IETF RFC 5545
Document Versions — IETF RFC 5545
-
▶ IETF RFC 5545 (2009-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- RFC5546 — RFC5546 EXTERNAL
- RFC6868 NOT IN REGISTRY
- RFC7529 NOT IN REGISTRY
- RFC7953 NOT IN REGISTRY
- RFC7986 NOT IN REGISTRY
- RFC9073 NOT IN REGISTRY
- RFC9074 NOT IN REGISTRY
- RFC9253 NOT IN REGISTRY
Normative Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- International Organization for Standardization, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", 2004. EXTERNAL
- International Organization for Standardization, "Information Technology_SGML Support Facilities -- Registration Procedures for Public Text Owner Identifiers, Second Edition", April 1991. EXTERNAL
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2368 [Superseded*]
- IETF RFC 3629 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 4648 [Active*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5646 [Active*]
Bibliographic Reference(s)
- ANSI.X3.61.1986 — ANSI INCITS 61-1986 EXTERNAL
- Eggert, P. and A.D. Olson, "Sources for Time Zone and Daylight Saving Time Data", July 2009, < http://www.twinsun.com/tz/tz-link.htm >. EXTERNAL
- Melnikov, A., "iCalendar Message-Based Interoperability Protocol (iMIP)", Work in Progress, June 2008. EXTERNAL
- Daboo, C., "iCalendar Transport-Independent Interoperability Protocol (iTIP)", Work in Progress, April 2009. EXTERNAL
- Internet Mail Consortium, "vCalendar: The Electronic Calendaring and Scheduling Exchange Format", September 1996, < http://www.imc.org/pdi/vcal-10.txt >. EXTERNAL
- IETF RFC 1738 [Superseded*]
- IETF RFC 2392 [Active*]
- IETF RFC 2397 [Active*]
- IETF RFC 2425 [Superseded*]
- IETF RFC 2426 [Superseded*]
- IETF RFC 2445 [Superseded*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 4516 [Active*]
- IETF RFC 4791 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5545.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar). Available at https://doi.org/10.17487/RFC5545
Snippet:
IETF RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar). Available at https://doi.org/10.17487/RFC5545
HTML (ISO 690 compliant)
Preview:
IETF RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar). Available at https://doi.org/10.17487/RFC5545
Snippet:
<span class="citation"><cite>IETF RFC 5545</cite>, Internet Calendaring and Scheduling Core Object Specification (iCalendar). Available at <a href="https://doi.org/10.17487/RFC5545" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5545</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar)
doi: 10.17487/RFC5545
url: https://doi.org/10.17487/RFC5545
doi: 10.17487/RFC5545
url: https://doi.org/10.17487/RFC5545
Snippet:
<li> <cite id="bib-rfc5545">IETF RFC 5545</cite>, Internet Calendaring and Scheduling Core Object Specification (iCalendar) <span class="doi">10.17487/RFC5545</span> </li>
Referenced By
- IETF RFC 6350 [Active*]
- IETF RFC 6557 [Active*]
- IETF RFC 6648 [Active*]