XCON WGIETF-73 Meeting

Instant Messaging Sessions with a Centralized Conferencing (XCON) System

draft-boulton-xcon-session-chat-02

Authors: Chris Boulton (cboulton@avaya.com) Mary Barnes (mary.barnes@nortel.com)

Overview• XCON Conference Framework Done

– Primarily focused on voice/video conferences

• XCON Protocol well underway• Framework introduces generic elements 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:– In conjunction with other media (e.g. Voice, Video)– Standalone (e.g. Chat Rooms)

• Independent of the work in SIMPLE WG: draft-ietf-simple-chat

• Protocol agnostic: Intent is to have no impact on existing IM/chat protocols

IM Client

IM Client

IM Client

IM ClientConferencing

System

Basic Model

Conferencing System is point of Inter-working for various IM chat clients – protocol agnostic

Current Status

• -02 updated to reflect move of detailed call flows to draft-barnes-xcon-examples

• Current focus of document is on the advanced operations. – Nicknames – Logging– History– Alternate Venue

Issues/Discussion

1. Suggestion to focus on ensuring applicability to other chat solutions (e.g., XMPP) rather than just MSRP

– Proposal: ensure reference to chat protocol is fairly generic with examples such as XMPP (along with MSRP).

– Consider applicability of currently proposed inter-working (e.g., XMPP-MSRP) • Intent (of this doc) is that the conferencing server is a natural

inter-working point

2. Suggestion to change terminology:• XCON IM Sessions -> XCON Group chat

Issues/Discussion – Nicknames

Proposal: Rather than define (in this WG) a very general Nickname mechanism, propose to scope nicknames unique within a conferencing system

• Nickname element is already defined in XCON data model

Suggest conferencing system allocates nicknames: – When creating a user for XCON, add the option to specify a

"nickname“ or infer that the inclusion of a proposed nickname implies a request for a nickname.

– (In the future) IF the conferencing client has other mechanisms for getting a "nickname", conferencing system can handle checks for consistency.

– In the case that the client is also using MSRP, client could just use the "nickname" provided when they setup the chat using XCON (when they create or update a userId)

Additional considerations

1. Nicknames:• Look into nickname mechanisms of other protocols, such as

XMPP, for consistency to minimize any inter-working problems• Consider impact to call signaling protocols that might have

nickname mechanisms – e.g., if a mechanism was added later to SIP.

2. Consider approaches for other features: Logging, History, Alternate Venue

• Again considering mechanisms used by other chat protocols – maximizing potential for inter-working is key.

Way Forward

• Need WG feedback

• Update document based on feedback

• Add details to chat call flows on use of Nicknames, since no normative protocol changes.

ANY COMMENTS/Questions?