metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)

Still current, but amended. Parts of this document are changed or extended by RFC 5546, RFC 6868, RFC 7529, RFC 7953, RFC 7986, RFC 9073, RFC 9074, RFC 9253. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5545
Published
September 2009
Authors
B. Desruisseaux
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
168
Also known as
—
Obsoletes:
RFC 2445
Updated by:
RFC 5546, RFC 6868, RFC 7529, RFC 7953, RFC 7986, RFC 9073, RFC 9074, RFC 9253

Topics

Referenced by

8 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5545-internet-calendaring-and-scheduling-core-object-specification-icalendar