AW: [XCON] A killing argument for SOAP-based Web ServicesapproachforXCON
"Leis, Peter" <peter.leis@siemens.com> Thu, 09 March 2006 13:01 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHKlL-0002oW-3F; Thu, 09 Mar 2006 08:01:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHKlK-0002oR-8W for xcon@ietf.org; Thu, 09 Mar 2006 08:01:02 -0500
Received: from lizzard.sbs.de ([194.138.37.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHKlJ-0000ja-Q8 for xcon@ietf.org; Thu, 09 Mar 2006 08:01:02 -0500
Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id k29D10fk014434; Thu, 9 Mar 2006 14:01:00 +0100
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id k29D10ua023264; Thu, 9 Mar 2006 14:01:00 +0100
Received: from MCHP7I5A.ww002.siemens.net ([139.25.131.136]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Mar 2006 14:00:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [XCON] A killing argument for SOAP-based Web ServicesapproachforXCON
Date: Thu, 09 Mar 2006 14:00:57 +0100
Message-ID: <784A66466728424D93027C59B6478B9E7782C6@MCHP7I5A.ww002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [XCON] A killing argument for SOAP-based Web ServicesapproachforXCON
Thread-Index: AcZDG3QKMaSCL4oDRl2La0bjfo4XfAATCgFQAAHK8pAAAc0qgAAArthA
From: "Leis, Peter" <peter.leis@siemens.com>
To: XCON-IETF <xcon@ietf.org>
X-OriginalArrivalTime: 09 Mar 2006 13:00:58.0143 (UTC) FILETIME=[8237B2F0:01C64379]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc:
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>
Errors-To: xcon-bounces@ietf.org
hello Oscar, CPCP was part of the early versions of 3GPP TS 24.147 in Release-6. However, due to its immaturity CPCP was scratched from Release 6 in November 2004 when Release 6 was frozen. For Rel-7 the situation with regards to CPCP has not changed, it is not part of TS 24.147. regards Peter > -----Ursprüngliche Nachricht----- > Von: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com] > Gesendet: Donnerstag, 9. März 2006 13:52 > An: Leis, Peter > Betreff: RE: [XCON] A killing argument for SOAP-based Web > ServicesapproachforXCON > > Hello Peter, > > I am not an expert in 3GPP but just as an example: > > TS 24.147 document, section "A.3.6 Conference creation with > CPCP" date 2004-09 (Release 6). > > This documentation is referring to > draft-ietf-xcon-cpcp-xcap-00 one of the protocols proposed in > the past by XCON. > > That's true in Rel-7 it doesn't appear because they decided > to remove it from the specifications. > > O. > > -----Original Message----- > From: Leis, Peter [mailto:peter.leis@siemens.com] > Sent: 9. maaliskuuta 2006 13:55 > To: XCON-IETF > Subject: AW: [XCON] A killing argument for SOAP-based Web > ServicesapproachforXCON > > hello, > > 3GPP does _NOT_ refer to CPCP as "conference policy control > protocol" in its specs for conferencing in Rel-6. > Even in Rel-7 the protocol to use for conferenc policy > control is for further study. > > regards > Peter > > ________________________________ > > Von: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com] > Gesendet: Donnerstag, 9. März 2006 12:08 > An: Orit Levin; XCON-IETF > Betreff: RE: [XCON] A killing argument for SOAP-based > Web Services approachforXCON > > > Hi Orit, > > If you take a look the one year old 3GPP > specifications, you can see most of them defined the CPCP > protocol as the "conference control protocol" for XCON. If > Parley X 2.0 /ETSI is using SOAP in their specifications is > not enough reason (at least for me ) to discard the other proposals. > > Oscar > > ________________________________ > > From: Orit Levin [mailto:oritl@microsoft.com] > Sent: 9. maaliskuuta 2006 3:48 > To: XCON-IETF > Subject: [XCON] A killing argument for SOAP-based Web > Services approach forXCON > > > > Guys, > > Take a look at the list of Web Services being defined > already by Parley X 2.0 /ETSI jointly with 3GPP... > > http://www.parlay.org/en/specifications/ > > > > Take a look at "Part 12" specifically, > > Orit. > > > _______________________________________________ > 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