Re: URGENT REMINDER: [XCON] Conference Control: Path Forward

> There's actually a 2nd SOAP proposal that I submitted right near the
> deadline that appeared on Jan 3rd:
> http://www.ietf.org/internet-drafts/draft-barnes-xcon-ccmp-00.txt
> 
> This proposal is very preliminary as there's several TBD sections, but I
> think it could be easily merged with Henning's COMP proposal as the
> approaches are quite similar.

That's certainly my intent and hope.

> 1. Same protocol for data manipulation and conference operations.
> 2. Based on a protocol that's already implemented (or needing to be
> implemented for other functionality) by clients. 

Or, possibly, protocol*s*, since some proposals use more than one (SIP 
for event notification, for example).

> 3. Affinity with the data model to reduce the complexity.  
> 
> In considering the 3 protocols on the table (considering Henning's COMP
> and CCMP as the same), I would still come up with a similar analysis as
> that chart 10, which I'll summarize below (and apolgize in advance if
> the formatting is funky):
> 
>                 CCCP       CSCP     CCMP/COMP
>                 --------------------------------------------------------
> Based on XML    Yes         No       No (but WSDL can be derived from
> XML)

I would consider CCMP/COMP as based on XML, in that the on-the-wire 
format is XML.

> 
> Existing        No        Yes(BFCP)  Yes
> protocol
> 
> Event           Yes        Yes (?)    No (plan to use SIP)
> Notification
> Mechanism 
> 
> Compact         No         Yes        No

In general, if XML is used over TLS, TLS will do gzip-style compression, 
probably reducing the packet size footprint considerably.

> 
> Efficient       Yes        Yes        Yes
> 
> Easy to         Yes        Yes        Yes
> Implement 
> 
> 

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon