Calendaring and Scheduling Standards Simplification (calsify)
-------------------------------------------------------------
Charter
Last Modified: 2006-04-25
Current Status: Active Working Group
Chair(s):
Eliot Lear <lear@cisco.com>
Aki Niemi <aki.niemi@nokia.com>
Applications Area Director(s):
Ted Hardie <hardie@qualcomm.com>
Lisa Dusseault <lisa@osafoundation.org>
Applications Area Advisor:
Lisa Dusseault <lisa@osafoundation.org>
Mailing Lists:
General Discussion:ietf-calsify@osafoundation.org
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:
Jul 2005 Submit draft documenting interoperability issues for use in
progressing RFCs to Draft Standard.
Done Submit iMIP bis draft 00
Done Submit iCalendar bis draft 00, with formatting changes from
RFC2445.
Done Submit iTIP bis draft 00
Oct 2005 Submit revised interoperability issues draft version based on
WG discussion.
Dec 2005 WG decision on what document(s) require transition mechanisms
and hopefully rough idea what these will look like (and add new
goals if needed)
Mar 2006 WG last call on interoperability issues draft.
May 2006 Submit interoperability issues document to IESG for
Informational RFC.
May 2006 Submit version of iCalendar bis draft that addresses known
interoperability issues from interop events.
Jun 2006 Submit versions of iTIP and iMIP that address known
interoprability issues.
Jul 2006 Submit version of iCalendar draft that addresses WG open
discussions.
Sep 2006 Submit version of iCalendar draft ready for WG last call.
Nov 2006 Complete WG last call of iCalendar and submit new draft.
Nov 2006 Submit versions of iTIP and iMIP ready for last call.
Jan 2007 Submit iCalendar (bis) to IESG for Draft Standard.
Jan 2007 Complete WG last call of iTIP
Feb 2007 Complete WG last call of iMIP
Mar 2007 Submit iTIP to IESG for Draft Standard.
Apr 2007 Submit iMIP to IESG for Draft Standard.
Internet-Drafts:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Aug 2005 Jun 2006 <draft-ietf-calsify-rfc2447bis-02.txt>
iCalendar Message-Based Interoperability Protocol(iMIP)
Oct 2005 Jun 2006 <draft-ietf-calsify-2446bis-02.txt>
iCalendar Transport-Independent Interoperability Protocol
(iTIP)
Oct 2005 Jun 2006 <draft-ietf-calsify-rfc2445bis-01.txt>
Internet Calendaring and Scheduling Core Object Specification
(iCalendar)
Request For Comments:
None to date.