Progress toward a standard content type

[anik@xxxxxxxxxx (Anik Ganguly)]

I am happy to report that the people who have been most active on the
subject of a standard content type (a.k.a. Core object specification) met
yesterday with the WG chairs and have come to an agreement that will help us
complete this work soon.

This agreement will be discussed at our meeting during the 37th IETF in San
Jose.

The chief elements of the agreement are as follows:

The basic document for the standard content type will be the one that is
currently named:
ftp://ds.internic.net/internet-drafts/draft-ietf-calsch-csct-00.txt
This document is edited by Frank Dawson and is based on Versit's vCalendar

Moving forward, this document will be co-edited by Derik Stenerson and Frank
Dawson and its name may change if necessary.

The specification in this document will be reviewed by the WG and any
errors, problems, "bugs" will be fixed to the satisfaction of the WG.  This
review and revision will not be constrained by a requirement for backward
compatibility with existing vCalendar implementations.  In other words, if
the WG agrees that something in the specification is broken, it cannot be
left broken just because some implementations out there use the "broken"
spec.  Conversely, however the specification will not be changed
capriciously -- if something in the specification is not broken, it will not
be changed.

The issues list that has been circulated on the mailing list accurately
reflects the set of issues recognized by the editors at the time they
created the list.  As new issues are identified, they will be added to the
list and as the issues are resolved, their resolution will be recorded there
as well.  This issues list will be discussed at the IETF meeting today.

In the event that the editors cannot agree on a resolution, Bob Moskowitz
will act as the arbitrator.  This was agreeable to both editors.

Anik Ganguly
OnTime
Campbell Services Inc.

http://www.ontime.com