[Sipping] Centralized Conferencing (xcon) BOF Announcement

Alan Johnston <alan.johnston@mci.com> Tue, 24 June 2003 19:18 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05403 for <sipping-archive@odin.ietf.org>; Tue, 24 Jun 2003 15:18:42 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OJIEO07157 for sipping-archive@odin.ietf.org; Tue, 24 Jun 2003 15:18:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UtJ0-0001rM-4m for sipping-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 15:18:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05310 for <sipping-web-archive@ietf.org>; Tue, 24 Jun 2003 15:18:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UtIy-0006Cp-00 for sipping-web-archive@ietf.org; Tue, 24 Jun 2003 15:18:12 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UtIs-0006Cm-00 for sipping-web-archive@ietf.org; Tue, 24 Jun 2003 15:18:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UtIo-0001eg-02; Tue, 24 Jun 2003 15:18:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UtIS-0001dj-83 for sipping@optimus.ietf.org; Tue, 24 Jun 2003 15:17:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05142 for <sipping@ietf.org>; Tue, 24 Jun 2003 15:17:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UtIC-0006Bp-00 for sipping@ietf.org; Tue, 24 Jun 2003 15:17:24 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17]) by ietf-mx with esmtp (Exim 4.12) id 19UtI1-0006BA-00 for sipping@ietf.org; Tue, 24 Jun 2003 15:17:13 -0400
Received: from pmismtp01.wcomnet.com ([166.38.62.36]) by firewall.wcom.com (Iplanet MTA 5.2) with ESMTP id <0HH0009BO2UYCN@firewall.wcom.com> for sipping@ietf.org; Tue, 24 Jun 2003 19:16:10 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with SMTP id <0HH000B012UV9X@pmismtp01.wcomnet.com>; Tue, 24 Jun 2003 19:16:10 +0000 (GMT)
Received: from xs578v3521.mci.com ([166.50.122.248]) by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTP id <0HH00093P2UUNV@pmismtp01.wcomnet.com>; Tue, 24 Jun 2003 19:16:08 +0000 (GMT)
Date: Tue, 24 Jun 2003 14:16:03 -0500
From: Alan Johnston <alan.johnston@mci.com>
X-Sender: Alan.Johnston@pop.mcit.com
To: sipping@ietf.org
Cc: Adam Roach <adam@dynamicsoft.com>
Message-id: <5.2.1.1.0.20030624141219.023d2e68@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Content-type: text/plain; charset="us-ascii"; format="flowed"
Subject: [Sipping] Centralized Conferencing (xcon) BOF Announcement
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>

FYI.

Centralized Conferencing BOF (xcon)

Tuesday, July 15 at 1700-1800
==============================

CHAIRS: Alan Johnston (alan.johnston@mci.com)
         Adam Roach (adam@dynamicsoft.com)

AGENDA:

- Intro and Agenda Bashing (5 min)
- Problem Statement and Overview of Scope (10 min)
- Charter Discussion (15 min)
- Open Discussion (30 min)


Description of Proposed Working Group


The focus of this working group is to develop a standardized suite of 
protocols for tightly-coupled multimedia conferences, where strong security 
and authorization requirements are integral to the solution. 
Tightly-coupled conferences have a central point of control and 
authorization so they can enforce specific media and membership 
relationships, and provide an accurate roster of participants. The media 
mixing or combining function of a tightly-coupled conference need not be 
performed centrally, however. Unlike previous attempts at standardizing 
conferencing-related activities, the scope of this effort is intentionally 
very narrow, and is intended to enable interoperability in a commercial 
environment which already has a number of implementations.


Privacy, security, and authorization mechanisms are integral to the 
solution generated by the working group. This includes allowing 
participants to be completely invisible or to be visible but participate 
anonymously with respect to some or all of the other participants. 
Authorization rules allow for participants and non-participants to have 
roles (ex: speaker, moderator, owner), and to be otherwise authorized to 
perform membership and media manipulation for or on behalf of other 
participants. In order to preserve these properties, the protocols used 
will require implementation of channel security and authentication services.


Initially this combination of protocols will be specified with respect to 
session setup with SIP, but most of the specific components would be 
applicable to conferences setup using other protocols. [None of the 
protocols defined by this group will be SIP or require SIP extensions.] The 
group will use the high-level requirements and framework already described 
by documents published by the SIPPING WG.


The deliverables for the group will be:
- A mechanism for membership and authorization control
- A mechanism to manipulate and describe media "layout" or "topology" for 
multiple media types (audio, video, text)
- A mechanism for notification of conference related events/changes (for 
example a roster)
- A basic floor control protocol
- Peer-to-peer cascading of conferences (one conference is a participant in 
another and vice versa)


The following items are specifically out-of-scope:
- Voting
- Multicast media (due to security concerns)
- Fully distributed conferences
- Loosely-coupled conferences (no central point of control)
- Far-end device control
- Protocol used between the conference controller and the mixer(s)
- Capabilities negotiation of the mixer(s)
- Master-slave cascaded conferences


The working group will coordinate closely with the SIPPING and MMUSIC 
working groups. In addition the working group will cooperate with other 
groups as needed, including SIP, AVT, and the W3C SMIL working groups.
In addition, the working group will consider a number of existing drafts (a 
non-exhaustive list is included below) as input to the working group.


Related documents in other working groups:
- draft-ietf-sipping-conferencing-requirements-00.txt
- draft-ietf-sipping-conferencing-framework-00.txt
- draft-ietf-sipping-cc-conferencing-00.txt
- draft-ietf-sipping-cc-framework-02.txt
- draft-ietf-sipping-conference-package-00.txt

Partial list of input documents:
(All documents available at http://ee.wustl.edu/~alan/xcon/ until they 
appear in the IETF archives.)

- draft-even-xcon-conference-scenarios-00.txt
- draft-koskelainen-xcon-cpcp-reqs-00.txt
- draft-even-xcon-media-policy-requirements-00.txt
- draft-koskelainen-xcon-floor-control-req-00.txt
- draft-koskelainen-xcon-xcap-cpcp-usage-00.txt
- draft-levin-xcon-cpcp-00.txt
- draft-mahy-xcon-media-policy-control-00.txt

Comments on the above drafts are welcome on the xcon mailing list:

Mailing-List:   xcon@softarmor.com
                 http://www.softarmor.com/mailman/listinfo/xcon









_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP