draft-ietf-xcon-cpcp-reqs-03.txt   draft-ietf-xcon-cpcp-reqs-04.txt 
XCON WG P. Koskelainen XCON WG P. Koskelainen
Internet-Draft H. Khartabil Internet-Draft H. Khartabil
Expires: October 25, 2004 Nokia Expires: February 10, 2005 Nokia
April 26, 2004 August 12, 2004
Requirements for Conference Policy Control Protocol Requirements for Conference Policy Control Protocol
draft-ietf-xcon-cpcp-reqs-03 draft-ietf-xcon-cpcp-reqs-04
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
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."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at
www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 25, 2004. This Internet-Draft will expire on February 10, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
The conference policy server allows clients to manipulate and The conference policy server allows clients to manipulate and
interact with the conference policy. One mechanism to manipulate the interact with the conference policy. One mechanism to manipulate the
policy is to use conference policy control protocol (CPCP). This policy is to use conference policy control protocol (CPCP). This
document gives the requirements for CPCP. document gives the requirements for CPCP.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Integration with Floor Control . . . . . . . . . . . . . . . . 6 4. Integration with Floor Control . . . . . . . . . . . . . . . . 6
5. Conference Policy Data Model . . . . . . . . . . . . . . . . . 7 5. Conference Policy Data Model . . . . . . . . . . . . . . . . . 7
6. CPCP Requirements . . . . . . . . . . . . . . . . . . . . . . 8 6. CPCP Requirements . . . . . . . . . . . . . . . . . . . . . . 8
6.1 Conference creation, termination and joining . . . . . . . . . 8 6.1 Conference creation, termination and joining . . . . . . . 8
6.2 Manipulating general conference attributes . . . . . . . . . . 9 6.2 Manipulating general conference attributes . . . . . . . . 9
6.3 Authentication and Security . . . . . . . . . . . . . . . . . 10 6.3 Authentication and Security . . . . . . . . . . . . . . . 10
6.4 Application and media manipulation . . . . . . . . . . . . . . 10 6.4 Application and media manipulation . . . . . . . . . . . . 10
6.5 ACL manipulation . . . . . . . . . . . . . . . . . . . . . . . 10 6.5 ACL manipulation . . . . . . . . . . . . . . . . . . . . . 10
6.6 Floor control . . . . . . . . . . . . . . . . . . . . . . . . 11 6.6 Floor control . . . . . . . . . . . . . . . . . . . . . . 11
6.7 Inviting and ejecting users . . . . . . . . . . . . . . . . . 11 6.7 Inviting and ejecting users . . . . . . . . . . . . . . . 12
6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . . . 12 6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . 12
6.9 General Protocol Requirements . . . . . . . . . . . . . . . . 12 6.9 General Protocol Requirements . . . . . . . . . . . . . . 12
7. Changes since draft-ietf-xcon-cpcp-reqs-02 . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. Changes since draft-ietf-xcon-cpcp-reqs-01 . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Changes since draft-ietf-xcon-cpcp-reqs-00 . . . . . . . . . . 16 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 15
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 8.2 Informative References . . . . . . . . . . . . . . . . . . . 15
Normative References . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15
Informative References . . . . . . . . . . . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . 20
1. Introduction 1. Introduction
The conferencing framework document [3] describes the overall The conferencing framework document [3] describes the overall
architecture, terminology, and protocol components needed for multi- architecture, terminology, and protocol components needed for multi-
party conferencing. It defines a logical function called a conference party conferencing. It defines a logical function called a
policy server which can store and manipulate rules associated with conference policy server which can store and manipulate rules
participation in a conference. These rules include directives on the associated with participation in a conference. These rules include
lifespan of the conference, who can and cannot join the conference, directives on the lifespan of the conference, who can and cannot join
definitions of roles available in the conference and the the conference, definitions of roles available in the conference and
responsibilities associated with those roles. the responsibilities associated with those roles.
The conference policy control protocol (CPCP) is a client-server
protocol that can be used by users to manipulate the rules associated
with the conference.
The conference policy is represented by a URI. There is a unique The conference policy is represented by a URI. There is a unique
conference policy for each conference. The conference policy URI conference policy for each conference. The conference policy URI
points to a conference policy server which can manipulate that points to a conference policy server which can manipulate that
conference policy. conference policy.
Conferencing framework describes also conference notification service
that is a logical function provided by the focus. It means that the
focus can act as a notifier, accepting subscriptions to the
conference state.
Note that CPCP is not the only mechanism to manipulate conference Note that CPCP is not the only mechanism to manipulate conference
policy, but other mechanisms exists as well, such as a Web interface. policy, but other mechanisms exists as well, such as a Web interface.
This document can be used with other documents, such as Conferencing This document is based on the definition and description of
framework document [3]. Moreover, [5] and [7] give useful background conference policy and the Conference Policy Control Protocol (CPCP)
in the Conferencing framework document [3], with the functionality of
CPCP being independent of SIP. Moreover, [6] give useful background
information about conferencing and floor control. information about conferencing and floor control.
2. Conventions Used in This Document 2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
3. Terminology 3. Terminology
skipping to change at page 6, line 15 skipping to change at page 6, line 15
4. Integration with Floor Control 4. Integration with Floor Control
Floor control is an optional feature often used by conferencing Floor control is an optional feature often used by conferencing
applications. It enables applications or users to gain safe and applications. It enables applications or users to gain safe and
mutually exclusive or non-exclusive input access to a shared object mutually exclusive or non-exclusive input access to a shared object
or resource. We define a floor as the temporary permission for a or resource. We define a floor as the temporary permission for a
conference participant to access or manipulate a specific shared conference participant to access or manipulate a specific shared
resource or group of resources. resource or group of resources.
We assume that the ability of users to create floors is governed by We assume that the ability of users to create floors is governed by
the conference policy. Conference user may use floor control protocol the conference policy. Conference user may use floor control
(see e.g. [6]) or some other mechanism to request floors. protocol (see e.g. [5]) or some other mechanism to request floors.
The conference policy also defines the floor control policy (e.g. The conference policy also defines the floor control policy (e.g.
moderator-controlled or server grants the floor randomly) and the moderator-controlled or server grants the floor randomly) and the
floor moderator, if the floor policy is moderator-controlled. floor moderator, if the floor policy is moderator-controlled.
The privileged user in a conference (such as the creator) can remove The privileged user in a conference (such as the creator) can remove
the floor at any time by modifying the conference policy (so that the the floor at any time by modifying the conference policy (so that the
resources are no longer floor- controlled), or change the floor resources are no longer floor- controlled), or change the floor
chair. chair.
skipping to change at page 9, line 9 skipping to change at page 9, line 9
REQ-A10: It MUST be possible to define the time after which users are REQ-A10: It MUST be possible to define the time after which users are
allowed to join the conference. allowed to join the conference.
REQ-A11: It MUST be possible to define the time after which new users REQ-A11: It MUST be possible to define the time after which new users
are not allowed to join the conference anymore. are not allowed to join the conference anymore.
REQ-A12: It MUST be possible to define the time when users or REQ-A12: It MUST be possible to define the time when users or
resources on the dial-out list are invited to join the conference. resources on the dial-out list are invited to join the conference.
REQ-A13: It MUST be possible define whether the conference can be REQ-A13: It MUST be possible define whether the conference can be
extended. Note: This does not guarantee that resources are available. extended. Note: This does not guarantee that resources are
available.
REQ-A14: It MUST be possible to indicate key participants. REQ-A14: It MUST be possible to indicate key participants.
REQ-A15a: It MUST be possible to define when media mixing starts REQ-A15a: It MUST be possible to define when media mixing starts
based on the latter of the mixing start time, and the time the first based on the latter of the mixing start time, and the time the first
participant arrives. participant arrives.
REQ X15b: It MUST be possible to define when media mixing starts REQ X15b: It MUST be possible to define when media mixing starts
based on the latter of the mixing start time, and the time the first based on the latter of the mixing start time, and the time the first
key participant arrives. key participant arrives.
skipping to change at page 10, line 18 skipping to change at page 10, line 20
can be per session or per media. can be per session or per media.
REQ-B7: It MUST be possible to set, modify and delete the parameter REQ-B7: It MUST be possible to set, modify and delete the parameter
for max number of conference participants. This defines the maximum for max number of conference participants. This defines the maximum
number of participants present at the same time. number of participants present at the same time.
REQ-B8: It MUST be possible to hide conference related information REQ-B8: It MUST be possible to hide conference related information
from non-privileged users. from non-privileged users.
Note: This defines the level of visibility of the basic conference Note: This defines the level of visibility of the basic conference
information (e.g. visible only to participants). This feature may be information (e.g. visible only to participants). This feature may
needed e.g. in search operations. be needed e.g. in search operations.
REQ-B9: It MUST be possible to set, modify and delete conference REQ-B9: It MUST be possible to set, modify and delete conference
Keywords. Keywords.
Note: (This may be useful e.g. for search engines). Note: (This may be useful e.g. for search engines).
6.3 Authentication and Security 6.3 Authentication and Security
REQ-C1: It MUST be possible to define appropriate authentication for REQ-C1: It MUST be possible to define appropriate authentication for
joining users. joining users.
skipping to change at page 11, line 14 skipping to change at page 11, line 16
the conference. the conference.
REQ-E4: It MUST be possible to define which users are allowed to join REQ-E4: It MUST be possible to define which users are allowed to join
a conference in a single operation. a conference in a single operation.
REQ-E5: It MUST be possible to define which users are places into REQ-E5: It MUST be possible to define which users are places into
pending list, waiting for further approval e.g. from moderator. pending list, waiting for further approval e.g. from moderator.
REQ-E6: It MUST be possible to use wildcards in ACL. REQ-E6: It MUST be possible to use wildcards in ACL.
REQ-E7: ACL conflicts MUST be solved in a well-defined way (e.g. what REQ-E7: ACL conflicts MUST be solved in a well-defined way (e.g.
if user appears both in blocked list and in allowed list) e.g. by what if user appears both in blocked list and in allowed list) e.g.
mandating the order in which ACL definitions are evaluated (e.g. most by mandating the order in which ACL definitions are evaluated (e.g.
specific expression first). most specific expression first).
REQ-E8: Conference MUST have default policy for those users that no REQ-E8: Conference MUST have default policy for those users that no
matching rule is found in ACL. matching rule is found in ACL.
REQ-E9: It MUST be possible to allow and disallow anonymous REQ-E9: It MUST be possible to allow and disallow anonymous
membership in a conference. membership in a conference.
6.6 Floor control 6.6 Floor control
REQ-F1: It MUST be possible to define whether floor control is in use REQ-F1: It MUST be possible to define whether floor control is in use
skipping to change at page 12, line 36 skipping to change at page 12, line 39
REQ-H2: It MUST be possible to give privileges to many users in a REQ-H2: It MUST be possible to give privileges to many users in a
single operation. single operation.
REQ-H3: It MUST be possible to remove a privilege from a user. REQ-H3: It MUST be possible to remove a privilege from a user.
REQ-H4: It MUST be possible to remove privileges from many users in a REQ-H4: It MUST be possible to remove privileges from many users in a
single operation. single operation.
REQ-H5: It MUST be possible to define users who are allowed to REQ-H5: It MUST be possible to define users who are allowed to
subscribe to the conference event package [4] subscribe to the conference event package [4].
REQ-H6: It MUST be only be possible for a users with sufficient REQ-H6: It MUST be only be possible for a users with sufficient
privileges to manipulate conference policy. privileges to manipulate conference policy.
Note: For example, the creator of the conference may manipulate Note: For example, the creator of the conference may manipulate
conference policy. conference policy.
6.9 General Protocol Requirements 6.9 General Protocol Requirements
REQ-CP-1: Protocol behaviour: CPCP protocol MUST be a reliable REQ-CP-1: Protocol behaviour: CPCP protocol MUST be a reliable
skipping to change at page 14, line 5 skipping to change at page 14, line 5
REQ-CP-4: It MUST be possible for the client to authenticate the REQ-CP-4: It MUST be possible for the client to authenticate the
server. server.
REQ-CP-5: It MUST be possible for message integrity to be ensured REQ-CP-5: It MUST be possible for message integrity to be ensured
between the client and the server. between the client and the server.
REQ-CP-6: It MUST be possible for privacy to be ensured between the REQ-CP-6: It MUST be possible for privacy to be ensured between the
client and server. client and server.
7. Changes since draft-ietf-xcon-cpcp-reqs-02 7. Acknowledgements
- start/stop time-related requirements clarified (requirements
A9-A17)
- removal of CP-3 (batching multiple operations) since it is
overlapping with other requirements e.g. H2
- removal of "moderator" in terminology (conflicts with floor
moderator)
8. Changes since draft-ietf-xcon-cpcp-reqs-01
- time definition changed: only start/stop times required
9. Changes since draft-ietf-xcon-cpcp-reqs-00
- floor control aligned with floor control requirements document
- removed the concept of hidden user
- anonymous membership modified
- removed "inactive"
- added media type requirement (e.g. audio, video)
10. Acknowledgements
The authors would like to thank Eric Burger, Keith Drage, Brian The authors would like to thank Eric Burger, Keith Drage, Brian
Rosen, Xiaotao Wu, Henning Schulzrinne, Simo Veikkolainen and IETF Rosen, Xiaotao Wu, Henning Schulzrinne, Simo Veikkolainen, Mary
conferencing design team for their feedback. Barnes and IETF conferencing design team for their feedback.
Normative References 8. References
8.1 Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCD 14, March 1997. Levels", RFC 2119, BCD 14, March 1997.
[2] Rosenberg et al., J., "SIP: Session Initiation Protocol", RFC [2] Rosenberg et al., J., "SIP: Session Initiation Protocol", RFC
3261, June 2002. 3261, June 2002.
[3] Rosenberg, J., "A Framework for Conferencing with the Session [3] Rosenberg, J., "A Framework for Conferencing with the Session
Initiation Protocol", Initiation Protocol",
draft-rosenberg-sipping-conferencing-framework-01 (work in draft-rosenberg-sipping-conferencing-framework-01 (work in
progress), February 2003. progress), February 2003.
[4] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [4] Rosenberg, J., "A Session Initiation Protocol (SIP) Event
Package for Conference State", Package for Conference State",
draft-ietf-sipping-conference-package-03 (work in progress), draft-ietf-sipping-conference-package-03 (work in progress),
February 2004. February 2004.
Informative References 8.2 Informative References
[5] Koskelainen, P., Schulzrinne, H. and X. Wu, "Additional
Requirements to Conferencing", October 2002.
[6] Wu, X., Schulzrinne, H. and P. Koskelainen, "Use of SIP and SOAP [5] Wu, X., Schulzrinne, H. and P. Koskelainen, "Use of SIP and SOAP
for conference floor control", January 2003. for conference floor control", draft-wu-sipping-floor-control-04
(work in progress), January 2003.
[7] Koskelainen, P., Schulzrinne, H. and X. Wu, "A sip-based [6] Koskelainen, P., Schulzrinne, H. and X. Wu, "A sip-based
conference control framework", Nossdav'2002 Miami Beach, May conference control framework", Nossdav'2002 Miami Beach, May
2002. 2002.
Authors' Addresses Authors' Addresses
Petri Koskelainen Petri Koskelainen
Nokia Nokia
P.O. Box 100 (Visiokatu 1) P.O. Box 100 (Visiokatu 1)
Tampere FIN-33721 Tampere FIN-33721
Finland Finland
skipping to change at page 20, line 8 skipping to change at page 17, line 8
Nokia Nokia
P.O. Box 321 P.O. Box 321
Helsinki FIN-00045 Helsinki FIN-00045
Finland Finland
EMail: hisham.khartabil@nokia.com EMail: hisham.khartabil@nokia.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/