OMA Instant Messaging Rel 1.0 Requirements with Possible Relevance to IETF Markus Isomäki OMA Issues BoF IETF #62

Objectives and Timeline The objective of OMA SIMPLE IM work is to define a complete Instant Messaging system specification including One-to-one one shot messaging One-to-many one shot messaging Using lists that can be shared with other applications, e.g. PoC or presence One-to-one session-based messaging One-to-many session-based messaging “Chatroom” or messaging conference Used together with other medias, e.g. PoC There is a strong inclination to keep the system components interoperable with IETF protocol specifications SIP MESSAGE, MESSAGE URI list, MSRP, XCAP, XCAP RLS App usage, etc. At the same time there is a strong industry demand for finalizing the system standard in a timely fashion According to the official schedule, the deadline for IM Rel 1.0 is 09/2005 Requirements work mainly done, architecture work ongoing

Instant Messaging Requirements – 1/2 “Store and Forward” support for SIP MESSAGE It must be possible to forward MESSAGEs to a “storage server” when recipient is off-line It must be possible to deliver the stored MESSAGEs to the recipient when she is back on-line It must be possible to notify the sender on the final delivery of the MESSAGE to the recipient Possible relevance to draft-burger-simple-imdn Mimic pager-mode messaging paradigm over session-based transport (needed to circumvent the content size limitations in SIP MESSAGE) It must be possible to indicate in (MSRP) session setup that the session is only used for transfering a single message Recipient behavior implications: open chat window vs. store the content in an inbox, etc. MESSAGE delivery lists Based on draft-sipping-uri-list-message It must be possible to setup a (resource) list for messaging, and use that list also for other services, such as PoC and Presence External reference from a service document to a resource list document It must be possible to define policies whether the recipient is able to see who else received the message

Instant Messaging Requirements – 2/2 Private messages within a multiparty chat conference Requirements similar to draft-niemi-simple-chat Nickname usage within a multiparty chat conference Requirements similar to draft-niemi-simple-chat

Data Manipulation Requirements OMA is also working on XML Document Management (XDM) enabler, which is based on IETF XCAP protocol First release of the XDM enabler has just been finalized Certain requirements were postponed for the second release, as there were no mechanisms to implement them Copying and Moving of XML resources XCAP augmented with WebDAV methods? Authorization for XML resources (e.g. resource lists) It must be possible to give authorize other users than the owner of the XML resource to do operations (GET, PUT, DELETE) on it Resource list extensions Towards vCard? (Network-stored phonebook) Search It must be possible to search e.g. PoC and chat conferences within a certain scope based on various attributes Subject, owner, start time, …