Calendaring and Scheduling Standards Simplification (calsify)
-------------------------------------------------------------
Charter
Last Modified: 2007-09-26
Current Status: Active Working Group
Chair(s):
Aki Niemi <
[email protected]>
Eliot Lear <
[email protected]>
Applications Area Director(s):
Chris Newman <
[email protected]>
Lisa Dusseault <
[email protected]>
Applications Area Advisor:
Lisa Dusseault <
[email protected]>
Mailing Lists:
General Discussion:
[email protected]
To 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 as been achieved between different scheduling systems.
The Calsify working group is chartered to:
(1) Publish the interoperability issues that have arisen between
calendaring and scheduling systems, as well as document the usage of
iCalendar by other specifications.
(2) Revise the Calendaring and Scheduling standards to advance the
state of interoperable calendaring and scheduling by addressing
the published interoperability issues. As far as it is possible, the
working group will ensure backwards compatibility with widely deployed
implementations and other specifications that use it.
(3) Clarify the registration process for iCalendar extensions (i.e.,
the current core object specification only provides a template
to register new properties).
(4) Advance the Calendaring and Scheduling standards to Draft Standard.
(5) Work on transition (upgrade or versioning) mechanisms for calendar
data exchange.
Proposing an XML representation or transformation of iCalendar
objects is out of the scope of this working group.
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:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Oct 2005 Nov 2007 <draft-ietf-calsify-2446bis-04.txt>
iCalendar Transport-Independent Interoperability Protocol
(iTIP)
Request For Comments:
None to date.
