RE: URGENT REMINDER: [XCON] Conference Control: Path Forward
"Mary Barnes" <mary.barnes@nortel.com> Sat, 14 January 2006 00:39 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 1ExZSH-0008NQ-Lb; Fri, 13 Jan 2006 19:39:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExZSG-0008NI-Cv for xcon@megatron.ietf.org; Fri, 13 Jan 2006 19:39: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 TAA26219 for <xcon@ietf.org>; Fri, 13 Jan 2006 19:38:18 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56] helo=zcars04e.nortel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ExZZe-0004Qa-4x for xcon@ietf.org; Fri, 13 Jan 2006 19:47:20 -0500
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id k0E0Z8W05604; Fri, 13 Jan 2006 19:35:09 -0500 (EST)
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
Subject: RE: URGENT REMINDER: [XCON] Conference Control: Path Forward
Date: Fri, 13 Jan 2006 18:38:47 -0600
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D564@zrc2hxm1.corp.nortel.com>
Thread-Topic: URGENT REMINDER: [XCON] Conference Control: Path Forward
Thread-Index: AcX0anPl0RYOuJqsTbW+Y3nLVXMSEQkMRL+wAAE4cJA=
From: Mary Barnes <mary.barnes@nortel.com>
To: Sean Olson <Sean.Olson@microsoft.com>, Adam Roach <adam@estacado.net>, Adam Roach <adam@nostrum.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: quoted-printable
Cc: XCON-IETF <xcon@ietf.org>
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
Sean, Thanks for re-starting this discussion. 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. I think what we should be doing now is debating the advantages and disadvantages of each of the proposals. I had a chart in the package I presented at IETF-64 during the framework discussion (chart 10): http://www.softarmor.com/xcon/meets/ietf64/agenda.pl This evaluation looked at some of the protocol motherhood statements and I tried to work through a more detailed set of requirements, but kept coming back to fundamentals such as: 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. 3. Affinity with the data model to reduce the complexity. I do think one of the difficulties is that we need to agree fundamental requirements or priority of some of the motherhood requirements to see which protocol is most suitable. 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) Existing No Yes(BFCP) Yes protocol Event Yes Yes (?) No (plan to use SIP) Notification Mechanism Compact No Yes No Efficient Yes Yes Yes Easy to Yes Yes Yes Implement And, I'm afraid this doesn't help much. I think any of the approaches could work. Of course, CCCP has been proven to work in one implementation, but SOAP has been successfully implemented in many implementations, albeit not for this application. And, I think the compact nature of CSCP might be appealing to the wireless folks. Obviously, my preference is for the COMP/CCMP approach. Mary -----Original Message----- From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Sean Olson Sent: Friday, January 13, 2006 5:52 PM To: Adam Roach; Adam Roach Cc: XCON-IETF Subject: RE: URGENT REMINDER: [XCON] Conference Control: Path Forward I haven't seen any discussion so far about the protocol submissions: - Henning's SOAP proposal (http://www.cs.columbia.edu/sip/draft/comp/draft-schulzrinne-xcon-comp-0 0.html) - Cullen/Oscar's CSCP proposal (http://users.piuha.net/gonzalo/temp/draft-jennings-xcon-cscp-02.txt) - Our CCCP proposal (http://tools.ietf.org/wg/xcon/draft-levin-xcon-cccp-04.txt) What are the next steps for evaluating these submissions? -----Original Message----- From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Adam Roach Sent: Monday, November 28, 2005 2:22 PM To: Adam Roach Cc: XCON-IETF Subject: URGENT REMINDER: [XCON] Conference Control: Path Forward [as chair] If anyone in the working group cares about the protocol we end up selecting for conference control -- or, indeed, finishing our work at all -- they are strongly advised to participate in this conversation. If we can't get any participation around our deliverables, we really have no choice but to shut the working group down. /a Adam Roach wrote: > [as chair] > > In Vancouver, the XCON chairs outlined a process by which we would > attempt to meet our proposed milestones. This message summarizes that > process, as amended by the input we received from the XCON participants. > > 1. Proposals for candidates for the Conference Control Protocol (CCP) > must be submitted in internet-draft format no later than December > 31st, 2005. The draft does not need to be complete; however, there > must be sufficient detail to make clear how the proposed protocol > would be used to modify information in both the Common Conference > Information and Conference Template. (See > draft-ietf-xcon-framework for definitions). > > 2. All protocols to be considered additionally need a brief message > from an author and/or proponent of the corresponding draft that > explains the design decisions taken in the design of the protocol, > as well as a summary of strengths and drawbacks of the approach. > Such proponents should contact the XCON chairs to coordinate. > * Such proponents should discuss implementation lessons, if > available, around using their proposed protocol to modify > the Common Conference Information. > * Separately, such proponents should additionally discuss > implementation lessons, if available, around using their > proposed protocol to modify the Conference Template. > > 3. Starting in early January, the chairs will call for discussion on > the mailing list to gauge the overall direction the working group > wishes to proceed. > > 4. Between now and January, interested parties should discuss their > requirements around the CCP on the mailing list. These discussions > should assist in coming to consensus on the CCP that XCON will use. > > Hopefully, the result of the January discussions will resolve to a > single approach (either by selection of one of the proposals or by > combining one or more of them into a unified proposal). > > /a > > _______________________________________________ > XCON mailing list > XCON@ietf.org > https://www1.ietf.org/mailman/listinfo/xcon > _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon
- RE: URGENT REMINDER: [XCON] Conference Control: P… Mary Barnes
- Re: URGENT REMINDER: [XCON] Conference Control: P… Adam Roach
- Re: URGENT REMINDER: [XCON] Conference Control: P… Joerg Ott
- RE: URGENT REMINDER: [XCON] Conference Control: P… Sean Olson
- RE: URGENT REMINDER: [XCON] Conference Control: P… Mary Barnes
- Re: URGENT REMINDER: [XCON] Conference Control: P… Henning Schulzrinne
- Re: URGENT REMINDER: [XCON] Conference Control: P… Gonzalo Camarillo
- Re: URGENT REMINDER: [XCON] Conference Control: P… Henning Schulzrinne
- RE: URGENT REMINDER: [XCON] Conference Control: P… Sean Olson