100 likes | 104 Views
This document discusses the integration of text-based "chat" as an alternative media type for the XCON conferencing framework, addressing chatroom discovery, nicknames, logging, history, and indicating alternate venues.
E N D
XCON WGIETF-70 Meeting Instant Messaging Sessions with a Centralized Conferencing (XCON) Systemdraft-boulton-xcon-session-chat-00 Authors: Chris Boulton (cboulton@avaya.com) Mary Barnes (mary.barnes@nortel.com)
Contents • Introduction • Background • Basic Model • Changes since last version • Issues • Way Forward • Comments/Questions
Introduction - General • XCON Conference Framework complete as an XCON WG item • Understandably discussions have primarily focused on voice/video conferences • Framework introduces generic topics applicable to multiple signalling protocols and media types • Conference Object • Cloning Tree Model • Text-based “chat” as an alternative media type provides a valid proof point for the XCON Framework • Augments the work in SIMPLE WG: draft-ietf-simple-chat • Intent is to have no impact on existing IM protocols
Introduction - Chat • Chat is a popular application and a good use case for an alternative conferencing media type • IM Conferencing (“Chat”) has an important role to play in future XCON architectures • In conjunction with other media (e.g. Voice, Video) • Standalone (e.g. Chat Rooms) • Existing chat systems have a broad range of features, from very simple to fairly complex • Initial evaluation highlights need for some enhancements to data model to support chat: draft-roach-xcon-chatroom-analysis-00
Document Background • This document replaces the draft-boulton-xcon-msrp-conferencing-05, which had originally focused on MSRP (-04 and earlier) • Rfcdiff provides a decent delta between the two documents
IM Client IM Client IM Client IM Client Basic Model Conferencing System
Changes since draft-boulton-xcon-msrp-conferencing-05 • Incorporated some of the concepts identified in chatroom analysis draft into the existing sections: • Chatroom discovery based on blueprints • Added new section to address some of the additional capabilities as identified in draft-roach-xcon-chatroom-analysis-00: • Nicknames • Logging • History • Indicating alternate venue • Removed additional MSRP details no applicable to this more general document. • Updated references
Document Issues/discussion • How much more detail needs to be added to addressing additional chatroom functionality? • Current version addresses the “top-runners”: Nicknames, History, Logging, Alternate Venue • If chatroom-analysis draft is not planned to be progressed, should we add more of the material as background to this document? • However, once protocol details get added to this document, it could get quite large.
Way Forward • Need WG feedback • Update document based on feedback: • Editorial nits • Clarification around scope per issues discussion • Update details as the protocol document evolves • Put in the queue for adding to XCON charter as other WG deliverables mature (e.g., protocol document).