2.1.  Published Documents

2.2.  New Internet Drafts Submitted to IETF

2.3.  Updated Internet Drafts and Published RFCs

3.1.  BOF — PUSH for CALDAV

We had a good discussion on whether/how to add push notification support to CalDAV (and WebDAV/CardDAV). It was clear there was a demand for some common way to push, maybe using dufferent push implementations. We will start an Ad Hoc Committee to move forward with this discussion and specify a TC charter.

3.2.  CALSCALE-ADHOC

The draft has been updated following the last Roundtable: Non-Gregorian Recurrence Rules in iCalendar. There have been no changes to the presentation since Roundtable XXVII in June; the presentation was repeated unchanged for those who were not at the June event. The draft specification is at the IETF and we are working to generate additional and broader interest in it. Libraries such as iCal4j have been updated to ensure that they will properly ignore the RSCALE parameter on RRULE when encountered. Google hopes to be able to conduct interoperability testing at CalConnect XXIX next February of their initial implementation of RSCALE.

3.3.  TC AUTODISCOVERY

Aggregated Service Discovery. We presentated the current state of the draft — the protocol has a new name: Automated Service Configuration. We showed a quick overview of how this protocol will be of benefit to users. We had agreement that this would be a benefit to a lot of users, but we really need buy in from client and OS system configuration, and IETF folks to move this forward.

We will continue to pursue those avenues as well as setup actual demos of the technology as a proof-of-concept.

3.4.  TC CALDAV

We first presented the changes in version 02 of the managed attachment draft https://tools.ietf.org/html/draft-daboo-caldav-attachments/[CalDAV Managed Attachments]. During the last interop, several new implementations of the managed attachment draft have emerged, raising new questions. We did discuss those, as well as the last few open issues remaining on the spec. We then had a very lively discussion around the notion of scheduling object draft. There seemed to be an agreement that it is an area where we should spend some time in the coming months. In our next call, we will discuss the prioritization of the various specs we are working on.

3.5.  TC EVENTPUB

We presented the two iCalendar extension specs that are being developed in this committee: https://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publication Extensions to iCalendar] and New Properties for iCalendar. The first specification adds STYLED-DESCRIPTION, ASSOCIATE, STRUCTURED-LOCATION and STRUCTURED-RESOURCE. We discussed the GROUP parameter (which probably has to be renamed). This allows different properties to be associated with each other — e.g. DESCRIPTION with a STYLED-DESCRIPTION.

The second specification allows many more properties on the VCALENDAR component and adds the COLOR and IMAGE properties. It also defines the DISPLAY parameter — indicating how an image should be used,and the EMAIL parameter for attendees and organizers. There was some discussion on the use of CSS3 names for color ending in general (if not complete) agreement. The issue of tzid on DATE was raised and discussed again — perhaps with less discernable consensus.

3.6.  TC FREEBUSY

We presented an overview of the VPOLL specification, which has not changed much since last time. We then saw a prototype VPOLL client demo illustrating the advantages of integrating a polling system directly with an existing calendaring and scheduling system such as CalDAV.

3.7.  TC IOPTEST

A successful session testing some new features and as ever testing some of the more mature parts of the protocol with new clients and servers. Tested jcal support for clients and servers. This appears to be working very well. Timezones by reference was tested together with the associated CalDAV extensions. Mostly successful with some minor issues to be resolved. Suggests we could move ahead after the resolution of those issues. Some testing was done on the prefer header for WebDAV and on managed attachments. We also tested VPOLL support including VPOLL in JSON. Cyrus presented the CalDAV test suite (again) and provided further assistance in getting it running.

3.8.  TC ISCHEDULE

Discussion on “identity crisis”. Presented 3 scenarios involving Webfinger redirect, iSchedule redirect and iMIP based interaction. Identity crisis not solved but it looks like Webfinger is part of the solution.

3.9.  TC RESOURCE

The session reviewed the work done so far. We had a discussion on possible DAV extensions for Resource discovery. Concentrating on extension of Principal properties to make search more efficient. Digressed into search in general too.

3.10.  TC TASKS

TC-TASKs has made good progress against the original scope and has now prepared two drafts:

Further discussion is required in the areas of task assignment and deadlines / escalations, which will continue to the next Roundtable (XXIX). From the work done to date GAP, SUBSTATE and the PREPARE status need to be revisited based on Roundtable feedback. In addition to this the publication and maintenance of domain specific data (e.g. namespaced reason codes, substates, related-ids etc) to support client customization is to be included in scope. Task time planning (e.g. allocated time, estimated time) will be investigated as extension of scope beyond the current work plan.

3.11.  TC TIMEZONE

Described why we got where we are and presented the current state of the server specification. The specification is now ready for last call at the IETF. Before we try to make progress with that last step we intend trying to engage other groups, for example the ICU and OS or API maintainers. We would like to see other implementations and uses. A discussion followed on some possible extensions to the timezone service and changes to the way timezone data is currently maintained.

3.12.  TC XML

Presented a description of the jCard and jCal formats with examples. jCard and jCal have made good progress through the IETF and are approaching RFC status. Most current issues with the specifications have been resolved and interop testing has shown that the fomat is relatively easy to use. We agreed that TC-XML has achieved its charter and milestones and that we should now shut it down. An Ad Hoc Committee will be set up to explore the remaining issue of calendaring APIs.

3.13.  WORKSHOP — Federated Shared Calendars

The broad topic of federating shared calendars across different services was discussed and explored. Several different use cases exist, some more complex than the others. There was broad interest in continuing to work on this problem, to define use cases, break it down into manageable pieces etc. An Ad Hoc Committee will be set up to continue this work.

3.14.  WORKSHOP — Travel Itineraries and Calendaring

We had a presentation and discussion about how a standards based approach, using iCalendar, could enhance the user experience with planning and managing travel itineraries. We determined that it is important to get involvement from industry experts to determine their needs and the scope of any problems to be solved. We will move forward by continuing with our Ad Hoc Committee, trying to garner interest from outside parties.