draft-ietf-xcon-examples-05.txt   draft-ietf-xcon-examples-06.txt 
XCON Working Group M. Barnes XCON Working Group M. Barnes
Internet-Draft Nortel Internet-Draft Polycom
Intended status: Informational L. Miniero Intended status: Informational L. Miniero
Expires: January 3, 2011 Meetecho Expires: January 13, 2011 Meetecho
R. Presta R. Presta
S P. Romano S P. Romano
University of Napoli University of Napoli
July 2, 2010 July 12, 2010
Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
draft-ietf-xcon-examples-05 draft-ietf-xcon-examples-06
Abstract Abstract
This document provides detailed call flows for the scenarios This document provides detailed call flows for the scenarios
documented in the Centralized Conferencing (XCON) Framework and the documented in the Centralized Conferencing (XCON) Framework and the
XCON Scenarios. The call flows document the use of the interface XCON Scenarios. The call flows document the use of the interface
between a conference control client and a conference control server between a conference control client and a conference control server
using the Centralized Conferencing Manipulation Protocol (CCMP). The using the Centralized Conferencing Manipulation Protocol (CCMP). The
objective is to provide a base reference for both protocol objective is to provide a base reference for both protocol
researchers and developers. researchers and developers.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on January 3, 2011. This Internet-Draft will expire on January 13, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
4.3. Conference Notifications . . . . . . . . . . . . . . . . . 10 4.3. Conference Notifications . . . . . . . . . . . . . . . . . 10
5. Conference Creation . . . . . . . . . . . . . . . . . . . . . 14 5. Conference Creation . . . . . . . . . . . . . . . . . . . . . 14
5.1. Basic Conference Creation . . . . . . . . . . . . . . . . 14 5.1. Basic Conference Creation . . . . . . . . . . . . . . . . 14
5.2. Conference Creation using Blueprints . . . . . . . . . . . 19 5.2. Conference Creation using Blueprints . . . . . . . . . . . 19
5.3. Conference Creation using User-Provided Conference 5.3. Conference Creation using User-Provided Conference
Information . . . . . . . . . . . . . . . . . . . . . . . 26 Information . . . . . . . . . . . . . . . . . . . . . . . 26
5.4. Cloning an Existing Conference . . . . . . . . . . . . . . 31 5.4. Cloning an Existing Conference . . . . . . . . . . . . . . 31
6. Conference Users Scenarios and Examples . . . . . . . . . . . 35 6. Conference Users Scenarios and Examples . . . . . . . . . . . 35
6.1. Adding a Party . . . . . . . . . . . . . . . . . . . . . . 35 6.1. Adding a Party . . . . . . . . . . . . . . . . . . . . . . 35
6.2. Muting a Party . . . . . . . . . . . . . . . . . . . . . . 39 6.2. Muting a Party . . . . . . . . . . . . . . . . . . . . . . 39
6.3. Conference Announcements and Recordings . . . . . . . . . 43 6.3. Conference Announcements and Recordings . . . . . . . . . 42
6.4. Monitoring for DTMF . . . . . . . . . . . . . . . . . . . 47 6.4. Monitoring for DTMF . . . . . . . . . . . . . . . . . . . 45
6.5. Entering a password-protected conference . . . . . . . . . 47 6.5. Entering a password-protected conference . . . . . . . . . 46
7. Sidebars Scenarios and Examples . . . . . . . . . . . . . . . 49 7. Sidebars Scenarios and Examples . . . . . . . . . . . . . . . 48
7.1. Internal Sidebar . . . . . . . . . . . . . . . . . . . . . 50 7.1. Internal Sidebar . . . . . . . . . . . . . . . . . . . . . 49
7.2. External Sidebar . . . . . . . . . . . . . . . . . . . . . 59 7.2. External Sidebar . . . . . . . . . . . . . . . . . . . . . 58
7.3. Private Messages . . . . . . . . . . . . . . . . . . . . . 66 7.3. Private Messages . . . . . . . . . . . . . . . . . . . . . 65
7.4. Observing and Coaching . . . . . . . . . . . . . . . . . . 70 7.4. Observing and Coaching . . . . . . . . . . . . . . . . . . 69
8. Removing Participants and Deleting Conferences . . . . . . . . 77 8. Removing Participants and Deleting Conferences . . . . . . . . 77
8.1. Removing a Party . . . . . . . . . . . . . . . . . . . . . 77 8.1. Removing a Party . . . . . . . . . . . . . . . . . . . . . 77
8.2. Deleting a Conference . . . . . . . . . . . . . . . . . . 80 8.2. Deleting a Conference . . . . . . . . . . . . . . . . . . 80
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81
10. Security Considerations . . . . . . . . . . . . . . . . . . . 81 10. Security Considerations . . . . . . . . . . . . . . . . . . . 82
11. Change Summary . . . . . . . . . . . . . . . . . . . . . . . . 82 11. Change Summary . . . . . . . . . . . . . . . . . . . . . . . . 82
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 84 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 84
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84
13.1. Normative References . . . . . . . . . . . . . . . . . . . 84 13.1. Normative References . . . . . . . . . . . . . . . . . . . 84
13.2. Informative References . . . . . . . . . . . . . . . . . . 84 13.2. Informative References . . . . . . . . . . . . . . . . . . 84
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 85
1. Introduction 1. Introduction
This document provides detailed call flows for the scenarios This document provides detailed call flows for the scenarios
skipping to change at page 8, line 39 skipping to change at page 8, line 39
Server: Sun GlassFish Communications Server 1.5 Server: Sun GlassFish Communications Server 1.5
Content-Type: application/ccmp+xml;charset=ISO-8859-1 Content-Type: application/ccmp+xml;charset=ISO-8859-1
Content-Length: 1652 Content-Length: 1652
Date: Thu, 04 Feb 2010 14:47:56 GMT Date: Thu, 04 Feb 2010 14:47:56 GMT
<?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
xsi:type="ccmp:ccmp-blueprint-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:AudioRoom@example.com</confObjID> <confObjID>xcon:AudioRoom@example.com</confObjID>
<operation>retrieve</operation> <operation>retrieve</operation>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<ccmp:blueprintResponse> <ccmp:blueprintResponse>
<blueprintInfo entity="xcon:AudioRoom@example.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>
<xcon:join-handling>allow</xcon:join-handling> <xcon:join-handling>allow</xcon:join-handling>
</info:users> </info:users>
<xcon:floor-information> <xcon:floor-information>
skipping to change at page 18, line 5 skipping to change at page 18, line 5
| | | | | | | |
|**CMCC1 then manipulates conference****| |**CMCC1 then manipulates conference****|
|** data and add addt'l users, etc. ***| |** data and add addt'l users, etc. ***|
' ' ' ' ' ' ' '
' ' ' ' ' ' ' '
' ' ' ' ' ' ' '
- -
Figure 5: Create Basic Conference - Annotated Flow Figure 5: Create Basic Conference - Annotated Flow
1. confRequest/create message (Alice creates a default conference) 1. confRequest/create message (Alice creates a default conference)
<?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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <operation>create</operation>
<ccmp:confRequest/> <ccmp:confRequest/>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. confResponse/create message ("success", created conference 2. confResponse/create message ("success", created conference
object returned) object returned)
<?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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<version>1</version> <version>1</version>
<ccmp:confResponse> <ccmp:confResponse>
<confInfo entity="xcon:8977794@example.com"> <confInfo entity="xcon:8977794@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
Default conference initiated by Alice Default conference initiated by Alice
</info:display-text> </info:display-text>
<info:conf-uris> <info:conf-uris>
<info:entry> <info:entry>
<info:uri> <info:uri>
xcon:8977794@example.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>
</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:available-media> </info:maximum-user-count>
<info:entry label="11"> <info:available-media>
<info:type>audio</info:type> <info:entry label="11">
</info:entry> <info:type>audio</info:type>
</info:available-media> </info:entry>
<info:conference-state> </info:available-media>
<active>false</active> <info:conference-state>
</info:conference-state> <active>false</active>
</info:conference-description> </info:conference-state>
<info:users> </info:conference-description>
<xcon:join-handling>allow</xcon:join-handling> <info:users>
<xcon:allowed-users-list> <xcon:join-handling>allow</xcon:join-handling>
<xcon:target uri="xcon-userid:Alice@example.com" <xcon:allowed-users-list>
method="dial-out"/> <xcon:target uri="xcon-userid:Alice@example.com"
</xcon:allowed-users-list> method="dial-out"/>
</info:users> </xcon:allowed-users-list>
</confInfo> </info:users>
</ccmp:confResponse> </confInfo>
</ccmpResponse> </ccmp:confResponse>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
Figure 6: Create Basic Conference (Annotated) Detailed Messaging Figure 6: Create Basic Conference (Annotated) Detailed Messaging
5.2. Conference Creation using Blueprints 5.2. Conference Creation using Blueprints
The previous example showed the creation of a new conference using The previous example showed the creation of a new conference using
default values. This means the client provided no information about default values. This means the client provided no information about
how she wanted the conference to be like. Anyway, the XCON framework how she wanted the conference to be like. Anyway, the XCON framework
(and CCMP as a consequence) allows for the exploitation of templates. (and CCMP as a consequence) allows for the exploitation of templates.
These templates are called "conference blueprints", and are basically These templates are called "conference blueprints", and are basically
skipping to change at page 22, line 11 skipping to change at page 22, line 14
6. Upon receipt of the "confRequest" message with a "create" 6. Upon receipt of the "confRequest" message with a "create"
operation, the conferencing system uses the received blueprint to operation, the conferencing system uses the received blueprint to
clone a conference, allocating a new XCON-URI (again called clone a conference, allocating a new XCON-URI (again called
"confObjID*" in the example). The conferencing server then sends "confObjID*" in the example). The conferencing server then sends
a "confResponse" message including the new "confObjID*" a "confResponse" message including the new "confObjID*"
associated with the newly created conference instance. Upon associated with the newly created conference instance. Upon
receipt of the "confResponse" message, Alice can now add other receipt of the "confResponse" message, Alice can now add other
users to the conference . users to the conference .
1. blueprintsRequest message (Alice requires the list of the 1. blueprintsRequest message (Alice requires the list of the
available blueprints with video support) available blueprints with video support)
<?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:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
xsi:type="xcon:ccmp-blueprints-request-message-type"> <ccmpRequest
<confUserID>xcon-userid:Alice@example.com</confUserID> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<ccmp:blueprintsRequest> xsi:type="xcon:ccmp-blueprints-request-message-type">
<xpathFilter>/conference-info[conference-description/ <confUserID>xcon-userid:Alice@example.com</confUserID>
available-media/entry/type='audio' and <ccmp:blueprintsRequest>
conference-description/available-media/entry/type='video'] <xpathFilter>/conference-info
</xpathFilter> [conference-description/
</ccmp:blueprintsRequest> available-media/entry/type='audio' and
</ccmpRequest> conference-description/available-media/
</ccmp:ccmpRequest> entry/type='video']
</xpathFilter>
</ccmp:blueprintsRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
2. blueprintsResponse message (the server provides a descriptions of 2. blueprintsResponse message (the server provides a
the available blueprints fitting Alice's request) descriptions of the available blueprints
fitting Alice's request)
<?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@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<ccmp:blueprintsResponse> <ccmp:blueprintsResponse>
<blueprintsInfo> <blueprintsInfo>
<info:entry> <info:entry>
<info:uri>xcon:VideoRoom@example.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,
4 users can talk and be seen at the same time,
and the floor requests are automatically accepted.
</info:purpose>
</info:entry>
<info:entry>
<info:uri>xcon:VideoConference1@example.com</info:uri>
<info:display-text>VideoConference1</info:display-text>
<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 4 users can talk and be seen at the same time,
and the floor requests are automatically accepted.
</info:purpose> </info:purpose>
</info:entry> </info:entry>
</blueprintsInfo> <info:entry>
</ccmp:blueprintsResponse> <info:uri>xcon:VideoConference1@example.com
</ccmpResponse> </info:uri>
</ccmp:ccmpResponse> <info:display-text>VideoConference1
</info:display-text>
3. blueprintRequest/retrieve message (Alice wants the <info:purpose>Public Video Conference: conference
"VideoRoom" blueprint) where both audio and video are available,
only one user can talk
</info:purpose>
</info:entry>
</blueprintsInfo>
</ccmp:blueprintsResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 3. blueprintRequest/retrieve message (Alice wants the
<ccmp:ccmpRequest "VideoRoom" blueprint)
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:VideoRoom@example.com</confObjID>
<operation>retrieve</operation>
<ccmp:blueprintRequest/>
</ccmpRequest>
</ccmp:ccmpRequest>
4. blueprintResponse/retrieve message ("VideoRoom" <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
conference object returned) <ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:VideoRoom@example.com</confObjID>
<operation>retrieve</operation>
<ccmp:blueprintRequest/>
</ccmpRequest>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> </ccmp:ccmpRequest>
<ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:VideoRoom@example.com</confObjID>
<operation>retrieve</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<ccmp:blueprintResponse>
<blueprintInfo entity="xcon:VideoRoom@example.com">
<info:conference-description>
<info:display-text>VideoRoom</info:display-text>
<info:maximum-user-count>4</info:maximum-user-count>
<info:available-media>
<info:entry label="audioLabel">
<info:type>audio</info:type>
</info:entry>
<info:entry label="videoLabel">
<info:type>video</info:type>
</info:entry>
</info:available-media>
</info:conference-description>
<info:users>
<xcon:join-handling>allow</xcon:join-handling>
</info:users>
<xcon:floor-information>
<xcon:floor-request-handling>confirm
</xcon:floor-request-handling>
<xcon:conference-floor-policy>
<xcon:floor id="audioLabel"></xcon:floor>
<xcon:floor id="videoLabel"></xcon:floor>
</xcon:conference-floor-policy>
</xcon:floor-information>
</blueprintInfo>
</ccmp:blueprintResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
5. confRequest/create message (Alice clones the "VideoRoom" blueprint) 4. blueprintResponse/retrieve message ("VideoRoom"
conference object returned)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-blueprint-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:VideoRoom@example.com</confObjID>
<operation>retrieve</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<ccmp:blueprintResponse>
<blueprintInfo entity="xcon:VideoRoom@example.com">
<info:conference-description>
<info:display-text>VideoRoom</info:display-text>
<info:maximum-user-count>4</info:maximum-user-count>
<info:available-media>
<info:entry label="audioLabel">
<info:type>audio</info:type>
</info:entry>
<info:entry label="videoLabel">
<info:type>video</info:type>
</info:entry>
</info:available-media>
</info:conference-description>
<info:users>
<xcon:join-handling>allow</xcon:join-handling>
</info:users>
<xcon:floor-information>
<xcon:floor-request-handling>confirm
</xcon:floor-request-handling>
<xcon:conference-floor-policy>
<xcon:floor id="audioLabel"></xcon:floor>
<xcon:floor id="videoLabel"></xcon:floor>
</xcon:conference-floor-policy>
</xcon:floor-information>
</blueprintInfo>
</ccmp:blueprintResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
5. confRequest/create message (Alice clones the "VideoRoom" blueprint)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:VideoRoom@example.com</confObjID> <confObjID>xcon:VideoRoom@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:confRequest/> <ccmp:confRequest/>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
6. confResponse/create message (cloned conference 6. confResponse/create message (cloned conference
object returned) object returned)
<?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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID> <confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<version>1</version> <version>1</version>
<ccmp:confResponse> <ccmp:confResponse>
<confInfo entity="xcon:8977794@example.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 VideoRoom New conference by Alice cloned from VideoRoom
</info:display-text> </info:display-text>
<info:conf-uris> <info:conf-uris>
<info:entry> <info:entry>
<info:uri> <info:uri>
xcon:8977794@example.com xcon:8977794@example.com
</info:uri> </info:uri>
<info:display-text> <info:display-text>
conference xcon-uri conference xcon-uri
</info:display-text>
<xcon:conference-password> </info:display-text>
8601 <xcon:conference-password>
</xcon:conference-password> 8601
</info:entry> </xcon:conference-password>
</info:conf-uris> </info:entry>
<info:maximum-user-count>10</info:maximum-user-count> </info:conf-uris>
<info:available-media> <info:maximum-user-count>10
<info:entry label="11"> </info:maximum-user-count>
<info:type>audio</info:type> <info:available-media>
</info:entry> <info:entry label="11">
<info:entry label="12"> <info:type>audio</info:type>
<info:type>video</info:type> </info:entry>
</info:entry> <info:entry label="12">
</info:available-media> <info:type>video</info:type>
</info:conference-description> </info:entry>
<info:users> </info:available-media>
<xcon:join-handling>allow</xcon:join-handling> </info:conference-description>
</info:users> <info:users>
<xcon:floor-information> <xcon:join-handling>allow</xcon:join-handling>
<xcon:floor-request-handling> </info:users>
confirm</xcon:floor-request-handling> <xcon:floor-information>
<xcon:conference-floor-policy> <xcon:floor-request-handling>
<xcon:floor id="11"/> confirm</xcon:floor-request-handling>
<xcon:floor id="12"/> <xcon:conference-floor-policy>
</xcon:conference-floor-policy> <xcon:floor id="11"/>
</xcon:floor-information> <xcon:floor id="12"/>
</confInfo> </xcon:conference-floor-policy>
</ccmp:confResponse> </xcon:floor-information>
</ccmpResponse> </confInfo>
</ccmp:ccmpResponse> </ccmp:confResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 8: Create Conference (Blueprint) Detailed Messaging Figure 8: Create Conference (Blueprint) Detailed Messaging
5.3. Conference Creation using User-Provided Conference Information 5.3. Conference Creation using User-Provided Conference Information
A conference can also be created by the client sending a A conference can also be created by the client sending a
"confRequest" message with the "create" operation, along with the "confRequest" message with the "create" operation, along with the
desired data in the form of the "confInfo" parameter for the desired data in the form of the "confInfo" parameter for the
conference to be created. The request also includes the "confUserID" conference to be created. The request also includes the "confUserID"
of the requesting entity. of the requesting entity.
skipping to change at page 29, line 30 skipping to change at page 29, line 40
| | | | | | | |
|<***All parties connected to conf Y***>| |<***All parties connected to conf Y***>|
| | | | | | | |
| | | | | | | |
" " " " " " " "
" " " " " " " "
" " " " " " " "
Figure 9: Create Basic Conference from user provided conference-info Figure 9: Create Basic Conference from user provided conference-info
1. confRequest/create message (Alice proposes a conference object 1. confRequest/create message (Alice proposes a conference object
to be created) to be created)
<?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"
xsi:type="ccmp:ccmp-conf-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation>
<ccmp:confRequest>
<confInfo entity="xcon:AUTO_GENERATE_1@example.com">
<info:conference-description>
<info:display-text>
Dial-out conference initiated by Alice
</info:display-text> <ccmpRequest
<info:maximum-user-count>10</info:maximum-user-count> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<info:available-media> xsi:type="ccmp:ccmp-conf-request-message-type">
<info:entry label="AUTO_GENERATE_2"> <confUserID>xcon-userid:Alice@example.com</confUserID>
<info:type>audio</info:type> <operation>create</operation>
</info:entry> <ccmp:confRequest>
</info:available-media> <confInfo entity="xcon:AUTO_GENERATE_1@example.com">
<xcon:conference-time> <info:conference-description>
<xcon:entry> <info:display-text>
<xcon:base> Dial-out conference initiated by Alice
BEGIN:VCALENDAR </info:display-text>
VERSION:2.0 <info:maximum-user-count>10
PRODID:-//Mozilla.org/NONSGML </info:maximum-user-count>
Mozilla Calendar V1.0//EN <info:available-media>
BEGIN:VEVENT <info:entry label="AUTO_GENERATE_2">
DTSTAMP: 20100127T140728Z <info:type>audio</info:type>
UID: 20100127T140728Z-345FDA-alice@example.com </info:entry>
ORGANIZER:MAILTO:alice@example.com </info:available-media>
DTSTART:20100127T143000Z <xcon:conference-time>
RRULE:FREQ=WEEKLY <xcon:entry>
DTEND: 20100127T163000Z <xcon:base>
END:VEVENT BEGIN:VCALENDAR
END:VCALENDAR VERSION:2.0
</xcon:base> PRODID:-//Mozilla.org/NONSGML
<xcon:mixing-start-offset Mozilla Calendar V1.0//EN
required-participant="moderator"> BEGIN:VEVENT
2010-01-27T14:29:00Z DTSTAMP: 20100127T140728Z
</xcon:mixing-start-offset> UID: 20100127T140728Z-345FDA-alice@example.com
<xcon:mixing-end-offset ORGANIZER:MAILTO:alice@example.com
required-participant="participant"> DTSTART:20100127T143000Z
2010-01-27T16:31:00Z RRULE:FREQ=WEEKLY
</xcon:mixing-end-offset> DTEND: 20100127T163000Z
<xcon:must-join-before-offset> END:VEVENT
2010-01-27T15:30:00Z END:VCALENDAR
</xcon:must-join-before-offset> </xcon:base>
</xcon:entry> <xcon:mixing-start-offset
</xcon:conference-time> required-participant="moderator">
</info:conference-description> 2010-01-27T14:29:00Z
<info:users> </xcon:mixing-start-offset>
<xcon:join-handling>allow</xcon:join-handling> <xcon:mixing-end-offset
<xcon: allowed-users-list> required-participant="participant">
<xcon:target uri="xcon-userid:alice@example.com" 2010-01-27T16:31:00Z
method="dial-out"/> </xcon:mixing-end-offset>
<xcon:target uri="sip:bob83@example.com" <xcon:must-join-before-offset>
method="dial-out"/> 2010-01-27T15:30:00Z
<xcon:target uri="sip:carol@example.com" </xcon:must-join-before-offset>
method="dial-out"/> </xcon:entry>
</xcon:allowed-users-list> </xcon:conference-time>
</info:users> </info:conference-description>
</confInfo> <info:users>
</ccmp:confRequest> <xcon:join-handling>allow</xcon:join-handling>
</ccmpRequest> <xcon: allowed-users-list>
</ccmp:ccmpRequest> <xcon:target uri="xcon-userid:alice@example.com"
method="dial-out"/>
<xcon:target uri="sip:bob83@example.com"
method="dial-out"/>
<xcon:target uri="sip:carol@example.com"
method="dial-out"/>
</xcon:allowed-users-list>
</info:users>
</confInfo>
</ccmp:confRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
2. confResponse/create message (200, "success") 2. confResponse/create message (200, "success")
<?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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:6845432@example.com</confObjID> <confObjID>xcon:6845432@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<response-code>200<response-code> <response-code>200<response-code>
<response-string>success<response-string> <response-string>success<response-string>
<version>1</version> <version>1</version>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
Figure 10: Create Basic Conference Detailed Messaging Figure 10: Create Basic Conference Detailed Messaging
5.4. Cloning an Existing Conference 5.4. Cloning an Existing Conference
A client can also create another conference by cloning an existing A client can also create another conference by cloning an existing
conference, such as an active conference or conference reservation. conference, such as an active conference or conference reservation.
This approach can be seen as a logical extension of the creation of a This approach can be seen as a logical extension of the creation of a
new conference using a blueprint: the difference is that, instead of new conference using a blueprint: the difference is that, instead of
cloning the pre-defined settings listed in a blueprint, the settings cloning the pre-defined settings listed in a blueprint, the settings
skipping to change at page 33, line 22 skipping to change at page 33, line 32
from the one associated with the conference to be cloned, since from the one associated with the conference to be cloned, since
it represents a different conference object. Any subsequent it represents a different conference object. Any subsequent
protocol requests from any of the members of the conference must protocol requests from any of the members of the conference must
use this new identifier. The conferencing system maintains the use this new identifier. The conferencing system maintains the
mapping between this conference ID and the parent conference mapping between this conference ID and the parent conference
object ID associated with the reservation through the conference object ID associated with the reservation through the conference
instance, and this mapping is explicitly addressed through the instance, and this mapping is explicitly addressed through the
"cloning-parent" element of the "conference-description" in the "cloning-parent" element of the "conference-description" in the
new conference object. new conference object.
1. confRequest/create message (Alice clones an existing conference) 1. confRequest/create message (Alice clones an existing conference)
<?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">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:6845432@example.com</confObjID> <confObjID>xcon:6845432@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. confResponse/create message (created conference 2. confResponse/create message (created conference
object returned) object returned)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>1</version>
<ccmp:confResponse>
<confInfo entity="xcon:8977794@example.com">
<info:conference-description>
<info:display-text>
New conference by Alice cloned from 6845432
</info:display-text>
<xcon:cloning-parent>
xcon:6845432@example.com
</xcon:cloning-parent>
<info:maximum-user-count>10
</info:maximum-user-count>
<info:available-media>
<info:entry label="11">
<info:type>audio</info:type>
</info:entry>
</info:available-media>
</info:conference-description>
<info:users>
<xcon:join-handling>allow</xcon:join-handling>
<xcon: allowed-users-list>
<xcon:target uri="sip:alice@example.com"
method="dial-out"/>
<xcon:target uri="sip:bob83@example.com"
method="dial-out"/>
<xcon:target uri="sip:carol@example.com"
method="dial-out"/>
</xcon:allowed-users-list>
</info:users>
<xcon:floor-information>
<xcon:floor-request-handling>
confirm</xcon:floor-request-handling>
<xcon:conference-floor-policy>
<xcon:floor id="11"/>
</xcon:conference-floor-policy>
</xcon:floor-information>
</confInfo>
</ccmp:confResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-conf-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>create</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>1</version>
<ccmp:confResponse>
<confInfo entity="xcon:8977794@example.com">
<info:conference-description>
<info:display-text>
New conference by Alice cloned from 6845432
</info:display-text>
<xcon:cloning-parent>
xcon:6845432@example.com
</xcon:cloning-parent>
<info:maximum-user-count>10</info:maximum-user-count>
<info:available-media>
<info:entry label="11">
<info:type>audio</info:type>
</info:entry>
</info:available-media>
</info:conference-description>
<info:users>
<xcon:join-handling>allow</xcon:join-handling>
<xcon: allowed-users-list>
<xcon:target uri="sip:alice@example.com"
method="dial-out"/>
<xcon:target uri="sip:bob83@example.com"
method="dial-out"/>
<xcon:target uri="sip:carol@example.com"
method="dial-out"/>
</xcon:allowed-users-list>
</info:users>
<xcon:floor-information>
<xcon:floor-request-handling>
confirm</xcon:floor-request-handling>
<xcon:conference-floor-policy>
<xcon:floor id="11"/>
</xcon:conference-floor-policy>
</xcon:floor-information>
</confInfo>
</ccmp:confResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 12: Create Basic Conference (Clone) Detailed Messaging Figure 12: Create Basic Conference (Clone) Detailed Messaging
6. Conference Users Scenarios and Examples 6. Conference Users Scenarios and Examples
Section 5 showed examples describing the several different ways a Section 5 showed examples describing the several different ways a
conference might be created using CCMP. This section instead focuses conference might be created using CCMP. This section instead focuses
on user-related scenarios, i.e. typical scenarios that may occur on user-related scenarios, i.e. typical scenarios that may occur
during the lifetime of a conference, like adding new users and during the lifetime of a conference, like adding new users and
handling their media. The following scenarios are based on those handling their media. The following scenarios are based on those
documented in the XCON framework. The examples assume that a documented in the XCON framework. The examples assume that a
skipping to change at page 37, line 38 skipping to change at page 37, line 38
notify Bob via mail of the new conference, including details as notify Bob via mail of the new conference, including details as
the date, password, expected participants and so on (see the date, password, expected participants and so on (see
Section 4.3). Section 4.3).
To conclude the overview on this scenario, once Bob has been To conclude the overview on this scenario, once Bob has been
successfully added to the specified conference, per updates to the successfully added to the specified conference, per updates to the
state, and depending upon the policies, other participants state, and depending upon the policies, other participants
(including Bob himself) may be notified of the addition of Bob to (including Bob himself) may be notified of the addition of Bob to
the conference via the Conference Notification Service in use. the conference via the Conference Notification Service in use.
1. userRequest/create message (Alice adds Bob) 1. userRequest/create message (Alice adds Bob)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977878@example.com</confObjID>
<operation>create</operation>
<ccmp:userRequest>
<userInfo entity="xcon-userid:AUTO_GENERATE@example.com">
<info:display-text>Bob</info:display-text>
<info:associated-aors>
<info:entry>
<info:uri>mailto:bob.depippis@example.com</info:uri>
<info:display-text>Bob's email</info:display-text>
</info:entry>
</info:associated-aors>
<info:endpoint entity="sip:bob83@example.com">
<info:display-text>Bob's laptop</info:display-text>
</info:endpoint>
</userInfo>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/create message (a new XCON-USERID is
created for Bob and he is added to the conference)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse 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">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest
xsi:type="ccmp:ccmp-user-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-user-request-message-type">
<confObjID>xcon:8977878@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8977878@example.com</confObjID>
<response-code>200</response-code> <operation>create</operation>
<response-string>success</response-string> <ccmp:userRequest>
<version>10</version> <userInfo entity="xcon-userid:AUTO_GENERATE@example.com">
<ccmp:userResponse> <info:display-text>Bob</info:display-text>
<userInfo entity="xcon-userid:Bob@example.com"> <info:associated-aors>
<info:display-text>Bob</info:display-text> <info:entry>
<info:associated-aors> <info:uri>mailto:bob.depippis@example.com
<info:entry> </info:uri>
<info:uri>mailto:bob.depippis@example.com</info:uri> <info:display-text>Bob's email
<info:display-text>Bob's email</info:display-text> </info:display-text>
</info:entry> </info:entry>
</info:associated-aors> </info:associated-aors>
<info:endpoint entity="sip:bob83@example.com"> <info:endpoint entity="sip:bob83@example.com">
<info:display-text>Bob's laptop</info:display-text> <info:display-text>Bob's laptop
</info:endpoint> </info:display-text>
</userInfo> </info:endpoint>
</ccmp:userResponse> </userInfo>
</ccmpResponse> </ccmp:userRequest>
</ccmp:ccmpResponse> </ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/create message (a new XCON-USERID is
created for Bob and he is added to the conference)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977878@example.com</confObjID>
<operation>create</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>10</version>
<ccmp:userResponse>
<userInfo entity="xcon-userid:Bob@example.com">
<info:display-text>Bob</info:display-text>
<info:associated-aors>
<info:entry>
<info:uri>mailto:bob.depippis@example.com
</info:uri>
<info:display-text>Bob's email
</info:display-text>
</info:entry>
</info:associated-aors>
<info:endpoint entity="sip:bob83@example.com">
<info:display-text>Bob's laptop
</info:display-text>
</info:endpoint>
</userInfo>
</ccmp:userResponse>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 14: Add Party Message Details Figure 14: Add Party Message Details
6.2. Muting a Party 6.2. Muting a Party
This section provides an example of the muting of a party in an This section provides an example of the muting of a party in an
active conference. We assume that the user to mute has already been active conference. We assume that the user to mute has already been
added to the conference. The document only addresses muting and not added to the conference. The document only addresses muting and not
unmuting as well, since it would involve an almost identical CCMP unmuting as well, since it would involve an almost identical CCMP
message flow anyway. Although, in case that any external floor message flow anyway. Although, in case that any external floor
control is involved, whether or not a particular conference client control is involved, whether or not a particular conference client
skipping to change at page 42, line 5 skipping to change at page 41, line 25
such a situation using the Media Server Control architecture is such a situation using the Media Server Control architecture is
described in [I-D.ietf-mediactrl-call-flows], at "Simple described in [I-D.ietf-mediactrl-call-flows], at "Simple
Bridging: Framework Transactions (2)". Bridging: Framework Transactions (2)".
2. A userResponse message with a "200" response-code ("success") is 2. A userResponse message with a "200" response-code ("success") is
then sent to Alice. Depending upon the policies, the conference then sent to Alice. Depending upon the policies, the conference
server may notify other participants (including Bob) of this server may notify other participants (including Bob) of this
update via any Conference Notification Service that may be in update via any Conference Notification Service that may be in
use. use.
1. userRequest/update message (Alice mutes Bob) 1. userRequest/update message (Alice mutes Bob)
<?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:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-request-message-type">
<subject>
<username>Alice83</username>
<password>13011983</password>
</subject>
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977878@example.com</confObjID>
<operation>update</operation>
<ccmp:userRequest>
<userInfo entity="xcon-userid:Bob@example.com">
<info:endpoint entity="sip:bob83@example.com">
<info:media id="1">
<info:label>123</info:label>
<info:status>recvonly</info:status>
</info:media>
</info:endpoint>
</userInfo>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
</t>
2. userResponse/update message (Bob has been muted)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
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" <ccmpResponse
xsi:type="ccmp:ccmp-user-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<subject> xsi:type="ccmp:ccmp-user-response-message-type">
<username>Alice83</username> <confUserID>xcon-userid:Alice@example.com</confUserID>
<password>13011983</password> <confObjID>xcon:8977878@example.com</confObjID>
</subject> <operation>update</operation>
<confUserID>xcon-userid:Alice@example.com</confUserID> <response-code>200</response-code>
<confObjID>xcon:8977878@example.com</confObjID> <response-string>success</response-string>
<operation>update</operation> <version>7</version>
<ccmp:userRequest> <ccmp:userResponse/>
<userInfo entity="xcon-userid:Bob@example.com"> </ccmpResponse>
<info:endpoint entity="sip:bob83@example.com"> </ccmp:ccmpResponse>
<info:media id="1">
<info:label>123</info:label>
<info:status>recvonly</info:status>
</info:media>
</info:endpoint>
</userInfo>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/update message (Bob has been muted)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977878@example.com</confObjID>
<operation>update</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>7</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 16: Mute Message Details Figure 16: Mute Message Details
6.3. Conference Announcements and Recordings 6.3. Conference Announcements and Recordings
This section deals with features that are typically required in a This section deals with features that are typically required in a
conferencing system, that are public announcements (e.g. to notify conferencing system, that are public announcements (e.g. to notify
vocally that a new user joined a conference) and name recording. vocally that a new user joined a conference) and name recording.
While this is not strictly CCMP-related (the CCMP signaling is While this is not strictly CCMP-related (the CCMP signaling is
actually the same as the one seen in Section 6.1) it is an actually the same as the one seen in Section 6.1) it is an
interesting scenario to address to see how the several components of interesting scenario to address to see how the several components of
skipping to change at page 46, line 5 skipping to change at page 44, line 35
conference (if she were to have the appropriate policies), conference (if she were to have the appropriate policies),
including registering for event notifications associated with the including registering for event notifications associated with the
conference. Once the call signaling indicates that Alice has conference. Once the call signaling indicates that Alice has
been successfully added to the specific conference, per updates been successfully added to the specific conference, per updates
to the state, and depending upon the policies, other participants to the state, and depending upon the policies, other participants
(e.g., Bob) are notified of the addition of Alice to the (e.g., Bob) are notified of the addition of Alice to the
conference via the conference notification service and an conference via the conference notification service and an
announcement is provided to all the participants indicating that announcement is provided to all the participants indicating that
Alice has joined the conference. Alice has joined the conference.
1. userRequest/create message (Alice - a new conferencing system client - 1. userRequest/create message (A new conferencing system client,
enters Bob's conference) Alice, enters Bob's conference)
<?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
xsi:type="ccmp:ccmp-user-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confObjID>xcon:bobConf@example.com</confObjID> xsi:type="ccmp:ccmp-user-request-message-type">
<operation>create</operation> <confObjID>xcon:bobConf@example.com</confObjID>
<ccmp:userRequest> <operation>create</operation>
<userInfo entity="xcon-userid:AUTO_GENERATE@example.com"> <ccmp:userRequest>
<info:associated-aors> <userInfo entity="xcon-userid:AUTO_GENERATE@example.com">
<info:entry> <info:associated-aors>
<info:uri> <info:entry>
mailto:Alice83@example.com <info:uri>
</info:uri> mailto:Alice83@example.com
<info:display-text>email</info:display-text> </info:uri>
</info:entry> <info:display-text>email</info:display-text>
</info:associated-aors> </info:entry>
<info:endpoint entity="sip:alice_789@example.com"/> </info:associated-aors>
</userInfo> <info:endpoint entity="sip:alice_789@example.com"/>
</ccmp:userRequest> </userInfo>
</ccmpRequest> </ccmp:userRequest>
</ccmp:ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/create (Alice provided with a new xcon-userid 2. userResponse/create (Alice provided with a new xcon-userid
and added to the conference) and added to the conference)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:bobConf@example.com</confObjID>
<operation>create</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>5</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:bobConf@example.com</confObjID>
<operation>create</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>5</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 18: Announcement Messaging Details Figure 18: Announcement Messaging Details
6.4. Monitoring for DTMF 6.4. Monitoring for DTMF
Conferencing systems often also need the capability to monitor for Conferencing systems often also need the capability to monitor for
DTMF from each individual participant. This would typically be used DTMF from each individual participant. This would typically be used
to enter the identifier and/or access code for joining a specific to enter the identifier and/or access code for joining a specific
conference. This feature is often also exploited to achieve conference. This feature is often also exploited to achieve
interaction between participants and the conference system for non- interaction between participants and the conference system for non-
XCON-aware user agents (e.g. using DTMF tones to get muted/unmuted). XCON-aware user agents (e.g. using DTMF tones to get muted/unmuted).
skipping to change at page 48, line 15 skipping to change at page 47, line 10
3. After getting the pass code through out-of-band mechanisms, Alice 3. After getting the pass code through out-of-band mechanisms, Alice
provides it in the proper "password" request field of a new provides it in the proper "password" request field of a new
userRequest/create message and sends the updated request back to userRequest/create message and sends the updated request back to
the server. the server.
4. The conferencing server checks the provided password and then 4. The conferencing server checks the provided password and then
adds Alice to the protected conference. After that, a adds Alice to the protected conference. After that, a
userResponse with a "200" response-code ("success") is sent to userResponse with a "200" response-code ("success") is sent to
Alice. Alice.
1. userRequest/create message (Alice tries to enter the conference 1. userRequest/create message (Alice tries to enter the conference
without providing the password) without providing the password)
<?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
xsi:type="ccmp:ccmp-user-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-user-request-message-type">
<confObjID>xcon:8977794@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8977794@example.com</confObjID>
<ccmp:userRequest/> <operation>create</operation>
</ccmpRequest> <ccmp:userRequest/>
</ccmp:ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/create message (423, "conference password required") 2. userResponse/create message (423, "conference password required")
<?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
xsi:type="ccmp:ccmp-user-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-user-response-message-type">
<confObjID>xcon:8977794@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8977794@example.com</confObjID>
<ccmp:response-code>423</ccmp:response-code> <operation>create</operation>
<ccmp:response-code>conference password required</ccmp:response-code> <ccmp:response-code>423</ccmp:response-code>
<ccmp:userResponse/> <ccmp:response-string>
</ccmpResponse> conference password required
</ccmp:ccmpResponse> </ccmp:response-string>
3. userRequest/create message (Alice provides the password) <ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 3. userRequest/create message (Alice provides the password)
<ccmp:ccmpRequest <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
xmlns:info="urn:ietf:params:xml:ns:conference-info" <ccmp:ccmpRequest
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
xsi:type="ccmp:ccmp-user-request-message-type"> <ccmpRequest
<confUserID>xcon-userid:Alice@example.com</confUserID> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confObjID>xcon:8977794@example.com</confObjID> xsi:type="ccmp:ccmp-user-request-message-type">
<operation>create</operation> <confUserID>xcon-userid:Alice@example.com</confUserID>
<conference-password>8601</conference-password> <confObjID>xcon:8977794@example.com</confObjID>
<ccmp:userRequest/> <operation>create</operation>
</ccmpRequest> <conference-password>8601</conference-password>
</ccmp:ccmpRequest> <ccmp:userRequest/>
</ccmpRequest>
</ccmp:ccmpRequest>
4. userResponse/create message (Alice has been added to the conference) 4. userResponse/create message
(Alice has been added to the conference)
<?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
xsi:type="ccmp:ccmp-user-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-user-response-message-type">
<confObjID>xcon:8977794@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8977794@example.com</confObjID>
<response-code>200</response-code> <operation>create</operation>
<response-string>success</response-string> <response-code>200</response-code>
<version>10</version> <response-string>success</response-string>
<ccmp:userResponse/> <version>10</version>
</ccmpResponse> <ccmp:userResponse/>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
Figure 19: Password-protected conference join messages details Figure 19: Password-protected conference join messages details
7. Sidebars Scenarios and Examples 7. Sidebars Scenarios and Examples
While creating conferences and manipulating users and their media may While creating conferences and manipulating users and their media may
be considered enough for many scenarios, there may be cases when a be considered enough for many scenarios, there may be cases when a
more complex management is needed. more complex management is needed.
In fact, a feature typically required in conferencing systems is the In fact, a feature typically required in conferencing systems is the
skipping to change at page 55, line 9 skipping to change at page 54, line 9
Figure 21: Conference with Alice, Bob and Carol Figure 21: Conference with Alice, Bob and Carol
This is the representation of the conference the sidebar is going to This is the representation of the conference the sidebar is going to
be created in. As such, it will be used by the conferencing system be created in. As such, it will be used by the conferencing system
in order to create the new conference object associated with the in order to create the new conference object associated with the
sidebar. In fact, the sidebar creation happens through a cloning of sidebar. In fact, the sidebar creation happens through a cloning of
the parent conference. Once the sidebar is created, an "update" the parent conference. Once the sidebar is created, an "update"
makes sure that the sidebar is customized as needed. The following makes sure that the sidebar is customized as needed. The following
protocol dump makes the process clearer. protocol dump makes the process clearer.
1. sidebarByValRequest/create message (Alice creates an 1. sidebarByValRequest/create message (Alice creates an
internal sidebar) internal sidebar)
<?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:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
xsi:type="ccmp:ccmp-sidebarByVal-request-message-type"> <ccmpRequest
<confUserID>xcon-userid:Alice@example.com</confUserID> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confObjID>xcon:8977878@example.com</confObjID> xsi:type="ccmp:ccmp-sidebarByVal-request-message-type">
<operation>create</operation> <confUserID>xcon-userid:Alice@example.com</confUserID>
<ccmp:sidebarByValRequest/> <confObjID>xcon:8977878@example.com</confObjID>
</ccmpRequest> <operation>create</operation>
</ccmp:ccmpRequest> <ccmp:sidebarByValRequest/>
</ccmpRequest>
</ccmp:ccmpRequest>
2. sidebarByValResponse/create message (sidebar returned) 2. sidebarByValResponse/create message (sidebar returned)
<?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
xsi:type="ccmp:ccmp-sidebarByVal-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByVal-response-message-type">
<confObjID>xcon:8974545@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8974545@example.com</confObjID>
<response-code>200</response-code> <operation>create</operation>
<response-string>success</response-string> <response-code>200</response-code>
<version>1</version> <response-string>success</response-string>
<ccmp:sidebarByValResponse> <version>1</version>
<sidebarByValInfo entity="xcon:8974545@example.com"> <ccmp:sidebarByValResponse>
<info:conference-description> <sidebarByValInfo entity="xcon:8974545@example.com">
<info:display-text> <info:conference-description>
SIDEBAR CONFERENCE registered by Alice <info:display-text>
</info:display-text> SIDEBAR CONFERENCE registered by Alice
<xcon:sidebar-parent> </info:display-text>
xcon:8977878@example.com <xcon:sidebar-parent>
</xcon:sidebar-parent> xcon:8977878@example.com
<info:available-media> </xcon:sidebar-parent>
<info:entry label="123"> <info:available-media>
<info:display-text> <info:entry label="123">
main conference audio <info:display-text>
</info:display-text> main conference audio
<info:type>audio</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>audio</info:type>
</info:entry> <info:status>sendrecv</info:status>
<info:entry label="456"> </info:entry>
<info:display-text> <info:entry label="456">
main conference video <info:display-text>
</info:display-text> main conference video
<info:type>video</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>video</info:type>
</info:entry> <info:status>sendrecv</info:status>
</info:available-media> </info:entry>
</info:conference-description> </info:available-media>
<info:conference-state> </info:conference-description>
<info:active>false</info:active> <info:conference-state>
</info:conference-state> <info:active>false</info:active>
<info:users> </info:conference-state>
<xcon:allowed-users-list> <info:users>
<xcon:target method="dial-in" <xcon:allowed-users-list>
uri="xcon-userid:Alice@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:Alice@example.com"/>
uri="xcon-userid:Bob@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:Bob@example.com"/>
uri="xcon-userid:Carol@example.com"/> <xcon:target method="dial-in"
</xcon:allowed-users-list> uri="xcon-userid:Carol@example.com"/>
</info:users> </xcon:allowed-users-list>
</sidebarByValInfo> </info:users>
</ccmp:sidebarByValResponse> </sidebarByValInfo>
</ccmpResponse> </ccmp:sidebarByValResponse>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
3. sidebarByValRequest/update message (Alice updates the 3. sidebarByValRequest/update message (Alice updates the
created sidebar) created sidebar)
<?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
xsi:type="ccmp:ccmp-sidebarByVal-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByVal-request-message-type">
<confObjID>xcon:8974545@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>update</operation> <confObjID>xcon:8974545@example.com</confObjID>
<ccmp:sidebarByValRequest> <operation>update</operation>
<sidebarByValInfo entity="xcon:8974545@example.com"> <ccmp:sidebarByValRequest>
<info:conference-description> <sidebarByValInfo entity="xcon:8974545@example.com">
<info:display-text> <info:conference-description>
private sidebar Alice - Bob <info:display-text>
</info:display-text> private sidebar Alice - Bob
<info:available-media> </info:display-text>
<info:entry label="123"> <info:available-media>
<info:display-text> <info:entry label="123">
main conference audio <info:display-text>
</info:display-text> main conference audio
<info:type>audio</info:type> </info:display-text>
<info:status>recvonly</info:status> <info:type>audio</info:type>
<xcon:controls> <info:status>recvonly</info:status>
<xcon:gain>-60</xcon:gain> <xcon:controls>
</xcon:controls> <xcon:gain>-60</xcon:gain>
</info:entry> </xcon:controls>
<info:entry label="456"> </info:entry>
<info:display-text> <info:entry label="456">
main conference video <info:display-text>
</info:display-text> main conference video
<info:type>video</info:type> </info:display-text>
<info:status>recvonly</info:status> <info:type>video</info:type>
</info:entry> <info:status>recvonly</info:status>
<info:entry label="AUTO_GENERATE_1"> </info:entry>
<info:display-text> <info:entry label="AUTO_GENERATE_1">
sidebar audio <info:display-text>
</info:display-text> sidebar audio
<info:type>audio</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>audio</info:type>
</info:entry> <info:status>sendrecv</info:status>
<info:entry label="AUTO_GENERATE_2"> </info:entry>
<info:display-text> <info:entry label="AUTO_GENERATE_2">
sidebar video <info:display-text>
</info:display-text> sidebar video
<info:type>video</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>video</info:type>
</info:entry> <info:status>sendrecv</info:status>
</info:available-media> </info:entry>
</info:conference-description> </info:available-media>
<info:users> </info:conference-description>
<xcon:allowed-users-list> <info:users>
<xcon:target method="dial-out" <xcon:allowed-users-list>
uri="xcon-userid:Alice@example.com"/> <xcon:target method="dial-out"
<xcon:target method="dial-out" uri="xcon-userid:Alice@example.com"/>
uri="xcon-userid:Bob@example.com"/> <xcon:target method="dial-out"
</xcon:allowed-users-list> uri="xcon-userid:Bob@example.com"/>
</xcon:allowed-users-list>
</info:users> </info:users>
</sidebarByValInfo> </sidebarByValInfo>
</ccmp:sidebarByValRequest> </ccmp:sidebarByValRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
4. sidebarByValResponse/update message (sidebar's
updates accepted)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByVal-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8974545@example.com</confObjID>
<operation>update</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>2</version>
<ccmp:sidebarByValResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
5. userRequest/update message (Bob updates his media) 4. sidebarByValResponse/update message (sidebar's
updates accepted)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest <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">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpResponse
xsi:type="ccmp:ccmp-user-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Bob@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByVal-response-message-type">
<confObjID>xcon:8974545@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>update</operation> <confObjID>xcon:8974545@example.com</confObjID>
<ccmp:userRequest> <operation>update</operation>
<userInfo entity="xcon-userid:Bob@example.com"> <response-code>200</response-code>
<info:endpoint entity="sip:bob83@example.com"> <response-string>success</response-string>
<info:media id="1"> <version>2</version>
<info:display-text> <ccmp:sidebarByValResponse/>
main conference audio </ccmpResponse>
</info:display-text> </ccmp:ccmpResponse>
<info:label>123</info:label>
<info:status>inactive</info:status>
</info:media>
</info:endpoint>
</userInfo>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
6. userResponse/update message (Bob's preferences setted) 5. userRequest/update message (Bob updates his media)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse xmlns:info="urn:ietf:params:xml:ns:conference-info" <ccmp:ccmpRequest
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"> xmlns:info="urn:ietf:params:xml:ns:conference-info"
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp">
xsi:type="ccmp:ccmp-user-response-message-type"> <ccmpRequest
<confUserID>xcon-userid:Bob@example.com</confUserID> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confObjID>xcon:8974545@example.com</confObjID> xsi:type="ccmp:ccmp-user-request-message-type">
<operation>update</operation> <confUserID>xcon-userid:Bob@example.com</confUserID>
<response-code>200</response-code> <confObjID>xcon:8974545@example.com</confObjID>
<response-string>success</response-string> <operation>update</operation>
<version>3</version> <ccmp:userRequest>
<ccmp:userResponse/> <userInfo entity="xcon-userid:Bob@example.com">
</ccmpResponse> <info:endpoint entity="sip:bob83@example.com">
</ccmp:ccmpResponse> <info:media id="1">
<info:display-text>
main conference audio
</info:display-text>
<info:label>123</info:label>
<info:status>inactive</info:status>
</info:media>
</info:endpoint>
</userInfo>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
6. userResponse/update message (Bob's preferences setted)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Bob@example.com</confUserID>
<confObjID>xcon:8974545@example.com</confObjID>
<operation>update</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>3</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 22: Internal Sidebar Messaging Details Figure 22: Internal Sidebar Messaging Details
7.2. External Sidebar 7.2. External Sidebar
Figure 23 provides an example of a different approach towards Figure 23 provides an example of a different approach towards
sidebar. In this scenario, one client, "Alice", is involved in an sidebar. In this scenario, one client, "Alice", is involved in an
active conference with "Bob", "Carol", "David" and "Ethel". Alice active conference with "Bob", "Carol", "David" and "Ethel". Alice
gets an important text message via a whisper from Bob that a critical gets an important text message via a whisper from Bob that a critical
customer needs to talk to Alice, Bob and Ethel. Alice creates a customer needs to talk to Alice, Bob and Ethel. Alice creates a
skipping to change at page 63, line 5 skipping to change at page 62, line 5
may be instigated through the Focus (e.g. if Fred had a "dial- may be instigated through the Focus (e.g. if Fred had a "dial-
out" method set as the target for him) at the actual activation out" method set as the target for him) at the actual activation
of the sidebar. of the sidebar.
4. The conference server sends a "sidebarByRefResponse" message and, 4. The conference server sends a "sidebarByRefResponse" message and,
depending upon the policies, the initiator of the request (i.e., depending upon the policies, the initiator of the request (i.e.,
Alice) and the participants in the sidebar (i.e., Bob and Ethel) Alice) and the participants in the sidebar (i.e., Bob and Ethel)
may be notified of his addition to the sidebar via the conference may be notified of his addition to the sidebar via the conference
notification service. notification service.
1. sidebarByRefRequest/create message (Alice creates an 1. sidebarByRefRequest/create message (Alice creates an
external sidebar) external sidebar)
<?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:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type"> <ccmpRequest
<confUserID>xcon-userid:Alice@example.com</confUserID> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confObjID>xcon:8977878@example.com</confObjID> xsi:type="ccmp:ccmp-sidebarByRef-request-message-type">
<operation>create</operation> <confUserID>xcon-userid:Alice@example.com</confUserID>
<ccmp:sidebarByRefRequest/> <confObjID>xcon:8977878@example.com</confObjID>
</ccmpRequest> <operation>create</operation>
</ccmp:ccmpRequest> <ccmp:sidebarByRefRequest/>
</ccmpRequest>
</ccmp:ccmpRequest>
2. sidebarByRefResponse/create message (created 2. sidebarByRefResponse/create message (created
sidebar returned) sidebar returned)
<?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
xsi:type="ccmp:ccmp-sidebarByRef-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByRef-response-message-type">
<confObjID>xcon:8971212@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>create</operation> <confObjID>xcon:8971212@example.com</confObjID>
<response-code>200</response-code> <operation>create</operation>
<response-string>success</response-string> <response-code>200</response-code>
<version>1</version> <response-string>success</response-string>
<ccmp:sidebarByRefResponse> <version>1</version>
<sidebarByRefInfo entity="xcon:8971212@example.com"> <ccmp:sidebarByRefResponse>
<info:conference-description> <sidebarByRefInfo entity="xcon:8971212@example.com">
<info:display-text> <info:conference-description>
SIDEBAR CONFERENCE registered by Alice <info:display-text>
</info:display-text> SIDEBAR CONFERENCE registered by Alice
<xcon:sidebar-parent> </info:display-text>
xcon:8977878@example.com <xcon:sidebar-parent>
</xcon:sidebar-parent> xcon:8977878@example.com
<info:available-media> </xcon:sidebar-parent>
<info:entry label="123"> <info:available-media>
<info:display-text> <info:entry label="123">
main conference audio <info:display-text>
</info:display-text> main conference audio
<info:type>audio</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>audio</info:type>
</info:entry> <info:status>sendrecv</info:status>
<info:entry label="456"> </info:entry>
<info:display-text> <info:entry label="456">
main conference video <info:display-text>
</info:display-text> main conference video
<info:type>video</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>video</info:type>
</info:entry> <info:status>sendrecv</info:status>
</info:available-media> </info:entry>
</info:conference-description> </info:available-media>
<info:conference-state> </info:conference-description>
<info:active>false</info:active> <info:conference-state>
</info:conference-state> <info:active>false</info:active>
<info:users> </info:conference-state>
<xcon:allowed-users-list> <info:users>
<xcon:target method="dial-in" <xcon:allowed-users-list>
uri="xcon-userid:Alice@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:Alice@example.com"/>
uri="xcon-userid:Bob@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:Bob@example.com"/>
uri="xcon-userid:Carol@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:Carol@example.com"/>
uri="xcon-userid:David@example.com"/> <xcon:target method="dial-in"
<xcon:target method="dial-in" uri="xcon-userid:David@example.com"/>
uri="xcon-userid:Ethel@example.com"/> <xcon:target method="dial-in"
</xcon:allowed-users-list> uri="xcon-userid:Ethel@example.com"/>
</info:users> </xcon:allowed-users-list>
</sidebarByRefInfo> </info:users>
</ccmp:sidebarByRefResponse> </sidebarByRefInfo>
</ccmpResponse> </ccmp:sidebarByRefResponse>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
3. sidebarByRefRequest/update message (Alice updates the sidebar) 3. sidebarByRefRequest/update message (Alice updates the sidebar)
<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
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByRef-request-message-type">
<confObjID>xcon:8971212@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>update</operation> <confObjID>xcon:8971212@example.com</confObjID>
<ccmp:sidebarByRefRequest> <operation>update</operation>
<sidebarByRefInfo entity="xcon:8971212@example.com"> <ccmp:sidebarByRefRequest>
<info:conference-description> <sidebarByRefInfo entity="xcon:8971212@example.com">
<info:display-text> <info:conference-description>
sidebar with Alice, Bob, Ethel & Fred <info:display-text>
</info:display-text> sidebar with Alice, Bob, Ethel & Fred
<info:available-media> </info:display-text>
<info:entry label="123"> <info:available-media>
<info:display-text> <info:entry label="123">
main conference audio <info:display-text>
</info:display-text> main conference audio
<info:type>audio</info:type> </info:display-text>
<info:status>inactive</info:status> <info:type>audio</info:type>
</info:entry> <info:status>inactive</info:status>
<info:entry label="456"> </info:entry>
<info:display-text> <info:entry label="456">
main conference video <info:display-text>
</info:display-text> main conference video
<info:type>video</info:type> </info:display-text>
<info:status>inactive</info:status> <info:type>video</info:type>
</info:entry> <info:status>inactive</info:status>
<info:entry label="AUTO_GENERATE_1"> </info:entry>
<info:display-text> <info:entry label="AUTO_GENERATE_1">
sidebar audio <info:display-text>
</info:display-text> sidebar audio
<info:type>audio</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>audio</info:type>
</info:entry> <info:status>sendrecv</info:status>
<info:entry label="AUTO_GENERATE_2"> </info:entry>
<info:display-text> <info:entry label="AUTO_GENERATE_2">
sidebar video <info:display-text>
</info:display-text> sidebar video
<info:type>video</info:type> </info:display-text>
<info:status>sendrecv</info:status> <info:type>video</info:type>
<xcon:controls> <info:status>sendrecv</info:status>
<xcon:video-layout> <xcon:controls>
single-view <xcon:video-layout>
</xcon:video-layout> single-view
</xcon:controls> </xcon:video-layout>
</info:entry> </xcon:controls>
</info:available-media> </info:entry>
</info:conference-description> </info:available-media>
<info:conference-state> </info:conference-description>
<info:active>false</info:active> <info:conference-state>
</info:conference-state> <info:active>false</info:active>
<info:users> </info:conference-state>
<xcon:allowed-users-list> <info:users>
<xcon:target method="dial-out" <xcon:allowed-users-list>
uri="xcon-userid:Alice@example.com"/> <xcon:target method="dial-out"
<xcon:target method="dial-out" uri="xcon-userid:Alice@example.com"/>
uri="xcon-userid:Bob@example.com"/> <xcon:target method="dial-out"
<xcon:target method="dial-out" uri="xcon-userid:Bob@example.com"/>
uri="sip:fred@example.com"/> <xcon:target method="dial-out"
</xcon:allowed-users-list> uri="sip:fred@example.com"/>
</info:users> </xcon:allowed-users-list>
</sidebarByRefInfo> </info:users>
</ccmp:sidebarByRefRequest> </sidebarByRefInfo>
</ccmpRequest> </ccmp:sidebarByRefRequest>
</ccmp:ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest>
4. sidebarByRefResponse/update message (sidebar updated) 4. sidebarByRefResponse/update message (sidebar updated)
<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
xsi:type="ccmp:ccmp-sidebarByref-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-sidebarByref-response-message-type">
<confObjID>xcon:8971212@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>update</operation> <confObjID>xcon:8971212@example.com</confObjID>
<response-code>200</response-code> <operation>update</operation>
<response-string>success</response-string> <response-code>200</response-code>
<version>2</version> <response-string>success</response-string>
<ccmp:sidebarByRefResponse/> <version>2</version>
</ccmpResponse> <ccmp:sidebarByRefResponse/>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
Figure 24: External Sidebar Messaging Details Figure 24: External Sidebar Messaging Details
7.3. Private Messages 7.3. Private Messages
The case of private messages can be handled as a sidebar with just The case of private messages can be handled as a sidebar with just
two participants, similarly to the example in Section 7.1. Unlike two participants, similarly to the example in Section 7.1. Unlike
the previous example, rather than using audio within the sidebar, the previous example, rather than using audio within the sidebar,
Alice could just add an additional text based media stream to the Alice could just add an additional text based media stream to the
sidebar in order to convey her textual messages to Bob, while still sidebar in order to convey her textual messages to Bob, while still
skipping to change at page 67, line 38 skipping to change at page 66, line 41
returned in the sidebarByValResponse message. Please notice returned in the sidebarByValResponse message. Please notice
that, according to the CCMP specification, the return of the that, according to the CCMP specification, the return of the
created sidebar data in this kind of "success" response is not created sidebar data in this kind of "success" response is not
mandatory. mandatory.
1. sidebarByValRequest/create message (Alice creates a private 1. sidebarByValRequest/create message (Alice creates a private
chat room between Bob and herself) chat room between Bob and herself)
<?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
xsi:type="ccmp:ccmp-sidebarByVal-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByVal-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977878@example.com</confObjID> <confObjID>xcon:8977878@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:sidebarByValRequest> <ccmp:sidebarByValRequest>
<sidebarByValInfo entity="xcon:AUTO_GENERATE_1@example.com"> <sidebarByValInfo entity="xcon:AUTO_GENERATE_1@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
private textual sidebar alice - bob private textual sidebar alice - bob
</info:display-text> </info:display-text>
<info:available-media> <info:available-media>
<info:entry label="123"> <info:entry label="123">
<info:display-text> <info:display-text>
main conference audio main conference audio
</info:display-text> </info:display-text>
<info:type>audio</info:type> <info:type>audio</info:type>
<info:status>recvonly</info:status> <info:status>recvonly</info:status>
</info:entry> </info:entry>
<info:entry label="456"> <info:entry label="456">
skipping to change at page 68, line 47 skipping to change at page 68, line 4
</info:users> </info:users>
</sidebarByValInfo> </sidebarByValInfo>
</ccmp:sidebarByValRequest> </ccmp:sidebarByValRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. sidebarByValResponse/create message (sidebar returned) 2. sidebarByValResponse/create message (sidebar returned)
<?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
xsi:type="ccmp:ccmp-sidebarByVal-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByVal-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8974545@example.com</confObjID> <confObjID>xcon:8974545@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<version>1</version> <version>1</version>
<ccmp:sidebarByValResponse> <ccmp:sidebarByValResponse>
<sidebarByValInfo entity="xcon:8974545@example.com"> <sidebarByValInfo entity="xcon:8974545@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
skipping to change at page 74, line 17 skipping to change at page 74, line 14
provided for Bob by Alice, the call signaling to add Bob to the provided for Bob by Alice, the call signaling to add Bob to the
sidebar with the appropriate media characteristics is instigated sidebar with the appropriate media characteristics is instigated
through the Focus. Bob is notified of his addition to the through the Focus. Bob is notified of his addition to the
sidebar via the conference notification service, thus he is aware sidebar via the conference notification service, thus he is aware
that Alice, the supervisor, is available for coaching him through that Alice, the supervisor, is available for coaching him through
this call. this call.
1. sidebarByRefRequest/create message (Alice as coach creates a sidebar) 1. sidebarByRefRequest/create message (Alice as coach creates a sidebar)
<?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:ccmp="urn:ietf:params:xml:ns:xcon:ccmp" xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type"> <ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8978383@example.com</confObjID> <confObjID>xcon:8978383@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:sidebarsByRefRequest/> <ccmp:sidebarsByRefRequest/>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
2. sidebarByRefResponse/create message (sidebar created) 2. sidebarByRefResponse/create message (sidebar created)
<?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
xsi:type="ccmp:ccmp-sidebarByRef-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByRef-response-message-type">
<confUserID>xcon-userid:alice@example.com</confUserID> <confUserID>xcon-userid:alice@example.com</confUserID>
<confObjID>xcon:8971313@example.com</confObjID> <confObjID>xcon:8971313@example.com</confObjID>
<operation>create</operation> <operation>create</operation>
<ccmp:response-code>200</ccmp:response-code> <ccmp:response-code>200</ccmp:response-code>
<ccmp:response-string>success</ccmp:response-string> <ccmp:response-string>success</ccmp:response-string>
<version>1</version> <version>1</version>
<ccmp:sidebarByRefResponse> <ccmp:sidebarByRefResponse>
<sidebarByRefInfo entity="xcon:8971313@example.com"> <sidebarByRefInfo entity="xcon:8971313@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
skipping to change at page 75, line 45 skipping to change at page 75, line 46
</info:users> </info:users>
</sidebarByRefInfo> </sidebarByRefInfo>
</ccmp:sidebarByRefResponse> </ccmp:sidebarByRefResponse>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
3. sidebarByRefRequest/update message (Alice introduces unilateral 3. sidebarByRefRequest/update message (Alice introduces unilateral
sidebar audio and excludes Carol from the sidebar) sidebar audio and excludes Carol from the sidebar)
<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
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByRef-request-message-type">
<confUserID>xcon-userid:alice@example.com</confUserID> <confUserID>xcon-userid:alice@example.com</confUserID>
<confObjID>xcon:8971313@example.com</confObjID> <confObjID>xcon:8971313@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<ccmp:sidebarByRefRequest> <ccmp:sidebarByRefRequest>
<sidebarByRefInfo entity="xcon:8971313@example.com"> <sidebarByRefInfo entity="xcon:8971313@example.com">
<info:conference-description> <info:conference-description>
<info:display-text> <info:display-text>
Coaching sidebar Alice and Bob Coaching sidebar Alice and Bob
</info:display-text> </info:display-text>
<info:available-media> <info:available-media>
skipping to change at page 76, line 50 skipping to change at page 77, line 4
<info:endpoint entity="sip:Bob@example.com"> <info:endpoint entity="sip:Bob@example.com">
<info:media id="AUTO_GENERATE_3"> <info:media id="AUTO_GENERATE_3">
<info:label>AUTO_GENERATE_1</info:label> <info:label>AUTO_GENERATE_1</info:label>
<info:status>recvonly</info:status> <info:status>recvonly</info:status>
</info:media> </info:media>
</info:endpoint> </info:endpoint>
</user> </user>
</info:users> </info:users>
</sidebarByRefInfo> </sidebarByRefInfo>
</ccmp:sidebarByRefRequest> </ccmp:sidebarByRefRequest>
</ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest> </ccmp:ccmpRequest>
4. sidebarByRefRequest/update message (updates accepted) 4. sidebarByRefRequest/update message (updates accepted)
<?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
xsi:type="ccmp:ccmp-sidebarByRef-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-sidebarByRef-response-message-type">
<confUserID>xcon-userid:alice@example.com</confUserID> <confUserID>xcon-userid:alice@example.com</confUserID>
<confObjID>xcon:8971313@example.com</confObjID> <confObjID>xcon:8971313@example.com</confObjID>
<operation>update</operation> <operation>update</operation>
<response-code>200</response-code> <response-code>200</response-code>
<response-string>success</response-string> <response-string>success</response-string>
<version>2</version> <version>2</version>
<ccmp:sidebarByRefResponse/> <ccmp:sidebarByRefResponse/>
</ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse> </ccmp:ccmpResponse>
skipping to change at page 79, line 9 skipping to change at page 79, line 9
object for Bob in the "userInfo" element, the conferencing system object for Bob in the "userInfo" element, the conferencing system
starts the process to remove Bob (e.g., the call signaling to starts the process to remove Bob (e.g., the call signaling to
remove Bob from the conference is instigated through the Focus). remove Bob from the conference is instigated through the Focus).
The conference server updates the data in the conference object, The conference server updates the data in the conference object,
thus removing Bob from the <users> list. After updating the thus removing Bob from the <users> list. After updating the
data, the conference server sends a userResponse message to data, the conference server sends a userResponse message to
Alice. Depending upon the policies, other participants (e.g. Alice. Depending upon the policies, other participants (e.g.
"Claire") may be notified of the removal of Bob from the "Claire") may be notified of the removal of Bob from the
conference via the Conference Notification Service. conference via the Conference Notification Service.
1. userRequest/delete message (Alice deletes Bob): 1. userRequest/delete message (Alice deletes Bob):
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>delete</operation>
<ccmp:userRequest>
<userInfo entity="xcon-userid:Bob@example.com"/>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
2. userResponse/delete message (Bob has been deleted) <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpRequest
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-request-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>delete</operation>
<ccmp:userRequest>
<userInfo entity="xcon-userid:Bob@example.com"/>
</ccmp:userRequest>
</ccmpRequest>
</ccmp:ccmpRequest>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> 2. userResponse/delete message (Bob has been deleted)
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>delete</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>17</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ccmp:ccmpResponse
xmlns:info="urn:ietf:params:xml:ns:conference-info"
xmlns:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-response-message-type">
<confUserID>xcon-userid:Alice@example.com</confUserID>
<confObjID>xcon:8977794@example.com</confObjID>
<operation>delete</operation>
<response-code>200</response-code>
<response-string>success</response-string>
<version>17</version>
<ccmp:userResponse/>
</ccmpResponse>
</ccmp:ccmpResponse>
Figure 30: Removing a Participant Messaging Details Figure 30: Removing a Participant Messaging Details
8.2. Deleting a Conference 8.2. Deleting a Conference
In this section, an example of a successful conference deletion is In this section, an example of a successful conference deletion is
provided (Figure 31). provided (Figure 31).
Alice ConfS Alice ConfS
| | | |
|(1)confRequest(confUserID, | |(1)confRequest(confUserID, |
skipping to change at page 81, line 5 skipping to change at page 81, line 5
"confUserID" included in the receipt request, ensures that Alice "confUserID" included in the receipt request, ensures that Alice
has the appropriate authority to fulfill the operation. has the appropriate authority to fulfill the operation.
2. After validating Alice's rights, the conferencing server 2. After validating Alice's rights, the conferencing server
instigates the process to delete the conference object, instigates the process to delete the conference object,
disconnetting participants and removing associated resources such disconnetting participants and removing associated resources such
as mixer instances. Then, the conference server returns a as mixer instances. Then, the conference server returns a
confResponse message to Alice with "200" as "response-code" and confResponse message to Alice with "200" as "response-code" and
the deleted conference XCON-URI in the "confObjID" field. the deleted conference XCON-URI in the "confObjID" field.
1. confRequest/delete message (Alice deletes a conference) 1. confRequest/delete message (Alice deletes a conference)
<?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
xsi:type="ccmp:ccmp-conf-request-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-conf-request-message-type">
<confObjID>xcon:8977794@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>delete</operation> <confObjID>xcon:8977794@example.com</confObjID>
<ccmp:confRequest/> <operation>delete</operation>
</ccmpRequest> <ccmp:confRequest/>
</ccmp:ccmpRequest> </ccmpRequest>
</ccmp:ccmpRequest>
2. confResponse/delete message (200, "success") 2. confResponse/delete message (200, "success")
<?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
xsi:type="ccmp:ccmp-conf-response-message-type"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<confUserID>xcon-userid:Alice@example.com</confUserID> xsi:type="ccmp:ccmp-conf-response-message-type">
<confObjID>xcon:8977794@example.com</confObjID> <confUserID>xcon-userid:Alice@example.com</confUserID>
<operation>delete</operation> <confObjID>xcon:8977794@example.com</confObjID>
<response-code>200</response-code> <operation>delete</operation>
<response-string>success</response-string> <response-code>200</response-code>
<ccmp:confResponse/> <response-string>success</response-string>
</ccmpResponse> <ccmp:confResponse/>
</ccmp:ccmpResponse> </ccmpResponse>
</ccmp:ccmpResponse>
Figure 32: Deleting a Conference Messaging Details Figure 32: Deleting a Conference Messaging Details
9. IANA Considerations 9. IANA Considerations
This document has no IANA considerations. This document has no IANA considerations.
10. Security Considerations 10. Security Considerations
The security considerations applicable to the implementation of these The security considerations applicable to the implementation of these
skipping to change at page 84, line 17 skipping to change at page 84, line 19
12. Acknowledgements 12. Acknowledgements
The detailed content for this document is derived from the prototype The detailed content for this document is derived from the prototype
work of Lorenzo Miniero, Simon Pietro-Romano, Tobia Castaldi and work of Lorenzo Miniero, Simon Pietro-Romano, Tobia Castaldi and
their colleagues at the University of Napoli. their colleagues at the University of Napoli.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[I-D.ietf-xcon-ccmp] [I-D.ietf-xcon-ccmp]
Barnes, M., Boulton, C., Romano, S., and H. Schulzrinne, Barnes, M., Boulton, C., Romano, S., and H. Schulzrinne,
"Centralized Conferencing Manipulation Protocol", "Centralized Conferencing Manipulation Protocol",
draft-ietf-xcon-ccmp-08 (work in progress), June 2010. draft-ietf-xcon-ccmp-09 (work in progress), July 2010.
13.2. Informative References 13.2. Informative References
[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS [RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999. Names", BCP 32, RFC 2606, June 1999.
[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,
June 2002. June 2002.
skipping to change at page 85, line 33 skipping to change at page 85, line 33
[RFC5567] Melanchuk, T., "An Architectural Framework for Media [RFC5567] Melanchuk, T., "An Architectural Framework for Media
Server Control", RFC 5567, June 2009. Server Control", RFC 5567, June 2009.
[I-D.ietf-mediactrl-mixer-control-package] [I-D.ietf-mediactrl-mixer-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "A Mixer McGlashan, S., Melanchuk, T., and C. Boulton, "A Mixer
Control Package for the Media Control Channel Framework", Control Package for the Media Control Channel Framework",
draft-ietf-mediactrl-mixer-control-package-11 (work in draft-ietf-mediactrl-mixer-control-package-11 (work in
progress), February 2010. progress), February 2010.
[I-D.boulton-xcon-session-chat]
Barnes, M., Boulton, C., and S. Loreto, "Chatrooms within
a Centralized Conferencing (XCON) System",
draft-boulton-xcon-session-chat-04 (work in progress),
July 2009.
Authors' Addresses Authors' Addresses
Mary Barnes Mary Barnes
Nortel Polycom
2201 Lakeside Blvd TX
Richardson, TX US
Email: mary.ietf.barnes@gmail.com
Email: mary.barnes@nortel.com
Lorenzo Miniero Lorenzo Miniero
Meetecho Meetecho
Via Carlo Poerio 89/a Via Carlo Poerio 89/a
Napoli 80121 Napoli 80121
Italy Italy
Email: lorenzo@meetecho.com Email: lorenzo@meetecho.com
Roberta Presta Roberta Presta
University of Napoli University of Napoli
Via Claudio 21 Via Claudio 21
Napoli 80125 Napoli 80125
Italy Italy
Email: roberta.presta@unina.it Email: roberta.presta@unina.it
Simon Pietro Romano Simon Pietro Romano
University of Napoli University of Napoli
 End of changes. 101 change blocks. 
1082 lines changed or deleted 1142 lines changed or added

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