|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
|
Last Update: May 8, 2008
-- Color Legend: RFC Editor Queue
/ Processed by IESG
/ ID Exists
/ Recently Expired
-- Each I-D name is a link to an I-D description, which points to a text version, a two-page and fit-in-window PDF version, as well as the IETF Tools' HTML version.
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
|
|
|
|
|
|
| The charter of the XCON working group
is reported below.
|
|
|
|
The focus of the Centralized Conferencing (XCON)
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 (known as a focus) 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.
The scope of this effort is intentionally more narrow than previous
attempts to standardize conferencing (e.g. centralized control), and is
intended to enable interoperability in a commercial environment which
already has a number of non-standard implementations using some of the
protocols.
Privacy, security, and authorization mechanisms are integral to the
solution generated by the working group. This includes allowing
participants to be invisible to all but the conference owner, 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.
Due to the centralized architecture of the WG, XCON's mechanisms will
place requirements on the signaling protocol used between the focus
and
the participants. At a high level, the signaling protocol must be able
to establish, tear down, modify, and perform call control operations on
multimedia streams, including voice, video, and instant messaging, in
both a centralized and distributed mixing architecture. SIP will be the
reference session signaling protocol used for examples; however, none of
the XCON solutions themselves will be signaling protocols, nor will XCON
extend existing signaling protocols. Other signaling protocols than SIP
may be used between the focus and participants, including non-IETF
protocols, but the requirements and possible extensions needed for other
signaling protocols to utilize the full functionality of the XCON
architecture is outside the scope of XCON.
The deliverables for the group will be:
|
|
| - |
A mechanism for membership and authorization control
|
| - |
A mechanism to manipulate and describe media "mixing" or "topology"
for multiple media types (audio, video, text)
|
| - |
A mechanism for notification of conference related events/changes
(for example a floor change)
|
| - |
A basic floor control protocol
|
|
The initial set of protocols will be developed for use in unicast media
conferences. The working group will perform a second round of work to
enhance the set of protocols as necessary for use with multicast media
after their initial publication.
The following items are specifically out-of-scope:
|
|
| - |
Voting
|
| - |
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
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
xcon-framework-11
RFC Ed Queue (05/08)
Apr 11, 2008
(67 p.)
[pdf(2)]
[html]
|
M. Barnes
C. Boulton
O. Levin |
| A Framework and Data Model
for Centralized Conferencing |
|
This document defines the framework for Centralized Conferencing.
The framework allows participants using various call signaling
protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange
media in a centralized unicast conference. The Centralized
Conferencing Framework defines logical entities and naming
conventions. The framework also outlines a set of conferencing
protocols, which are complementary to the call signaling protocols,
for building advanced conferencing applications. The framework binds
all the defined components together for the benefit of builders of
conferencing systems.
|
|
|
| |
| Up List |
Intended Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
| -
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
xcon-common-
data-model-10
ID Exists
Mar 28, 2008
(75 p.)
[pdf(2)]
[html]
|
O. Novo
G. Camarillo
D. Morgan
R. Even |
|
Conference Information Data Model for Centralized Conferencing (XCON) |
|
This document defines an Extensible Markup Language (XML)-based
conference information data model for centralized conferencing
(XCON). A conference information data model is designed to convey
information about the conference and about participation in the
conference. The conference information data model defined in this
document constitutes an extension of the data format specified in the
Session Initiation Protocol (SIP) Event Package for Conference State.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| Real-time Applications & Infrastructure (RAI) area |
|
|
|
|
|
|
|
##
##
##
##
##
##
##
##
##
##
##
## XCONwg
##
##
##
##
##
|
|
|
|
|
|
|
|
|
|
| | |
barnes-xcon-
ccmp-04
ID Exists
Feb 25, 2008
(35 p.)
[pdf(2)]
[html]
|
M. Barnes
C. Boulton
H. Schulzrinne |
|
Centralized Conferencing Manipulation Protocol |
|
The Centralized Conferencing Manipulation Protocol (CCMP) defined in
this document provides the mechanisms to create, change and delete
objects related to centralized conferences, including participants,
their media and their roles. The protocol relies on web services and
SIP event notification as its infrastructure, but can control
conferences that use any signaling protocol to invite users. CCMP is
based on the Simple Object Access Protocol (SOAP), with the data
necessary for the interactions specified via Web Services Description
Language (WSDL).
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
sandbakken-xcon-
bfcp-udp-00
ID Exists
(Recently Expired)
Oct 10, 2007
(8 p.)
[pdf(2)]
[html]
|
G. Sandbakken
T. Andersen
A. Heggestad |
|
Binary Floor Control Protocol over UDP |
|
This memo extends the Binary Floor Control Protocol enabling it to
use UDP as a transport. In order to use an unreliable transport
mechanism this draft utilizes the existing transaction model in BFCP
to achieve reliability. Each request now has an appropriate response
to complete the transaction. It also defines a keep alive behavior
needed to keep NAT bindings open.
|
|
|
| |
| Up List |
Intended Status: | Standards Track |
|
|
|
|
|
|
|
|
|
|
