Re: [XCON] New draft on manipulating state in a conference

[Cullen Jennings <fluffy at cisco.com>]

I started thinking about something separate that had the semantics of more
or less the current CSCP but was not based on BFCP. I realized that, other
than how the bits were arranged, it was more or less the same as BFCP. It
seem like the clients would much rather implement one thing, have less
streams to set up etc. I guess it is sort f apple pie to reuse BFCP if we
can - the question is, how much is reusing it warping CSCP. What would we do
differently in CSCP if we were not basing on BFCP at all? It's well worth
talking about - I'm not sure.


On 2/14/05 6:11 AM, "Chris Boulton" <cboulton at ubiquity.net> wrote:

> Hi Cullen ­ I actually quite like this idea, it certainly has benefits.  One
> concern I have is the ?bending¹ of BFCP to fit this solution.  It¹s almost
> like we are trying to push a square peg into a round hole.  One idea might be
> to spit BFCP into a core Binary Control Protocol (BCP).  The floor control and
> CSCP would just then be uses of the core protocol (one for the purists ;-).
> What do you think?
>  
> Chris.
>    
>  
> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy at cisco.com]
> Sent: 13 February 2005 01:46
> To: XCON-IETF
> Cc: Adam Roach
> Subject: [XCON] New draft on manipulating state in a conference
>  
> 
> Adam and I put together a draft as a trial balloon to get an idea of what
> folks think. Until it shows up in the archives, you can find it at
> 
> http://scm.sipfoundry.org/rep/ietf-drafts/fluffy/draft-jennings-xcon-cscp-00.h
> tml
> 
> (there is a .txt version too)
> 
> Abstract is
> 
>    Conference State Control Protocol (CSCP) is a means to modify the
>    state in a conference service.  It extends the Binary Floor Control
>    Protocol and adds commands to get, set, add, and delete fields in the
>    conference state.
> 
> 
> This email and any attached files are confidential and copyright protected.
> If you are not the addressee, any dissemination, distribution or copying of
> this communication is strictly prohibited.  Unless otherwise expressly agreed
> in writing, nothing stated in this communication shall be legally binding.
> 



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