2.1.3 Calendaring and Scheduling Standards Simplification (calsify)

NOTE: This charter is a snapshot of the 66th IETF Meeting in Montreal, Quebec Canada. It may now be out-of-date.

Last Modified: 2006-07-26

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:

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
Sep 2006  Working Group Last Call on rfc2445bis draft
Oct 2006  Working Group Last Call on rfc2446bis draft
Oct 2006  Working Group Last Call on rfc2447bis draft
Nov 2006  Decide whether documents move to PS or DS
Jan 2007  Submit rfc2446bis draft to IESG
Jan 2007  Submit rfc2445bis to IESG
Jan 2007  Submit rfc2447bis to IESG

Internet-Drafts:

  • draft-ietf-calsify-rfc2447bis-02.txt
  • draft-ietf-calsify-2446bis-02.txt
  • draft-ietf-calsify-rfc2445bis-03.txt

    No Request For Comments

    Meeting Minutes


    Slides

    Agenda bash and chair update
    RFC2445bis Issues
    RFC2446bis Issues