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

Exceptions, alarms, and limits

05

RECURRENCE-ID addresses an occurrence; VALARM describes a reminder rather than arbitrary executable code.

Related RFCs and changes

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

RFC 5545 · § 3.8.4.4EXAMPLE
3 / 3
Exceptions, alarms, and limitsRECURRENCE-ID addresses an occurrence; VALARM describes a reminder rather than arbitrary executable code.Exceptions, alarms, and limits3101724move one18Alarm requires safe application handling
03
Handle alarms safely

A reminder is processed with user permissions and safe resource handling.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

An exception identifies the original scheduled occurrence with RECURRENCE-ID.

  • An exception identifies the original scheduled occurrence with RECURRENCE-ID.
  • VALARM has its own required properties and trigger semantics.
  • Calendar data is untrusted input; access control and safe handling remain application responsibilities.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗