Visual RFC.
ALL RFCs / RFC 5545
Read the RFC ↗
RFC 5545 / MECHANISM GUIDE

Calendar and component structure

01

A VCALENDAR contains components such as VEVENT rather than being only a row of dates.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.4 ↗
RFC 5545 · § 3.4EXAMPLE
3 / 3
Calendar and component structureA VCALENDAR contains components such as VEVENT rather than being only a row of dates.Calendar and component structureBEGIN:VCALENDARVERSION:2.0BEGIN:VEVENTUID:example-42END:VEVENT / END:VCALENDARFolded physical lines unfold into one property
03
Unfold content lines

A folded physical line still represents one property.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 2445 recurrence featuresRFC 5545 Appendix A.3

EXRULE, the THISANDPRIOR range value, and PROCEDURE alarms are removed. Use the supported recurrence and alarm properties instead.

Read the updated RFC section ↗
KEY POINT

BEGIN/END delimit calendar objects and components.

  • BEGIN/END delimit calendar objects and components.
  • Properties use content-line syntax with parameters.
  • Long lines should fold at 75 octets using CRLF plus whitespace; unfolding restores the logical line.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Calendar and component structure
  2. Event identity and end time
  3. UTC, local time, and zones
  4. Recurrence and exclusions
  5. Exceptions, alarms, and limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗