draft-ietf-xcon-ccmp-03.txt   draft-ietf-xcon-ccmp-04.txt 
XCON Working Group M. Barnes XCON Working Group M. Barnes
Internet-Draft Nortel Internet-Draft Nortel
Intended status: Standards Track C. Boulton Intended status: Standards Track C. Boulton
Expires: January 14, 2010 NS-Technologies Expires: May 16, 2010 NS-Technologies
S P. Romano S P. Romano
University of Napoli University of Napoli
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
July 13, 2009 November 12, 2009
Centralized Conferencing Manipulation Protocol Centralized Conferencing Manipulation Protocol
draft-ietf-xcon-ccmp-03 draft-ietf-xcon-ccmp-04
Abstract
The Centralized Conferencing Manipulation Protocol (CCMP) can create,
retrieve, change and delete objects describing a centralized
conference, such as state and capabilities of the conference,
participants, and their roles. The conference information is
contained in XML documents and fragments conforming to the
centralized conferencing data model schema. Even though the goal of
the CCMP is to appropriately manage conference state, the mechanisms
upon which the protocol itself is built are based on a state-less
request/response paradigm. Conferencing clients send requests to
conference servers, which respond to the client with the conference
information.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 2, line 5
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2010. This Internet-Draft will expire on May 16, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
The Centralized Conferencing Manipulation Protocol (CCMP) can create, described in the BSD License.
retrieve, change and delete objects describing a centralized
conference, such as state and capabilities of the conference,
participants, and their roles. The conference information is
contained in XML documents and fragments conforming to the
centralized conferencing data model schema. CCMP is a state-less
client-server protocol based on a request/response model.
Conferencing clients send requests to conference servers, which
respond to the client with the conference information.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7 4. XCON Conference Control System Architecture . . . . . . . . . 7
5. System Architecture . . . . . . . . . . . . . . . . . . . . . 9 4.1. Conference Objects . . . . . . . . . . . . . . . . . . . . 8
6. Conference Object and User Identifiers . . . . . . . . . . . . 11 4.2. Conference Users . . . . . . . . . . . . . . . . . . . . . 8
6.1. Conference Object . . . . . . . . . . . . . . . . . . . . 11 5. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 10
6.2. Conference Users and Participants . . . . . . . . . . . . 11 5.1. Protocol Operations . . . . . . . . . . . . . . . . . . . 10
7. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 13 5.2. Implementation Approach . . . . . . . . . . . . . . . . . 12
7.1. Implementation Approach . . . . . . . . . . . . . . . . . 14 6. CCMP messages . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2. CCMP protocol messages . . . . . . . . . . . . . . . . . . 14 6.1. CCMP Request Message Type . . . . . . . . . . . . . . . . 13
7.2.1. CCMP Request Message . . . . . . . . . . . . . . . . . 14 6.2. CCMP Response Message Type . . . . . . . . . . . . . . . . 14
7.2.2. CCMP Response Message . . . . . . . . . . . . . . . . 16 6.3. Detailed messages . . . . . . . . . . . . . . . . . . . . 16
7.2.2.1. CCMP Response Codes . . . . . . . . . . . . . . . 18 6.3.1. blueprintsRequest and blueprintsResponse . . . . . . . 19
7.2.3. Detailed CCMP Messages . . . . . . . . . . . . . . . . 21 6.3.2. confsRequest and confsResponse . . . . . . . . . . . . 21
7.2.3.1. blueprintsRequest and blueprintsResponse 6.3.3. blueprintRequest and blueprintResponse . . . . . . . . 22
messages . . . . . . . . . . . . . . . . . . . . . 23 6.3.4. confRequest and confResponse . . . . . . . . . . . . . 24
7.2.3.2. confsRequest and confsResponse messages . . . . . 25 6.3.5. usersRequest and usersResponse . . . . . . . . . . . . 27
7.2.3.3. blueprintRequest and blueprintResponse messages . 26 6.3.6. userRequest and userResponse . . . . . . . . . . . . . 30
7.2.3.4. confRequest and confResponse messages . . . . . . 28 6.3.7. sidebarsByValRequest and sidebarsByValResponse . . . . 34
7.2.3.5. usersRequest and usersResponse messages . . . . . 31 6.3.8. sidebarByValRequest and sidebarByValResponse . . . . . 36
7.2.3.6. userRequest and userResponse messages . . . . . . 34 6.3.9. sidebarsByRefRequest and sidebarsByRefResponse . . . . 39
7.2.3.7. sidebarsByValRequest and sidebarsByValResponse 6.3.10. sidebarByRefRequest and sidebarByRefResponse . . . . . 41
messages . . . . . . . . . . . . . . . . . . . . . 39 6.4. CCMP Response Codes . . . . . . . . . . . . . . . . . . . 44
7.2.3.8. sidebarByValRequest and sidebarByValResponse 7. A complete example of the CCMP in action . . . . . . . . . . . 48
messages . . . . . . . . . . . . . . . . . . . . . 41 7.1. Alice retrieves the available blueprints . . . . . . . . . 48
7.2.3.9. sidebarsByRefRequest and sidebarsByRefResponse 7.2. Alice gets detailed information about a specific
messages . . . . . . . . . . . . . . . . . . . . . 44 blueprint . . . . . . . . . . . . . . . . . . . . . . . . 51
7.2.3.10. sidebarByRefRequest and sidebarByRefResponse 7.3. Alice creates a new conference through a cloning
messages . . . . . . . . . . . . . . . . . . . . . 46 operation . . . . . . . . . . . . . . . . . . . . . . . . 53
8. A complete example of the CCMP in action . . . . . . . . . . . 50 7.4. Alice updates conference information . . . . . . . . . . . 55
8.1. Alice retrieves the available blueprints . . . . . . . . . 50 7.5. Alice inserts a list of users in the conference object . . 57
8.2. Alice gets detailed information about a specific 7.6. Alice joins the conference . . . . . . . . . . . . . . . . 59
blueprint . . . . . . . . . . . . . . . . . . . . . . . . 53 7.7. Alice adds a new user to the conference . . . . . . . . . 61
8.3. Alice creates a new conference through a cloning 8. Locating a Conference Control Server . . . . . . . . . . . . . 64
operation . . . . . . . . . . . . . . . . . . . . . . . . 55 9. Managing Notifications . . . . . . . . . . . . . . . . . . . . 66
8.4. Alice updates conference information . . . . . . . . . . . 57 10. HTTP Transport . . . . . . . . . . . . . . . . . . . . . . . . 67
8.5. Alice inserts a list of users in the conference object . . 59 11. Security Considerations . . . . . . . . . . . . . . . . . . . 69
8.6. Alice joins the conference . . . . . . . . . . . . . . . . 61 11.1. Assuring that the Proper Conferencing Server has been
8.7. Alice adds a new user to the conference . . . . . . . . . 63 contacted . . . . . . . . . . . . . . . . . . . . . . . . 70
9. Locating a Conference Control Server . . . . . . . . . . . . . 66 11.2. User Authentication and Authorization . . . . . . . . . . 70
10. Managing Notifications . . . . . . . . . . . . . . . . . . . . 68 11.3. Security and Privacy of Identity . . . . . . . . . . . . . 71
11. HTTP Transport . . . . . . . . . . . . . . . . . . . . . . . . 69 12. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 72
12. Security Considerations . . . . . . . . . . . . . . . . . . . 71 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 83
12.1. Assuring that the Proper Conferencing Server has been 13.1. URN Sub-Namespace Registration . . . . . . . . . . . . . . 83
contacted . . . . . . . . . . . . . . . . . . . . . . . . 72 13.2. XML Schema Registration . . . . . . . . . . . . . . . . . 83
12.2. User Authentication and Authorization . . . . . . . . . . 72 13.3. MIME Media Type Registration for 'application/ccmp+xml' . 84
12.3. Security and Privacy of Identity . . . . . . . . . . . . . 73 13.4. DNS Registrations . . . . . . . . . . . . . . . . . . . . 85
13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13.4.1. Registration of a Conference Control Server
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 85 Application Service Tag . . . . . . . . . . . . . . . 85
14.1. URN Sub-Namespace Registration . . . . . . . . . . . . . . 85 13.4.2. Registration of a Conference Control Server
14.2. XML Schema Registration . . . . . . . . . . . . . . . . . 85 Application Protocol Tag for CCMP . . . . . . . . . . 85
14.3. MIME Media Type Registration for 'application/ccmp+xml' . 86 13.5. CCMP Protocol Registry . . . . . . . . . . . . . . . . . . 86
14.4. DNS Registrations . . . . . . . . . . . . . . . . . . . . 87 13.5.1. CCMP Message Types . . . . . . . . . . . . . . . . . . 86
14.4.1. Registration of a Location Server Application 13.5.2. CCMP Response Codes . . . . . . . . . . . . . . . . . 87
Service Tag . . . . . . . . . . . . . . . . . . . . . 87 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 90
14.4.2. Registration of a Location Server Application 15. Changes since last Version . . . . . . . . . . . . . . . . . . 91
Protocol Tag for HELD . . . . . . . . . . . . . . . . 87 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 93
14.5. CCMP Protocol Registry . . . . . . . . . . . . . . . . . . 88 16.1. Normative References . . . . . . . . . . . . . . . . . . . 93
14.5.1. CCMP Message Types . . . . . . . . . . . . . . . . . . 88 16.2. Informative References . . . . . . . . . . . . . . . . . . 93
14.5.2. CCMP Response Codes . . . . . . . . . . . . . . . . . 89
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 92
16. Changes since last Version . . . . . . . . . . . . . . . . . . 93
17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 95
17.1. Normative References . . . . . . . . . . . . . . . . . . . 95
17.2. Informative References . . . . . . . . . . . . . . . . . . 95
Appendix A. Appendix A: Other protocol models and transports Appendix A. Appendix A: Other protocol models and transports
considered for CCMP . . . . . . . . . . . . . . . . . 97 considered for CCMP . . . . . . . . . . . . . . . . . 95
A.1. Using SOAP for the CCMP . . . . . . . . . . . . . . . . . 97 A.1. Using SOAP for the CCMP . . . . . . . . . . . . . . . . . 95
A.2. A RESTful approach for the CCMP . . . . . . . . . . . . . 98 A.2. A RESTful approach for the CCMP . . . . . . . . . . . . . 96
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 97
1. Introduction 1. Introduction
The Framework for Centralized Conferencing [RFC5239] (XCON Framework) The Framework for Centralized Conferencing [RFC5239] (XCON Framework)
defines a signaling-agnostic framework, naming conventions and defines a signaling-agnostic framework, naming conventions and
logical entities required for building advanced conferencing systems. logical entities required for building advanced conferencing systems.
The XCON Framework introduces the conference object as a logical The XCON Framework introduces the conference object as a logical
representation of a conference instance, representing the current representation of a conference instance, representing the current
state and capabilities of a conference. state and capabilities of a conference.
skipping to change at page 4, line 28 skipping to change at page 5, line 28
well as adding and removing media streams and associated end points. well as adding and removing media streams and associated end points.
The CCMP implements the client-server model within the XCON The CCMP implements the client-server model within the XCON
Framework, with the conferencing client and conference control server Framework, with the conferencing client and conference control server
acting as client and server, respectively. The CCMP uses HTTP acting as client and server, respectively. The CCMP uses HTTP
[RFC2616] as the protocol to transfer the CCMP requests and [RFC2616] as the protocol to transfer the CCMP requests and
responses, which contain the domain-specific XML-encoded data objects responses, which contain the domain-specific XML-encoded data objects
defined in the Conference Information Data Model for Centralized defined in the Conference Information Data Model for Centralized
Conferencing (XCON Data Model) [I-D.ietf-xcon-common-data-model]. Conferencing (XCON Data Model) [I-D.ietf-xcon-common-data-model].
Other protocol models such as the use of a REST (REpresentational Other protocol models such as the use of a REST (REpresentational
State Transfer) architectural style [REST] were considered. However, State Transfer) architectural style [REST] were considered.
the CCMP is a request/response protocol with new or updated data
relevant to the specific conference object returned in the response.
Whereas, a REST approach involves singular/monolithic operations on
data, with the response typically indicating either success or
failure, rather than providing updated data based on a specific
operation, thus, it was not considered a good choice. Details of the
use of REST for the CCMP, as well as other protocols considered
(e.g., SOAP) are provided in Appendix A.
Section 4 provides an overview of the design of the CCMP, followed by Section 4 provides an overview of the Conference Control
the system architecture in Section 5. Section 6 discusses the functionality of the XCON framework, together with a description of
primary keys in the conference object carried in the protocol. An the main targets CCMP deals with, namely conference objects and
overview of the operations associated with each protocol request and conference users. A general description of the operations associated
response is provided in Section 7. A complete example of the with protocol messages is given in Section 5 together with
operation of the CCMP, describing a typical call flow associated with implementation details. A complete example of the operation of the
conference creation and manipulation, is provided in Section 8. CCMP, describing a typical call flow associated with conference
Section 13 provides the XML schema. creation and manipulation, is provided in Section 7. Section 12
provides the XML schema.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Terminology 3. Terminology
In additon to the terms defined in the Framework for Centralized In additon to the terms defined in the Framework for Centralized
skipping to change at page 7, line 5 skipping to change at page 8, line 5
is based on the consideration that a software architecture can is based on the consideration that a software architecture can
often be specified as an appropriate configuration of components, often be specified as an appropriate configuration of components,
data and connectors, all coordinated through constraining their data and connectors, all coordinated through constraining their
mutual relationships. Coordination and constraints help achieve a mutual relationships. Coordination and constraints help achieve a
desired set of architectural properties. [REST] desired set of architectural properties. [REST]
SOAP: Simple Object Access Protocol defined in SOAP: Simple Object Access Protocol defined in
[W3C.REC-soap12-part1-20030624] and [W3C.REC-soap12-part1-20030624] and
[W3C.REC-soap12-part2-20030624]. [W3C.REC-soap12-part2-20030624].
4. Protocol Overview 4. XCON Conference Control System Architecture
This document specifies the basic operations that can create,
retrieve, modify and delete conference-related information in a
centralized conference. The core set of objects manipulated in the
CCMP protocol described in this document includes conference
blueprints, the conference object, users, and sidebars.
Each operation in the protocol model is atomic and either succeeds or
fails as a whole. The conference server MUST ensure that the
operations are atomic in that the operation invoked by a specific
conference client completes prior to another client's operation on
the same conference object. The details for this data locking
functionality are out of scope for the CCMP protocol specification
and are implementation specific for a conference server. Thus, the
conference server first checks all the parameters, before making any
changes to the internal representation of the conference object. For
example, it would be undesirable to change the <subject> of the
conference, but then detect an invalid URI in one of the <service-
uris> and abort the remaining updates. Also, since multiple clients
can modify the same conference objects, conference clients SHOULD
first obtain the current object from the conference server and then
update the relevant data elements in the conference object prior to
invoking a specific operation on the conference server. In some
cases, the data changes are not fully applied, since a previous
operation by another conference client may have altered some of the
data. Where appropriate (i.e., depending upon the specific data and
policies), the conference server SHOULD indicate that the data has
been modified and return the current conference object to the client.
For example, one conferencing client may add a new user to the
conference object. Thus, a subsequent request by another
conferencing client should provide a conference object containing
this new user.
It is likely that implementations and future standardization work
will add more conference attributes and parameters. There are three
types of extensions. The first and simplest type of extension adds
elements to the overall conference description, media descriptions or
descriptions of users. The XML namespace mechanism makes such
extensions relatively easy, although implementations still have to
deal with companion implementations that may not understand the new
namespaces. The CCMP "blueprintsRequest" message allows clients to
determine the capabilities of a specific server, reflected by the
specific blueprints supported by that server.
A second type of extension replaces the conference, user or media
objects with completely new schema definitions, i.e., the namespaces
for these objects themselves differ from the basic one defined in
this document. As long as the blueprintsRequest message remains
available and keeps to a mutually-understood definition, a compatible
client and server will be able to bootstrap themselves into using
these new objects.
Finally, it is conceivable that new object types are needed beyond
the core conference, user and media objects and their children.
These would also be introduced by namespaces and new URIs.
5. System Architecture
CCMP supports the XCON framework . Figure 1 depicts a subset of the CCMP supports the XCON framework . Figure 1 depicts a subset of the
'Conferencing System Logical Decomposition' architecture from the "Conferencing System Logical Decomposition" architecture from the
XCON framework document. It illustrates the role that CCMP assumes XCON framework document. It illustrates the role that CCMP assumes
within the overall centralized architecture. within the overall centralized architecture.
........................................................ ........................................................
. Conferencing System . . Conferencing System .
. . . .
. +---------------------------------------+ . . +---------------------------------------+ .
. | C O N F E R E N C E O B J E C T | . . | C O N F E R E N C E O B J E C T | .
. +-+-------------------------------------+ | . . +-+-------------------------------------+ | .
. | C O N F E R E N C E O B J E C T | | . . | C O N F E R E N C E O B J E C T | | .
. +-+-------------------------------------+ | | . . +-+-------------------------------------+ | | .
. | C O N F E R E N C E O B J E C T | | | . . | C O N F E R E N C E O B J E C T | | | .
. | | | | .
. | | |-+ . . | | |-+ .
. | |-+ . . | |-+ .
. +---------------------------------------+ . . +---------------------------------------+ .
. ^ . . ^ .
. | . . | .
. v . . v .
. +-------------------+ . . +-------------------+ .
. | Conference Control| . . | Conference Control| .
. | Server | . . | Server | .
. +-------------------+ . . +-------------------+ .
skipping to change at page 11, line 5 skipping to change at page 9, line 12
Figure 1: Conference Client Interaction Figure 1: Conference Client Interaction
CCMP serves as the Conference Control Protocol, allowing the CCMP serves as the Conference Control Protocol, allowing the
conference control client to interface with the conference object conference control client to interface with the conference object
maintained by the conferencing system, as represented in Figure 1. maintained by the conferencing system, as represented in Figure 1.
Conference Control is one part of functionality for advanced Conference Control is one part of functionality for advanced
conferencing supported by a conferencing client. Other functions are conferencing supported by a conferencing client. Other functions are
discussed in the XCON framework and related documents. discussed in the XCON framework and related documents.
6. Conference Object and User Identifiers Conference object and conference users do represent key elements
involved in Conference Control operations. Their identifiers are
This section provides an overview of the conference object and widely used for creating the CCMP requests and responses. Such
conference users which are key protocol elements for creating the identifiers, used in CCMP for the conference object (XCON-URI) and
CCMP requests and responses. The identifiers used in CCMP for the conference user (XCON-USERID), are introduced in the XCON framework
conference object (XCON-URI) and conference user (XCON-USERID) are and defined in the XCON data model [I-D.ietf-xcon-common-data-model].
introduced in the XCON framework and defined in the XCON data model The main conference objects and users features are briefly described
[I-D.ietf-xcon-common-data-model]. in the following subsections.
6.1. Conference Object 4.1. Conference Objects
Conference objects feature a simple dynamic inheritance-and-override Conference objects feature a simple dynamic inheritance-and-override
mechanism. Conference objects are linked into a tree, where each mechanism. Conference objects are linked into a tree known as
tree node inherits attributes from its parent node. The roots of "cloning tree" (see Section 7.1 of [RFC5239]). Each cloning tree
these inheritance trees are also known as "blueprints". Nodes in the node inherits attributes from its parent node. The roots of these
inheritance trees are also known as "blueprints". Nodes in the
inheritance tree can be active conferences or simply descriptions inheritance tree can be active conferences or simply descriptions
that do not currently have any resources associated with them. An that do not currently have any resources associated with them. An
object can mark certain of its properties as unalterable, so that object can mark certain of its properties as unalterable, so that
they cannot be overridden. they cannot be overridden.
The schema for the conference object is defined in the XCON data The schema for the conference object is defined in the XCON data
model. Conference objects are uniquely identified by the XCON-URI. model. Conference objects are uniquely identified by the XCON-URI.
A client MAY specify a parent element that indicates the parent from A client MAY specify a parent object (a conference or blueprint) from
which the conference is to inherit values. When creating which to inherit values.
conferences, the XCON-URI included by the client is only a
suggestion. To avoid identifier collisions and to conform to local
server policy, the conference control server MAY choose a different
identifier.
6.2. Conference Users and Participants 4.2. Conference Users
Each conference can have zero or more users. All conference Each conference can have zero or more users. All conference
participants are users, but some users may have only administrative participants are users, but some users may have only administrative
functions and do not contribute or receive media. Users are added functions and do not contribute or receive media. Users are added
one user at a time to simplify error reporting. Users are inherited one user at a time to simplify error reporting. When a conference is
as well, so that it is easy to set up a conference that has the same cloned from a parent object, users are inherited as well, so that it
set of participants or a common administrator. The Conference is easy to set up a conference that has the same set of participants
Control Server creates individual users, assigning them a unique or a common administrator. The Conference Control Server creates
Conference User Identifier (XCON-USERID). individual users, assigning them a unique Conference User Identifier
(XCON-USERID).
A variety of elements defined in the common <conference-info> element A variety of elements defined in the common <conference-info> element
as specified in the XCON data model are used to determine how a as specified in the XCON data model are used to determine how a
specific user expects and is allowed to join a conference as a specific user expects and is allowed to join a conference as a
participant or as a user with specific privileges (e.g., observer). participant or as a user with specific privileges (e.g., observer).
For example, the <method> attribute defines how the caller joins the For example, each <target> element representing a user in the
conference, with a set of defined XML elements, namely <dial-in> for conference <allowed-user-list> shows a "method" attribute which
users that are allowed to dial in and <dial-out> for users that the defines how the user is expected to join the conference, i.e.
conference focus will be trying to reach. <dial-in> is the default. "dial-in" for users that are allowed to dial, "dial-out" for users
that the conference focus will be trying to reach. "dial-in" is the
default. If the conference is currently active, dial-out users are
contacted immediately; otherwise, they are contacted at the start of
the conference. The conference control protocol provides a mean to
manipulate these and other kinds of user-related features.
If the conference is currently active, dial-out users are contacted The conference control server assigns a unique Conference User
immediately; otherwise, they are contacted at the start of the Identifier (XCON-USERID) to each conferencing system user. The
conference. The conference control server assigns a unique
Conference User Identifier (XCON-USERID) to each user. The
conference control server uses the XCON-USERID to change or delete conference control server uses the XCON-USERID to change or delete
<user> elements. Depending upon policies and privileges, specific <user> elements. Depending upon policies and privileges, specific
users MAY also manipulate <user> elements. conference control clients MAY also manipulate <user> elements.
In many conferences, users can dial in if they know the XCON-URI and
an access code shared by all conference participants. In this case,
the system is typically not aware of the call signaling URL. Thus,
the initial <user> element does not have an entity attribute and the
default type of <dial-in> is used to support this type of user. For
this case, the server assigns a locally-unique URI, such as a
locally-scoped tel URI [RFC3966]. The conference control server
assigns a unique Conference User Identifier (XCON-USERID) to these
users when they dial-in to join the conference. If the user supports
the notification event package [I-D.ietf-xcon-event-package], they
can receive their XCON-USERID, thus allowing them to also manipulate
the <user> attribute, including the entity attribute, in the
conference object.
7. Protocol Operations 5. Protocol Overview
CCMP is a client-server, XML-based, stateless protocol, which has CCMP is a client-server, XML-based, state-less protocol, which has
been specifically conceived to provide users with the necessary means been specifically conceived to provide users with the necessary means
for the creation, retrieval, modification and deletion of conference for the creation, retrieval, modification and deletion of conference
objects. Conference-related information is encapsulated into CCMP objects.
messages in the form of documents or document fragments compliant
with the XCON data model representation. Section 5.1 specifies the basic operations that can create, retrieve,
modify and delete conference-related information in a centralized
conference. The core set of objects manipulated in the CCMP protocol
includes conference blueprints, the conference object, users, and
sidebars.
Conference-related information is encapsulated into CCMP messages in
the form of documents or document fragments compliant with the XCON
data model representation. Implementation details are presented in
Section 5.2
5.1. Protocol Operations
The main operations provided by CCMP belong in four general The main operations provided by CCMP belong in four general
categories: categories:
create: for the creation of a conference, a conference user, a create: for the creation of a conference, a conference user, a
sidebar, or a blueprint. sidebar, or a blueprint.
retrieve: to get information about the current state of either a retrieve: to get information about the current state of either a
conference object (be it an actual conference or a blueprint, or a conference object (be it an actual conference or a blueprint, or a
sidebar) or a conference user. A retrieve operation can also be sidebar) or a conference user. A retrieve operation can also be
skipping to change at page 14, line 5 skipping to change at page 12, line 11
o conference objects associated with sidebars, both embedded in the o conference objects associated with sidebars, both embedded in the
main conference (i.e. <sidebars-by-value> elements) and external main conference (i.e. <sidebars-by-value> elements) and external
to it (i.e. <sidebars-by-ref> elements), to it (i.e. <sidebars-by-ref> elements),
o <user> elements associated with conference users, o <user> elements associated with conference users,
o the list of XCON-URIs related to conferences and blueprints o the list of XCON-URIs related to conferences and blueprints
available at the server, for which only retrieval operations are available at the server, for which only retrieval operations are
allowed. allowed.
7.1. Implementation Approach Each operation in the protocol model is atomic and either succeeds or
fails as a whole. The conference server MUST ensure that the
operations are atomic in that the operation invoked by a specific
conference client completes prior to another client's operation on
the same conference object. The details for this data locking
functionality are out of scope for the CCMP protocol specification
and are implementation specific for a conference server. Thus, the
conference server first checks all the parameters, before making any
changes to the internal representation of the conference object. For
example, it would be undesirable to change the <subject> of the
conference, but then detect an invalid URI in one of the <service-
uris> and abort the remaining updates. Also, since multiple clients
can modify the same conference objects, conference clients SHOULD
first obtain the current object from the conference server and then
update the relevant data elements in the conference object prior to
invoking a specific operation on the conference server. In order to
effectively manage modifications to conference data, a versioning
approach is exploited in the CCMP. More precisely, each conference
object is associated with a version number indicating the most up to
date view of the conference at the server's side. Such version
number is reported to the clients when answering their requests. A
client willing to make modifications to a conference object has to
send an update message to the server. In case the modifications are
all successfully applied, the server sends back to the client a
"success" response which also carries information about the current
server-side version of the modified object. With such approach, a
client which is working on version "X" of a conference object and
finds inside a "success" response a version number which is "X+1" can
be sure that the version it was aware of was the most up to date. On
the other hand, if the "success" response carries back a version
which is at least "X+2", the client can detect that the object that
has been modified at the server's side was more up to date than the
one it was working upon. This is clearly due to the effect of
concurrent modification requests issued by independent clients.
Hence, for the sake of having available the latest version of the
modified object, the client can send to the conference server a
further "retrieve" request. In no case a copy of the conference
object available at the server is returned to the client as part of
the update response message. Such a copy can always be obtained
through an ad-hoc "retrieve" message. Based on the above
considerations, all CCMP response messages except those associated
with the retrieval of either the list of blueprints or the list of
conferences will have to contain a mandatory "version" parameter.
This does not hold for request messages, for which the "version"
parameter is not at all required, since it represents useless
information for the server: as long as the required modifications can
be applied to the target conference object with no conflicts, the
server does not care whether or not the client had an up to date view
of the information stored at its side. This said, it stands clear
that a client which has subscribed at the server, through the XCON
event package [I-D.ietf-xcon-event-package], to notifications about
conference object modifications, will always have the most up to date
version of that object available at his side.
5.2. Implementation Approach
There have been a number of different proposals as to the most There have been a number of different proposals as to the most
suitable implementation solution for the CCMP. A non-exhaustive suitable implementation solution for the CCMP. A non-exhaustive
summary of the most interesting ones is provided in Appendix A. The summary of the most interesting ones is provided in Appendix A. The
solution for the CCMP defined in this document is viewed as a good solution for the CCMP defined in this document is viewed as a good
compromise amongst the most notable past candidates and is referred compromise amongst the most notable past candidates and is referred
to as 'HTTP transport plus CCMP body'. With this approach, CCMP is to as "HTTP transport plus CCMP body". With this approach, CCMP is
able to take advantage of existing HTTP functionality. As with SOAP, able to take advantage of existing HTTP functionality. As with SOAP,
the CCMP uses a 'single HTTP verb' for transport (i.e. a single the CCMP uses a "single HTTP verb" for transport (i.e. a single
transaction type for each request/response pair); this allows transaction type for each request/response pair); this allows
decoupling CCMP messages from HTTP messages. Similarly, as with any decoupling CCMP messages from HTTP messages. Similarly, as with any
RESTful approach, CCMP messages are inserted directly in the body of RESTful approach, CCMP messages are inserted directly in the body of
HTTP messages, thus avoiding any unnecessary processing and HTTP messages, thus avoiding any unnecessary processing and
communication burden associated with further intermediaries. With communication burden associated with further intermediaries. With
this approach, no modification to the CCMP messages/operations is this approach, no modification to the CCMP messages/operations is
required to use a different transport protocol. required to use a different transport protocol.
The remainder of this document focuses on the selected approach. The The remainder of this document focuses on the selected approach. The
CCMP protocol inserts XML-based CCMP requests into the body of HTTP CCMP protocol inserts XML-based CCMP requests into the body of HTTP
POST operations and retrieves responses from the body of HTTP '200 POST operations and retrieves responses from the body of HTTP "200
OK' messages. CCMP messages have a MIME-type of "application/ OK" messages. CCMP messages have a MIME-type of "application/
ccmp+xml", which appears inside the "Content-Type" and "Accept" ccmp+xml", which appears inside the "Content-Type" and "Accept"
fields of HTTP requests and responses. Section 11 provides the fields of HTTP requests and responses. Section 10 provides the
complete requirements for an HTTP implementation to support the CCMP. complete requirements for an HTTP implementation to support the CCMP.
7.2. CCMP protocol messages 6. CCMP messages
CCMP messages are either requests or responses. The general CCMP CCMP messages are either requests or responses. The general CCMP
request message is defined in Section 7.2.1. The general CCMP request message is defined in Section 6.1. The general CCMP response
response message is defined in Section 7.2.2. The details of the message is defined in Section 6.2. The details of the specific
specific message type which is carried in the CCMP request and message type which is carried in the CCMP request and response
response messages are described in Section 7.2.3. messages are described in Section 6.3. CCMP response codes are
listed in Section 6.4
7.2.1. CCMP Request Message 6.1. CCMP Request Message Type
A CCMP request message is comprised of the following parameters: A CCMP request message is comprised of the following parameters:
confUserId: An optional parameter containing the XCON-USERID of the confUserId: An optional parameter containing the XCON-USERID of the
client. The "confUserID" parameter is used to determine if the client. The "confUserID" parameter is used to determine if the
conference control client has the authority to perform the conference control client has the authority to perform the
operation, as well as other Authorization, Authentication and operation, as well as other Authorization, Authentication and
Accounting (AAA) procedures. The attribute is required in the Accounting (AAA) procedures. The attribute is REQUIRED in the
CCMP request and response messages with the exception of the case CCMP request and response messages with the exception of the case
of a user who has no XCON-USERID and who wants to enter, via CCMP, of a user who has no XCON-USERID and who wants to enter, via CCMP,
a conference whose identifier is known. In such case, a side- a conference whose identifier is known. In such case, a side-
effect of the request is that the user is provided with an effect of the request is that the user is provided with an
appropriate XCON-USERID. An example of the above mentioned case appropriate XCON-USERID. An example of the above mentioned case
will be provided in Section 7.2.3.6. will be provided in Section 6.3.6.
confObjId: An optional parameter containing the XCON-URI of the confObjId: An optional parameter containing the XCON-URI of the
target conference object. target conference object.
operation: An optional parameter refining the type of specialized operation: An optional parameter refining the type of specialized
request message. The "operation" parameter is REQUIRED in all request message. The "operation" parameter is REQUIRED in all
requests except for the "blueprintsRequest" and "confsRequest" requests except for the "blueprintsRequest" and "confsRequest"
specialized messages. specialized messages.
password: An optional parameter that MUST be inserted in all password: An optional parameter that MUST be inserted in all
requests whose target conference object is password-protected (as requests whose target conference object is password-protected (as
per the <conference-password> element in per the <conference-password> element in
[I-D.ietf-xcon-common-data-model]). [I-D.ietf-xcon-common-data-model]).
specialized request message: This is specialization of the generic specialized request message: This is specialization of the generic
request message (e.g., blueprintsRequest), containing parameters request message (e.g., blueprintsRequest), containing parameters
that are dependent on the specific request sent to the server. A that are dependent on the specific request sent to the server. A
specialized response message MUST be included in the CCMP request specialized request message MUST be included in the CCMP request
message. The details for the specialized messages and associated message. The details for the specialized messages and associated
parameters are provided in Section 7.2.3. parameters are provided in Section 6.3.
<xs:element name="ccmpRequest" type="ccmp-request-type" /> <xs:element name="ccmpRequest" type="ccmp-request-type" />
<!-- CCMP request definition --> <!-- CCMP request definition -->
<xs:complexType name="ccmp-request-type"> <xs:complexType name="ccmp-request-type">
<xs:sequence> <xs:sequence>
<xs:element name="ccmpRequest" <xs:element name="ccmpRequest"
type="ccmp-request-message-type" /> type="ccmp-request-message-type" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- Definition of ccmp-request-message-type --> <!-- Definition of ccmp-request-message-type -->
<xs:complexType abstract="true" <xs:complexType abstract="true"
name="ccmp-request-message-type"> name="ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element name="confUserID" type="xs:string" <xs:element name="confUserID" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="confObjID" type="xs:string" <xs:element name="confObjID" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="operation" type="operationType" <xs:element name="operation" type="operationType"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="password" type="xs:string" <xs:element name="password" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 2: Structure of CCMP Request messages Figure 2: Structure of CCMP Request messages
7.2.2. CCMP Response Message 6.2. CCMP Response Message Type
A CCMP response message is comprised of the following parameters: A CCMP response message is comprised of the following parameters:
confUserId: A mandatory parameter in CCMP response messages confUserId: A mandatory parameter in CCMP response messages
containing the XCON-USERID of the conferencing client who issued containing the XCON-USERID of the conferencing client who issued
the CCMP request message. the CCMP request message.
confObjId: An optional parameter containing the XCON-URI of the confObjId: An optional parameter containing the XCON-URI of the
target conference object. target conference object.
operation: An optional parameter for CCMP response messages. This operation: An optional parameter for CCMP response messages. This
parameter is REQUIRED in all responses except for the parameter is REQUIRED in all responses except for the
"blueprintsResponse" and "confsResponse" specialized messages. "blueprintsResponse" and "confsResponse" specialized messages.
responseCode: A mandatory parameter containing the response code response-code: A mandatory parameter containing the response code
associated with the request. The response code MUST be chosen associated with the request. The response code MUST be chosen
from the codes listed in Section 7.2.2.1. from the codes listed in Section 6.4.
response-string: An optional reason string associated with the
response. In case of an error, in particular, such string can be
used to provide the client with detailed information about the
error itself.
specialized response message: This is specialization of the generic specialized response message: This is specialization of the generic
response message, containing parameters that are dependent on the response message, containing parameters that are dependent on the
specific request sent to the server (e.g., blueprintsResponse). A specific request sent to the server (e.g., blueprintsResponse). A
specialized request message SHOULD be included in the CCMP specialized response message SHOULD be included in the CCMP
response message, except in an error situation where the CCMP response message, except in an error situation where the CCMP
request message did not contain a valid specialized message. In request message did not contain a valid specialized message. In
this case, the conference server MUST return a responseCode of this case, the conference server MUST return a responseCode of
"badRequest". The details for the specialized messages and "badRequest". The details for the specialized messages and
associated parameters are provided in Section 7.2.3. associated parameters are provided in Section 6.3.
<xs:element name="ccmpResponse" type="ccmp-response-type" /> <xs:element name="ccmpResponse" type="ccmp-response-type" />
<!-- CCMP response definition --> <!-- CCMP response definition -->
<xs:complexType name="ccmp-response-type"> <xs:complexType name="ccmp-response-type">
<xs:sequence> <xs:sequence>
<xs:element name="ccmpResponse" <xs:element name="ccmpResponse"
type="ccmp-response-message-type" /> type="ccmp-response-message-type" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- Definition of ccmp-response-message-type --> <!-- Definition of ccmp-response-message-type -->
<xs:complexType abstract="true" <xs:complexType abstract="true"
name="ccmp-response-message-type"> name="ccmp-response-message-type">
<xs:sequence> <xs:sequence>
<xs:element name="confUserID" type="xs:string" <xs:element name="confUserID" type="xs:string"
minOccurs="1" maxOccurs="1" /> minOccurs="1" maxOccurs="1" />
<xs:element name="confObjID" type="xs:string" <xs:element name="confObjID" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="operation" minOccurs="0" <xs:element name="operation" type="operationType"
maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element ref="response-code" minOccurs="1" <xs:element ref="response-code" minOccurs="1"
maxOccurs="1" /> maxOccurs="1" />
<xs:element name="response-string" type="xs:string"
minOccurs="0" maxOccurs="1" />
<xs:element name="version" type="xs:positiveInteger"
minOccurs="0" maxOccurs="1" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 3: Structure of CCMP Response message Figure 3: Structure of CCMP Response message
7.2.2.1. CCMP Response Codes 6.3. Detailed messages
All CCMP response messages MUST include a "responseCode". The
following summarizes the CCMP response codes:
success: Successful completion of the requested operation.
modified: Successful completion of the requested operation, with
partial data returned in the confObjID having been modified from
the data included in the confObjID included request, either for a
"create" or a "change" operation
badRequest: Syntactically malformed request
objectNotFound: Target conference object missing at the server (it
refers to the 'confObjId' parameter in the generic request
message)
userNotFound: Target user missing at the server (it is related to
the XCON-USERID in the 'entity' attribute of the 'userInfo'
parameter when it is included in userRequests)
invalidConfUserID: User missing at the server (this code is returned
in the case of requests in which the 'confUserID' of the sender is
invalid).
invalidPassword: Target conference object's password contained in
the request is wrong.
passwordRequired: Conference password missing in a request to access
a password-protected conference object.
unauthorized: User not allowed to perform the required operation
forbidden: Operation not allowed (e.g., cancellation of a blueprint)
forbiddenDeleteParent: Cancel operation failed since the target
object is a parent of child objects which depend on it, or because
it effects, based on the 'parent-enforceable' mechanism, the
corresponding element in a child object
forbiddenChangeProtected: Update refused by the server because the
target element cannot be modified due to its implicit dependence
on the value of a parent object ('parent-enforceable' mechanism)
requestTimeout: The time required to serve the request has exceeded
the envisaged service threshold
serverInternalError: The server cannot complete the required service
due to a system internal error
notImplemented: Operation envisaged in the protocol, but not
implemented in the contacted server.
The handling of a responseCode of 'modified', 'objectNotFound',
'userNotFound', 'deleteParentFailed' and 'changeFailedProtected' are
only applicable to specific operations for specialized message
responses and the details are provided in Section 7.2.3. The
following table summarizes these responseCodes and the specialized
message and operation to which they are applicable:
+---------------+------------+------------+------------+------------+
| Response code | Create | Retrieve | Update | Delete |
+---------------+------------+------------+------------+------------+
| Modified | All create | N/A | All update | N/A |
| | requests | | requests | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| objectNotFoun | userReques | All | All update | All delete |
| d | t, | retrieve | requests | requests |
| | sidebarBy | requests, | | |
| | ValRequest | EXCEPT: | | |
| | sidebars | blueprints | | |
| | ByRefReque | Request, | | |
| | st | confsRequ | | |
| | | est | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| userNotFound | userReques | userReques | userReques | userReques |
| | t(3rd part | t | t | t |
| | yinvite | | | |
| | with thir | | | |
| | duser | | | |
| | entity) | | | |
| | (*) | | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| invalidConfUs | All create | All | All update | All delete |
| erID | requests, | retrieve | requests | requests |
| | EXCEPT: | requests | | |
| | userReques | | | |
| | twith no | | | |
| | confUserI | | | |
| | D(**) | | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| forbiddenDele | N/A | N/A | N/A | All delete |
| teParent | | | | request |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| forbiddenChan | N/A | N/A | All update | N/A |
| geProtected | | | requests | |
+---------------+------------+------------+------------+------------+
Table 1: Response codes and associated operations
(*) 'userNotFound' in answer to a 'userRequest/create' operation: in
the case of a third-party invite, this code can be returned if the
'confUserId' (contained in the 'entity' attribute of the 'userInfo'
parameter) of the user to be added is unknown. In the case above, if
instead it is the 'confUserID' of the sender of the request that is
invalid, an 'invalidConfUserID' error code is returned to the client.
(**) 'invalidConfUserID' is not sent in answers to 'userRequest/
create' messages having a 'null' confUserId, since this case is
associated with a user who is unaware of his own XCON-USERID, but
wants to enter a known conference.
In the case of a response code of 'requestTimeout', a conferencing
client MAY re-attempt the request within a period of time that would
be specific to a conference control client or conference control
server.
A response code of 'badRequest' indicates that the conference control
client sent a malformed request, which is indicative of an error in
the conference control client or in the conference control server.
The handling is specific to the conference control client
implementation (e.g., generate a log, display an error message,
etc.). It is NOT RECOMMENDED that the client re-attempt the request
in this case.
Response codes such as 'unauthorized', "forbidden' and
'operationNotAllowed' indicate the client does not have the
appropriate permissions, there is an error in the permissions, or
there is a system error in the client or conference control server,
thus re-attempting the request would likely not succeed and thus is
NOT RECOMMENDED.
Any unexpected or unknown responseCode SHOULD be treated by the
client in the same manner as a 'serverInternalError' responseCode,
the handling of which is specific to the conference control client
implementation.
7.2.3. Detailed CCMP Messages
Based on the request and response message structures described in Based on the request and response message structures described in
Section 7.2.1 and Section 7.2.2, the following summarizes the Section 6.1 and Section 6.2, the following summarizes the specialized
specialized CCMP request/response types described in this document: CCMP request/response types described in this document:
1. blueprintsRequest/blueprintsResponse 1. blueprintsRequest/blueprintsResponse
2. confsRequest/confsResponse 2. confsRequest/confsResponse
3. blueprintRequest/blueprintResponse 3. blueprintRequest/blueprintResponse
4. confRequest/confResponse 4. confRequest/confResponse
5. usersRequest/usersResponse 5. usersRequest/usersResponse
6. userRequest/userResponse 6. userRequest/userResponse
7. sidebarsByValRequest/sidebarsByValResponse 7. sidebarsByValRequest/sidebarsByValResponse
8. sidebarsByRefRequest/sidebarsByRefResponse 8. sidebarsByRefRequest/sidebarsByRefResponse
9. sidebarByValRequest/sidebarByValResponse 9. sidebarByValRequest/sidebarByValResponse
skipping to change at page 21, line 41 skipping to change at page 18, line 17
7. sidebarsByValRequest/sidebarsByValResponse 7. sidebarsByValRequest/sidebarsByValResponse
8. sidebarsByRefRequest/sidebarsByRefResponse 8. sidebarsByRefRequest/sidebarsByRefResponse
9. sidebarByValRequest/sidebarByValResponse 9. sidebarByValRequest/sidebarByValResponse
10. sidebarByRefRequest/sidebarByRefResponse 10. sidebarByRefRequest/sidebarByRefResponse
These CCMP request/response pairs use the fundamental CCMP operations These CCMP request/response pairs use the fundamental CCMP operations
as defined in Section 7 to manipulate the conference data. Table 2 as defined in Section 5.1 to manipulate the conference data. Table 1
summarizes the CCMP operations and corresponding actions that are summarizes the CCMP operations and corresponding actions that are
valid for a specific CCMP request type, noting that neither the valid for a specific CCMP request type, noting that neither the
blueprintsRequest/blueprintsResponse or confsRequest/ConfsResponse blueprintsRequest/blueprintsResponse nor confsRequest/confsResponse
require an "operation" parameter. The corresponding response MUST require an "operation" parameter. The corresponding response MUST
contain the same operation. Note that some entries are labeled "N/A" contain the same operation. Note that some entries are labeled "N/A"
indicating the operation is invalid for that request type. In the indicating the operation is invalid for that request type. In the
case of an "N/A*", the operation MAY be allowed for specific case of an "N/A*", the operation MAY be allowed for specific
privileged users or system administrators, but is not part of the privileged users or system administrators, but is not part of the
functionality included in this document. functionality included in this document.
+---------------+------------+------------+------------+------------+ +---------------+------------+------------+------------+------------+
| Operation | Retrieve | Create | Update | Delete | | Operation | Retrieve | Create | Update | Delete |
| ------------- | | | | | | ------------- | | | | |
skipping to change at page 22, line 44 skipping to change at page 19, line 44
| | | | | | | | | | | |
| usersRequest | Gets | N/A | Changes | N/A | | usersRequest | Gets | N/A | Changes | N/A |
| | specific | | specified | | | | specific | | specified | |
| | users | | users | | | | users | | users | |
| | element | | element | | | | element | | element | |
| | | | | | | | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- | | ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | | | | | | | |
| userRequest | Gets | Adds a | Changes | Deletes | | userRequest | Gets | Adds a | Changes | Deletes |
| | specific | user to a | specified | user | | | specific | user to a | specified | user |
| | user | conference | user | element as | | | user | conf (**) | user | element as |
| | element. | . * | element. | a whole. | | | element | | element | a whole |
| | | | | | | | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- | | ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | | | | | | | |
| sidebarsByVal | Gets | N/A | N/A | N/A | | sidebarsByVal | Gets | N/A | N/A | N/A |
| Request | sidebars-b | | | | | Request | sidebars-b | | | |
| | y -val | | | | | | y -val | | | |
| | element | | | | | | element | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- | | ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | | | | | | | |
| sidebarsByRef | Gets | N/A | N/A | N/A | | sidebarsByRef | Gets | N/A | N/A | N/A |
skipping to change at page 23, line 30 skipping to change at page 20, line 30
| ------------- | ---------- | ---------- | ---------- | ---------- | | ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | | | | | | | |
| sidebarByRefR | Gets a | Creates | Adds or | Removes/ | | sidebarByRefR | Gets a | Creates | Adds or | Removes/ |
| equest | sidebar | sidebar by | modifies | deletes | | equest | sidebar | sidebar by | modifies | deletes |
| | element | cloning | sidebar | entire | | | element | cloning | sidebar | entire |
| | | existing | | sidebar | | | | existing | | sidebar |
| | | conf | | | | | | conf | | |
| | | object | | | | | | object | | |
+---------------+------------+------------+------------+------------+ +---------------+------------+------------+------------+------------+
Table 2: Request Type Operation Specific Processing Table 1: Request Type Operation Specific Processing
*: This operation can involve the creation of an XCON-UserID, if the (**): This operation can involve the creation of an XCON-UserID, if
sender does not add it in the 'confUserId' parameter, or if the the sender does not add it in the "confUserId" parameter, or if the
'entity' field of the userInfo parameter is void. "entity" field of the userInfo parameter is void.
Additional parameters included in the specialized CCMP request/ Additional parameters included in the specialized CCMP request/
response messages are detailed in the subsequent sections. response messages are detailed in the subsequent sections.
7.2.3.1. blueprintsRequest and blueprintsResponse messages 6.3.1. blueprintsRequest and blueprintsResponse
A 'blueprintsRequest' (Figure 4) message is sent to request the list A "blueprintsRequest" (Figure 4) message is sent to request the list
of XCON-URIs associated with the available blueprints from the of XCON-URIs associated with the available blueprints from the
conference server. Such URIs can be subsequently used by the client conference server. Such URIs can be subsequently used by the client
to access detailed information about a specified blueprint with a to access detailed information about a specified blueprint with a
specific 'blueprintRequest' message per Section 7.2.3.3. A specific "blueprintRequest" message per Section 6.3.3. A
'blueprintsRequest' message REQUIRES no additional parameters beyond "blueprintsRequest" message REQUIRES no additional parameters beyond
those specified for the basic CCMP request message. The 'confObjId' those specified for the basic CCMP request message. The "confObjId"
and 'operation' parameters MUST NOT be included in the request or and "operation" parameters MUST NOT be included in the request or
response for this transaction. response for this transaction.
The associated 'blueprintsResponse' message SHOULD contain, as shown The associated "blueprintsResponse" message SHOULD contain, as shown
in Figure 4, a 'blueprintsInfo' parameter containing the above in Figure 4, a "blueprintsInfo" parameter containing the above
mentioned XCON-URI list. If the 'blueprintsInfo' parameter is empty, mentioned XCON-URI list. If the "blueprintsInfo" parameter is empty,
the conference control client MAY attempt to use a local default the conference control client MAY attempt to use a local default
blueprint to create conferences. However, the handling in this blueprint to create conferences. However, the handling in this
situation is specific to the conference control client situation is specific to the conference control client
implementation. implementation.
<!-- blueprintsRequest --> <!-- blueprintsRequest -->
<xs:complexType name="ccmp-blueprints-request-message-type"> <xs:complexType name="ccmp-blueprints-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/> <xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent> </xs:complexContent>
skipping to change at page 25, line 5 skipping to change at page 22, line 5
<xs:complexType name="blueprintsResponseType"> <xs:complexType name="blueprintsResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="blueprintsInfo" <xs:element name="blueprintsInfo"
type="info:uris-type" minOccurs="0"/> type="info:uris-type" minOccurs="0"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 4: Structure of the blueprintsRequest and blueprintsResponse Figure 4: Structure of the blueprintsRequest and blueprintsResponse
messages messages
7.2.3.2. confsRequest and confsResponse messages 6.3.2. confsRequest and confsResponse
A 'confsRequest' message is used to retrieve, from the server, the A "confsRequest" message is used to retrieve, from the server, the
list of XCON-URIs associated with active and registered conferences A list of XCON-URIs associated with active and registered conferences A
'confsRequest' message REQUIRES no additional parameters beyond those "confsRequest" message REQUIRES no additional parameters beyond those
specified for the basic CCMP request message. The 'confObjId' specified for the basic CCMP request message. The "confObjId"
parameter MUST NOT be included in the confsRequest message. The parameter MUST NOT be included in the confsRequest message. The
'confsRequest' message is of a "retrieve-only" type, since the sole "confsRequest" message is of a "retrieve-only" type, since the sole
purpose is to collect information available at the conference server. purpose is to collect information available at the conference server.
Thus, an 'operation' parameter MUST NOT be included in a Thus, an "operation" parameter MUST NOT be included in a
'confsRequest' message. The associated 'confsResponse' message "confsRequest" message. The associated "confsResponse" message
SHOULD contain the list of XCON-URIs in the 'confsInfo' parameter. A SHOULD contain the list of XCON-URIs in the "confsInfo" parameter. A
user, upon receipt of the response message, can interact with the user, upon receipt of the response message, can interact with the
available conference objects through further CCMP messages. available conference objects through further CCMP messages.
<!-- confsRequest --> <!-- confsRequest -->
<xs:complexType name="ccmp-confs-request-message-type"> <xs:complexType name="ccmp-confs-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/> <xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
skipping to change at page 26, line 6 skipping to change at page 23, line 6
<xs:element name="confsResponse" type="confsResponseType"/> <xs:element name="confsResponse" type="confsResponseType"/>
<xs:complexType name="confsResponseType"> <xs:complexType name="confsResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="confsInfo" <xs:element name="confsInfo"
type="info:uris-type" minOccurs="0"/> type="info:uris-type" minOccurs="0"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 5: Structure of the confsRequest and confsResponse messages Figure 5: Structure of the confsRequest and confsResponse messages
7.2.3.3. blueprintRequest and blueprintResponse messages 6.3.3. blueprintRequest and blueprintResponse
Through a 'blueprintRequest', a client can manipulate the conference Through a "blueprintRequest", a client can manipulate the conference
object associated with a specified blueprint. The request MUST object associated with a specified blueprint. The request MUST
include an 'operation' parameter and a 'confObjId' parameter. The include an "operation" parameter and a "confObjId" parameter. The
'confObjId' parameter MUST contain the XCON-URI of the blueprint, "confObjId" parameter MUST contain the XCON-URI of the blueprint,
which might have been previously retrieved through a which might have been previously retrieved through a
'blueprintsRequest' message. The blueprintRequest message SHOULD NOT "blueprintsRequest" message. The blueprintRequest message SHOULD NOT
contain an 'operation' parameter other than 'retrieve'. The contain an "operation" parameter other than "retrieve". The
'create', 'update' and 'delete' operations SHOULD NOT be included in "create", "update" and "delete" operations SHOULD NOT be included in
a 'blueprintRequest' message except in the case of privileged users a "blueprintRequest" message except in the case of privileged users
(e.g. the conference server administration staff). (e.g. the conference server administration staff).
In the case of responseCode of "success" for a 'retrieve' operation, In the case of responseCode of "success" for a "retrieve" operation,
the 'blueprintInfo' parameter MUST be included in the the "blueprintInfo" parameter MUST be included in the
'blueprintResponse' message. The 'blueprintInfo' parameter contains "blueprintResponse" message. The "blueprintInfo" parameter contains
the conference document associated with the blueprint as identified the conference document associated with the blueprint as identified
by the 'confObjID' parameter specified in the blueprintRequest. by the "confObjID" parameter specified in the blueprintRequest.
If a response code of "objectNotFound" is received in a If a response code fo "objectNotFound" is received in a
'blueprintResponse' message, it is RECOMMENDED that a conference "blueprintResponse" message, a conference control client may attempt
control client attempt to retrieve another conference blueprint if to retrieve another conference blueprint if more than one had been
more than one had been received in the "blueprintsResponse" message. received in the "blueprintsResponse" message. If there was only one
If there was only one blueprint in the "blueprintsResponse" blueprint in the "blueprintsResponse" initially, then the client
initially, then the client should send another "blueprintsRequest" should send another "blueprintsRequest" message to determine if there
message to determine if there may be new or additional blueprints for may be new or additional blueprints for the specific conferencing
the specific conferencing system. If this "blueprintsResponse" system. If this "blueprintsResponse" message contains no blueprints,
message contains no blueprints, the handling is specific to the the handling is specific to the conference control client.
conference control client.
<!-- blueprintRequest --> <!-- blueprintRequest -->
<xs:complexType name="ccmp-blueprint-request-message-type"> <xs:complexType name="ccmp-blueprint-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="blueprintRequest" /> <xs:element ref="blueprintRequest" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
skipping to change at page 28, line 5 skipping to change at page 25, line 5
<xs:complexType name="blueprintResponseType"> <xs:complexType name="blueprintResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="blueprintInfo" type="info:conference-type"/> <xs:element name="blueprintInfo" type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 6: Structure of the blueprintRequest and blueprintResponse Figure 6: Structure of the blueprintRequest and blueprintResponse
messages messages
7.2.3.4. confRequest and confResponse messages 6.3.4. confRequest and confResponse
With a 'confRequest' message, CCMP clients can manipulate conference With a "confRequest" message, CCMP clients can manipulate conference
objects associated with either active or registered conferences objects associated with either active or registered conferences
(blueprints or reservations). The request MUST include an (blueprints or reservations). The request MUST include an
'operation' parameter. Depending upon the type of 'operation' a "operation" parameter. Depending upon the type of "operation" a
'confObjId' parameter MAY be included. The 'confObjId' parameter "confObjId" parameter MAY be included. The "confObjId" parameter
contains the XCON-URI of the specific active or registered contains the XCON-URI of the specific active or registered
conference. The requirements for inclusion of 'confInfo' parameter conference. The requirements for inclusion of "confInfo" parameter
depends upon the specific 'operation' in the confRequest/confResponse depends upon the specific "operation" in the confRequest/confResponse
and are detailed below. The detailed information included in the and are detailed below. The detailed information included in the
'confInfo' parameter MUST follow the rules as specified in the XCON "confInfo" parameter MUST follow the rules as specified in the XCON
Data Model document [I-D.ietf-xcon-common-data-model]. Data Model document [I-D.ietf-xcon-common-data-model].
To create a new conference through a 'confRequest' message, two To create a new conference through a "confRequest" message, two
approaches can be considered: approaches can be considered:
1. Creation through explicit cloning: the 'confObjId' parameter MUST 1. Creation through explicit cloning: the "confObjId" parameter MUST
contain the XCON-URI of the blueprint to be cloned, while the contain the XCON-URI of the blueprint to be cloned, while the
'confInfo' parameter MUST NOT be included in the confRequest; "confInfo" parameter MUST NOT be included in the confRequest;
2. Creation through implicit cloning (also known as "direct 2. Creation through implicit cloning (also known as "direct
creation"): the 'confObjId' parameter MUST NOT be included in the creation"): the "confObjId" parameter MUST NOT be included in the
request, whereas the 'confInfo' parameter describing the request, whereas the "confInfo" parameter describing the
conference to be created MUST be included in the confRequest. conference to be created MUST be included in the confRequest.
In both cases, the confResponse, for a successful completion of a In both cases, the confResponse, for a successful completion of a
'create' operation, contains a responseCode of 'success' and MUST "create" operation, contains a responseCode of "success" and MUST
contain the XCON-URI of the created conference in the 'confObjID' contain the XCON-URI of the created conference in the "confObjID"
parameter. In addition, the 'confInfo' parameter transporting the parameter. In addition, the "confInfo" parameter transporting the
created conference document MUST be included. Obviously, the newly created conference document MAY be included. Obviously, the newly
created object can be manipulated by the client through a subsequent created object can be manipulated by the client through a subsequent
'update' operation. For example, after the creation and addition of "update" operation. For example, after the creation and addition of
the participants, the creator may want to lock the conference object. the participants, the creator may want to lock the conference object.
This can be accomplished with a confRequest with an operation of This can be accomplished with a confRequest with an operation of
'update' by setting the 'locked' element in the confInfo included in "update" by setting the "locked" element in the confInfo included in
the confRequest message described below. the confRequest message described below.
In the case of a confRequest with a 'retrieve' operation, the In the case of a confRequest with a "retrieve" operation, the
'confObjId' representing the XCON-URI of the target conference the "confObjId" representing the XCON-URI of the target conference the
conference control client MUST be included and the 'confInfo' conference control client MUST be included and the "confInfo"
parameter SHOULD NOT be included in the request. The conferencing parameter SHOULD NOT be included in the request. The conferencing
server MUST ignore any 'confInfo' parameter that is received in a server MUST ignore any "confInfo" parameter that is received in a
'confRequest' and this 'confInfo' parameter MUST NOT be included in "confRequest" and this "confInfo" parameter MUST NOT be included in
the confResponse. If the confResponse for the 'retrieve' operation the confResponse. If the confResponse for the "retrieve" operation
contains a responseCode of 'success', the 'confInfo' parameter MUST contains a responseCode of "success", the "confInfo" parameter MUST
be included in the response. The 'confInfo' parameter MUST contain be included in the response. The "confInfo" parameter MUST contain
the entire conference document describing the target conference the entire conference document describing the target conference
object in its current state. object in its current state.
In case of of a confRequest with an 'update' operation, the In case of a confRequest with an "update" operation, the "confInfo"
'confInfo' and 'confObjID' MUST be included in the request. The and "confObjID" MUST be included in the request. The "confInfo"
'confInfo' represents an object of type "conference-type" containing represents an object of type "conference-type" containing all the
all the changes to be applied to the conference whose identifier is changes to be applied to the conference whose identifier is
'confObjId'. In the case of a confResponse with a responseCode of "confObjId". In the case of a confResponse with a responseCode of
'success', no additional information is REQUIRED in the "success", no additional information is required in the
'confResponse' message. A responseCode of 'success' indicates that "confResponse" message. A responseCode of "success" indicates that
the referenced conference document has not been changed by the the referenced conference document has been changed by the conference
conference server. However, if the target conference object was not server. A responseCode of "changeFailedProtected" indicates that the
updated exactly as indicated by the client a responseCode of conferencing client is not allowed to make the changes reflected in
'modified' MUST be included in the 'confResponse' and the 'confInfo' the "confInfo" in the initial request. This could be due to
parameter MUST contain the entire conference document to which any policies, roles, specific privileges, etc.), with the reason specific
changes have been applied. A responseCode of 'changeFailedProtected' to a conferencing system and its configuration. Thus, it is
indicates that the conferencing client is not allowed to make the RECOMMENDED that the client continue using the previous version of
changes reflected in the 'confInfo' in the initial request. This the "confInfo", if the conference was active. If the conference was
could be due to policies, roles, specific privileges, etc.), with the not active, it is RECOMMENDED that the client revert to an original
reason specific to a conferencing system and its configuration. version of the blueprint or use another blueprint - one previously
Thus, it is RECOMMENDED that the client continue using the previous retrieved with a blueprintRequest or one obtained via a new
version of the 'confInfo', if the conference was active. If the blueprintsRequest/blueprintRequest sequence.
conference was not active, it is RECOMMENDED that the client revert
to an original version of the blueprint or use another blueprint -
one previously retrieved with a blueprintRequest or one obtained via
a new blueprintsRequest/blueprintRequest sequence.
In the case of a confRequest with a 'delete' operation, the In the case of a confRequest with a "delete" operation, the
'confObjId' representing the XCON-URI of the target conference MUST "confObjId" representing the XCON-URI of the target conference MUST
be included and the 'confInfo' SHOULD NOT be included in the request. be included and the "confInfo" SHOULD NOT be included in the request.
The conferencing server MUST ignore any 'confInfo' parameter that is The conferencing server MUST ignore any "confInfo" parameter that is
received. The confResponse MUST contain the same 'confObjId'that was received. The confResponse MUST contain the same "confObjId" that
included in the confRequest. The confResponse MUST contain a was included in the confRequest. The confResponse MUST contain a
responseCode of 'success' if the targeted conference is successfully responseCode of "success" if the targeted conference is successfully
deleted. If the confResponse for the 'retrieve' operation contains a deleted. If the confResponse for the "retrieve" operation contains a
responseCode of 'success', the confResponse SHOULD NOT contain the responseCode of "success", the confResponse SHOULD NOT contain the
'confInfo' parameter. If the conferencing server cannot delete the "confInfo" parameter. If the conferencing server cannot delete the
conference referenced by the 'confObjId' received in the confRequest conference referenced by the "confObjId" received in the confRequest
because it is the parent of another conference object that is in use, because it is the parent of another conference object that is in use,
the conferencing server MUST return a responseCode of the conferencing server MUST return a responseCode of
'deleteParentFailed'. "deleteParentFailed".
The schema for the confRequest/confResponse pair is shown in The schema for the confRequest/confResponse pair is shown in
Figure 7. Figure 7.
<!-- confRequest --> <!-- confRequest -->
<xs:complexType name="ccmp-conf-request-message-type"> <xs:complexType name="ccmp-conf-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="confRequest" /> <xs:element ref="confRequest" />
skipping to change at page 30, line 50 skipping to change at page 27, line 50
<xs:element name="confResponse" type="confResponseType" /> <xs:element name="confResponse" type="confResponseType" />
<xs:complexType name="confResponseType"> <xs:complexType name="confResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="confInfo" type="info:conference-type"/> <xs:element name="confInfo" type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 7: Structure of the confRequest and confResponse messages Figure 7: Structure of the confRequest and confResponse messages
The following provides an example of the 'confInfo' parameter The following provides an example of the "confInfo" parameter
required to change the title of a conference: required to change the title of a conference:
<conf-info entity="123"> <conf-info entity="123">
<conference-description> <conference-description>
<display-text>New conference title</display-text> <display-text>New conference title</display-text>
</conference-description> </conference-description>
</conf-info> </conf-info>
Figure 8: Updating a conference object: modifying the title of a Figure 8: Updating a conference object: modifying the title of a
conference conference
Similarly, to remove the title of an existing conference, an 'update' Similarly, to remove the title of an existing conference, an "update"
operation carrying the following 'confInfo' parameter would do the operation carrying the following "confInfo" parameter would do the
job. job.
<conf-info entity="123"> <conf-info entity="123">
<conference-description> <conference-description>
<display-text/> <display-text/>
</conference-description> </conference-description>
</conf-info> </conf-info>
Figure 9: Updating a conference object: removing the title of a Figure 9: Updating a conference object: removing the title of a
conference conference
7.2.3.5. usersRequest and usersResponse messages 6.3.5. usersRequest and usersResponse
Through a usersRequest message the CCMP client manipulates the Through a usersRequest message the CCMP client manipulates the
<users> element of the conference document associated with the <users> element of the conference document associated with the
conference identified by the 'confObjId' parameter. Inside the conference identified by the "confObjId" parameter. Inside the
<users> element, along with the list of conference users, there is <users> element, along with the list of conference users, there is
information that the client may be interested in controlling, such as information that the client may be interested in controlling, such as
the lists of users to which access to the conference is allowed/ the lists of users to which access to the conference is allowed/
denied, conference participation policies, etc.; for this reason, a denied, conference participation policies, etc.; for this reason, a
customized message has been designed to allow for the manipulation of customized message has been designed to allow for the manipulation of
this specific part of a conference document. this specific part of a conference document.
A 'usersInfo' parameter MAY be included in a usersRequest message A "usersInfo" parameter MAY be included in a usersRequest message
depending upon the operation. If the 'userInfo' parameter is depending upon the operation. If the "usersInfo" parameter is
included in the usersRequest message, the parameter MUST be compliant included in the usersRequest message, the parameter MUST be compliant
with the <users> field of the XCON data model. with the <users> field of the XCON data model.
Two operations are allowed for a "usersRequest" message: Two operations are allowed for a "usersRequest" message:
1. retrieve: In this case the request SHOULD NOT include a 1. "retrieve": In this case the request MUST NOT include a
'usersInfo' parameter, while a successful response MUST contain "usersInfo" parameter, while a successful response MUST contain
the desired <users> element in the 'usersInfo' parameter. The the desired <users> element in the "usersInfo" parameter. The
conference server MUST be ignore a 'usersInfo' parameter if it is conference server MUST be ignore a "usersInfo" parameter if it is
received in a request with a 'retrieve' operation. received in a request with a "retrieve" operation.
2. update: In this case, the 'usersInfo' parameter MUST contain the 2. update: In this case, the "usersInfo" parameter MUST contain the
modifications to be applied to the referred <users> element. If modifications to be applied to the referred <users> element. If
the responseCode is 'success', then the 'usersInfo' parameter the responseCode is "success", then the "usersInfo" parameter
SHOULD NOT be returned. Any 'usersInfo' parameter that is SHOULD NOT be returned. Any "usersInfo" parameter that is
returned SHOULD be ignored. If the responseCode is 'modified', returned SHOULD be ignored. A responseCode of
the 'usersInfo' parameter MUST be included in the response. The "changeFailedProtected" indicates that the conferencing client is
'usersInfo' reflects to the client the (partial) modifications not allowed to make the changes reflected in the "usersInfo" in
that have been applied. A responseCode of
'changeFailedProtected' indicates that the conferencing client is
not allowed to make the changes reflected in the 'usersInfo' in
usersRequest message. This could be due to policies, roles, usersRequest message. This could be due to policies, roles,
specific privileges, etc.), with the reason specific to a specific privileges, etc.), with the reason specific to a
conferencing system and its configuration. Thus, it is conferencing system and its configuration. Thus, it is
RECOMMENDED that the client continue using the previous version RECOMMENDED that the client continue using the previous version
of the 'usersInfo'. of the "usersInfo".
Operations of 'create' and 'delete' are not applicable to a Operations of "create" and "delete" are not applicable to a
usersRequest message and MUST NOT be considered by the server, which usersRequest message and MUST NOT be considered by the server, which
means that a responseCode of 'forbidden' MUST be included in the means that a responseCode of "forbidden" MUST be included in the
usersResponse message. usersResponse message.
<!-- usersRequest --> <!-- usersRequest -->
<xs:complexType name="ccmp-users-request-message-type"> <xs:complexType name="ccmp-users-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="usersRequest" /> <xs:element ref="usersRequest" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
skipping to change at page 34, line 5 skipping to change at page 31, line 5
<xs:element name="usersResponse" type="usersResponseType" /> <xs:element name="usersResponse" type="usersResponseType" />
<xs:complexType name="usersResponseType"> <xs:complexType name="usersResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="usersInfo" type="info:users-type"/> <xs:element name="usersInfo" type="info:users-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 10: Structure of the usersRequest and usersResponse messages Figure 10: Structure of the usersRequest and usersResponse messages
7.2.3.6. userRequest and userResponse messages 6.3.6. userRequest and userResponse
A "userRequest" message is used to manipulate <user> elements inside A "userRequest" message is used to manipulate <user> elements inside
a conference document associated with a conference identified by the a conference document associated with a conference identified by the
'confObjId' parameter. Besides retrieving information about a "confObjId" parameter. Besides retrieving information about a
specific conference user, the message is used to request that the specific conference user, the message is used to request that the
conference server either create, modify, or delete information about conference server either create, modify, or delete information about
a user. A "userRequest" message MUST include the 'confObjID', the a user. A "userRequest" message MUST include the "confObjID", the
'operation' parameter, and MAY include a 'userInfo' parameter "operation" parameter, and MAY include a "userInfo" parameter
containing the detailed user's information depending upon the containing the detailed user's information depending upon the
operation and whether the 'userInfo' has already been populated for a operation and whether the "userInfo" has already been populated for a
specific user. Note that a user may not necessarily be a specific user. Note that a user may not necessarily be a
conferencing control client (i.e., some participants in a conference conferencing control client (i.e., some participants in a conference
are not "XCON aware"). are not "XCON aware").
We remark that an XCON-USERID SHOULD be assigned to each and every An XCON-USERID SHOULD be assigned to each and every user subscribed
user subscribed to the system. In such a way, a user who is not a to the system. In such a way, a user who is not a conference
conference participant can make requests (provided she has participant can make requests (provided she has successfully passed
successfully passed AAA checks), like creating a conference, AAA checks), like creating a conference, retrieving conference
retrieving conference information, etc.. information, etc..
Conference users can be created in a number of different ways. In Conference users can be created in a number of different ways. In
each of these cases the operation MUST be set to "create" in the each of these cases the operation MUST be set to "create" in the
userRequest message. Each of the userResponse messages for these userRequest message. Each of the userResponse messages for these
cases MUST include the 'confObjID', 'confUserID', 'operation' and cases MUST include the "confObjID", "confUserID", "operation" and
'responseCode' parameters. In the case of a response code of "responseCode" parameters. In the case of a response code of
'success', the userResponse message MAY include the 'userInfo' "success", the userResponse message MAY include the "userInfo"
parameter depending upon the manner in which the user was created: parameter depending upon the manner in which the user was created:
o Conferencing client with an XCON-USERID adds itself to the o Conferencing client with an XCON-USERID adds itself to the
conference: In this case, the 'userInfo' parameter MAY be included conference: In this case, the "userInfo" parameter MAY be included
in the userRequest. The 'userInfo' parameter MUST contain a in the userRequest. The "userInfo" parameter MUST contain a
<user> element (compliant with the XCON data model) and the <user> element (compliant with the XCON data model) and the
'entity' attribute MUST be set to a value which represents the "entity" attribute MUST be set to a value which represents the
XCON-USERID of the user initiating the request. No additional XCON-USERID of the user initiating the request. No additional
parameters beyond those previously described are REQUIRED in the parameters beyond those previously described are required in the
userResponse message, in the case of a responseCode of 'success'. userResponse message, in the case of a responseCode of "success".
o Conferencing client acts on behalf of a third user whose XCON- o Conferencing client acts on behalf of a third user whose XCON-
USERID is known: in this case, the 'userInfo' parameter MUST be USERID is known: in this case, the "userInfo" parameter MUST be
included in the userRequest. The 'userInfo' parameter MUST included in the userRequest. The "userInfo" parameter MUST
contain a <user> element and the 'entity' attribute value MUST be contain a <user> element and the "entity" attribute value MUST be
set to the XCON-USERID of the third user in question. No set to the XCON-USERID of the third user in question. No
additional parameters beyond those previously described are additional parameters beyond those previously described are
REQUIRED in the userResponse message, in the case of a required in the userResponse message, in the case of a
responseCode of 'success'. responseCode of "success".
o A conferencing client who has no XCON-USERID and who wants to o A conferencing client who has no XCON-USERID and who wants to
enter, via CCMP, a conference whose identifier is known. In such enter, via CCMP, a conference whose identifier is known. In such
case, a side-effect of the request is that the user is provided case, a side-effect of the request is that the user is provided
with an appropriate XCON-USERID. The involved messages with an appropriate XCON-USERID. The involved messages
(userRequest and userResponse) in such case should look like the (userRequest and userResponse) in such case should look like the
following: following:
Request fields: Request fields:
confUserId=null; confUserId=null;
confObjId=confXYZ; confObjId=confXYZ;
operation=create; operation=create;
userInfo= userInfo=
<userInfo entity=null> <userInfo entity=null>
<endpoint entity=''sip:GHIL345@blablabla''> <endpoint entity="sip:GHIL345@blablabla">
... ...
Response fields (in case of success): Response fields (in case of success):
confUserId=user345; confUserId=user345;
confObjId=confXYZ; confObjId=confXYZ;
operation=create; operation=create;
response-code=success; response-code=success;
userInfo=null; //or the entire userInfo object userInfo=null; //or the entire userInfo object
Figure 11: userRequest and userResponse in the absence of an xcon- Figure 11: userRequest and userResponse in the absence of an xcon-
userid userid
o Conferencing client is unaware of the XCON-USERID of a third user: o Conferencing client is unaware of the XCON-USERID of a third user:
In this case, the 'entity' attribute MUST NOT be included in the In this case, the "entity" attribute MUST NOT be included in the
request. The XCON-USERID generated by the conference server for request. The XCON-USERID generated by the conference server for
such a user MUST also be returned to the client as the value of such a user MUST also be returned to the client as the value of
the 'entity' attribute in the 'userInfo' parameter of the response the "entity" attribute in the "userInfo" parameter of the response
if the responseCode is "success". This scenario is mainly if the responseCode is "success". This scenario is mainly
intended to support the case whereby an XCON aware client is added intended to support the case whereby an XCON aware client is added
to a conference by a third party, e.g. the chairperson of the to a conference by a third party, e.g. the chairperson of the
conference. conference.
o Conferencing client obtains a new user profile in the context of a o Conferencing client obtains a new user profile in the context of a
conference: this case is handled in the same manner as the conference: this case is handled in the same manner as the
previous case associated with the creation of a user on behalf of previous case associated with the creation of a user on behalf of
a third party when the XCON-USERID is unknown, thus indicating to a third party when the XCON-USERID is unknown, thus indicating to
the conference server that the client wants a new XCON-USERID and the conference server that the client wants a new XCON-USERID and
associated 'userInfo' parameter to be allocated and populated associated "userInfo" parameter to be allocated and populated
respectively. respectively.
In both cases, the confResponse, for a successful completion of a In the case of a userRequest with a "retrieve" operation, the
'create' operation, contains a responseCode of 'success' and MUST "confObjId" representing the XCON-URI of the target conference MUST
contain the XCON-URI of the created conference in the 'confObjID' be included. The "confUserId" MUST be included in the userRequest
parameter. In addition, the 'confInfo' parameter transporting the message. This "confUserId" indicates the specific <user> element in
created conference document MUST be included. Obviously, the newly XCON data model, as reflected by the "entity" attribute in the <user>
created object can be manipulated by the client through a subsequent element that the conference client is requesting to retrieve. The
'update' operation. "userInfo" parameter MUST NOT be included in the request. The
conferencing server MUST ignore any "userInfo" parameter that is
In the case of a userRequest with a 'retrieve' operation, the received in a "userRequest" and this "userInfo" parameter MUST NOT be
'confObjId' representing the XCON-URI of the target conference MUST included in the userResponse. If the userResponse for the "retrieve"
be included. The 'confUserId' MUST be included in the userRequest operation contains a responseCode of "success", the "userInfo"
message. This 'confUserId' indicates the specific <user> element in
XCON data model, as reflected by the 'entity' attribute in the <user>
element that the conference client is requesting to retrive. The
'userInfo' parameter SHOULD NOT be included in the request. The
conferencing server MUST ignore any 'userInfo' parameter that is
received in a 'userRequest' and this 'userInfo' parameter MUST NOT be
included in the userResponse. If the userResponse for the 'retrieve'
operation contains a responseCode of 'success', the 'userInfo'
parameter MUST be included in the response. parameter MUST be included in the response.
In case of of a userRequest with an 'update' operation, the In case of a userRequest with an "update" operation, the "confObjID",
'confObjID', 'confUserID' and 'userInfo' MUST be included in the "confUserID" and "userInfo" MUST be included in the request. The
request. The 'userInfo' is of type "user-type" and contains all the "userInfo" is of type "user-type" and contains all the changes to be
changes to be applied to a specific <user> element in the conference applied to a specific <user> element in the conference object
object identified by the 'confObjId' in the userRequest message. The identified by the "confObjId" in the userRequest message. In the
'entity' attribute in the 'userInfo' MUST be equal to the case of a user Response with a responseCode of "success", no
'confUserID' in the userRequest message. In the case of a user additional information is required in the "confResponse" message. A
Response with a responseCode of 'success', no additional information responseCode of "success" indicates that the referenced user element
is REQUIRED in the 'confResponse' message. A responseCode of has been updated by the conference server. A responseCode of
'success' indicates that the referenced user element has been updated "changeFailedProtected" indicates that the conferencing client is not
by the conference server. However, if the specific <user> element allowed to make the changes reflected in the "userInfo" in the
was not updated exactly as indicated by the client a responseCode of
'modified' MUST be included in the 'confResponse' and the 'userInfo'
parameter MUST contain the entire <user> element which to which the
conference server has applied changes. A responseCode of
'changeFailedProtected' indicates that the conferencing client is not
allowed to make the changes reflected in the 'userInfo' in the
initial request. This could be due to policies, roles, specific initial request. This could be due to policies, roles, specific
privileges, etc., with the reason specific to a conferencing system privileges, etc., with the reason specific to a conferencing system
and its configuration. Thus, it is RECOMMENDED that the client and its configuration. Thus, it is RECOMMENDED that the client
continue using the previous version of the 'userInfo'. continue using the previous version of the "userInfo".
In the case of a userRequest with a 'delete' operation, the In the case of a userRequest with a "delete" operation, the
'confObjId' representing the XCON-URI of the target conference and "confObjId" representing the XCON-URI of the target conference and
the 'confUserID' associated with the specific <user> element (i.e., the "confUserID" associated with the specific <user> element (i.e.,
matching the 'entity' attribute) that the conferencing client is matching the "entity" attribute) that the conferencing client is
requesting be deleted MUST be included in the userRequest message. requesting to be deleted MUST be included in the userRequest message.
The 'userInfo' SHOULD NOT be included in the request. The The userResponse MUST contain the same "confObjId" that was included
conferencing server MUST ignore any 'userInfo' parameter that is in the userRequest. The userResponse MUST contain a responseCode of
received. The userResponse MUST contain the same 'confObjId' that "success" if the target <user> element has been successfully deleted.
was included in the userRequest. The userResponse MUST contain a If the userResponse for the "delete" operation contains a
responseCode of 'success' if the <user> element associated with the responseCode of "success", the userResponse MUST NOT contain the
specific 'confUserId' is successfully deleted. If the userResponse "userInfo" parameter.
for the 'retrieve' operation contains a responseCode of 'success',
the userResponse SHOULD NOT contain the 'userInfo' parameter.
<!-- userRequest --> <!-- userRequest -->
<xs:complexType name="ccmp-user-request-message-type"> <xs:complexType name="ccmp-user-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="userRequest" /> <xs:element ref="userRequest" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
skipping to change at page 39, line 5 skipping to change at page 35, line 5
<xs:element name="userResponse" type="userResponseType" /> <xs:element name="userResponse" type="userResponseType" />
<xs:complexType name="userResponseType"> <xs:complexType name="userResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="userInfo" type="info:user-type"/> <xs:element name="userInfo" type="info:user-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 12: Structure of the userRequest and userResponse messages Figure 12: Structure of the userRequest and userResponse messages
7.2.3.7. sidebarsByValRequest and sidebarsByValResponse messages 6.3.7. sidebarsByValRequest and sidebarsByValResponse
A "sidebarsByValRequest" is used to execute a retrieve-only operation A "sidebarsByValRequest" is used to execute a retrieve-only operation
on the <sidebars-by-val> field of the conference object represented on the <sidebars-by-val> field of the conference object represented
by the 'confObjId'. The request MUST include an 'operation' of by the "confObjId". The "sidebarsByValRequest" message is of a
"retrieve" and a 'confObjId' parameter. Operations of 'create', "retrieve-only" type, so an "operation" parameter MUST NOT be
'update' and 'delete' MUST NOT be included in a sidebarsByValRequest included in a "sidebarsByValRequest" message. A
message. A "sidebarsByValResponse" with a responseCode of 'success' "sidebarsByValResponse" with a responseCode of "success" MUST contain
MUST contain a 'sidebarsByValInfo' parameter containing the desired a "sidebarsByValInfo" parameter containing the desired <sidebars-by-
<sidebars-by-val> element. The 'sidebarsByValInfo' parameter val> element. The "sidebarsByValInfo" parameter contains the list of
contains the identifiers of the sidebars derived from the main the conference objects associated with the sidebars by value derived
conference in the form of XCON-URIs. The retrieved sidebars can then from the main conference. The retrieved sidebars can then be updated
be updated or deleted using the "sidebarByValRequest" message, which or deleted using the "sidebarByValRequest" message, which is
is described in Section 7.2.3.8. described in Section 6.3.8.
<!-- sidebarsByValRequest --> <!-- sidebarsByValRequest -->
<xs:complexType name="ccmp-sidebarsByVal-request-message-type"> <xs:complexType name="ccmp-sidebarsByVal-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarsByValRequest"/> <xs:element ref="sidebarsByValRequest"/>
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
skipping to change at page 41, line 7 skipping to change at page 37, line 7
<xs:complexType name="sidebarsByValResponseType"> <xs:complexType name="sidebarsByValResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarsByValInfo" <xs:element name="sidebarsByValInfo"
type="info:sidebars-by-val-type"/> type="info:sidebars-by-val-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 13: Structure of the sidebarsByValRequest and Figure 13: Structure of the sidebarsByValRequest and
sidebarsByValResponse messages sidebarsByValResponse messages
7.2.3.8. sidebarByValRequest and sidebarByValResponse messages 6.3.8. sidebarByValRequest and sidebarByValResponse
A sidebarByValRequest message MUST contain the 'operation' parameter A sidebarByValRequest message MUST contain the "operation" parameter
which discriminates among retrieval, creation, modification and which discriminates among retrieval, creation, modification and
deletion of a specific sidebar. The other required parameters depend deletion of a specific sidebar. The other required parameters depend
upon the type of operation. upon the type of operation.
In the case of a 'create' operation, the 'confObjId' parameter MUST In the case of a "create" operation, the "confObjId" parameter MUST
be included in the sidebyValRequest message. In this case, the be included in the sidebyValRequest message. In this case, the
'confObjId' parameter contains the XCON-URI of the main conference in "confObjID" parameter contains the XCON-URI of the main conference in
which the sidebar is to be created. The 'sidebarByValInfo' parameter which the sidebar is to be created. The "sidebarByValInfo" parameter
SHOULD NOT be included in the request, since, as envisaged in the SHOULD NOT be included in the request, since, as envisaged in the
XCON framework ([RFC5239]), sidebars are always created by cloning XCON framework ([RFC5239]), sidebars are always created by cloning
the main conference. Any 'sidebarByValInfo' included in the request the main conference. Any "sidebarByValInfo" included in the request
MUST be ignored. The conference server sets the 'active' element to MUST be ignored. The conference server sets the "active" element to
'false' of the cloned conference to reflect that it is a "reserved" "false" of the cloned conference to reflect that it is a "reserved"
conference. The conference server MUST update the conference object conference. The conference server MUST update the conference object
reflected by the 'confObjID' parameter, in the sidebarbyVal request reflected by the "confObjID" parameter, in the sidebarbyVal request
message, from which the sidebar was created to reflect the newly message, from which the sidebar was created to reflect the newly
created sidebar. The newly created conference object MUST be created sidebar. The newly created conference object MAY be included
included in the response in the 'sidebarByValInfo' parameter, if the in the response in the "sidebarByValInfo" parameter, if the
responseCode is 'success'. The URI for the conference object responseCode is "success". The URI of the conference object
associated with the newly created sidebar object MUST appear in the associated with the newly created sidebar object MUST appear in the
'entity' attribute in the 'sidebarByValInfo'. The conference server "confObjId" parameter of the response. The conference server can
can notify any conferencing clients that have subscribed to the notify any conferencing clients that have subscribed to the
conference event package, and are authorized to receive the conference event package, and are authorized to receive the
notifications, of the addition of the sidebar to the conference. notifications, of the addition of the sidebar to the conference.
In the case of a 'sidebarByVal' request with an operation of In the case of a "sidebarByVal" request with an operation of
'retrieve', the URI for the conference object created for the "retrieve", the URI for the conference object created for the sidebar
sidebar, as reflected by the 'entity' attribute in the (received in the response to a "create" operation or in a
'sidebarByValInfo', received in the response to a 'create' operation sidebarsByValResponse message) MUST be included in the "confObjID"
or in a sidebarsByValResponse message, MUST be included in the parameter in the request. This "retrieve" operation is handled by
'confObjID' parameter in the request. This 'retrieve' operation is the conference server in the same manner as a "retrieve" operation
handled by the conference server in the same manner as a 'retrieve' included in a confRequest message as detailed in Section 6.3.4.
operation included in a confRequest message as detailed in
Section 7.2.3.4.
In the case of a 'sidebarByVal' request with an operation of In the case of a "sidebarByVal" request with an operation of
'update', the 'sidebarByValInfo' MUST also be included in the "update", the "sidebarByValInfo" MUST also be included in the
request. The 'entity' attribute in the 'sidebarByValInfo' identifies request. The "confObjID" parameter contained in the request message
the specific sidebar instance to be updated. The URI for the identifies the specific sidebar instance to be updated. An "update"
conference object containing the specific sidebar-by-value element to operation on the "sidebarByValInfo" is handled by the conference
be updated MUST be included in the 'confObjID' parameter in the server in the same manner as an "update" operation on the confInfo
request. An 'update' operation on the 'sidebarByValInfo' is handled included in a confRequest message as detailed in Section 6.3.4.
by the conference server in the same manner as an 'update' operation
on the confInfo included in a confRequest message as detailed in
Section 7.2.3.4.
If an 'operation' of 'delete' is included in the sidebarByVal If an "operation" of "delete" is included in the sidebarByVal
request, the 'sidebarByValInfo' parameter SHOULD NOT be included in request, the "sidebarByValInfo" parameter MUST NOT be included in the
the request. Any 'sidebarByValInfo' included in the request SHOULD request. Any "sidebarByValInfo" included in the request MUST be
be ignored by the conference server. The URI for the conference ignored by the conference server. The URI for the conference object
object for the sidebar, as reflected by the 'entity' attribute in the associated with the sidebar MUST be included in the "confObjID"
'sidebarByValInfo', received in the response to a 'create' operation parameter in the request. If the specific conferencing user as
or in a sidebarsByValResponse message, MUST be included in the reflected by the "confUserID" in the request is authorized to delete
'confObjID' parameter in the request. If the specific conferencing the conference, the conference server deletes the conference object
user as reflected by the 'confUserID' in the request is authorized to reflected by the "confObjID" parameter and updates the data in the
delete the conference, the conference server deletes the conference conference object from which the sidebar was cloned. The conference
object reflected by the 'confObjID' parameter and updates the data in server can notify any conferencing clients that have subscribed to
the conference object from which the sidebar was cloned. The the conference event package, and are authorized to receive the
conference server can notify any conferencing clients that have notifications, of the deletion of the sidebar to the conference.
subscribed to the conference event package, and are authorized to
receive the notifications, of the deletion of the sidebar to the
conference.
<!-- sidebarByValRequest --> <!-- sidebarByValRequest -->
<xs:complexType name="ccmp-sidebarByVal-request-message-type"> <xs:complexType name="ccmp-sidebarByVal-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarByValRequest"/> <xs:element ref="sidebarByValRequest"/>
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
skipping to change at page 44, line 7 skipping to change at page 40, line 7
<xs:complexType name="sidebarByValResponseType"> <xs:complexType name="sidebarByValResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarByValInfo" <xs:element name="sidebarByValInfo"
type="info:conference-type"/> type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 14: Structure of the sidebarByValRequest and Figure 14: Structure of the sidebarByValRequest and
sidebarByValResponse messages sidebarByValResponse messages
7.2.3.9. sidebarsByRefRequest and sidebarsByRefResponse messages 6.3.9. sidebarsByRefRequest and sidebarsByRefResponse
Similar to the sidebarsByValRequest, a sidebarsByRefRequest can be Similar to the sidebarsByValRequest, a sidebarsByRefRequest can be
invoked to retrieve the <sidebars-by-ref> element of the conference invoked to retrieve the <sidebars-by-ref> element of the conference
object identified by the 'confObjId' parameter. The 'confObjID' object identified by the "confObjId" parameter. The
parameter MUST be included in the request. An operation of "sidebarsByRefRequest" message is of a "retrieve-only" type, so an
'retrieve' MUST also be included in the request. Operations of "operation" parameter MUST NOT be included in a
'create', 'update' and 'delete' MUST NOT be included in a "sidebarsByRefRequest" message. In the case of a responseCode of
sidebarsByValRequest message. In the case of a responseCode of "success", the "sidebarsByRefInfo" parameter, containing the
'success', the 'sidebarsByRefInfo' parameter, containing the
<sidebars-by-ref> element of the conference object, MUST be included <sidebars-by-ref> element of the conference object, MUST be included
in the response. The <sidebars-by-ref> element represents the set of in the response. The <sidebars-by-ref> element represents the set of
URIs of the sidebars associated with the main conference, whose URIs of the sidebars associated with the main conference, whose
description (in the form of a standard XCON conference document) is description (in the form of a standard XCON conference document) is
external to the main conference itself. Through the retrieved URIs, external to the main conference itself. Through the retrieved URIs,
it is then possible to access single sidebars using the it is then possible to access single sidebars using the
"sidebarByRef" request message, described in Section 7.2.3.10. "sidebarByRef" request message, described in Section 6.3.10.
<!-- sidebarsByRefRequest --> <!-- sidebarsByRefRequest -->
<xs:complexType name="ccmp-sidebarsByRef-request-message-type"> <xs:complexType name="ccmp-sidebarsByRef-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarsByRefRequest"/> <xs:element ref="sidebarsByRefRequest"/>
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
skipping to change at page 46, line 7 skipping to change at page 42, line 7
<xs:complexType name="sidebarsByRefResponseType"> <xs:complexType name="sidebarsByRefResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarsByRefInfo" <xs:element name="sidebarsByRefInfo"
type="info:uris-type"/> type="info:uris-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 15: Structure of the sidebarsByRefRequest and Figure 15: Structure of the sidebarsByRefRequest and
sidebarsByRefResponse messages sidebarsByRefResponse messages
7.2.3.10. sidebarByRefRequest and sidebarByRefResponse messages 6.3.10. sidebarByRefRequest and sidebarByRefResponse
A sidebarByRefRequest message MUST contain the 'operation' parameter A sidebarByRefRequest message MUST contain the "operation" parameter
which discriminates among retrieval, creation, modification and which discriminates among retrieval, creation, modification and
deletion of a specific sidebar. The other required parameters depend deletion of a specific sidebar. The other required parameters depend
upon the type of operation. upon the type of operation.
In the case of an 'operation of 'create', the 'confObjId' parameter In the case of an "operation of "create", the "confObjId" parameter
representing the XCON-URI of the conference from which the sidebar is representing the XCON-URI of the conference from which the sidebar is
to be created (cloned) MUST be included in all sidebarByRefRequest to be created (cloned) MUST be included in all sidebarByRefRequest
messages. The'sidebarByRefInfo' parameter SHOULD NOT be included in messages. The "sidebarByRefInfo" parameter SHOULD NOT be included in
the request, since, as envisaged in the XCON framework ([RFC5239]), the request, since, as envisaged in the XCON framework ([RFC5239]),
sidebars are always created by cloning the main conference. Any sidebars are always created by cloning the main conference. Any
'sidebarByRefInfo' included in the request MUST be ignored. If the "sidebarByRefInfo" included in the request MUST be ignored. If the
creation of the sidebar is successful, the conference server MUST creation of the sidebar is successful, the conference server MUST
update the 'sidebars-by-ref' element in the conference object from update the "sidebars-by-ref" element in the conference object from
which the sidebar was created (i.e., as identified by the 'confObjID' which the sidebar was created (i.e., as identified by the "confObjID"
in the original sidebarByRef request), with the URI for the newly in the original sidebarByRef request), with the URI for the newly
created sidebar. The newly created conference object MUST be created sidebar. The newly created conference object MAY be included
included in the response in the 'sidebarByRefInfo' parameter with a in the response in the "sidebarByRefInfo" parameter with a
responseCode 'success'. The URI for the conference object associated responseCode "success". The URI for the conference object associated
with the newly created sidebar object MUST appear in the 'entity' with the newly created sidebar object MUST appear in the "confObjID"
attribute in the 'sidebarByRefInfo'. The conference server can parameter of the response. The conference server can notify any
notify any conferencing clients that have subscribed to the conferencing clients that have subscribed to the conference event
conference event package, and are authorized to receive the package, and are authorized to receive the notifications, of the
notifications, of the addition of the sidebar to the conference. addition of the sidebar to the conference.
In the case of a 'sidebarByRef' request with an operation of In the case of a "sidebarByRef" request with an operation of
'retrieve', the URI for the conference object created for the sidebar "retrieve", the URI for the conference object created for the sidebar
MUST be included in the 'confObjID' parameter in the request. The MUST be included in the "confObjID" parameter in the request. A
'sidebarByRefInfo' MUST also be included in the request in the case "retrieve" operation on the "sidebarByRefInfo" is handled by the
of an 'operation' of 'update'. An 'update' operation on the conference server in the same manner as a "retrieve" operation on the
'sidebarByRefInfo' is handled by the conference server in the same confInfo included in a confRequest message as detailed in
manner as a 'retrieve' operation on the confInfo included in a Section 6.3.4.
confRequest message as detailed in Section 7.2.3.4.
In the case of a 'sidebarByRef' request with an operation of In the case of a "sidebarByRef" request with an operation of
'update', the URI for the conference object created for the sidebar "update", the URI for the conference object created for the sidebar
MUST be included in the 'confObjID' parameter in the request. The MUST be included in the "confObjID" parameter in the request. The
'sidebarByRefInfo' MUST also be included in the request in the case "sidebarByRefInfo" MUST also be included in the request in the case
of an 'operation' of 'update'. An 'update' operation on the of an "operation" of "update". An "update" operation on the
'sidebarByRefInfo' is handled by the conference server in the same "sidebarByRefInfo" is handled by the conference server in the same
manner as an 'update' operation on the confInfo included in a manner as an "update" operation on the confInfo included in a
confRequest message as detailed in Section 7.2.3.4. confRequest message as detailed in Section 6.3.4.
If an 'operation' of 'delete' is included in the sidebarByRef If an "operation" of "delete" is included in the sidebarByRef
request, the 'sidebarByRefInfo' parameter SHOULD NOT be included in request, the "sidebarByRefInfo" parameter MUST NOT be included in the
the request. Any 'sidebarByRefInfo' included in the request SHOULD request. Any "sidebarByRefInfo" included in the request MUST be
be ignored by the conference server. The URI for the conference ignored by the conference server. The URI for the conference object
object for the sidebar MUST be included in the 'confObjID' parameter for the sidebar MUST be included in the "confObjID" parameter in the
in the request. If the specific conferencing user as reflected by request. If the specific conferencing user as reflected by the
the 'confUserID' in the request is authorized to delete the "confUserID" in the request is authorized to delete the conference,
conference, the conference server SHOULD delete the conference object the conference server SHOULD delete the conference object reflected
reflected by the 'confObjID' parameter and SHOULD update the by the "confObjID" parameter and SHOULD update the "sidebars-by-ref"
'sidebars-by-ref' element in the conference object from which the element in the conference object from which the sidebar was
sidebar was originally cloned. The conference server can notify any originally cloned. The conference server can notify any conferencing
conferencing clients that have subscribed to the conference event clients that have subscribed to the conference event package, and are
package, and are authorized to receive the notifications, of the authorized to receive the notifications, of the deletion of the
deletion of the sidebar. sidebar.
<!-- sidebarByRefRequest --> <!-- sidebarByRefRequest -->
<xs:complexType name="ccmp-sidebarByRef-request-message-type"> <xs:complexType name="ccmp-sidebarByRef-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarByRefRequest"/> <xs:element ref="sidebarByRefRequest"/>
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
skipping to change at page 50, line 5 skipping to change at page 45, line 7
<xs:complexType name="sidebarByRefResponseType"> <xs:complexType name="sidebarByRefResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarByRefInfo" <xs:element name="sidebarByRefInfo"
type="info:conference-type"/> type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
Figure 16: Structure of the sidebarByRefRequest and Figure 16: Structure of the sidebarByRefRequest and
sidebarByRefResponse messages sidebarByRefResponse messages
8. A complete example of the CCMP in action 6.4. CCMP Response Codes
All CCMP response messages MUST include a "responseCode". The
following summarizes the CCMP response codes:
success: Successful completion of the requested operation.
badRequest: Syntactically malformed request.
objectNotFound: Target conference object missing at the server (it
refers to the "confObjId" parameter in the generic request
message)
userNotFound: Target user missing at the server (it is related to
the XCON-USERID in the "entity" attribute of the "userInfo"
parameter when it is included in userRequests)
invalidConfUserID: User missing at the server (this code is returned
in the case of requests in which the "confUserID" of the sender is
invalid).
invalidPassword: Target conference object's password contained in
the request is wrong.
passwordRequired: Conference password missing in a request to access
a password-protected conference object.
unauthorized: User not allowed to perform the required operation.
forbidden: Operation not allowed (e.g., cancellation of a
blueprint).
forbiddenDeleteParent: Cancel operation failed since the target
object is a parent of child objects which depend on it, or because
it effects, based on the "parent-enforceable" mechanism, the
corresponding element in a child object.
forbiddenChangeProtected: Update refused by the server because the
target element cannot be modified due to its implicit dependence
on the value of a parent object ("parent-enforceable" mechanism).
requestTimeout: The time required to serve the request has exceeded
the envisaged service threshold.
serverInternalError: The server cannot complete the required service
due to a system internal error.
notImplemented: Operation envisaged in the protocol, but not
implemented in the contacted server.
updateFailed A generic error associated with all those situations in
which a requested "update" cannot be successfully completed by the
server. An example of such situation is when the modification of
an object cannot be applied due to conflicts arising at the
server's side (e.g. because the client version of the object is an
obsolete one and the requested modifications collide with the up-
to-date state of the object stored at the server).
The handling of a "responseCode" of "objectNotFound", "userNotFound",
"deleteParentFailed" and "changeFailedProtected" are only applicable
to specific operations for specialized message responses and the
details are provided in Section 6.3. The following table summarizes
these "responseCodes" and the specialized message and operation to
which they are applicable:
+---------------+------------+------------+------------+------------+
| Response code | Create | Retrieve | Update | Delete |
+---------------+------------+------------+------------+------------+
| updateFailed | N/A | N/A | All update | N/A |
| | | | requests | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| objectNotFoun | userReques | All | All update | All delete |
| d | t, | retrieve | requests | requests |
| | sidebarBy | requests, | | |
| | ValRequest | EXCEPT: | | |
| | sidebars | blueprints | | |
| | ByRefReque | Request, | | |
| | st | confsRequ | | |
| | | est | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| userNotFound | userReques | userReques | userReques | userReques |
| | t(3rd part | t | t | t |
| | yinvite | | | |
| | with thir | | | |
| | duser | | | |
| | entity) | | | |
| | (*) | | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| invalidConfUs | All create | All | All update | All delete |
| erID | requests, | retrieve | requests | requests |
| | EXCEPT: | requests | | |
| | userReques | | | |
| | twith no | | | |
| | confUserI | | | |
| | D(**) | | | |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| forbiddenDele | N/A | N/A | N/A | All delete |
| teParent | | | | request |
| | | | | |
| ------------- | ---------- | ---------- | ---------- | ---------- |
| | | | | |
| forbiddenChan | N/A | N/A | All update | N/A |
| geProtected | | | requests | |
+---------------+------------+------------+------------+------------+
Table 2: Response codes and associated operations
(*) "userNotFound" in answer to a "userRequest/create" operation: in
the case of a third-party invite, this code can be returned if the
"confUserId" (contained in the "entity" attribute of the "userInfo"
parameter) of the user to be added is unknown. In the case above, if
instead it is the "confUserID" of the sender of the request that is
invalid, an "invalidConfUserID" error code is returned to the client.
(**) "invalidConfUserID" is not sent in answers to "userRequest/
create" messages having a "null" confUserId, since this case is
associated with a user who is unaware of his own XCON-USERID, but
wants to enter a known conference.
In the case of a response code of "requestTimeout", a conferencing
client MAY re-attempt the request within a period of time that would
be specific to a conference control client or conference control
server.
A response code of "badRequest" indicates that the conference control
client sent a malformed request, which is indicative of an error in
the conference control client or in the conference control server.
The handling is specific to the conference control client
implementation (e.g., generate a log, display an error message,
etc.). It is NOT RECOMMENDED that the client re-attempt the request
in this case.
Response codes such as "unauthorized" and "forbidden" indicate the
client does not have the appropriate permissions, or there is an
error in the permissions: re-attempting the request would likely not
succeed and thus it is NOT RECOMMENDED.
Any unexpected or unknown responseCode SHOULD be treated by the
client in the same manner as a "serverInternalError" responseCode,
the handling of which is specific to the conference control client
implementation.
7. A complete example of the CCMP in action
[spromano-09] This section has to be updated, since we added the [spromano-09] This section has to be updated, since we added the
'operation' parameter in response messages. Hence, we first have to "operation" parameter in response messages. Hence, we first have to
update the schema file; then, we have to change the excrpts in this update the schema file; then, we have to change the excrpts in this
section. section.
In this section a typical scenario in which the CCMP comes into play In this section a typical scenario in which the CCMP comes into play
is described, by showing the actual composition of the various CCMP is described, by showing the actual composition of the various CCMP
messages. In the call flows of the example, the Conference Control messages. In the call flows of the example, the Conference Control
Client is a CCMP-enabled client, whereas the Conference Control Client is a CCMP-enabled client, whereas the Conference Control
Server is a CCMP-enabled server. The 'confUserId' of the client is Server is a CCMP-enabled server. The "confUserId" of the client is
"Alice" and appears in all requests. The sequence of operations is "Alice" and appears in all requests. The sequence of operations is
as follows: as follows:
1. Alice retrieves from the server the list of available blueprints 1. Alice retrieves from the server the list of available blueprints
(Section 8.1); (Section 7.1);
2. Alice asks for detailed information about a specific blueprint 2. Alice asks for detailed information about a specific blueprint
(Section 8.2); (Section 7.2);
3. Alice decides to create a new conference by cloning the retrieved 3. Alice decides to create a new conference by cloning the retrieved
blueprint (Section 8.3); blueprint (Section 7.3);
4. Alice modifies information (e.g. XCON-URI, name, description) 4. Alice modifies information (e.g. XCON-URI, name, description)
associated with the newly created blueprint (Section 8.4); associated with the newly created blueprint (Section 7.4);
5. Alice specifies a list of users to be contacted when the 5. Alice specifies a list of users to be contacted when the
conference is activated (Section 8.5); conference is activated (Section 7.5);
6. Alice joins the conference (Section 8.6); 6. Alice joins the conference (Section 7.6);
7. Alice lets a new user (whose 'confUserId' is "Ciccio") join the 7. Alice lets a new user (whose "confUserId" is "Ciccio") join the
conference (Section 8.7). conference (Section 7.7).
Note, the examples do not include any details beyond the basic Note, the examples do not include any details beyond the basic
operation. operation.
In the following sections we deal with each of the above mentioned In the following sections we deal with each of the above mentioned
actions separately. actions separately.
8.1. Alice retrieves the available blueprints 7.1. Alice retrieves the available blueprints
This section illustrates the transaction associated with retrieval of This section illustrates the transaction associated with retrieval of
the blueprints, together with a dump of the two messages exchanged the blueprints, together with a dump of the two messages exchanged
("blueprintsRequest" and "blueprintsResponse"). As it comes out from ("blueprintsRequest" and "blueprintsResponse"). As it comes out from
the figure, the "blueprintsResponse" message contains, in the the figure, the "blueprintsResponse" message contains, in the
'blueprintsInfo' parameter, information about the available "blueprintsInfo" parameter, information about the available
blueprints, in the form of the standard XCON-URI of the blueprint, blueprints, in the form of the standard XCON-URI of the blueprint,
plus additional (and optional) information, like its display-text and plus additional (and optional) information, like its display-text and
purpose. purpose.
Alice retrieves from the server the list of available blueprints: Alice retrieves from the server the list of available blueprints:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP blueprintsRequest message | | CCMP blueprintsRequest message |
| - confUserID: Alice | | - confUserID: Alice |
skipping to change at page 51, line 35 skipping to change at page 50, line 35
. . . .
1. blueprintsRequest message: 1. blueprintsRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest xmlns:info="urn:ietf:params:xml:ns:conference-info" <ccmp:ccmpRequest xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="xcon:ccmp-blueprints-request-message-type"> xsi:type="xcon:ccmp-blueprints-request-message-type">
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. blueprintsResponse message form the server: 2. blueprintsResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse <ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprints-response-message-type"> xsi:type="ccmp:ccmp-blueprints-response-message-type">
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:blueprintsResponse> <ccmp:blueprintsResponse>
<blueprintsInfo> <blueprintsInfo>
<info:entry> <info:entry>
<info:uri>xcon:AudioRoom@meetecho.com</info:uri> <info:uri>xcon:AudioRoom@example.com</info:uri>
<info:display-text>AudioRoom</info:display-text> <info:display-text>AudioRoom</info:display-text>
<info:purpose>Simple Room: <info:purpose>Simple Room:
conference room with public access, conference room with public access,
where only audio is available, more users where only audio is available, more users
can talk at the same time can talk at the same time
and the requests for the AudioFloor and the requests for the AudioFloor
are automatically accepted. are automatically accepted.
</info:purpose> </info:purpose>
</info:entry> </info:entry>
<info:entry> <info:entry>
<info:uri>xcon:VideoRoom@meetecho.com</info:uri> <info:uri>xcon:VideoRoom@example.com</info:uri>
<info:display-text>VideoRoom</info:display-text> <info:display-text>VideoRoom</info:display-text>
<info:purpose>Video Room: <info:purpose>Video Room:
conference room with public access, conference room with public access,
where both audio and video are available, where both audio and video are available,
8 users can talk and be seen at the same time, 8 users can talk and be seen at the same time,
and the floor requests are automatically accepted. and the floor requests are automatically accepted.
</info:purpose> </info:purpose>
</info:entry> </info:entry>
<info:entry> <info:entry>
<info:uri>xcon:AudioConference1@meetecho.com</info:uri> <info:uri>xcon:AudioConference1@example.com</info:uri>
<info:display-text>AudioConference1</info:display-text> <info:display-text>AudioConference1</info:display-text>
<info:purpose>Public Audio Conference: <info:purpose>Public Audio Conference:
conference with public access, conference with public access,
where only audio is available, where only audio is available,
only one user can talk at the same time, only one user can talk at the same time,
and the requests for the AudioFloor MUST and the requests for the AudioFloor MUST
be accepted by a Chair. be accepted by a Chair.
</info:purpose> </info:purpose>
</info:entry> </info:entry>
<info:entry> <info:entry>
<info:uri>xcon:VideoConference1@meetecho.com</info:uri> <info:uri>xcon:VideoConference1@example.com</info:uri>
<info:display-text>VideoConference1</info:display-text> <info:display-text>VideoConference1</info:display-text>
<info:purpose>Public Video Conference: conference <info:purpose>Public Video Conference: conference
where both audio and video are available, where both audio and video are available,
only one user can talk only one user can talk
</info:purpose> </info:purpose>
</info:entry> </info:entry>
<info:entry> <info:entry>
<info:uri>xcon:AudioConference2@meetecho.com</info:uri> <info:uri>xcon:AudioConference2@example.com</info:uri>
<info:display-text>AudioConference2</info:display-text> <info:display-text>AudioConference2</info:display-text>
<info:purpose>Basic Audio Conference: <info:purpose>Basic Audio Conference:
conference with private access, conference with private access,
where only audio is available, where only audio is available,
only one user can talk at the same time, only one user can talk at the same time,
and the requests for the AudioFloor MUST and the requests for the AudioFloor MUST
be accepted by a Chair. be accepted by a Chair.
</info:purpose> </info:purpose>
</info:entry> </info:entry>
</blueprintsInfo> </blueprintsInfo>
</ccmp:blueprintsResponse> </ccmp:blueprintsResponse>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 17: Getting blueprints from the server Figure 17: Getting blueprints from the server
8.2. Alice gets detailed information about a specific blueprint 7.2. Alice gets detailed information about a specific blueprint
This section illustrates the second transaction in the overall flow. This section illustrates the second transaction in the overall flow.
In this case, Alice, who now knows the XCON-URIs of the blueprints In this case, Alice, who now knows the XCON-URIs of the blueprints
available at the server, makes a drill-down query, in the form of a available at the server, makes a drill-down query, in the form of a
CCMP "blueprintRequest" message, to get detailed information about CCMP "blueprintRequest" message, to get detailed information about
one of them (the one called with XCON-URI one of them (the one called with XCON-URI
"xcon:AudioRoom@meetecho.com"). The picture shows such transaction. "xcon:AudioRoom@example.com"). The picture shows such transaction.
Notice that the response contains, in the 'blueprintInfo' parameter, Notice that the response contains, in the "blueprintInfo" parameter,
a document compliant with the standard XCON data model. a document compliant with the standard XCON data model.
Alice retrieves detailed information about a specified blueprint: Alice retrieves detailed information about a specified blueprint:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP blueprintRequest message | | CCMP blueprintRequest message |
| - confUserID: Alice | | - confUserID: Alice |
| - confObjId: bp123 | | - confObjId: bp123 |
| - operation: retrieve | | - operation: retrieve |
skipping to change at page 54, line 17 skipping to change at page 53, line 17
1. blueprintRequest message: 1. blueprintRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-request-message-type"> xsi:type="ccmp:ccmp-blueprint-request-message-type">
<confObjID>xcon:AudioRoom@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:AudioRoom@example.com</confObjID>
<operation>retrieve</operation> <operation>retrieve</operation>
<ccmp:blueprintRequest/> <ccmp:blueprintRequest/>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. blueprintResponse message form the server: 2. blueprintResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-response-message-type"> xsi:type="ccmp:ccmp-blueprint-response-message-type">
<confObjID>xcon:AudioRoom@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:AudioRoom@example.com</confObjID>
<operation>retrieve</operation> <operation>retrieve</operation>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:blueprintResponse> <ccmp:blueprintResponse>
<blueprintInfo entity="xcon:AudioRoom@meetecho.com"> <blueprintInfo entity="xcon:AudioRoom@example.com">
<info:conference-description> <info:conference-description>
<info:display-text>AudioRoom</info:display-text> <info:display-text>AudioRoom</info:display-text>
<info:maximum-user-count>2</info:maximum-user-count> <info:maximum-user-count>2</info:maximum-user-count>
<info:available-media> <info:available-media>
<info:entry label="audioLabel"> <info:entry label="audioLabel">
<info:type>audio</info:type> <info:type>audio</info:type>
</info:entry> </info:entry>
</info:available-media> </info:available-media>
</info:conference-description> </info:conference-description>
<info:users> <info:users>
skipping to change at page 55, line 17 skipping to change at page 54, line 17
<xcon:floor id="audioLabel"></xcon:floor> <xcon:floor id="audioLabel"></xcon:floor>
</xcon:conference-floor-policy> </xcon:conference-floor-policy>
</xcon:floor-information> </xcon:floor-information>
</blueprintInfo> </blueprintInfo>
</ccmp:blueprintResponse> </ccmp:blueprintResponse>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 18: Getting info about a specific blueprint Figure 18: Getting info about a specific blueprint
8.3. Alice creates a new conference through a cloning operation 7.3. Alice creates a new conference through a cloning operation
This section illustrates the third transaction in the overall flow. This section illustrates the third transaction in the overall flow.
Alice decides to create a new conference by cloning the blueprint Alice decides to create a new conference by cloning the blueprint
having XCON-URI "xcon:AudioRoom@meetecho.com", for which she just having XCON-URI "xcon:AudioRoom@example.com", for which she just
retrieved detailed information through the "blueprintRequest" retrieved detailed information through the "blueprintRequest"
message. This is achieved by sending a "confRequest/create" message message. This is achieved by sending a "confRequest/create" message
having the blueprint's URI in the 'confObjId' parameter. The picture having the blueprint's URI in the "confObjId" parameter. The picture
shows such transaction. Notice that the response contains, in the shows such transaction. Notice that the response contains, in the
'confInfo' parameter, the document associated with the newly created "confInfo" parameter, the document associated with the newly created
conference, which is compliant with the standard XCON data model. conference, which is compliant with the standard XCON data model.
The 'confObjId' in the response is set to the XCON-URI of the new The "confObjId" in the response is set to the XCON-URI of the new
conference (in this case, "xcon:8977794@meetecho.com"). We also conference (in this case, "xcon:8977794@example.com"). We also
notice that this value is equal to the value of the "entity" notice that this value is equal to the value of the "entity"
attribute of the <conference-info> element of the document attribute of the <conference-info> element of the document
representing the newly created conference object. representing the newly created conference object.
Alice creates a new conference by cloning the Alice creates a new conference by cloning the
"xcon:AudioRoom@meetecho.com" blueprint: "xcon:AudioRoom@example.com" blueprint:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP confRequest message | | CCMP confRequest message |
| - confUserID: Alice | | - confUserID: Alice |
| - confObjId: AudioRoom | | - confObjId: AudioRoom |
| - operation: create | | - operation: create |
| - confInfo: (null) | | - confInfo: (null) |
|------------------------------------------------------>| |------------------------------------------------------>|
| | | |
skipping to change at page 56, line 24 skipping to change at page 55, line 24
1. confRequest message: 1. confRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest <ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-request-message-type"> xsi:type="ccmp:ccmp-conf-request-message-type">
<confObjID>xcon:AudioRoom@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:AudioRoom@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:confRequest/> <ccmp:confRequest/>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. confResponse message from the server: 2. confResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse <ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-response-message-type"> xsi:type="ccmp:ccmp-conf-response-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:confResponse> <ccmp:confResponse>
<confInfo entity="xcon:8977794@meetecho.com"> <confInfo entity="xcon:8977794@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
New conference by Alice cloned from AudioRoom New conference by Alice cloned from AudioRoom
</info:display-text> </info:display-text>
<info:conf-uris> <info:conf-uris>
<info:entry> <info:entry>
<info:uri> <info:uri>
xcon:8977794@meetecho.com xcon:8977794@example.com
</info:uri> </info:uri>
<info:display-text> <info:display-text>
conference xcon-uri conference xcon-uri
</info:display-text> </info:display-text>
<xcon:conference-password> <xcon:conference-password>
8601 8601
</xcon:conference-password> </xcon:conference-password>
</info:entry> </info:entry>
</info:conf-uris> </info:conf-uris>
<info:maximum-user-count>10</info:maximum-user-count> <info:maximum-user-count>10</info:maximum-user-count>
skipping to change at page 57, line 41 skipping to change at page 56, line 41
<xcon:floor id="11"/> <xcon:floor id="11"/>
</xcon:conference-floor-policy> </xcon:conference-floor-policy>
</xcon:floor-information> </xcon:floor-information>
</confInfo> </confInfo>
</ccmp:confResponse> </ccmp:confResponse>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 19: Creating a new conference by cloning a blueprint Figure 19: Creating a new conference by cloning a blueprint
8.4. Alice updates conference information 7.4. Alice updates conference information
This section illustrates the fourth transaction in the overall flow. This section illustrates the fourth transaction in the overall flow.
Alice decides to modify some of the details associated with the Alice decides to modify some of the details associated with the
conference she just created. More precisely, she changes the conference she just created. More precisely, she changes the
<display-text> element under the <conference-description> element of <display-text> element under the <conference-description> element of
the document representing the conference. This is achieved through a the document representing the conference. This is achieved through a
"confRequest/update" message carrying the fragment of the conference "confRequest/update" message carrying the fragment of the conference
document to which the required changes have to be applied. As shown document to which the required changes have to be applied. As shown
in the picture, the response contains a code of 'success', which in the picture, the response contains a code of "success", which
acknowledges the modifications requested by the client. acknowledges the modifications requested by the client.
Alice updates information about the conference she just created: Alice updates information about the conference she just created:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP confRequest message | | CCMP confRequest message |
| - confUserID: Alice | | - confUserID: Alice |
| - confObjId: 897779 | | - confObjId: 8977794 |
| - operation: update | | - operation: update |
| - confInfo: conf456Updates | | - confInfo: confUpdates |
|------------------------------------------------------>| |------------------------------------------------------>|
| | | |
| CCMP confResponse message | | CCMP confResponse message |
| - confUserID: Alice | | - confUserID: Alice |
| - confObjId: 8977794 | | - confObjId: 8977794 |
| - operation: update | | - operation: update |
| - responseCode: success | | - responseCode: success |
| - confInfo: (null) | | - confInfo: (null) |
|<------------------------------------------------------| |<------------------------------------------------------|
| | | |
skipping to change at page 58, line 40 skipping to change at page 57, line 40
1. confRequest message: 1. confRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest <ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-request-message-type"> xsi:type="ccmp:ccmp-conf-request-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<ccmp:confRequest> <ccmp:confRequest>
<confInfo entity="xcon:8977794@meetecho.com"> <confInfo entity="xcon:8977794@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
Alice's conference Alice's conference
</info:display-text> </info:display-text>
</info:conference-description> </info:conference-description>
</confInfo> </confInfo>
</ccmp:confRequest> </ccmp:confRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. confResponse message form the server: 2. confResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-response-message-type"> xsi:type="ccmp:ccmp-conf-response-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:confResponse/> <ccmp:confResponse/>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 20: Updating conference information Figure 20: Updating conference information
8.5. Alice inserts a list of users in the conference object 7.5. Alice inserts a list of users in the conference object
This section illustrates the fifth transaction in the overall flow. This section illustrates the fifth transaction in the overall flow.
Alice modifies the <allowed-users-list> under the <users> element in Alice modifies the <allowed-users-list> under the <users> element in
the document associated with the conference she created. To the the document associated with the conference she created. To the
purpose, she exploits the "usersRequest" message provided by the purpose, she exploits the "usersRequest" message provided by the
CCMP. The picture below shows the transaction. CCMP. The picture below shows the transaction.
Alice updates information about the list of users to whom access to Alice updates information about the list of users to whom access to
the conference is permitted: the conference is permitted:
skipping to change at page 60, line 27 skipping to change at page 59, line 27
1. usersRequest message: 1. usersRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-users-request-message-type"> xsi:type="ccmp:ccmp-users-request-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<ccmp:usersRequest> <ccmp:usersRequest>
<usersInfo> <usersInfo>
<xcon:allowed-users-list> <xcon:allowed-users-list>
<xcon:target method="dial out" <xcon:target method="dial out"
uri="xmpp:cicciolo@pippozzo.com"/> uri="xmpp:cicciolo@pippozzo.com"/>
<xcon:target method="refer" <xcon:target method="refer"
uri="tel:+390817683823"/> uri="tel:+390817683823"/>
<xcon:target method="refer" <xcon:target method="refer"
uri="sip:Carol@example.com"/> uri="sip:Carol@example.com"/>
</xcon:allowed-users-list> </xcon:allowed-users-list>
</usersInfo> </usersInfo>
</ccmp:usersRequest> </ccmp:usersRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. usersResponse message form the server: 2. usersResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-response-message-type"> xsi:type="ccmp:ccmp-conf-response-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:confResponse/> <ccmp:confResponse/>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 21: Updating the list of allowed users for the conference Figure 21: Updating the list of allowed users for the conference
'xcon:8977794@meetecho.com' 'xcon:8977794@example.com'
8.6. Alice joins the conference 7.6. Alice joins the conference
This section illustrates the sixth transaction in the overall flow. This section illustrates the sixth transaction in the overall flow.
Alice uses the CCMP to add herself to the newly created conference. Alice uses the CCMP to add herself to the newly created conference.
This is achieved through a "userRequest/create" message containing, This is achieved through a "userRequest/create" message containing,
in the 'userInfo' parameter, a <user> element compliant with the XCON in the "userInfo" parameter, a <user> element compliant with the XCON
data model representation. Notice that such element includes data model representation. Notice that such element includes
information about the user's Address of Records, as well as her information about the user's Address of Records, as well as her
current end-point. The picture below shows the transaction. Notice current end-point. The picture below shows the transaction. Notice
how the 'confUserId' parameter is equal to the "entity" attribute of how the "confUserId" parameter is equal to the "entity" attribute of
the <userInfo> element, which indicates that the request issued by the <userInfo> element, which indicates that the request issued by
the client is a first-party one. the client is a first-party one.
Alice joins the conference by issuing a "userRequest/create" message Alice joins the conference by issuing a "userRequest/create" message
with her own id to the server: with her own id to the server:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP userRequest message | | CCMP userRequest message |
| - confUserID: Alice | | - confUserID: Alice |
skipping to change at page 62, line 18 skipping to change at page 61, line 18
. . . .
1. userRequest message: 1. userRequest message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-confUser-request-message-type"> xsi:type="ccmp:ccmp-user-request-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:confUserRequest> <ccmp:userRequest>
<userInfo entity="xcon-userid:Alice@meetecho.com"> <userInfo entity="xcon-userid:Alice@example.com">
<info:associated-aors> <info:associated-aors>
<info:entry> <info:entry>
<info:uri> <info:uri>
mailto:Alice83@example.com mailto:Alice83@example.com
</info:uri> </info:uri>
<info:display-text>email</info:display-text> <info:display-text>email</info:display-text>
</info:entry> </info:entry>
</info:associated-aors> </info:associated-aors>
<info:endpoint entity="sip:alice_789@example.com"/> <info:endpoint entity="sip:alice_789@example.com"/>
</userInfo> </userInfo>
</ccmp:confUserRequest> </ccmp:userRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. userResponse message form the server: 2. userResponse message from the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-confUser-response-message-type"> xsi:type="ccmp:ccmp-user-response-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:response-code>success</ccmp:response-code> <ccmp:response-code>success</ccmp:response-code>
<ccmp:confUserResponse/> <ccmp:userResponse/>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 22: Alice joins the conference through the CCMP Figure 22: Alice joins the conference through the CCMP
8.7. Alice adds a new user to the conference 7.7. Alice adds a new user to the conference
This section illustrates the seventh and last transaction in the This section illustrates the seventh and last transaction in the
overall flow. Alice uses the CCMP to add a new user to the overall flow. Alice uses the CCMP to add a new user to the
conference. This is achieved through a "userRequest/create" message conference. This is achieved through a "userRequest/create" message
containing, in the 'userInfo' parameter, a <user> element compliant containing, in the "userInfo" parameter, a <user> element compliant
with the XCON data model representation. Notice that such element with the XCON data model representation. Notice that such element
includes information about the user's Address of Records, as well as includes information about the user's Address of Records, as well as
his current end-point. The picture below shows the transaction. his current end-point. The picture below shows the transaction.
Notice how the 'confUserId' parameter in the request is Alice's id, Notice how the "confUserId" parameter in the request is Alice's id,
whereas the <userInfo> element has no "entity" attribute and contains whereas the <userInfo> element has no "entity" attribute and contains
information about a different user, thus indicating that the request information about a different user, thus indicating that the request
issued by the client is a third-party one. This is also reflected in issued by the client is a third-party one. This is also reflected in
the response coming from the server, which this time contains a non- the response coming from the server, which this time contains a
void <userInfo> element, whose "entity" attribute has been set by the "confUserID" parameter representing the conference user id of the
server to the value of the newly created conference user id. user just added to the conference with Alice's third-party request.
Alice adds user "Ciccio" to the conference by issuing a third-party Alice adds user "Ciccio" to the conference by issuing a third-party
"userRequest/create" message to the server: "userRequest/create" message to the server:
CCMP Client CCMP Server CCMP Client CCMP Server
| | | |
| CCMP userRequest message | | CCMP userRequest message |
| - confUserID: Alice | | - confUserID: Alice |
| - confObjId: 8977794 | | - confObjId: 8977794 |
| - operation: create | | - operation: create |
| - usersInfo: CiccioUserInfo | | - userInfo: CiccioUserInfo |
|------------------------------------------------------>| |------------------------------------------------------>|
| | | |
| CCMP userResponse message | | CCMP userResponse message |
| - confUserID: Alice | | - confUserID: ciccio |
| - confObjId: 8977794 | | - confObjId: 8977794 |
| - operation: create | | - operation: create |
| - responseCode: success | | - responseCode: success |
| - usersInfo: (not null!)| | - userInfo: (null) |
|<------------------------------------------------------| |<------------------------------------------------------|
| | | |
. . . .
. . . .
1. "third party" userRequest message from Alice: 1. "third party" userRequest message from Alice:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-confUser-request-message-type"> xsi:type="ccmp:ccmp-user-request-message-type">
<confObjID>xcon:8977794@meetecho.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:confUserRequest> <ccmp:userRequest>
<userInfo> <userInfo>
<info:associated-aors> <info:associated-aors>
<info:entry> <info:entry>
<info:uri> <info:uri>
mailto:ciccio@pernacchio.com mailto:ciccio@pernacchio.com
</info:uri> </info:uri>
<info:display-text>email</info:display-text> <info:display-text>email</info:display-text>
</info:entry> </info:entry>
</info:associated-aors> </info:associated-aors>
<info:endpoint entity="sip:ciccio@pernacchio.com"/> <info:endpoint entity="sip:ciccio@pernacchio.com"/>
</userInfo> </userInfo>
</ccmp:confUserRequest> </ccmp:userRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. "third party" userResponse message form the server: 2. "third party" userResponse message form the server:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse <ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-confUser-response-message-type"> xsi:type="ccmp:ccmp-user-response-message-type">
<confObjID>8977794</confObjID> <confUserID>xcon-userid:ciccio@example.com</confUserID>
<confUserID>xcon-userid:Alice@meetecho.com</confUserID> <confObjID>xcon:8977794@example.com</confObjID>
<ccmp:response-code>success</ccmp:response-code>
<operation>create</operation> <operation>create</operation>
<ccmp:confUserResponse> <ccmp:response-code>success</ccmp:response-code>
<confUserInfo entity="xcon-userid:bn90ujbkj@meetecho.com"> <ccmp:userResponse/>
<info:associated-aors>
<info:entry>
<info:uri>
mailto:ciccio@pernacchio.com
</info:uri>
<info:display-text>email</info:display-text>
</info:entry>
</info:associated-aors>
<info:endpoint entity="sip:ciccio@pernacchio.com"/>
</confUserInfo>
</ccmp:confUserResponse>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 23: Alice adds a new user to the conference through the CCMP Figure 23: Alice adds a new user to the conference through the CCMP
9. Locating a Conference Control Server 8. Locating a Conference Control Server
If a conference control client is not pre-configured to use a If a conference control client is not pre-configured to use a
specific conference control server for the requests, the client MUST specific conference control server for the requests, the client MUST
first discover the conference control server before it can send any first discover the conference control server before it can send any
requests. The result of the discovery process, is the address of the requests. The result of the discovery process, is the address of the
server supporting conferencing. In this document, the result is an server supporting conferencing. In this document, the result is an
http: or https: URI, which identifies a conference server. http: or https: URI, which identifies a conference server.
This document proposes the use of DNS to locate the conferencing This document proposes the use of DNS to locate the conferencing
server. U-NAPTR resolution for conferencing takes a domain name as server. U-NAPTR resolution for conferencing takes a domain name as
input and produces a URI that identifies the conferencing server. input and produces a URI that identifies the conferencing server.
This process also requires an Application Service tag and an This process also requires an Application Service tag and an
Application Protocol tag, which differentiate conferencing-related Application Protocol tag, which differentiate conferencing-related
NAPTR records from other records for that domain. NAPTR records from other records for that domain.
Section 14.4.1 defines an Application Service tag of "XCON", which is Section 13.4.1 defines an Application Service tag of "XCON", which is
used to identify the centralized conferencing (XCON) server for a used to identify the centralized conferencing (XCON) server for a
particular domain. The Application Protocol tag "CCMP", defined in particular domain. The Application Protocol tag "CCMP", defined in
Section 14.4.2, is used to identify an XCON server that understands Section 13.4.2, is used to identify an XCON server that understands
the CCMP protocol. the CCMP protocol.
The NAPTR records in the following example Figure 24 demonstrate the The NAPTR records in the following example Figure 24 demonstrate the
use of the Application Service and Protocol tags. Iterative NAPTR use of the Application Service and Protocol tags. Iterative NAPTR
resolution is used to delegate responsibility for the conferencing resolution is used to delegate responsibility for the conferencing
service from "zonea.example.com." and "zoneb.example.com." to service from "zonea.example.com." and "zoneb.example.com." to
"outsource.example.com.". "outsource.example.com.".
zonea.example.com. zonea.example.com.
;; order pref flags ;; order pref flags
skipping to change at page 67, line 7 skipping to change at page 66, line 7
) )
outsource.example.com. outsource.example.com.
;; order pref flags ;; order pref flags
IN NAPTR 100 10 "u" "XCON:CCMP" ( ; service IN NAPTR 100 10 "u" "XCON:CCMP" ( ; service
"!*.!https://confs.example.com/!" ; regex "!*.!https://confs.example.com/!" ; regex
. ; replacement . ; replacement
) )
Figure 24: Sample XCON:CCMP Service NAPTR Records Figure 24: Sample XCON:CCMP Service NAPTR Records
Details for the "XCON" Application Service tag and the "CCMP" Details for the "XCON" Application Service tag and the "CCMP"
Application Protocol tag are included in Section 14.4. Application Protocol tag are included in Section 13.4.
10. Managing Notifications 9. Managing Notifications
In cases where the conference control client uses SIP [RFC3261] as In cases where the conference control client uses SIP [RFC3261] as
the signaling protocol to participate in the conference, SIP event the signaling protocol to participate in the conference, SIP event
notification can be used. This would REQUIRE the conference control notification can be used. This would REQUIRE the conference control
client to implement the Conference event package for XCON client to implement the Conference event package for XCON
[I-D.ietf-xcon-event-package]. This is the default mechanism for [I-D.ietf-xcon-event-package]. This is the default mechanism for
conferencing clients as is SIP for signaling per the XCON Framework conferencing clients as is SIP for signaling per the XCON Framework
[RFC5239]. [RFC5239].
In the case where the interface to the conference server is entirely In the case where the interface to the conference server is entirely
skipping to change at page 69, line 5 skipping to change at page 68, line 5
mechanism for e-commerce. This works well in the scenarios whereby mechanism for e-commerce. This works well in the scenarios whereby
the conferencing client is a web server that provides the graphical the conferencing client is a web server that provides the graphical
HTML user interface and uses CCMP as the backend interface to the HTML user interface and uses CCMP as the backend interface to the
conference server. And, this model can co-exist with the SIP event conference server. And, this model can co-exist with the SIP event
notification model. PC-based clients behind NATs could provide a SIP notification model. PC-based clients behind NATs could provide a SIP
event URI, whereas web servers would probably find the HTTP model event URI, whereas web servers would probably find the HTTP model
much easier to program. The details of this approach are out of much easier to program. The details of this approach are out of
scope for the CCMP per se, thus the expectation is that a future scope for the CCMP per se, thus the expectation is that a future
specification will document this solution. specification will document this solution.
11. HTTP Transport 10. HTTP Transport
This section describes the use of HTTP [RFC2616] and HTTP Over TLS This section describes the use of HTTP [RFC2616] and HTTP Over TLS
[RFC2818] as transport mechanisms for the CCMP protocol, which a [RFC2818] as transport mechanisms for the CCMP protocol, which a
conforming conference Server and Conferencing client MUST support. conforming conference Server and Conferencing client MUST support.
Although CCMP uses HTTP as a transport, it uses a strict subset of Although CCMP uses HTTP as a transport, it uses a strict subset of
HTTP features, and due to the restrictions of some features, a HTTP features, and due to the restrictions of some features, a
conferencing server may not a fully compliant HTTP server. It is conferencing server may not a fully compliant HTTP server. It is
intended that a conference server can easily be built using an HTTP intended that a conference server can easily be built using an HTTP
server with extensibility mechanisms, and that a conferencing client server with extensibility mechanisms, and that a conferencing client
can trivially use existing HTTP libraries. This subset of can trivially use existing HTTP libraries. This subset of
requirements helps implementors avoid ambiguity with the many options requirements helps implementors avoid ambiguity with the many options
the full HTTP protocol offers. the full HTTP protocol offers.
A conferencing client that conforms to this specification SHOULD NOT A conferencing client that conforms to this specification is not
be required to support HTTP authentication [RFC2617] or cookies required to support HTTP authentication [RFC2617] or cookies
[RFC2965]. Because the conferencing client and the conference server [RFC2965]. These mechanism are unnecessary because CCMP requests
may have a prior relationship, the conference server SHOULD NOT carry their own authentication information (in the "confUserId" and
require a conferencing client to authenticate, either using the above "password" fields; see Section 7.2.1).
HTTP authentication methods or TLS client authentication.
A CCMP request is carried in the body of an HTTP POST request. The A CCMP request is carried in the body of an HTTP POST request. The
conferencing client MUST include a Host header in the request. conferencing client MUST include a Host header in the request.
The MIME type of CCMP request and response bodies is "application/ The MIME type of CCMP request and response bodies is "application/
ccmp+xml". The conference server and conferencing client MUST ccmp+xml". The conference server and conferencing client MUST
provide this value in the HTTP Content-Type and Accept header fields. provide this value in the HTTP Content-Type and Accept header fields.
If the conference server does not receive the appropriate Content- If the conference server does not receive the appropriate Content-
Type and Accept header fields, the conference server SHOULD fail the Type and Accept header fields, the conference server SHOULD fail the
request, returning a 406 (not acceptable) response. CCMP responses request, returning a 406 (not acceptable) response. CCMP responses
skipping to change at page 69, line 51 skipping to change at page 68, line 50
the case that the conference server receives a request from the the case that the conference server receives a request from the
conferencing client containing a If-* (conditional) header, the conferencing client containing a If-* (conditional) header, the
conference server SHOULD return a 412 (precondition failed) response. conference server SHOULD return a 412 (precondition failed) response.
The POST method is the only method REQUIRED for CCMP. If a The POST method is the only method REQUIRED for CCMP. If a
conference server chooses to support GET or HEAD, it SHOULD consider conference server chooses to support GET or HEAD, it SHOULD consider
the kind of application doing the GET. Since a conferencing client the kind of application doing the GET. Since a conferencing client
only uses a POST method, the GET or HEAD MUST be either an escaped only uses a POST method, the GET or HEAD MUST be either an escaped
URL (e.g., somebody found a URL in protocol traces or log files and URL (e.g., somebody found a URL in protocol traces or log files and
fed it into their browser) or somebody doing testing/ debugging. The fed it into their browser) or somebody doing testing/ debugging. The
conference server could provide information in the HELD response conference server could provide information in the CCMP response
indicating that the URL corresponds to a conference server and only indicating that the URL corresponds to a conference server and only
responds to CCMP POST requests or the conference server could instead responds to CCMP POST requests or the conference server could instead
try to avoid any leak of information by returning a very generic HTTP try to avoid any leak of information by returning a very generic HTTP
error message such as 404 (not found). error message such as 405 (method not allowed).
The conference server populates the HTTP headers of responses so that The conference server populates the HTTP headers of responses so that
they are consistent with the contents of the message. In particular, they are consistent with the contents of the message. In particular,
the "CacheControl" header SHOULD be set to disable caching of any the "CacheControl" header SHOULD be set to disable caching of any
conference information by HTTP intermediaries. Otherwise, there is conference information by HTTP intermediaries. Otherwise, there is
the risk of stale information and/or the unauthorized disclosure of the risk of stale information and/or the unauthorized disclosure of
the information. The HTTP status code MUST indicate a 2xx series the information. The HTTP status code MUST indicate a 2xx series
response for all CCMP Response and Error messages. response for all CCMP Response and Error messages.
The conference server MAY redirect a CCMP request. A conferencing The conference server MAY redirect a CCMP request. A conferencing
skipping to change at page 71, line 5 skipping to change at page 70, line 5
transport over TLS [RFC2818]. TLS provides message integrity and transport over TLS [RFC2818]. TLS provides message integrity and
confidentiality between the conference control client and the confidentiality between the conference control client and the
conference control server. The conferencing client MUST implement conference control server. The conferencing client MUST implement
the server authentication method described in HTTPS [RFC2818]. The the server authentication method described in HTTPS [RFC2818]. The
device uses the URI obtained during conference server discovery to device uses the URI obtained during conference server discovery to
authenticate the server. The details of this authentication method authenticate the server. The details of this authentication method
are provided in section 3.1 of HTTPS [RFC2818]. When TLS is used, are provided in section 3.1 of HTTPS [RFC2818]. When TLS is used,
the conferencing client SHOULD fail a request if server the conferencing client SHOULD fail a request if server
authentication fails. authentication fails.
12. Security Considerations 11. Security Considerations
As identified in the XCON framework [RFC5239], there are a wide As identified in the XCON framework [RFC5239], there are a wide
variety of potential attacks related to conferencing, due to the variety of potential attacks related to conferencing, due to the
natural involvement of multiple endpoints and the capability to natural involvement of multiple endpoints and the capability to
manipulate the data on the conference server using CCMP. Examples of manipulate the data on the conference server using CCMP. Examples of
attacks include the following: an endpoint attempting to listen to attacks include the following: an endpoint attempting to listen to
conferences in which it is not authorized to participate, an endpoint conferences in which it is not authorized to participate, an endpoint
attempting to disconnect or mute other users, and theft of service by attempting to disconnect or mute other users, and theft of service by
an endpoint in attempting to create conferences it is not allowed to an endpoint in attempting to create conferences it is not allowed to
create. create.
The following summarizes the security considerations for CCMP: The following summarizes the security considerations for CCMP:
1. The client MUST determine the proper conference server. The 1. The client MUST determine the proper conference server. The
conference server discovery is described in . conference server discovery is described in Section 8.
2. The client MSUT connect to the proper conference server. The 2. The client MUST connect to the proper conference server. The
mechanisms for addressing this security consideration are mechanisms for addressing this security consideration are
described in Section 12.1. described in Section 11.1.
3. The protocol MUST support a confidentiality and integrity 3. The protocol MUST support a confidentiality and integrity
mechanism. As described in Section 11, implementations of CCMP mechanism. As described in Section 10, implementations of CCMP
MUST implement the HTTP transport over TLS [RFC2818]. MUST implement the HTTP transport over TLS [RFC2818].
4. There are security issues associated with the authorization to 4. There are security issues associated with the authorization to
perform actions on the conferencing system to invoke specific perform actions on the conferencing system to invoke specific
capabilities. A conference server SHOULD ensure that only capabilities. A conference server SHOULD ensure that only
authorized entities can manipulate the conference data. The authorized entities can manipulate the conference data. The
mechanisms for addressing this security consideration are mechanisms for addressing this security consideration are
described in Section 12.2. described in Section 11.2.
5. The privacy and security of the identity of a user in the 5. The privacy and security of the identity of a user in the
conference MUST be assured. The mechanisms to ensure the conference MUST be assured. The mechanisms to ensure the
security and privacy of identity are discussed in Section 12.3. security and privacy of identity are discussed in Section 11.3.
6. A final issue is related to Denial of Service (DoS) attacks on 6. A final issue is related to Denial of Service (DoS) attacks on
the conferencing server itself. In order to minimize the the conferencing server itself. In order to minimize the
potential for DoS attacks, it is RECOMMENDED that conferencing potential for DoS attacks, it is RECOMMENDED that conferencing
systems require user authentication and authorization for any systems require user authentication and authorization for any
client participating in a conference. This can be accomplished client participating in a conference. This can be accomplished
through the use of the mechanisms described in Section 12.2, as through the use of the mechanisms described in Section 11.2, as
well as by using the security mechanisms associated with the well as by using the security mechanisms associated with the
specific signaling (e.g., SIPS) and media protocols (e.g., SRTP). specific signaling (e.g., SIPS) and media protocols (e.g., SRTP).
12.1. Assuring that the Proper Conferencing Server has been contacted 11.1. Assuring that the Proper Conferencing Server has been contacted
When the CCMP transaction is conducted using TLS [RFC5246], the When the CCMP transaction is conducted using TLS [RFC5246], the
conference server can authenticate its identity, either as a domain conference server can authenticate its identity, either as a domain
name or as an IP address, to the conference client by presenting a name or as an IP address, to the conference client by presenting a
certificate containing that identifier as a subjectAltName (i.e., as certificate containing that identifier as a subjectAltName (i.e., as
an iPAddress or dNSName, respectively). With the use of HTTP as a an iPAddress or dNSName, respectively). With the use of HTTP as a
transport for CCMP, this is exactly the authentication described by transport for CCMP, this is exactly the authentication described by
TLS [RFC2818]. If the client has external information as to the TLS [RFC2818]. If the client has external information as to the
expected identity or credentials of the proper conference server expected identity or credentials of the proper conference server
(e.g., a certificate fingerprint), these checks MAY be omitted. Any (e.g., a certificate fingerprint), these checks MAY be omitted. Any
implementation of CCMP MUST be capable of being transacted over TLS implementation of CCMP MUST be capable of being transacted over TLS
so that the client can request the above authentication, and a so that the client can request the above authentication, and a
conference server implementation MUST include this feature. Note conference server implementation MUST include this feature. Note
that in order for the presented certificate to be valid at the that in order for the presented certificate to be valid at the
client, the client must be able to validate the certificate. In client, the client must be able to validate the certificate. In
particular, the validation path of the certificate must end in one of particular, the validation path of the certificate must end in one of
the client's trust anchors, even if that trust anchor is the the client's trust anchors, even if that trust anchor is the
conference server certificate itself. conference server certificate itself.
12.2. User Authentication and Authorization 11.2. User Authentication and Authorization
Many policy authorization decisions are based on the identity of the Many policy authorization decisions are based on the identity of the
user or the role that a user may have. The conferencing server MUST user or the role that a user may have. The conferencing server MUST
implement mechanisms for authentication of users to validate their implement mechanisms for authentication of users to validate their
identity. There are several ways that a user might authenticate its identity. There are several ways that a user might authenticate its
identity to the system. For users joining a conference using one of identity to the system. For users joining a conference using one of
the call signaling protocols, the user authentication mechanisms for the call signaling protocols, the user authentication mechanisms for
the specific protocol can be used. For the case of users joining the the specific protocol can be used. For the case of users joining the
conference using the CCMP, TLS is RECOMMENDED. conference using the CCMP, TLS is RECOMMENDED.
skipping to change at page 73, line 11 skipping to change at page 72, line 11
MUST allocate a conference user identifier (XCON-USERID) and SHOULD MUST allocate a conference user identifier (XCON-USERID) and SHOULD
associate the XCON-USERID with any signaling specific user associate the XCON-USERID with any signaling specific user
identifiers that were used for authentication and authorization. identifiers that were used for authentication and authorization.
This XCON-USERID can be provided to a specific user through the This XCON-USERID can be provided to a specific user through the
conference notification interface and MUST be provided to users that conference notification interface and MUST be provided to users that
interact with the conferencing system using the CCMP (i.e., in the interact with the conferencing system using the CCMP (i.e., in the
appropriate CCMP response messages). This conference user identifier appropriate CCMP response messages). This conference user identifier
is REQUIRED for any subsequent operations on the conference object. is REQUIRED for any subsequent operations on the conference object.
12.3. Security and Privacy of Identity 11.3. Security and Privacy of Identity
An overview of the REQUIRED privacy and anonymity for users of a An overview of the required privacy and anonymity for users of a
conferencing system are provided in the XCON Framework [RFC5239]. conferencing system are provided in the XCON Framework [RFC5239].
The security of the identity in the form of the XCON-USERID is The security of the identity in the form of the XCON-USERID is
provided in the CCMP protocol through the use of TLS. provided in the CCMP protocol through the use of TLS.
The conference server SHOULD provide mechanisms to ensure the privacy The conference server SHOULD provide mechanisms to ensure the privacy
of the XCON-USERID. This is accomplished by the conference client of the XCON-USERID. This is accomplished by the conference client
manipulation of the "provide-anonymity" element defined in the XCON manipulation of the "provide-anonymity" element defined in the XCON
data model ([I-D.ietf-xcon-common-data-model]. The "provide- data model ([I-D.ietf-xcon-common-data-model]. The "provide-
anonymity" element controls the degree to which a user reveals their anonymity" element controls the degree to which a user reveals their
identity. The conference client MUST set the "provide-anonymity" identity. The conference client MUST set the "provide-anonymity"
element to "hidden" if the user does not want other participants to element to "hidden" if the user does not want other participants to
even be aware that there is an additional participant in the even be aware that there is an additional participant in the
conference. The conference client MUST set the "provide-anonymity" conference. The conference client MUST set the "provide-anonymity"
field to "private" the user wants to be entirely "anonymous" (i.e., field to "private" if the user wants to be entirely "anonymous"
other participants are aware that there is another participant, but (i.e., other participants are aware that there is another
have no information as to their identity). The conference client participant, but have no information as to their identity). The
MUST set the "provide-anonymity" field to "semi-private" if their conference client MUST set the "provide-anonymity" field to "semi-
identity is only to be revealed to other participants or users that private" if their identity is only to be revealed to other
have a higher level authorization (e.g., a conferencing system can be participants or users that have a higher level authorization (e.g., a
configured such that an administrator can see all users). To provide conferencing system can be configured such that an administrator can
the required privacy, the conference client SHOULD include the see all users). To provide the required privacy, the conference
"provide-anonymity" element in the "confInfo" parameter in a CCMP client SHOULD include the "provide-anonymity" element in the
confRequest message with an "update" or "create" operation or in the "confInfo" parameter in a CCMP confRequest message with an "update"
"userInfo" parameter in a CCMP userRequest message with an "update" or "create" operation or in the "userInfo" parameter in a CCMP
or "create" operation, to ensure the user is provided the appropriate userRequest message with an "update" or "create" operation, to ensure
level of privacy. If the "provide-anonymity" element is not included the user is provided the appropriate level of privacy. If the
in the conference object, then other users can see the participant's "provide-anonymity" element is not included in the conference object,
identity. then other users can see the participant's identity.
13. XML Schema 12. XML Schema
This section provides the XML schema definition of the "application/ This section provides the XML schema definition of the "application/
ccmp+xml" format. ccmp+xml" format.
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="utf-8"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:xcon:ccmp" targetNamespace="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="urn:ietf:params:xml:ns:xcon:ccmp" xmlns="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:tns="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:tns="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:dm="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:dm="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"> xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import <xs:import
namespace="urn:ietf:params:xml:ns:xcon-conference-info" namespace="urn:ietf:params:xml:ns:xcon-conference-info"
schemaLocation="DataModel.xsd"/> schemaLocation="DataModel.xsd"/>
<xs:import <xs:import namespace="urn:ietf:params:xml:ns:conference-info"
namespace="urn:ietf:params:xml:ns:conference-info" schemaLocation="rfc4575.xsd"/>
schemaLocation="rfc4575.xsd"/>
<xs:element name="ccmpRequest" type="ccmp-request-type" /> <xs:element name="ccmpRequest" type="ccmp-request-type" />
<xs:element name="ccmpResponse" type="ccmp-response-type" /> <xs:element name="ccmpResponse" type="ccmp-response-type" />
<!-- CCMP request definition --> <!-- CCMP request definition -->
<xs:complexType name="ccmp-request-type"> <xs:complexType name="ccmp-request-type">
<xs:sequence> <xs:sequence>
<xs:element name="ccmpRequest" <xs:element name="ccmpRequest"
type="ccmp-request-message-type" /> type="ccmp-request-message-type" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- CCMP response definition --> <!-- CCMP response definition -->
<xs:complexType name="ccmp-response-type"> <xs:complexType name="ccmp-response-type">
<xs:sequence> <xs:sequence>
<xs:element name="ccmpResponse" <xs:element name="ccmpResponse"
type="ccmp-response-message-type" /> type="ccmp-response-message-type" />
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- Definition of ccmp-request-message-type --> <!-- Definition of ccmp-request-message-type -->
<xs:complexType abstract="true" <xs:complexType abstract="true"
name="ccmp-request-message-type"> name="ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element name="confUserID" type="xs:string" <xs:element name="confUserID" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="confObjID" type="xs:string" <xs:element name="confObjID" type="xs:string"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:element name="operation" type="operationType" <xs:element name="operation"
minOccurs="0" maxOccurs="1" /> type="operationType"
<xs:element name="password" type="xs:string" minOccurs="0" maxOccurs="1" />
minOccurs="0" maxOccurs="1" /> <xs:element name="password" type="xs:string"
</xs:sequence> minOccurs="0" maxOccurs="1" />
</xs:complexType> </xs:sequence>
</xs:complexType>
<!-- blueprintsRequest --> <!-- blueprintsRequest -->
<xs:complexType name="ccmp-blueprints-request-message-type"> <xs:complexType name="ccmp-blueprints-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/> <xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- blueprintRequest --> <!-- blueprintRequest -->
<xs:complexType name="ccmp-blueprint-request-message-type"> <xs:complexType name="ccmp-blueprint-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"> <xs:extension base="tns:ccmp-request-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="blueprintRequest" /> <xs:element ref="blueprintRequest" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- blueprintRequestType --> <!-- blueprintRequestType -->
<xs:element name="blueprintRequest" type="blueprintRequestType" /> <xs:element name="blueprintRequest"
type="blueprintRequestType" />
<xs:complexType name="blueprintRequestType"> <xs:complexType name="blueprintRequestType">
<xs:sequence> <xs:sequence>
<xs:element name="blueprintInfo" <xs:element name="blueprintInfo"
type="info:conference-type" minOccurs="0"/> type="info:conference-type"
</xs:sequence> minOccurs="0"/>
</xs:complexType> </xs:sequence>
</xs:complexType>
<!-- confsRequest --> <!-- confsRequest -->
<xs:complexType name="ccmp-confs-request-message-type"> <xs:complexType name="ccmp-confs-request-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/> <xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType>
</xs:complexType> <!-- confRequest -->
<xs:complexType name="ccmp-conf-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="confRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- confRequest --> <!-- confRequestType -->
<xs:complexType name="ccmp-conf-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="confRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- confRequestType --> <xs:element name="confRequest" type="confRequestType" />
<xs:element name="confRequest" type="confRequestType" /> <xs:complexType name="confRequestType">
<xs:sequence>
<xs:element name="confInfo"
type="info:conference-type"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="confRequestType"> <!-- usersRequest -->
<xs:sequence> <xs:complexType name="ccmp-users-request-message-type">
<xs:element name="confInfo" <xs:complexContent>
type="info:conference-type" minOccurs="0"/> <xs:extension base="tns:ccmp-request-message-type">
</xs:sequence> <xs:sequence>
</xs:complexType> <xs:element ref="usersRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- usersRequest --> <!-- usersRequestType -->
<xs:complexType name="ccmp-users-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="usersRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- usersRequestType --> <xs:element name="usersRequest" type="usersRequestType" />
<xs:complexType name="usersRequestType">
<xs:sequence>
<xs:element name="usersInfo"
type="info:users-type"
minOccurs="0" />
<xs:element name="usersRequest" type="usersRequestType" /> </xs:sequence>
</xs:complexType>
<xs:complexType name="usersRequestType"> <!-- userRequest -->
<xs:sequence> <xs:complexType name="ccmp-user-request-message-type">
<xs:element name="usersInfo" <xs:complexContent>
type="info:users-type" minOccurs="0" /> <xs:extension base="tns:ccmp-request-message-type">
</xs:sequence> <xs:sequence>
</xs:complexType> <xs:element ref="userRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- userRequest --> <!-- userRequestType -->
<xs:complexType name="ccmp-user-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="userRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- userRequestType --> <xs:element name="userRequest" type="userRequestType" />
<xs:element name="userRequest" type="userRequestType" /> <xs:complexType name="userRequestType">
<xs:sequence>
<xs:element name="userInfo"
type="info:user-type"
minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="userRequestType"> <!-- sidebarsByValRequest -->
<xs:sequence>
<xs:element name="userInfo"
type="info:user-type" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<!-- sidebarsByValRequest --> <xs:complexType name="ccmp-sidebarsByVal-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ccmp-sidebarsByVal-request-message-type"> <!-- sidebarsByRefRequest -->
<xs:complexContent> <xs:complexType name="ccmp-sidebarsByRef-request-message-type">
<xs:extension base="tns:ccmp-request-message-type"/> <xs:complexContent>
</xs:complexContent> <xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexType> </xs:complexContent>
</xs:complexType>
<!-- sidebarsByRefRequest --> <!-- sidebarByValRequest -->
<xs:complexType name="ccmp-sidebarsByRef-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type"/>
</xs:complexContent>
</xs:complexType>
<!-- sidebarByValRequest --> <xs:complexType name="ccmp-sidebarByVal-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="sidebarByValRequest" />
<xs:complexType name="ccmp-sidebarByVal-request-message-type"> </xs:sequence>
<xs:complexContent> </xs:extension>
<xs:extension base="tns:ccmp-request-message-type"> </xs:complexContent>
<xs:sequence> </xs:complexType>
<xs:element ref="sidebarByValRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- sidebarByValRequestType -->
<xs:element name="sidebarByValRequest" <!-- sidebarByValRequestType -->
type="sidebarByValRequestType" />
<xs:complexType name="sidebarByValRequestType"> <xs:element name="sidebarByValRequest"
<xs:sequence> type="sidebarByValRequestType" />
<xs:element name="sidebarByValInfo"
type="info:conference-type" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<!-- sidebarByRefRequest --> <xs:complexType name="sidebarByValRequestType">
<xs:sequence>
<xs:element name="sidebarByValInfo"
type="info:conference-type"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ccmp-sidebarByRef-request-message-type"> <!-- sidebarByRefRequest -->
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="sidebarByRefRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- sidebarByRefRequestType --> <xs:complexType name="ccmp-sidebarByRef-request-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-request-message-type">
<xs:sequence>
<xs:element ref="sidebarByRefRequest" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="sidebarByRefRequest" <!-- sidebarByRefRequestType -->
type="sidebarByRefRequestType" />
<xs:complexType name="sidebarByRefRequestType"> <xs:element name="sidebarByRefRequest"
<xs:sequence> type="sidebarByRefRequestType" />
<xs:element name="sidebarByRefInfo"
type="info:conference-type" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<!-- Definition of ccmp-response-message-type --> <xs:complexType name="sidebarByRefRequestType">
<xs:sequence>
<xs:element name="sidebarByRefInfo"
type="info:conference-type"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType abstract="true" <!-- Definition of ccmp-response-message-type -->
name="ccmp-response-message-type">
<xs:sequence>
<xs:element name="confUserID" type="xs:string"
minOccurs="1" maxOccurs="1" />
<xs:element name="confObjID" type="xs:string"
minOccurs="0" maxOccurs="1" />
<xs:element name="operation" minOccurs="0"
maxOccurs="1" />
<xs:element ref="response-code" minOccurs="1"
maxOccurs="1" />
</xs:sequence>
</xs:complexType>
<!-- blueprintsResponse --> <xs:complexType abstract="true"
<xs:complexType name="ccmp-blueprints-response-message-type"> name="ccmp-response-message-type">
<xs:complexContent> <xs:sequence>
<xs:extension base="tns:ccmp-response-message-type"> <xs:element name="confUserID" type="xs:string"
<xs:sequence> minOccurs="1" maxOccurs="1" />
<xs:element ref="blueprintsResponse" /> <xs:element name="confObjID" type="xs:string"
</xs:sequence> minOccurs="0" maxOccurs="1" />
</xs:extension> <xs:element name="operation"
</xs:complexContent> minOccurs="0"
</xs:complexType> maxOccurs="1" />
<xs:element ref="response-code" minOccurs="1"
maxOccurs="1" />
<xs:element name="response-string"
type="xs:string"
minOccurs="0" maxOccurs="1" />
<xs:element name="version"
type="xs:positiveInteger"
minOccurs="0" maxOccurs="1" />
</xs:sequence>
</xs:complexType>
<!-- blueprintsResponseType --> <!-- blueprintsResponse -->
<xs:complexType name="ccmp-blueprints-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="blueprintsResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="blueprintsResponse" <!-- blueprintsResponseType -->
type="blueprintsResponseType" />
<xs:complexType name="blueprintsResponseType"> <xs:element name="blueprintsResponse"
<xs:sequence> type="blueprintsResponseType" />
<xs:element name="blueprintsInfo"
type="info:uris-type" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<!-- blueprintResponse --> <xs:complexType name="blueprintsResponseType">
<xs:complexType name="ccmp-blueprint-response-message-type"> <xs:sequence>
<xs:complexContent> <xs:element name="blueprintsInfo"
<xs:extension base="tns:ccmp-response-message-type"> type="info:uris-type" minOccurs="0"/>
<xs:sequence> </xs:sequence>
<xs:element ref="blueprintResponse" /> </xs:complexType>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- blueprintResponseType --> <!-- blueprintResponse -->
<xs:complexType name="ccmp-blueprint-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="blueprintResponse" />
</xs:sequence>
<xs:element name="blueprintResponse" </xs:extension>
type="blueprintResponseType" /> </xs:complexContent>
<xs:complexType name="blueprintResponseType"> </xs:complexType>
<xs:sequence>
<xs:element name="blueprintInfo" type="info:conference-type"/>
</xs:sequence>
</xs:complexType>
<!-- confsResponse -->
<xs:complexType name="ccmp-confs-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="confsResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- confsResponseType --> <!-- blueprintResponseType -->
<xs:element name="confsResponse" <xs:element name="blueprintResponse"
type="confsResponseType" /> type="blueprintResponseType" />
<xs:complexType name="confsResponseType"> <xs:complexType name="blueprintResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="confsInfo" <xs:element name="blueprintInfo"
type="info:uris-type" minOccurs="0"/> type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- confResponse --> <!-- confsResponse -->
<xs:complexType name="ccmp-conf-response-message-type"> <xs:complexType name="ccmp-confs-response-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type"> <xs:extension base="tns:ccmp-response-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="confResponse" /> <xs:element ref="confsResponse" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- confResponseType --> <!-- confsResponseType -->
<xs:element name="confResponse" <xs:element name="confsResponse" type="confsResponseType" />
type="confResponseType" />
<xs:complexType name="confResponseType">
<xs:sequence>
<xs:element name="confInfo"
type="info:conference-type"/>
</xs:sequence>
</xs:complexType>
<!-- usersResponse --> <xs:complexType name="confsResponseType">
<xs:complexType name="ccmp-users-response-message-type"> <xs:sequence>
<xs:complexContent> <xs:element name="confsInfo"
<xs:extension base="tns:ccmp-response-message-type"> type="info:uris-type"
<xs:sequence> minOccurs="0"/>
<xs:element ref="usersResponse" /> </xs:sequence>
</xs:sequence> </xs:complexType>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- usersResponseType --> <!-- confResponse -->
<xs:complexType name="ccmp-conf-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="confResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
<xs:element name="usersResponse" type="usersResponseType" /> </xs:complexType>
<xs:complexType name="usersResponseType"> <!-- confResponseType -->
<xs:sequence>
<xs:element name="usersInfo" type="info:users-type"/>
</xs:sequence>
</xs:complexType>
<!-- userResponse --> <xs:element name="confResponse" type="confResponseType" />
<xs:complexType name="ccmp-user-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="userResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- userResponseType --> <xs:complexType name="confResponseType">
<xs:sequence>
<xs:element name="confInfo" type="info:conference-type"/>
</xs:sequence>
</xs:complexType>
<xs:element name="userResponse" type="userResponseType" /> <!-- usersResponse -->
<xs:complexType name="userResponseType"> <xs:complexType name="ccmp-users-response-message-type">
<xs:sequence> <xs:complexContent>
<xs:element name="userInfo" type="info:user-type"/> <xs:extension base="tns:ccmp-response-message-type">
</xs:sequence> <xs:sequence>
</xs:complexType> <xs:element ref="usersResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- sidebarsByValResponse --> <!-- usersResponseType -->
<xs:complexType name="ccmp-sidebarsByVal-response-message-type"> <xs:element name="usersResponse" type="usersResponseType" />
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="sidebarsByValResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent> <xs:complexType name="usersResponseType">
</xs:complexType> <xs:sequence>
<xs:element name="usersInfo" type="info:users-type"/>
</xs:sequence>
</xs:complexType>
<!-- sidebarsByValResponseType --> <!-- userResponse -->
<xs:complexType name="ccmp-user-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="userResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="sidebarsByValResponse" <!-- userResponseType -->
type="sidebarsByValResponseType" />
<xs:complexType name="sidebarsByValResponseType"> <xs:element name="userResponse" type="userResponseType" />
<xs:sequence> <xs:complexType name="userResponseType">
<xs:element name="sidebarsByValInfo" <xs:sequence>
type="info:sidebars-by-val-type"/> <xs:element name="userInfo" type="info:user-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- sidebarsByRefResponse --> <!-- sidebarsByValResponse -->
<xs:complexType name="ccmp-sidebarsByref-response-message-type"> <xs:complexType name="ccmp-sidebarsByVal-response-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type"> <xs:extension base="tns:ccmp-response-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarsByRefResponse" /> <xs:element ref="sidebarsByValResponse" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- sidebarsByRefResponseType --> <!-- sidebarsByValResponseType -->
<xs:element name="sidebarsByRefResponse" <xs:element name="sidebarsByValResponse"
type="sidebarsByRefResponseType" /> type="sidebarsByValResponseType" />
<xs:complexType name="sidebarsByRefResponseType">
<xs:sequence>
<xs:element name="sidebarsByRefInfo"
type="info:uris-type"/>
</xs:sequence>
</xs:complexType>
<!-- sidebarByValResponse --> <xs:complexType name="sidebarsByValResponseType">
<xs:sequence>
<xs:element name="sidebarsByValInfo"
type="info:sidebars-by-val-type"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ccmp-sidebarByVal-response-message-type"> <!-- sidebarsByRefResponse -->
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="sidebarByValResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType> <xs:complexType name="ccmp-sidebarsByref-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="sidebarsByRefResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- sidebarByValResponseType --> <!-- sidebarsByRefResponseType -->
<xs:element name="sidebarByValResponse" <xs:element name="sidebarsByRefResponse"
type="sidebarByValResponseType" /> type="sidebarsByRefResponseType" />
<xs:complexType name="sidebarByValResponseType"> <xs:complexType name="sidebarsByRefResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarByValInfo" <xs:element name="sidebarsByRefInfo"
type="info:conference-type"/> type="info:uris-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- sidebarByRefResponse --> <!-- sidebarByValResponse -->
<xs:complexType name="ccmp-sidebarByref-response-message-type"> <xs:complexType name="ccmp-sidebarByVal-response-message-type">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type"> <xs:extension base="tns:ccmp-response-message-type">
<xs:sequence> <xs:sequence>
<xs:element ref="sidebarByRefResponse" /> <xs:element ref="sidebarByValResponse" />
</xs:sequence> </xs:sequence>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- sidebarByRefResponseType --> <!-- sidebarByValResponseType -->
<xs:element name="sidebarByRefResponse" <xs:element name="sidebarByValResponse"
type="sidebarByRefResponseType" /> type="sidebarByValResponseType" />
<xs:complexType name="sidebarByRefResponseType"> <xs:complexType name="sidebarByValResponseType">
<xs:sequence> <xs:sequence>
<xs:element name="sidebarByRefInfo" <xs:element name="sidebarByValInfo"
type="info:conference-type"/> type="info:conference-type"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- response-code --> <!-- sidebarByRefResponse -->
<xs:element name="response-code" type="response-codeType" /> <xs:complexType name="ccmp-sidebarByref-response-message-type">
<xs:complexContent>
<xs:extension base="tns:ccmp-response-message-type">
<xs:sequence>
<xs:element ref="sidebarByRefResponse" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:simpleType name="response-codeType"> <!-- sidebarByRefResponseType -->
<xs:restriction base="xs:token">
<xs:enumeration value="success"/>
<xs:enumeration value="pending"/>
<xs:enumeration value="modified"/>
<xs:enumeration value="badRequest"/>
<xs:enumeration value="unauthorized"/>
<xs:enumeration value="forbidden"/>
<xs:enumeration value="objectNotFound"/>
<xs:enumeration value="userNotFound"/>
<xs:enumeration value="invalidConfUserID"/>
<xs:enumeration value="passwordRequired"/>
<xs:enumeration value="invalidPassword"/>
<xs:enumeration value="forbiddenDeleteParent"/>
<xs:enumeration value="forbiddenChangeProtected"/>
<xs:enumeration value="requestTimeout"/>
<xs:enumeration value="serverInternalError"/>
<xs:enumeration value="notImplemented"/>
</xs:restriction>
</xs:simpleType>
<!-- operationType --> <xs:element name="sidebarByRefResponse"
type="sidebarByRefResponseType" />
<xs:simpleType name="operationType"> <xs:complexType name="sidebarByRefResponseType">
<xs:restriction base="xs:token"> <xs:sequence>
<xs:enumeration value="retrieve"/> <xs:element name="sidebarByRefInfo"
<xs:enumeration value="create"/> type="info:conference-type"/>
<xs:enumeration value="update"/> </xs:sequence>
<xs:enumeration value="delete"/> </xs:complexType>
</xs:restriction>
</xs:simpleType> <!-- response-code -->
</xs:schema>
<xs:element name="response-code" type="response-codeType" />
<xs:simpleType name="response-codeType">
<xs:restriction base="xs:token">
<xs:enumeration value="success"/>
<xs:enumeration value="updateFailed"/>
<xs:enumeration value="badRequest"/>
<xs:enumeration value="unauthorized"/>
<xs:enumeration value="forbidden"/>
<xs:enumeration value="objectNotFound"/>
<xs:enumeration value="userNotFound"/>
<xs:enumeration value="invalidConfUserID"/>
<xs:enumeration value="passwordRequired"/>
<xs:enumeration value="invalidPassword"/>
<xs:enumeration value="forbiddenDeleteParent"/>
<xs:enumeration value="forbiddenChangeProtected"/>
<xs:enumeration value="requestTimeout"/>
<xs:enumeration value="serverInternalError"/>
<xs:enumeration value="notImplemented"/>
</xs:restriction>
</xs:simpleType>
<!-- operationType -->
<xs:simpleType name="operationType">
<xs:restriction base="xs:token">
<xs:enumeration value="retrieve"/>
<xs:enumeration value="create"/>
<xs:enumeration value="update"/>
<xs:enumeration value="delete"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
Figure 25 Figure 25
14. IANA Considerations 13. IANA Considerations
This document registers a new XML namespace, a new XML schema, and This document registers a new XML namespace, a new XML schema, and
the MIME type for the schema. This document also registers the the MIME type for the schema. This document also registers the
"XCON" Application Service tag and the "CCMP" Application Protocol "XCON" Application Service tag and the "CCMP" Application Protocol
tag. This document also defines registries for the CCMP operation tag. This document also defines registries for the CCMP operation
types and response codes. types and response codes.
14.1. URN Sub-Namespace Registration 13.1. URN Sub-Namespace Registration
This section registers a new XML namespace, This section registers a new XML namespace,
""urn:ietf:params:xml:ns:xcon:ccmp"". ""urn:ietf:params:xml:ns:xcon:ccmp"".
URI: "urn:ietf:params:xml:ns:xcon:ccmp" URI: "urn:ietf:params:xml:ns:xcon:ccmp"
Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Registrant Contact: IETF, XCON working group, (xcon@ietf.org),
Mary Barnes (mary.barnes@nortel.com). Mary Barnes (mary.barnes@nortel.com).
XML: XML:
skipping to change at page 85, line 43 skipping to change at page 84, line 43
<body> <body>
<h1>Namespace for CCMP Messages</h1> <h1>Namespace for CCMP Messages</h1>
<h2>urn:ietf:params:xml:ns:xcon:ccmp</h2> <h2>urn:ietf:params:xml:ns:xcon:ccmp</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
14.2. XML Schema Registration 13.2. XML Schema Registration
This section registers an XML schema as per the guidelines in This section registers an XML schema as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:xcon:ccmp URI: urn:ietf:params:xml:schema:xcon:ccmp
Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary
Barnes (mary.barnes@nortel.com). Barnes (mary.barnes@nortel.com).
Schema: The XML for this schema can be found as the entirety of Schema: The XML for this schema can be found as the entirety of
Section 13 of this document. Section 12 of this document.
14.3. MIME Media Type Registration for 'application/ccmp+xml' 13.3. MIME Media Type Registration for 'application/ccmp+xml'
This section registers the "application/ccmp+xml" MIME type. This section registers the "application/ccmp+xml" MIME type.
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of MIME media type application/ccmp+xml Subject: Registration of MIME media type application/ccmp+xml
MIME media type name: application MIME media type name: application
MIME subtype name: ccmp+xml MIME subtype name: ccmp+xml
skipping to change at page 87, line 16 skipping to change at page 86, line 16
Barnes <mary.barnes@nortel.com> Barnes <mary.barnes@nortel.com>
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author/Change controller: The IETF Author/Change controller: The IETF
Other information: This media type is a specialization of Other information: This media type is a specialization of
application/xml [RFC3023], and many of the considerations application/xml [RFC3023], and many of the considerations
described there also apply to application/ccmp+xml. described there also apply to application/ccmp+xml.
14.4. DNS Registrations 13.4. DNS Registrations
Section 14.4.1 defines an Application Service tag of "XCON", which is Section 13.4.1 defines an Application Service tag of "XCON", which is
used to identify the centralized conferencing (XCON) server for a used to identify the centralized conferencing (XCON) server for a
particular domain. The Application Protocol tag "CCMP", defined in particular domain. The Application Protocol tag "CCMP", defined in
Section 14.4.2, is used to identify an XCON server that understands Section 13.4.2, is used to identify an XCON server that understands
the CCMP protocol. the CCMP protocol.
14.4.1. Registration of a Location Server Application Service Tag 13.4.1. Registration of a Conference Control Server Application Service
Tag
This section registers a new S-NAPTR/U-NAPTR Application Service tag This section registers a new S-NAPTR/U-NAPTR Application Service tag
for XCON, as mandated by [RFC3958]. for XCON, as mandated by [RFC3958].
Application Service Tag: XCON Application Service Tag: XCON
Intended usage: Identifies a server that supports centralized Intended usage: Identifies a server that supports centralized
conferencing. conferencing.
Defining publication: RFCXXXX Defining publication: RFCXXXX
Contact information: The authors of this document Contact information: The authors of this document
Author/Change controller: The IESG Author/Change controller: The IESG
14.4.2. Registration of a Location Server Application Protocol Tag for 13.4.2. Registration of a Conference Control Server Application
HELD Protocol Tag for CCMP
This section registers a new S-NAPTR/U-NAPTR Application Protocol tag This section registers a new S-NAPTR/U-NAPTR Application Protocol tag
for the CCMP protocol, as mandated by [RFC3958]. for the CCMP protocol, as mandated by [RFC3958].
Application Service Tag: CCMP Application Service Tag: CCMP
Intended Usage: Identifies the Centralized Conferencing (XCON) Intended Usage: Identifies the Centralized Conferencing (XCON)
Manipulation Protocol. Manipulation Protocol.
Applicable Service Tag(s): XCON Applicable Service Tag(s): XCON
Terminal NAPTR Record Type(s): U Terminal NAPTR Record Type(s): U
Defining Publication: RFCXXXX Defining Publication: RFCXXXX
Contact Information: The authors of this document Contact Information: The authors of this document
Author/Change Controller: The IESG Author/Change Controller: The IESG
14.5. CCMP Protocol Registry 13.5. CCMP Protocol Registry
This document requests that the IANA create a new registry for the This document requests that the IANA create a new registry for the
CCMP protocol including an initial registry for operation types and CCMP protocol including an initial registry for operation types and
response codes. response codes.
14.5.1. CCMP Message Types 13.5.1. CCMP Message Types
The CCMP messages are described in Section 7 and defined in the XML The CCMP messages are described in Section 5.1 and defined in the XML
schema in Section 13. The following summarizes the requested schema in Section 12. The following summarizes the requested
registry: registry:
Related Registry: CCMP Message Types Registry Related Registry: CCMP Message Types Registry
Defining RFC: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX Defining RFC: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
with the RFC number for this specification.] with the RFC number for this specification.]
Registration/Assignment Procedures: New CCMP message types are Registration/Assignment Procedures: New CCMP message types are
allocated on a specification required basis. allocated on a specification required basis.
Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary
Barnes (mary.barnes@nortel.com). Barnes (mary.barnes@nortel.com).
This section pre-registers the following initial CCMP message types: This section pre-registers the following initial CCMP message types:
blueprintsRequest: Used by a conference control client to query a blueprintsRequest: Used by a conference control client to query a
conferencing system for its capabilities, in terms of available conferencing system for its capabilities, in terms of available
conference blueprints. conference blueprints.
blueprintsResponse: The optionsResponse returns a list of Blueprints blueprintsResponse: The blueprintsResponse returns a list of
supported by the specific conference server. blueprints supported by the specific conference server.
confsRequest: Used by a conference control client to query a confsRequest: Used by a conference control client to query a
conferencing system for its scheduled/active conferences. conferencing system for its scheduled/active conferences.
confsResponse: The confsResponse returns the list of the currently confsResponse: The "confsResponse" returns the list of the currently
activated/scheduled conferences at the server. activated/scheduled conferences at the server.
confRequest: The confRequest is used to create a conference object confRequest: The "confRequest" is used to create a conference object
and/or to request an operation on the conference object as a and/or to request an operation on the conference object as a
whole. whole.
confResponse: The confResponse indicates the result of the operation confResponse: The "confResponse" indicates the result of the
on the conference object as a whole. operation on the conference object as a whole.
userRequest: The userRequest is used to request an operation on the userRequest: The "userRequest" is used to request an operation on
"user" element in the conference object. the "user" element in the conference object.
userResponse: The userResponse indicates the result of the requested userResponse: The "userResponse" indicates the result of the
operation on the "user" element in the conference object. requested operation on the "user" element in the conference
object.
usersRequest This usersRequest is used to manipulate the "users" usersRequest This "usersRequest" is used to manipulate the "users"
element in the conference object, including parameters such as the element in the conference object, including parameters such as the
allowed-users-list, join-handling, etc. "allowed-users-list", "join-handling", etc.
usersResponse: This usersResponse indicates the result of the usersResponse: This "usersResponse" indicates the result of the
request to manipulate the "users" element in the conference request to manipulate the "users" element in the conference
object. object.
sidebarRequest: This sidebarRequest is used to retrieve the sidebarRequest: This "sidebarRequest" is used to retrieve the
information related to a sidebar or to create, change or delete a information related to a sidebar or to create, change or delete a
specific sidebar. specific sidebar.
sidebarResponse: This sidebarResponse indicates the result of the sidebarResponse: This "sidebarResponse" indicates the result of the
sidebarRequest. sidebarRequest.
14.5.2. CCMP Response Codes 13.5.2. CCMP Response Codes
The following summarizes the requested registry for CCMP Response The following summarizes the requested registry for CCMP Response
codes: codes:
Related Registry: CCMP Response Code Registry Related Registry: CCMP Response Code Registry
Defining RFC: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX Defining RFC: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
with the RFC number for this specification.] with the RFC number for this specification.]
Registration/Assignment Procedures: New response codes are allocated Registration/Assignment Procedures: New response codes are allocated
on a first-come/first-serve basis with specification required. on a first-come/first-serve basis with specification required.
Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary Registrant Contact: IETF, XCON working group, (xcon@ietf.org), Mary
Barnes (mary.barnes@nortel.com). Barnes (mary.barnes@nortel.com).
This section pre-registers the following thirteen initial response This section pre-registers the following thirteen initial response
codes as described above in Section 7: codes as described above in Section 5.1:
success: This code indicates that the request was successfully success: This code indicates that the request was successfully
processed. processed.
modified: This code indicates that the object was created, but may updateFailed: This code indicates that a requested "update" cannot
differ from the request. be successfully completed by the server. An example of such
situation is when the modification of an object cannot be applied
due to conflicts arising at the server's side (e.g. because the
client version of the object is an obsolete one and the requested
modifications collide with the up-to-date state of the object
stored at the server).
badRequest: This code indicates that the request was badly formed in badRequest: This code indicates that the request was badly formed in
some fashion. some fashion.
unauthorized: This code indicates that the user was not authorized unauthorized: This code indicates that the user was not authorized
for the specific operation on the conference object. for the specific operation on the conference object.
forbidden: This code indicates that the specific operation is not forbidden: This code indicates that the specific operation is not
valid for the target conference object. valid for the target conference object.
objectNotFound: This code indicates that the specific conference objectNotFound: This code indicates that the specific conference
object was not found. object was not found.
userNotFound: This code is returned in answer to a 'userRequest/ userNotFound: This code is returned in answer to a "userRequest/
create' operation, in the case of a third-party invite, when the create" operation, in the case of a third-party invite, when the
'confUserId' (contained in the 'entity' attribute of the "confUserId" (contained in the "entity" attribute of the
'userInfo' parameter) of the user to be added is unknown. "userInfo" parameter) of the user to be added is unknown.
invalidConfUserID: This code is returned in the case of requests in invalidConfUserID: This code is returned in the case of requests in
which the 'confUserID' of the sender is invalid. which the "confUserID" of the sender is invalid.
invalidPassword: This code is returned in response to all requests invalidPassword: This code is returned in response to all requests
wishing to access/manipulate a password-protected conference wishing to access/manipulate a password-protected conference
object, when the 'password' parameter contained in the request is object, when the "password" parameter contained in the request is
wrong. wrong.
passwordRequired: This code is returned in response to all requests passwordRequired: This code is returned in response to all requests
wishing to access/manipulate a password-protected conference wishing to access/manipulate a password-protected conference
object, when the 'password' parameter is missing in the request. object, when the "password" parameter is missing in the request.
operationNotAllowed: This code indicates that the specific operation
is not allowed for the target conference object (e.g.., due to
policies, etc.)
deleteFailedParent: This code indicates that the conferencing system forbiddenDeleteParent: This code indicates that the conferencing
cannot delete the specific conference object because it is a system cannot delete the specific conference object because it is
parent for another conference object. a parent for another conference object.
changeFailedProtected: This code indicates that the target forbiddenChangeProtected: This code indicates that the target
conference object cannot be changed (e.g., due to policies, roles, conference object cannot be changed (e.g., due to policies, roles,
privileges, etc.). privileges, etc.).
requestTimeout: This code indicates that the request could not be requestTimeout: This code indicates that the request could not be
processed within a reasonable time, with the time specific to a processed within a reasonable time, with the time specific to a
conferencing system implementation. conferencing system implementation.
serverInternalError: This code indicates that the conferencing serverInternalError: This code indicates that the conferencing
system experienced some sort of internal error. system experienced some sort of internal error.
notImplemented: This code indicates that the specific operation is notImplemented: This code indicates that the specific operation is
not implemented on that conferencing system. not implemented on that conferencing system.
15. Acknowledgments 14. Acknowledgments
The authors appreciate the feedback provided by Dave Morgan, Pierre The authors appreciate the feedback provided by Dave Morgan, Pierre
Tane, Lorenzo Miniero, Tobia Castaldi, Theo Zourzouvillys, Sean Duddy Tane, Lorenzo Miniero, Tobia Castaldi, Theo Zourzouvillys, Sean
and Oscar Novo. Special thanks go to Roberta Presta for her Duddy, Oscar Novo, Richard Barnes and Simo Veikkolainen. Special
invaluable contribution to this document. Roberta has worked on the thanks go to Roberta Presta for her invaluable contribution to this
specification of the CCMP protocol at the University of Napoli for document. Roberta has worked on the specification of the CCMP
the preparation of her Master thesis. She has also implemented the protocol at the University of Napoli for the preparation of her
CCMP prototype used for the trials and from which the dumps provided Master thesis. She has also implemented the CCMP prototype used for
in Section 8 have been extracted. the trials and from which the dumps provided in Section 7 have been
extracted.
16. Changes since last Version 15. Changes since last Version
NOTE TO THE RFC-Editor: Please remove this section prior to NOTE TO THE RFC-Editor: Please remove this section prior to
publication as an RFC. publication as an RFC.
The following summarizes the changes between the WG 03 and the 04:
1. Re-organized document based on feedback from Richard Barnes.
2. Editorial clarifications and nits, including those identified by
Richard and Simo Veikkolainen.
The following summarizes the changes between the WG 02 and the 03: The following summarizes the changes between the WG 02 and the 03:
1. Clarified that the confUserID is optional in the generic CCMP 1. Clarified that the confUserID is optional in the generic CCMP
request message for a userRequest with a "create" operation. request message for a userRequest with a "create" operation.
2. Added responseCode (error cases) handling - a general section for 2. Added responseCode (error cases) handling - a general section for
each of the operations (as part of CCMP Response Code section), each of the operations (as part of CCMP Response Code section),
so we don't need to re-iterate for each of the messages and so we don't need to re-iterate for each of the messages and
message specific cases as appropriate (e.g., deleteParentFailed, message specific cases as appropriate (e.g., deleteParentFailed,
modified) modified)
skipping to change at page 95, line 5 skipping to change at page 94, line 5
6. Added placeholders for Notifications and Role Based Access 6. Added placeholders for Notifications and Role Based Access
Control. Control.
7. Added some text for discovery using DNS (including IANA 7. Added some text for discovery using DNS (including IANA
registrations) registrations)
8. Updated References: updated XCON FW RFC, SOAP/W3C moved to 8. Updated References: updated XCON FW RFC, SOAP/W3C moved to
informational section. informational section.
17. References 16. References
17.1. Normative References 16.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Leach, P., Luotonen, A., and L. Stewart, "HTTP
skipping to change at page 95, line 38 skipping to change at page 94, line 38
[RFC5239] Barnes, M., Boulton, C., and O. Levin, "A Framework for [RFC5239] Barnes, M., Boulton, C., and O. Levin, "A Framework for
Centralized Conferencing", RFC 5239, June 2008. Centralized Conferencing", RFC 5239, June 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[I-D.ietf-xcon-common-data-model] [I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen, Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized "Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-13 Conferencing (XCON)", draft-ietf-xcon-common-data-model-14
(work in progress), April 2009. (work in progress), November 2009.
17.2. Informative References 16.2. Informative References
[REST] Fielding, "Architectural Styles and the Design of Network- [REST] Fielding, "Architectural Styles and the Design of Network-
based Software Architectures", 2000. based Software Architectures", 2000.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
skipping to change at page 96, line 15 skipping to change at page 95, line 15
[RFC3958] Daigle, L. and A. Newton, "Domain-Based Application [RFC3958] Daigle, L. and A. Newton, "Domain-Based Application
Service Location Using SRV RRs and the Dynamic Delegation Service Location Using SRV RRs and the Dynamic Delegation
Discovery Service (DDDS)", RFC 3958, January 2005. Discovery Service (DDDS)", RFC 3958, January 2005.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
RFC 3966, December 2004. RFC 3966, December 2004.
[I-D.ietf-xcon-event-package] [I-D.ietf-xcon-event-package]
Camarillo, G., Srinivasan, S., Even, R., and J. Camarillo, G., Srinivasan, S., Even, R., and J.
Urpalainen, "Conference Event Package Data Format Urpalainen, "Conference Event Package Data Format
Extension for Centralized Conferencing (XCON)", Extension for Centralized Conferencing (XCON)",
draft-ietf-xcon-event-package-01 (work in progress), draft-ietf-xcon-event-package-01 (work in progress),
September 2008. September 2008.
[I-D.ietf-xcon-examples]
Barnes, M., Boulton, C., Miniero, L., Presta, R., and S.
Romano, "Centralized Conferencing Manipulation Protocol
(CCMP) Call Flow Examples", draft-ietf-xcon-examples-01
(work in progress), July 2009.
[W3C.REC-soap12-part1-20030624] [W3C.REC-soap12-part1-20030624]
Mendelsohn, N., Gudgin, M., Nielsen, H., Moreau, J., and Nielsen, H., Gudgin, M., Moreau, J., Mendelsohn, N., and
M. Hadley, "SOAP Version 1.2 Part 1: Messaging Framework", M. Hadley, "SOAP Version 1.2 Part 1: Messaging Framework",
World Wide Web Consortium FirstEdition REC-soap12-part1- World Wide Web Consortium FirstEdition REC-soap12-part1-
20030624, June 2003, 20030624, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part1-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part1-20030624>.
[W3C.REC-soap12-part2-20030624] [W3C.REC-soap12-part2-20030624]
Gudgin, M., Mendelsohn, N., Nielsen, H., Moreau, J., and Hadley, M., Mendelsohn, N., Gudgin, M., Moreau, J., and H.
M. Hadley, "SOAP Version 1.2 Part 2: Adjuncts", World Wide Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide
Web Consortium FirstEdition REC-soap12-part2-20030624, Web Consortium FirstEdition REC-soap12-part2-20030624,
June 2003, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part2-20030624>.
Appendix A. Appendix A: Other protocol models and transports considered Appendix A. Appendix A: Other protocol models and transports considered
for CCMP for CCMP
The operations on the objects can be implemented in at least two The operations on the objects can be implemented in at least two
different ways, namely as remote procedure calls - using SOAP as different ways, namely as remote procedure calls - using SOAP as
described in Appendix A.1 and by defining resources following a described in Appendix A.1 and by defining resources following a
 End of changes. 380 change blocks. 
1351 lines changed or deleted 1335 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/