draft-ietf-xcon-examples-09.txt   draft-ietf-xcon-examples-10.txt 
XCON Working Group M. Barnes XCON Working Group M. Barnes
Internet-Draft Polycom Internet-Draft Polycom
Intended status: Informational L. Miniero Intended status: Informational L. Miniero
Expires: January 12, 2012 Meetecho Expires: February 3, 2012 Meetecho
R. Presta R. Presta
S P. Romano S P. Romano
University of Napoli University of Napoli
July 11, 2011 August 2, 2011
Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
draft-ietf-xcon-examples-09 draft-ietf-xcon-examples-10
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 12, 2012. This Internet-Draft will expire on February 3, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 43 skipping to change at page 2, line 43
7.1. Internal Sidebar . . . . . . . . . . . . . . . . . . . . . 47 7.1. Internal Sidebar . . . . . . . . . . . . . . . . . . . . . 47
7.2. External Sidebar . . . . . . . . . . . . . . . . . . . . . 56 7.2. External Sidebar . . . . . . . . . . . . . . . . . . . . . 56
7.3. Private Messages . . . . . . . . . . . . . . . . . . . . . 63 7.3. Private Messages . . . . . . . . . . . . . . . . . . . . . 63
7.4. Observing and Coaching . . . . . . . . . . . . . . . . . . 67 7.4. Observing and Coaching . . . . . . . . . . . . . . . . . . 67
8. Removing Participants and Deleting Conferences . . . . . . . . 74 8. Removing Participants and Deleting Conferences . . . . . . . . 74
8.1. Removing a Party . . . . . . . . . . . . . . . . . . . . . 74 8.1. Removing a Party . . . . . . . . . . . . . . . . . . . . . 74
8.2. Deleting a Conference . . . . . . . . . . . . . . . . . . 77 8.2. Deleting a Conference . . . . . . . . . . . . . . . . . . 77
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 78 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 78
10. Security Considerations . . . . . . . . . . . . . . . . . . . 78 10. Security Considerations . . . . . . . . . . . . . . . . . . . 78
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 79 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 79
12. Informative References . . . . . . . . . . . . . . . . . . . . 79 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.1. Normative References . . . . . . . . . . . . . . . . . . . 79
12.2. Informative References . . . . . . . . . . . . . . . . . . 79
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 80
1. Introduction 1. Introduction
This document provides detailed call flows for the scenarios This document provides detailed call flows for the scenarios
documented in the Framework for Centralized Conferencing (XCON documented in the Framework for Centralized Conferencing (XCON
Framework) [RFC5239] and the XCON Scenarios [RFC4597]. The XCON Framework) [RFC5239] and the XCON Scenarios [RFC4597]. The XCON
scenarios describe a broad range of use cases taking advantage of the scenarios describe a broad range of use cases taking advantage of the
advanced conferencing capabilities provided by a system realization advanced conferencing capabilities provided by a system realization
of the XCON framework. The call flows document the use of the of the XCON framework. The call flows document the use of the
skipping to change at page 4, line 35 skipping to change at page 4, line 35
framework. With the exception of an initial example with media framework. With the exception of an initial example with media
control messaging, the examples do not include the details for the control messaging, the examples do not include the details for the
media control [I-D.ietf-mediactrl-mixer-control-package], call media control [I-D.ietf-mediactrl-mixer-control-package], call
signaling or binary floor control [RFC4582] protocols. This document signaling or binary floor control [RFC4582] protocols. This document
references the scenarios in the Media Control call flows references the scenarios in the Media Control call flows
[I-D.ietf-mediactrl-call-flows], SIP Call Control Conferencing [I-D.ietf-mediactrl-call-flows], SIP Call Control Conferencing
[RFC4579] and binary floor control protocol documents. [RFC4579] and binary floor control protocol documents.
The rest of this document is organized as follows. Section 4 The rest of this document is organized as follows. Section 4
presents an overview on CCMP, together with some implementation- presents an overview on CCMP, together with some implementation-
related details and related matters like HTTP transport and related details and related matters like HTTPS transport and
notifications. Section 5 presents the reader with examples showing notifications. Section 5 presents the reader with examples showing
the different approaches CCMP provides to create a new conference. the different approaches CCMP provides to create a new conference.
Section 6 more generally addresses the different user-related Section 6 more generally addresses the different user-related
manipulations that can be achieved by means of CCMP, by presenting a manipulations that can be achieved by means of CCMP, by presenting a
number of interesting scenarios. Section 7 addresses the several number of interesting scenarios. Section 7 addresses the several
scenarios that may involve the use of sidebars. Section 8 shows how scenarios that may involve the use of sidebars. Section 8 shows how
CCMP can be used to remove conferences and users from the system. CCMP can be used to remove conferences and users from the system.
Finally, Section 10 provides a few details for what concerns the Finally, Section 10 provides a few details for what concerns the
Security Considerations when it comes to implementing CCMP. Security Considerations when it comes to implementing CCMP.
skipping to change at page 5, line 12 skipping to change at page 5, line 12
Conferencing Manipulation Protocol (CCMP) [I-D.ietf-xcon-ccmp] works Conferencing Manipulation Protocol (CCMP) [I-D.ietf-xcon-ccmp] works
and how it can be transported across a network. A typical CCMP and how it can be transported across a network. A typical CCMP
interaction focusing on relevant aspects of the client-server interaction focusing on relevant aspects of the client-server
communication is described. Please note that this section assumes communication is described. Please note that this section assumes
the reader has an understanding of and has read the CCMP document. the reader has an understanding of and has read the CCMP document.
This section is intended to help the reader understand the actual This section is intended to help the reader understand the actual
protocol interactions. protocol interactions.
First a description of the protocol itself is provided Section 4.1, First a description of the protocol itself is provided Section 4.1,
including some implementation considerations. In Section 4.2, an including some implementation considerations. In Section 4.2, an
effective CCMP interaction is presented by exploiting HTTP as a effective CCMP interaction is presented by exploiting HTTPS as a
transport. Finally, notifications are described in Section 4.3. transport. Finally, notifications are described in Section 4.3.
The document then presents and describes some actual flows in detail The document then presents and describes some actual flows in detail
in the sections to follow. in the sections to follow.
4.1. CCMP and the Data Model 4.1. CCMP and the Data Model
CCMP is an XML-based protocol. It has been designed as a request/ CCMP is an XML-based protocol. It has been designed as a request/
response protocol. It is completely stateless, which means response protocol. It is completely stateless, which means
implementations can safely handle transactions independently from implementations can safely handle transactions independently from
skipping to change at page 11, line 47 skipping to change at page 11, line 47
5. Conference Creation 5. Conference Creation
This section provides details associated with the various ways in This section provides details associated with the various ways in
which a conference can be created using CCMP and the XCON framework which a conference can be created using CCMP and the XCON framework
constructs. As previously mentioned, the details of the media constructs. As previously mentioned, the details of the media
control, call signaling and floor control protocols, where control, call signaling and floor control protocols, where
applicable, are annotated in the flows without showing all the applicable, are annotated in the flows without showing all the
details. This also applies to CCMP, whose flows are related to the details. This also applies to CCMP, whose flows are related to the
protocol alone, hiding any detail concerning the transport that may protocol alone, hiding any detail concerning the transport that may
have been used (e.g., HTTP). However, for clarification purposes, have been used (e.g., HTTPS). However, for clarification purposes,
the first example Section 5.1 provides the details of the media the first example Section 5.1 provides the details of the media
control messaging with the standard annotation used throughout the control messaging with the standard annotation used throughout the
remainder of this document. In subsequent flows, only this remainder of this document. In subsequent flows, only this
annotation (identified by lower case letters) is included and the annotation (identified by lower case letters) is included and the
reader is encouraged to refer to the call flows in the relevant reader is encouraged to refer to the call flows in the relevant
documents for details about the other protocols. The annotations for documents for details about the other protocols. The annotations for
the call signaling are on the left side of the conferencing server the call signaling are on the left side of the conferencing server
vertical bar and those for the media control messaging are on the vertical bar and those for the media control messaging are on the
right side. right side.
skipping to change at page 39, line 15 skipping to change at page 39, line 15
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:ccmp="urn:ietf:params:xml:ns:xcon:ccmp"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"> xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info">
<ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <ccmpRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ccmp:ccmp-user-request-message-type"> xsi:type="ccmp:ccmp-user-request-message-type">
<subject> <subject>
<username>Alice83</username> <username>Alice83</username>
<password>13011983</password> <conference-password>13011983</conference-password>
</subject> </subject>
<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>update</operation> <operation>update</operation>
<ccmp:userRequest> <ccmp:userRequest>
<userInfo entity="xcon-userid:Bob@example.com"> <userInfo entity="xcon-userid:Bob@example.com">
<info:endpoint entity="sip:bob83@example.com"> <info:endpoint entity="sip:bob83@example.com">
<info:media id="1"> <info:media id="1">
<info:label>123</info:label> <info:label>123</info:label>
<info:status>recvonly</info:status> <info:status>recvonly</info:status>
skipping to change at page 79, line 16 skipping to change at page 79, line 16
flows, however, this is for informational purposes only. The flows, however, this is for informational purposes only. The
implementor is encouraged to carefully consider the security implementor is encouraged to carefully consider the security
requirements in the normative documents. requirements in the normative documents.
11. Acknowledgements 11. 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.
12. Informative References 12. References
12.1. Normative References
[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-13 (work in progress), May 2011. draft-ietf-xcon-ccmp-14 (work in progress), July 2011.
[I-D.ietf-xcon-event-package]
Camarillo, G., Srinivasan, S., Even, R., and J.
Urpalainen, "Conference Event Package Data Format
Extension for Centralized Conferencing (XCON)",
draft-ietf-xcon-event-package-01 (work in progress),
September 2008.
[I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-31
(work in progress), June 2011.
12.2. Informative References
[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.
[RFC4579] Johnston, A. and O. Levin, "Session Initiation Protocol [RFC4579] Johnston, A. and O. Levin, "Session Initiation Protocol
(SIP) Call Control - Conferencing for User Agents", (SIP) Call Control - Conferencing for User Agents",
BCP 119, RFC 4579, August 2006. BCP 119, RFC 4579, August 2006.
[RFC4597] Even, R. and N. Ismail, "Conferencing Scenarios", [RFC4597] Even, R. and N. Ismail, "Conferencing Scenarios",
RFC 4597, August 2006. RFC 4597, August 2006.
[RFC4582] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor [RFC4582] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor
Control Protocol (BFCP)", RFC 4582, November 2006. Control Protocol (BFCP)", RFC 4582, November 2006.
[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Initiation Protocol (SIP) Event Package for Conference Initiation Protocol (SIP) Event Package for Conference
State", RFC 4575, August 2006. State", RFC 4575, August 2006.
[I-D.ietf-xcon-event-package]
Camarillo, G., Srinivasan, S., Even, R., and J.
Urpalainen, "Conference Event Package Data Format
Extension for Centralized Conferencing (XCON)",
draft-ietf-xcon-event-package-01 (work in progress),
September 2008.
[I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-31
(work in progress), June 2011.
[I-D.ietf-mediactrl-call-flows] [I-D.ietf-mediactrl-call-flows]
Amirante, A., Castaldi, T., Miniero, L., and S. Romano, Amirante, A., Castaldi, T., Miniero, L., and S. Romano,
"Media Control Channel Framework (CFW) Call Flow "Media Control Channel Framework (CFW) Call Flow
Examples", draft-ietf-mediactrl-call-flows-07 (work in Examples", draft-ietf-mediactrl-call-flows-07 (work in
progress), July 2011. progress), July 2011.
[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]
 End of changes. 12 change blocks. 
24 lines changed or deleted 30 lines changed or added

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