Minutes Minutes CCaallCCoonnnneecctt T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M Volume 5, Issue 3 October 2012 From the Executive Director Dear Members, • Calendaring futures and CalConnect • CalConnect XXVII, June 3-7, 2013, directions University of Wisconsin, Madison, CalConnect events generally consist of Wisconsin two parts: the first half of the week is • Internationalization/Localization for interoperability testing, and the last half calendaring • CalConnect XXVIII, Autumn, 2013, is the Roundtable Technical data TBD Conference. At CalConnect XXV in Zurich, our second full CalConnect • Best practices Based on the success of this event event in Europe, for publishing and last year’s European event in nearly everyone iCalendar data Innovation Prague, we are looking forward to who participated to ensure CalConnect in the optimum interoperability XXVIII being interoperability hosted in Europe, • BOF on VTODOs Tests testing stayed for and are soliciting the Roundtable, • BOF on Consensus Scheduling offers to host the Events and we had a few additional event from our participants, making a total of 26 at the Following the BOF on VTODOs, a European members. We hope to be Roundtable, of which 17 were VTODO Ad Hoc able to announce the week, city, and European, overall representing 11 Committee was host by our next event at Oracle in late members and 5 observers (prospective formed to January. examine members). Members requirements and CalConnect’s European events are ongoing work on restructured to move the formal VTODOs and recommend future technical committee sessions to the activity in this area to CalConnect. The afternoon (to allow remote attendance Ad Hoc committee will report out at Dave Thewlis from North America), and special Roundtable XXVI. symposia and BOFs (birds of a feather sessions) are offered on Thursday and More detail about the event may be Friday mornings. The special offerings found at Report on Roundtable XXV. this time were: Next CalConnect events: • Improving the web calendaring • CalConnect XXVI, January 28- experience for end users February 1, 2013, Oracle, Santa Clara, California CalConnect XXVI Oracle Corporation Santa Clara, California Interoperability Test Event January 28 - 30 Roundtable XXVI January 30 - February 1 Inside this Minutes: • Executive Director’s Letter – page 1 New Members Welcome – page 5 • Interop Report – page 2 CalConnect XXV photos – page 6 • Tech Committees Summaries – pages 3 & 4 About CalConnect – page 7 M i n u t e s Page 2 C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012 Interop Report DaviCal Problems with content type Oracle (Oracle Communications Redirections causing issues Calendar Server) Lack of support for required A number of those present properties concentrated on iSchedule with DKIM Errors in report formats The testing event drew 22 on-site and discovery. Testing was fairly participants, 14 from Europe, intensive and participants found a As ever, the benefits of working representing the following number of issues with the draft together in one room to discover and organizations and products: protocol as well as with server fix interoperability issues were implementations. A number of servers enormous. Most of the participants Apple (iCal Server, iCal Client, managed to connect successfully and test remotely during the year, iCloud Server, iCloud Outlook interact with each other, handling however, these sessions provide a Client, iOS 6) freebusy requests and meeting much more productive environment. Bedework invitations and replies. Many participants were staying for the following Roundtable and took the Testing of sharing and notifications CalDAV-Sync and CardDAV- opportunity to continue testing. Sync also took place with a generally successful outcome for all. Bugs in Mike Douglass, Senior Systems Evolution plugin the client and server software were Programmer, Communication & EGroupware found and rectified when possible. Collaboration Technologies at RPI, served as CalConnect Interoperability emClient Discovery was also a hot topic and Test Event Manager. there were a number of issues Google discovered in the current use of .well- Kerio Technologies known and SRV records. Some CalConnect XXVI participants also tested the Brief and Mozilla Prefer header. Oracle Corporation SabreDAV In addition, many issues surfaced Santa Clara, California Zimbra when participants tested the basic Interoperability Test Event CalDAV and CardDAV access In addition, the following January 28 - 30 protocols. The kinds of issues seen organizations/products participated remotely: were: Roundtable XXVI January 30 - February 1 AOL (AOL Calendar Server) Misreporting of missing DAV properties CMU (Cyrus Calendar Server) About CalConnect Minutes Issued after each CalConnect Roundtable, this newsletter provides highlights of those gatherings and links to more in-depth coverage on the CalConnect web site. You will also find links to new Technical Committee Reports. This is also a source for details on upcoming CalConnect meetings and conferences. To subscribe to CalConnect Minutes send an e-mail to [email protected] and put "Subscribe " in the subject line. M i n u t e s Page 3 C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012 Tech Committee Summaries – Roundtable XXV means to do that, in consultation with incorporated into the next version of the Internet Engineering Task Force the draft. Testing will continue to (IETF). verify that reliable levels of interoperability are achievable. TC-Eventpub The Committee will next progress the The Committee presented the new specification at the IETF. TC-AutoDiscovery properties: styled descriptions (aka The Committee presented the "rich text"), structured location, TC-Resource motivation behind autodiscovery in structured resource, and participants. The TC presented information about addition to introducing the technical They discussed some implications the latest version of the Committee’s solution itself to all CalConnect for CalDAVsize of the property, calendar resource specification. attendees. Members then went allowing suppression of rich text, They have moved to a new model, through open questions that need to language negotiation—and defining an “objectClass” that be addressed and collected described how Participants and represents a schedulable entity with feedback. The next steps are locations could refer to a vcard and a set of attributes that can be added continuing the standardization about the overall requirement to to any vCard to indicate how process and encouraging early search and index. It was noted that scheduling will take place with the implementations of the autodiscovery Structured location has superseded entity that the vCard represents. draft. TC participants believe that the earlier venue effort. Structured Next steps are to take this work to they will get some client support resources builds upon the work of the IETF for further discussion and soon and anticipate being ready for TC-Resource. The value could be to consider possible enhancements testing by the next interoperability URI, with the same syntax as to CalDAV to provide a richer testing event in January 2013. Structured location. Next steps resource scheduling experience include finishing the IETF RFC draft there. TC-CalDAV and starting on implementations. The TC discussed managed TC-Timezone attachments, sharing and TC-Freebusy The Committee presented a notifications and the prefer header. The TC had a lively discussion of the description of the timezone service On managed attachments, the group proposed VPOLL specification, as presently defined and discussed the issue of what limits drilling down into some key details of implemented. The intent is to try to a server should advertise and how a the specification. The group hopes to have systems treat timezones as client should react to those, as continue development of a full data rather than system components. well as how they would handle the specification and encourage more Participants talked about the case of attendees being able to implementations, particularly from possible future role of a timezone add attachments themselves. The clients. They also discussed the service and what, if any, were latter option will need follow- “reverse” poll idea as it pertains to the implications of a JSON iCalendar up discussion and specification by booking systems. representation on such a service. They presented the current state of the TC. For sharing, the Committee TC-iSchedule the draft and the implementations. discussed the current sharing draft Members presented an overview of and how it might be extended to the iSchedule protocol including the The TC felt it was clear they should facilitate some “public events” style new DKIM security pieces that the advertise the Committee’s services sharing modes, as well as per-event TC has been working on. Results on the CalConnect site so that others sharing. On prefer, they discussed from the successful interoperability can test against them. They the issue of whether servers need to event were discussed. Several indicated how much timezone related indicate to clients that the prefer issues found during testing were data, such as borders, aliases, and behavior was triggered, and settled discussed and solutions proposed even the names themselves, are on using the Vary header as a and agreed upon, and will be politically sensitive. (continued) M i n u t e s Page 4 C a l C o n n e c t T H E C A L E N D A R I N G A N D S C H E D U L I N G C O N S O R T I U M October 2012 Tech Committee Summaries – Roundtable XXV (continued) Continued from Page 3 – A higher priority, however, is to handle those types that were forward.