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

Event identity and end time

02

UID identifies an event, while start/end properties describe its interval.

Related RFCs and changes

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

RFC 5545 · § 3.6.1EXAMPLE
3 / 3
Event identity and end timeUID identifies an event, while start/end properties describe its interval.Event identity and end time1718192019 = exclusive endUID identifies the event, not a date position
03
Keep identity separate

Changing the interval does not require pretending this is a different UID.

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

DTSTART is inclusive; DTEND is non-inclusive for VEVENT.

  • DTSTART is inclusive; DTEND is non-inclusive for VEVENT.
  • DTEND and DURATION must not both occur in the same VEVENT.
  • The DTEND value type must match DTSTART, and its value must be later.
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 ↗