%ents; ]>
iCal Envelope A simple mechanism to transport iCal data over the jabber protocol &LEGALNOTICE; 0097 Deferred Standards Track Standards Council XEP-0030 ice Justin Kirby justin@openaether.org zion@openaether.org 0.1 2003-06-10 jk Initial draft (jk).

This will be the first, in a series (hopefully), of specifications which will define how to utilize GroupWare over jabber. While GroupWare is extremely broad subject, this document will focus on iCaliCalendar http://www.ietf.org/html.charters/calsch-charter.html. Since iCal is a defined standard which is transport-agnostic, all this document will do is define how iCal will be transported over Jabber.

What this document will cover:

Before sending iCal messages to a jabber entity, a disco query should be performed in order to discover whether or not that entity supports iCal Envelopes.

]]>

If the jabber entity supports iCal Envelopes, then it MUST respond with http://jabber.org/protocol/gw/ical as a feature.

]]>

To send iCal, all that needs to be done is wrap the iCal data in a ical element. All iCal data sent MUST be in the ical element in the http://jabber.org/protocol/gw/ical namespace. The CDATA section is optional and is used here simply to make it readable.

Other than wrapping iCal in XML, the data itself MUST follow the ietf 2445 RFC2445 RFC http://www.ietf.org/rfc/rfc2445.txt

Protocol gathering every Tuesday at 22:00 UTC located in foundation@conference.jabber.org BEGIN:VCALENDAR PRODID:-//Ximian//NONSGML Evolution Calendar//EN VERSION:2.0 METHOD:PUBLISH BEGIN:VEVENT UID:20030418T014238Z-5727-500-1-2@oadev DTSTAMP:20030418T014238Z DTSTART:20030422T220000Z DTEND:20030422T230000Z SEQUENCE:3 SUMMARY:XEPs LOCATION:foundation@conference.jabber.org CATEGORIES:XSF CLASS:PUBLIC TRANSP:OPAQUE LAST-MODIFIED:20030418T014527Z DESCRIPTION:discuss jeps RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU END:VEVENT END:VCALENDAR ]]>

As a convenience for users which do not have ical support the sender may want to place human readable information in the <body/> for the receiver to read.

When a client receives a message containing iCal data there are a few options which are considered reasonable.

Per the jabber standard, any message received which the entity does not understand CAN be ignored. This behavior is expected of clients which have not implemenred this jep.

The entity may display the ical data as text to the user, this is not recommended for obvious reasons. However, some data is better than no data, so this is considered preferable to just dropping the message stanza.

Most users today have some form of calendaring functionality available to them which supports the iCal standard. Simply redirecting the received ical to the user's preferred calendaring application would be the ideal scenario.

This document requires no interaction with the Internet Assigned Numbers Authority (IANA)

The 'http://jabber.org/protocol/gw/ical' namespace is registered with the XMPP Registrar as a result of this document.

TBD

TBD

The following are issues that need to be resolved