[XCON] New version of CSCP draft
"Oscar Novo \(JO/LMF\)" <oscar.novo@ericsson.com> Wed, 14 December 2005 07:46 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmRLV-0000v9-Mz; Wed, 14 Dec 2005 02:46:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmRLU-0000tF-Lj for xcon@megatron.ietf.org; Wed, 14 Dec 2005 02:46:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12254 for <xcon@ietf.org>; Wed, 14 Dec 2005 02:45:43 -0500 (EST)
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmRMY-0001mv-J0 for xcon@ietf.org; Wed, 14 Dec 2005 02:47:52 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 04C294F004F; Wed, 14 Dec 2005 08:46:33 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Dec 2005 08:46:29 +0100
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Dec 2005 08:46:21 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Dec 2005 08:46:20 +0100
Message-ID: <A91F30A632473A47B40C18D2B107CA6F01B5276F@esealmw105.eemea.ericsson.se>
Thread-Topic: New version of CSCP draft
Thread-Index: AcYAbz2Ce/P5lmxiEdq0TwARJEEJ/AAEskTw
From: "Oscar Novo (JO/LMF)" <oscar.novo@ericsson.com>
To: Cullen Jennings <fluffy@cisco.com>, Adam Roach <adam@nostrum.com>, XCON-IETF <xcon@ietf.org>, "Gonzalo Camarillo (JO/LMF)" <gonzalo.camarillo@ericsson.com>, ajohnston@tello.com
X-OriginalArrivalTime: 14 Dec 2005 07:46:21.0685 (UTC) FILETIME=[79DC0A50:01C60082]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [XCON] New version of CSCP draft
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org
Hello, We would like to notify the new version of the CSCP draft. Until it appears in the archives, you can fetch it from: http://users.piuha.net/gonzalo/temp/draft-jennings-xcon-cscp-02.txt CSCP is an extension of the BFCP. In this version we have aligned the CSCP draft with the "Binary Floor Control Protocol (BFCP)" draft and the "Connection Establishment in the Binary Floor Control Protocol (BFCP)" draft. Here's an overall summary of the changes: - We have aligned the CSCP draft with the "Binary Floor Control Protocol (BFCP)" draft and the "Connection Establishment in the Binary Floor Control Protocol (BFCP)" draft - Definition and explanation of the main errors of the CSCP protocol. - Added a new section 6 (Server Behaviour) - In Section 7 (example) added a new example and additional text explaining the example - Updated sections 9 (IANA Considerations) and section 10 (Security Considerations) CSCP is not done yet. There are changes that have to be incorporated in the following versions: - Definition of new operations (creation of a conference, termination of a conference, etc...) - Definition of new error values of the protocol - Better explanation of some operations (Adding Elements, etc...) - Discussion about the need of the synchronous "query" mechanism in the protocol But we believe it's enough to understand the propose of this protocol and to discuss in the mailing list if this protocol is a good option. The strengths of CSCP are: - CSCP is based on BFCP, reducing the number of protocols required to be supported by clients - It can modify the "variable" part data and the "common" part data using the same operations. - Easy to implement - Compact and Efficient Regards, Oscar _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon
- [XCON] New version of CSCP draft Oscar Novo (JO/LMF)
- Re: [XCON] New version of CSCP draft Alan Johnston
- RE: [XCON] New version of CSCP draft Umesh.Chandra
- Re: [XCON] New version of CSCP draft Gonzalo Camarillo
- [XCON] New version of CSCP draft Oscar Novo (JO/LMF)
- RE: [XCON] New version of CSCP draft Even, Roni
- RE: [XCON] New version of CSCP draft Oscar Novo (JO/LMF)
- RE: [XCON] New version of CSCP draft Even, Roni
- RE: [XCON] New version of CSCP draft Oscar Novo (JO/LMF)