tag:blogger.com,1999:blog-13722520.post7879920387475141122..comments2024-01-23T17:05:43.163-08:00Comments on Calendar Swamp: iSchedule draft published at the IETFScott Macehttp://www.blogger.com/profile/01831862884367555570noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13722520.post-8225531331600738392010-03-28T02:07:31.654-07:002010-03-28T02:07:31.654-07:00Great summary Bernard!Great summary Bernard!Bryan Otishttp://www.intand.comnoreply@blogger.comtag:blogger.com,1999:blog-13722520.post-24325150488666935942010-03-24T10:39:27.532-07:002010-03-24T10:39:27.532-07:00iSchedule provides a secure interoperable cross-do...iSchedule provides a secure interoperable cross-domain scheduling solution transparent to end users.<br /><br />iSchedule is independent of the calendar access protocol used by calendar client applications as well as the calendar store used by the calendar services.<br /><br />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.<br /><br />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.<br /><br />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.<br /><br />Motivations for this work can be found in the draft: http://tools.ietf.org/html/draft-desruisseaux-ischedule-01#section-1.1<br /><br />Discussion on iSchedule is taking place on the following mailing: list https://www.ietf.org/mailman/listinfo/ischedule<br /><br />Bernard Desruisseaux, co-author of iSchedule and chair of TC iSchedule at CalConnectBernard Desruisseauxhttps://www.blogger.com/profile/12970454492364562645noreply@blogger.com