Calendaring and Scheduling Standards Simplification (calsify) Internet Drafts
| iCalendar Message-Based Interoperability Protocol (iMIP) | |||||||||||||||||
|
This document, iCalendar Message-Based Interoperability Protocol (iMIP), specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCAL) are composed using constructs from RFC 2822, RFC 2045, RFC 2046, RFC 2047 and RFC 2049. This document is a product of Calendaring and Scheduling Standards Simplification (calsify) working group. More information about the IETF CALSIFY working group activities can be found on the IETF web site at | ||||||||||||||||
| iCalendar Transport-Independent Interoperability Protocol (iTIP) | |||||||||||||||||
|
This document specifies a protocol using the iCalendar object specification to provide scheduling interoperability between different calendar systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol using specific interoperable methods of communications between systems. iTIP complements the iCalendar object specification by adding semantics for group scheduling methods commonly available in current calendar systems. These scheduling methods permit two or more calendar systems to perform transactions such as publish, schedule, reschedule, respond to scheduling requests, negotiation of changes or cancel. | ||||||||||||||||
| Internet Calendaring and Scheduling Core Object Specification (iCalendar) | |||||||||||||||||
|
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to- dos, journal entries and free/busy information, independent of any particular calendar service or protocol. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Calendaring and Scheduling Standards Simplification (calsify)
Last Modified: 2008-04-23
Additional information is available at tools.ietf.org/wg/calsify
Chair(s):
Applications Area Director(s):
Applications Area Advisor:
Mailing Lists:
General Discussion: ietf-calsify@osafoundation.orgTo Subscribe: http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
Archive: http://lists.osafoundation.org/pipermail/ietf-calsify/
Description of Working Group:
The Calendaring and Scheduling standards, defined in RFC's 2445, 2446,and 2447 were released in November 1998, and further described in RFC
3283. They were designed to progress the level of interoperability
between dissimilar calendaring and scheduling systems. The Calendaring
and Scheduling Core Object Specification, iCalendar, succeeded in
establishing itself as the common format for exchanging calendaring
information across the Internet. On the other hand, only basic
interoperability has been achieved between different scheduling
systems.
The Calsify working group is chartered to:
(1) Revise the Calendaring and Scheduling Standards to advance the
state of interoperable calendaring and scheduling by addressing
the known interoperability issues, errata, and problems found based on
implementation experience.
(2) Clarify the registration process for iCalendar extensions (i.e.,
the current core object specification only provides a template
to register new properties).
(3) Provide a means to ease transition from, and to co-exist with,
the earlier iCalendar standards to the new ones.
Proposing an XML representation or transformation of iCalendar
objects is out of the scope of this working group.
Depending on the results of the update process on the standards
documents the working group will consider whether advancing the
documents to draft standard is appropriate. If we decide to move the
documents to draft status, milestones may get changed and/or added
to allow for any additional work necessary to advance the documents.
Goals and Milestones:
| Done | Submit iMIP bis draft 00 | |
| Done | Submit iCalendar bis draft 00, with formatting changes from RFC2445. | |
| Done | Submit iTIP bis draft 00 | |
| Done | Submit updated version of rfc2447bis draft | |
| Done | Submit updated version of rfc2446bis draft | |
| Done | Submit updated version of rfc2445bis draft | |
| Done | Working Group Last Call on rfc2445bis draft | |
| Jun 2007 | Submit rfc2445bis draft to IESG | |
| Jun 2007 | Working Group Last Call on rfc2446bis draft | |
| Jun 2007 | Working Group Last Call on rfc2447bis draft | |
| Jul 2007 | Submit rfc2446bis to IESG | |
| Jul 2007 | Submit rfc2447bis to IESG |
Internet-Drafts:
iCalendar Message-Based Interoperability Protocol (iMIP) (39982 bytes)iCalendar Transport-Independent Interoperability Protocol (iTIP) (299954 bytes)
Internet Calendaring and Scheduling Core Object Specification (iCalendar) (350334 bytes)
No Request For Comments
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
