From xcon-bounces@ietf.org Wed Aug 02 09:48:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8H5k-0004iv-Sx; Wed, 02 Aug 2006 09:48:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8H5j-0004ip-VE
	for xcon@ietf.org; Wed, 02 Aug 2006 09:48:55 -0400
Received: from webmail.unina.it ([192.132.34.212])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8H5h-0001hE-S9
	for xcon@ietf.org; Wed, 02 Aug 2006 09:48:55 -0400
Received: from webmail.unina.it (localhost [127.0.0.1])
	by webmail.unina.it (8.12.11/8.12.11) with ESMTP id k72DoaUJ023342;
	Wed, 2 Aug 2006 15:50:36 +0200
Received: (from nobody@localhost)
	by webmail.unina.it (8.12.11/8.12.11/Submit) id k72Doavk023341;
	Wed, 2 Aug 2006 15:50:36 +0200
X-Authentication-Warning: webmail.unina.it: nobody set sender to
	spromano@unina.it using -f
Received: from 143.225.229.2 ([143.225.229.2]) 
	by webmail.unina.it (IMP) with HTTP 
	for <spromano@192.132.34.41>; Wed,  2 Aug 2006 15:50:36 +0200
Message-ID: <1154526636.44d0adac79410@webmail.unina.it>
Date: Wed,  2 Aug 2006 15:50:36 +0200
From: Simon Pietro Romano <spromano@unina.it>
To: Liu Ya <liuya@huawei.com>
Subject: Re: [XCON] Is there available running code for XCON?
References: <09ce01c69e4f$9e9aade0$3c726e0a@china.huawei.com>
In-Reply-To: <09ce01c69e4f$9e9aade0$3c726e0a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 143.225.229.2
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by webmail.unina.it id
	k72DoaUJ023342
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 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>
Errors-To: xcon-bounces@ietf.org

Hi all,

University of Naples, in cooperation with Ericsson Nomadic Lab in Helsink=
y, has
just released its first running implementation of the XCON framework. We =
called
the project CONFIANCE (CONFerencing IMS-enabled Architecture for
Next-generation Communication Experience). You can find the entire bundle=
 at
the following sourceforge url:

https://sourceforge.net/projects/confiance/

Comments, feedback and suggestions are more than welcome.

Cheers,

Simon

--=20
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department=20
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: spromano@unina.it

    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli=20
   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/




Scrive Liu Ya <liuya@huawei.com>:

> Hi all,
>     I'm doing some research about security of group communications. And=
 XCON
> is a very suitable example scenario. So a set of XCON running code will=
 do a
> great help to my work. Could you tell me if there is XCON implementaion=
s=20
> available now?
>=20
>=20
> Thanks.
> Liu Ya
>=20
>=20
> --=20
> Il messaggio e' stato analizzato alla ricerca di virus o
> contenuti pericolosi da MailScanner, ed e'
> risultato non infetto.
>=20
>=20


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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



From xcon-bounces@ietf.org Thu Aug 31 08:04:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIlHe-0001F1-F9; Thu, 31 Aug 2006 08:04:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIlHd-0001Eu-9N
	for xcon@ietf.org; Thu, 31 Aug 2006 08:04:33 -0400
Received: from mxs1.siemens.at ([194.138.12.131] helo=atvies1zqx.siemens.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIlHT-0003FI-P0
	for xcon@ietf.org; Thu, 31 Aug 2006 08:04:33 -0400
Received: from vies1kbx.sie.siemens.at ([158.226.129.82])
	by atvies1zqx.siemens.at  with ESMTP id k7VC4oxt008834
	for <xcon@ietf.org>; Thu, 31 Aug 2006 14:04:50 +0200
Received: from localhost ([158.226.129.98])
	by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with SMTP id
	k7VC4FgU027647 for <xcon@ietf.org>; Thu, 31 Aug 2006 14:04:16 +0200
Received: from prga004a.ww300.siemens.net ([163.242.71.105]) by
	nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Aug 2006 13:53:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [xcon] Removing media stream from all legs or from own leg in tightly
	coupled SIP conferencing
Date: Thu, 31 Aug 2006 13:53:10 +0200
Message-ID: <3E4278088AD82C48B4663DDFE762CEF301A1C5C0@prga004a.ww300.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [xcon] Removing media stream from all legs or from own leg in
	tightly coupled SIP conferencing
Thread-Index: AcbM9Ag+S04SmPyRQbu6c6qO9hF1Pg==
From: "Sedlacek, Ivo" <ivo.sedlacek@siemens.com>
To: <xcon@ietf.org>
X-OriginalArrivalTime: 31 Aug 2006 11:53:11.0110 (UTC)
	FILETIME=[085DF660:01C6CCF4]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
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>
Content-Type: multipart/mixed; boundary="===============1664059520=="
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1664059520==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6CCF4.080D7B80"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6CCF4.080D7B80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
=20
RFC4353 defines the tightly coupled SIP conferencing.=20
=20
It also defines how the media streams are removed from the conference
(5.6. Adding and Removing Media). It says that when the port of media
stream is set to 0 in an SDP offer/answer from a participant, the
participant does not want to use the media stream any more. The focus
may accept this for the participant leg's only or the focus may apply
this request to all the legs - the processing is left open in RFC4353.
=20
In some conference types both options may be allowed for a participant.
Thus the participant may have possibility to signal both actions:
1) either participant wants to remove the media stream from own leg
(between participant and focus)
2) or participant wants to remove the media stream from all the legs
(completely from the conference)
=20
Based on the participant's signalling, the focus has to distinguish 1)
and 2) and to do the appropriate actions.

Is there any SIP/SDP mechanism how to detect whether the participant
wants 1) or 2)?
=20
I noticed the CPPP and COMP, but they seem to be based on SOAP or HTTP.
=20
Kind regards
=20
Ivo Sedlacek
Siemens
ANF DATA MCS CD3
phone: +420 54310 6532
mailto: ivo.sedlacek@siemens.com
=20
Mailcode: C0gmHhFp=20
=20
=20

------_=_NextPart_001_01C6CCF4.080D7B80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial><FONT size=3D2>Hello,<BR>&nbsp;<BR>RFC4353 =
defines the=20
tightly coupled SIP conferencing<SPAN class=3D239521108-31082006>.=20
</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D239521108-31082006></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D239521108-31082006>It=20
</SPAN><SPAN class=3D239521108-31082006>also&nbsp;defines how the media =
streams=20
are removed from the conference (</SPAN>5.6. Adding and Removing =
Media<SPAN=20
class=3D239521108-31082006>). </SPAN></FONT></FONT><FONT face=3DArial =
size=3D2><SPAN=20
class=3D239521108-31082006>It says that when the port of =
media&nbsp;stream is set=20
to 0 in an SDP offer/answer from&nbsp;a participant, the participant =
does not=20
want to use the media stream any more.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN class=3D239521108-31082006>The focus may&nbsp;accept this =
for the=20
participant leg's only or&nbsp;the focus may apply this request to all=20
the&nbsp;legs - the processing is left open in =
RFC4353.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D239521108-31082006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D239521108-31082006>In =
some conference=20
types both options&nbsp;may be&nbsp;allowed for a participant. <SPAN=20
class=3D239521108-31082006>Thus&nbsp;the participant may have =
possibility to=20
signal&nbsp;both actions:</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D239521108-31082006>1) =
either=20
participant wants to remove the media stream from own leg (between =
participant=20
and focus)<BR>2) or participant wants to remove the media stream from =
all the=20
legs (completely from the conference)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D239521108-31082006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D239521108-31082006>Based =
on the=20
participant's signalling, the focus has to distinguish 1) and 2) and to =
do the=20
appropriate actions.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
class=3D239521108-31082006><BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D239521108-31082006>Is =
there any SIP/SDP=20
mechanism how to detect whether the participant wants 1) or=20
2)?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D239521108-31082006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D239521108-31082006>I =
noticed the CPPP=20
and COMP, but they seem to be based on SOAP or HTTP.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;<BR>Kind regards</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ivo Sedlacek<BR>Siemens<BR>ANF DATA MCS =

CD3<BR>phone: +420 54310 6532<BR>mailto: <A=20
title=3Dmailto:ivo.sedlacek@siemens.com=20
href=3D"mailto:ivo.sedlacek@siemens.com">ivo.sedlacek@siemens.com</A></FO=
NT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Mailcode: C0gmHhFp </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C6CCF4.080D7B80--



--===============1664059520==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1664059520==--