From July 2008:
The iSchedule Technical Committee will develop a proposal for the Internet Scheduling Protocol (iSchedule) which will specify a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to the Hypertext Transfer Protocol (HTTP).
March 8, 2010: The first draft proposal for iSchedule is published by the Internet Engineering Task Force.
Calendar standards folks, feel free to explain the significance of this in the comments to this post!
iSchedule provides a secure interoperable cross-domain scheduling solution transparent to end users.
ReplyDeleteiSchedule is independent of the calendar access protocol used by calendar client applications as well as the calendar store used by the calendar services.
iSchedule specifies how a calendar service (iSchedule Sender) can discover and transmit scheduling messages (iTIP messages) to the calendar service (iSchedule Receiver) of another domain.
iSchedule allows synchronous search for busy time information (a.k.a., free/busy lookups) which weren't possible with solutions that relied on an email-based transport.
iSchedule leverages the DomainKeys Identified Mail (DKIM) service to provide end-to-end domain-level authentication based on message content that doesn't require prior arrangement between domains.
Motivations for this work can be found in the draft: http://tools.ietf.org/html/draft-desruisseaux-ischedule-01#section-1.1
Discussion on iSchedule is taking place on the following mailing: list https://www.ietf.org/mailman/listinfo/ischedule
Bernard Desruisseaux, co-author of iSchedule and chair of TC iSchedule at CalConnect
Great summary Bernard!
ReplyDelete