60 likes | 82 Views
Join the design team to discuss & design advanced IM requirements. Proposals include draft IMDN and IM receipts for messaging improvements. Goal is to address delivery status, composing status, content capabilities, and page-mode groups.
E N D
Advanced IM Capabilities Hisham Khartabil
draft-rosenberg-simple-messaging-requirements-01.txt • Found on jdrosen.net or softarmor.com (in the morgue) • Do we want to adopt it as a WG item? • If so: • Needs to be revived • Need to agree on the set of requirements
Requirements • Delivery Status Reporting • draft-burger-simple-imdn-03.txt • draft-khartabil-simple-im-receipts-00.txt • Is-Composing - Done. • Content Capabilities - Done, sort of • Page-Mode Groups - being done in SIPPING • Invitations to Non-Real-Time Sessions
Design Team • Meet Thursday Afternoon Session II to kick off the work • Goal of design team is to discuss and design solutions for the remaining advanced IM requirements • Depending on number of participants, we may work in smaller design teams to meet different requirements
IMDN • 2 proposals • draft-burger-simple-imdn-03.txt • draft-khartabil-simple-im-receipts-00.txt • 1st attempt at merging failed
IMDN Open Issues • Disposition-notification header vs. Receipt-Request header • Do we want aggregated receipts at the B2BUA (exploder). Who decides? • B2BUA reporting it received the IM • What else do we need receipts for besides delivered and read? • Allow more than 1 receipt per IM (see above) • Do we keep state at the client?