XCON Notes

 

Agenda

6 confirmed and 1 maybe intend to go to Malta.

Work Item status – data model frozen

Event package is done

 

 

CCMP

Simon presented

CCMP is based on REST and not SOAP

Implemented CCMP in meetecho. The implementation was presented

Dan York– did you bench mark your experience with conference manipulation since tried different protocols.

Simon – It is in premature stage for CCMP to give a benchmark

From IETF 72 – added XSD data model (thanks to Oscar)

There are 5 open issues.

  1. Additional data required in data model.
  2. Only discrete elements  have request response propose add support to access other elements
  3. The version work fine but is not  complete – need feedback both  to review and suggest features

Theo read not look restful.

Marry – the document is not 100% rest approach. There will be more work to specify transactions

Simon – not to have ccmp as http but to differentiate.

Theo – use Soap and not HTTP if not restful

Mary – want to keep less restful.

 Dan – the danger you run is that if it want it to be adopted is that it is between rest and soap and that may alienate Soap or Rest program

Simon – it is not if it is rest , it is just that it is not tied to HTTP enabling using separately if there will be changed

Dan – need to explain the motivation

Lisa – Rest is not TCP, it is stateless. It should use HTTP echo system. The error messages are http.

Simon – want to have error codes.

Theo – do not send errors in 200

Mary – in term of http we are not broken.

 

Simon ask to comment on CCMP and not on the transport before discussing the transport

 

  1. Define role based acces control
  2. Manage notification, couple of options

Use SIP notifications

HTTP “call back”

Mixture of the above

BOSH 

XMPP

Plain sockets

 

Theo – use hybrid approach.

Adam – why are we adding work, there is event package

Mary- there are other clients.

Adam – suggest that notification will be in the protocol used to access  the server.

 

Way forward need comments

Adam – read the document and provide feedback

 

 

 

XCON chat

The new functionality needed for text chat

XCON is chat protocol agnostic.

Issues:

Nicknames – suggest to scope nicknames unique within a conference system

Look at mechanisms in other protocols.

 

Need to look at logging, history, etc.,

Need WG feedback

 

Dan York read the document- not clear if you are creating an architecture that IM clients connect to the server. Not addressing the media. Who will use it.

Mary: you get it for free to MSRP

Dan – who will use XCON

Alan – Avaya is looking at it

Dan – chat will be added to the conference control in XCON as another media

Adam, Mary, Simon talked about the motivation to support the CCMP