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

UTC, local time, and zones

03

DATE-TIME can be UTC, local with a time-zone reference, or floating local time.

Related RFCs and changes

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

RFC 5545 · § 3.3.5EXAMPLE
3 / 3
UTC, local time, and zonesDATE-TIME can be UTC, local with a time-zone reference, or floating local time.UTC, local time, and zones09:00 without TZID or Z → floatingA zone applies its rules, including offset changesFloating time is not one fixed global instant
03
Recognize floating time

An unqualified local time is not a globally fixed instant.

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

A trailing Z denotes UTC.

  • A trailing Z denotes UTC.
  • TZID references a time-zone definition rather than a fixed offset copied into every occurrence.
  • Floating time has neither Z nor TZID and follows the consuming context’s local-time interpretation.
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 ↗