110 likes | 237 Views
SIMPLE WG IETF-68 Meeting. Centralized Conferencing (XCON) using the Message Session Relay Protocol (MSRP) draft-boulton-xcon-msrp-conferencing-04. Editors: Chris Boulton ( cboulton@ubiquitysoftware.com) Mary Barnes (mary.barnes@nortel.com). Contents. Background Overview Scope
E N D
SIMPLE WGIETF-68 Meeting Centralized Conferencing (XCON) using the Message Session Relay Protocol (MSRP)draft-boulton-xcon-msrp-conferencing-04 Editors: Chris Boulton (cboulton@ubiquitysoftware.com) Mary Barnes (mary.barnes@nortel.com)
Contents • Background • Overview • Scope • Relation to draft-niemi-simple-chat • Issues/Discussion • Way Forward
Background • Topic discussed in the past in the XCON WG: • 02 presented at IETF-64 as a ‘Work-In-Progress’ • Introduced the concept of an XCON Conference Object with MSRP as the media type • Discussed on Tuesday, March 20th – charts in the archives (RAI – XCON – MSRP Conferencing) https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=68
Overview • XCON Conference Framework almost 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 • MSRP as an alternative media type provides a valid proof point for the XCON Framework
Overview • MSRP connection to Conference System is used to send messages to a Conference Instance
Overview • MSRP SEND message is then distributed to relevant participants of the Conference Instance
Scope • Document in ‘no-way’ impacts the core MSRP protocol • Simply applies XCON Framework principles • Document complements draft-niemi-simple-chat-06 by focusing on the framework aspects rather than the MRSP specific details. • Nicknames aren’t addressed as they’re deemed a more general problem.
Differences between boulton-xcon-msrp-conferencing versus draft-niemi-simple-chat
Issues/discussion • Should a more general Nickname mechanism be developed ? Or, is a MSRP specific solution (and thus later other solutions such as for XCON) a better path?
Way Forward • Plans are to update document based on feedback: • Editorial nits • Clarification around scope per issues discussion in XCON on March 20th: • Put forth as a more general text based solution, with MSRP used as an example. • Put in more text on fundamental chat functionality (implied by requirements which are met). • This document doesn’t contradict niemi-simple-chat, but complements, thus both docs can be progressed in parallel