metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 2446: iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5546.

Current version: RFC 5546 — iCalendar Transport-Independent Interoperability Protocol (iTIP)

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

This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. [STANDARDS-TRACK]

Document record

Document ID
RFC2446
Published
November 1998
Authors
S. Silverberg; S. Mansour; F. Dawson; R. Hopson
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
109
Also known as
—
Obsoleted by:
RFC 5546

Topics

Referenced by

One later RFC formally updates or obsoletes 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/2446-icalendar-transport-independent-interoperability-protocol-itip-scheduling-events