draft-ietf-xcon-cpcp-reqs-00.txt   draft-ietf-xcon-cpcp-reqs-01.txt 
XCON WG P. Koskelainen XCON WG P. Koskelainen
Internet-Draft H. Khartabil Internet-Draft H. Khartabil
Expires: June 7, 2004 Nokia Expires: July 19, 2004 Nokia
December 8, 2003 January 19, 2004
Requirements for Conference Policy Control Protocol Requirements for Conference Policy Control Protocol
draft-ietf-xcon-cpcp-reqs-00 draft-ietf-xcon-cpcp-reqs-01
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 http://
www.ietf.org/ietf/1id-abstracts.txt. 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 June 7, 2004. This Internet-Draft will expire on July 19, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). 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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
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 . . . . . . . . . . 8 6.2 Manipulating general conference attributes . . . . . . . . . . 8
6.3 Authentication and Security . . . . . . . . . . . . . . . . . 9 6.3 Authentication and Security . . . . . . . . . . . . . . . . . 9
6.4 Application and media manipulation . . . . . . . . . . . . . . 9 6.4 Application and media manipulation . . . . . . . . . . . . . . 9
6.5 ACL manipulation . . . . . . . . . . . . . . . . . . . . . . . 9 6.5 ACL manipulation . . . . . . . . . . . . . . . . . . . . . . . 9
6.6 Floor control . . . . . . . . . . . . . . . . . . . . . . . . 10 6.6 Floor control . . . . . . . . . . . . . . . . . . . . . . . . 10
6.7 Inviting and ejecting users . . . . . . . . . . . . . . . . . 10 6.7 Inviting and ejecting users . . . . . . . . . . . . . . . . . 11
6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . . . 10 6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . . . 11
6.9 General Protocol Requirements . . . . . . . . . . . . . . . . 11 6.9 General Protocol Requirements . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Changes since draft-ietf-xcon-cpcp-reqs-00 . . . . . . . . . . 13
Normative References . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
Informative References . . . . . . . . . . . . . . . . . . . . 14 Normative References . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14 Informative References . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . 17
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 conference
policy server (CPS) which can store and manipulate rules associated policy server (CPS) which can store and manipulate rules associated
with participation in a conference. These rules include directives with participation in a conference. These rules include directives
on the lifespan of the conference, who can and cannot join the on the lifespan of the conference, who can and cannot join the
conference, definitions of roles available in the conference and the conference, definitions of roles available in the conference and the
responsibilities associated with those roles, and policies on who is responsibilities associated with those roles.
allowed to request which roles.
The conference policy control protocol (CPCP) is a client-server The conference policy control protocol (CPCP) is a client-server
protocol that can be used by users to manipulate the rules associated protocol that can be used by users to manipulate the rules associated
with the conference. 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.
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. Privileged conference user may use floor the conference policy. Conference user may use floor control protocol
control protocol (see e.g. [6]) or some other mechanism to create (see e.g. [6]) or some other mechanism to request floors.
floors.
The conference policy defines who is allowed to create, change, and
remove floors using the floor control protocol.
Floor chair is also appointed using the floor control protocol when The conference policy also defines the floor control policy (e.g.
the floor is created. Typically, only conference moderators are moderator-controlled or server grants the floor randomly) and the
allowed to use these commands. floor moderator, if the floor policy is moderator-controlled.
The conference moderator can remove the floor at any time using floor The privileged user in a conference (such as the creator) can remove
control protocol (so that the resources are no longer floor- the floor at any time by modifying the conference policy (so that the
controlled), or change the floor chair or the floor parameters. resources are no longer floor- controlled), or change the floor
chair.
The floor chair just controls the access to the floor, according to The floor moderator just controls the access to the floor, according
the floor policy, defined at a time when the floor is created. to the floor policy, defined by the conference policy at a time when
the floor is created.
5. Conference Policy Data Model 5. Conference Policy Data Model
Conference policy data is relatively static. It is not updated Conference policy data is relatively static. It is not updated
frequently as e.g. participant list is not part of conference policy. frequently as e.g. participant list is not part of conference policy.
Users with sufficient privileges are able to manipulate conference Users with sufficient privileges are able to manipulate conference
policy. For example, a user with sufficient privileges may policy. For example, a user with sufficient privileges may
manipulate conference's access control list by adding a user into the manipulate conference's access control list by adding a user into the
ACL allowed list. ACL allowed list.
6. CPCP Requirements 6. CPCP Requirements
This section describes requirements for the conference policy This section describes requirements for the conference policy control
protocol. protocol (CPCP).
6.1 Conference creation, termination and joining 6.1 Conference creation, termination and joining
REQ-A1: It MUST be possible to create a new conference addressable by REQ-A1: It MUST be possible to create a new conference addressable by
a URI. a URI.
REQ-A2: It MUST be possible to associate policy attributes to a REQ-A2: It MUST be possible to associate policy attributes to a
conference URI. conference URI.
REQ-A3: It MUST be possible to reserve a conference URI for future REQ-A3: It MUST be possible to reserve a conference URI for future
use with or without associating policy attributes to it. use with or without associating policy attributes to it.
REQ-A4: It SHOULD be possible for a privileged user to read REQ-A4: It MUST be possible for a privileged user to read conference
conference policy for a given conference URI, during and before policy for a given conference URI, during and before joining the
joining the conference. conference.
REQ-A5: It MUST be possible to delete existing conference policy. REQ-A5: It MUST be possible to delete existing conference policy.
This results in terminating the conference, deleting conference URI This results in terminating the conference, deleting conference URI
and releasing all resources associated with it. and releasing all resources associated with it.
REQ-A6: It SHOULD be possible to anonymously participate in a REQ-A6: It MUST be possible to anonymously participate in a
conference. conference.
REQ-A7: It SHOULD be possible to participate in a conference as a REQ-A7: It MUST NOT be possible for a user to authenticate himself as
hidden user. Hidden user is present in a conference, but his presense an anonymous user.
is not revealed.
Note: A conference focus must not accept users to authenticate
themselves with a username "anonymous" (like in Digest
authentication).
REQ-A8: It MUST be possible to assign multiple conference URIs to a REQ-A8: It MUST be possible to assign multiple conference URIs to a
conference, one for each call signaling protocol that the conference conference, one for each session signaling protocol scheme that the
server supports. conference server supports.
6.2 Manipulating general conference attributes 6.2 Manipulating general conference attributes
REQ-B1: It MUST be possible to set, modify and delete a conference REQ-B1: It MUST be possible to set, modify and delete a conference
Subject. Subject.
REQ-B2: It MUST be possible to set, modify and delete conference URI REQ-B2: It MUST be possible to set, modify and delete conference URI
display name. display name.
REQ-B3: It MUST be possible to set, modify and delete conference REQ-B3: It MUST be possible to set, modify and delete conference
skipping to change at page 9, line 12 skipping to change at page 9, line 15
REQ-B4: It MUST be possible to set, modify and delete conference URI REQ-B4: It MUST be possible to set, modify and delete conference URI
link for more information (as used e.g. in SDP u line). link for more information (as used e.g. in SDP u line).
REQ-B5: It MUST be possible to set, modify and delete conference host REQ-B5: It MUST be possible to set, modify and delete conference host
contact information (as used e.g. in SDP e and p lines). contact information (as used e.g. in SDP e and p lines).
REQ-B6: It MUST be possible to set, modify and delete short REQ-B6: It MUST be possible to set, modify and delete short
conference session description (as used e.g. in SDP i line). This conference session description (as used e.g. in SDP i line). This
can be per session or per media. can be per session or per media.
REQ-B7: It SHOULD 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 how many for max number of conference participants. This defines the maximum
users at max can be 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.
REQ-B9: It MUST be possible to inactive a conference for defined Note: This defines the level of visibility of the basic conference
period of time. information (e.g. visible only to participants). This feature may be
needed e.g. in search operations.
REQ-B10: It SHOULD be possible to set, modify and delete conference REQ-B9: It MUST be possible to set, modify and delete conference
Keywords. (This may be useful e.g. for search engines). Keywords.
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.
REQ-C2: It MUST be possible to use sips: scheme as a conference URI.
6.4 Application and media manipulation 6.4 Application and media manipulation
REQ-D1: It MAY be possible to define media policy within conference REQ-D1: It MAY be possible to define media policy within conference
policy. policy.
REQ-D2: It MUST be possible to define the media types for the
conference.
Note: This means MIME main types, such as audio and video. The
conference server can use this information e.g when placing m lines
in SIP/SDP dial-outs.
6.5 ACL manipulation 6.5 ACL manipulation
REQ-E1: It MUST be possible to define which users are not allowed to REQ-E1: It MUST be possible to define which users are not allowed to
join the conference. join the conference.
REQ-E2: It MUST be possible to define which users are not allowed to REQ-E2: It MUST be possible to define which users are not allowed to
join a conference in a single operation. join a conference in a single operation.
REQ-E3: It MUST be possible to define which users are allowed to join REQ-E3: It MUST be possible to define which users are allowed to join
the conference. the conference.
skipping to change at page 10, line 19 skipping to change at page 10, line 31
if user appears both in blocked list and in allowed list) e.g. by if user appears both in blocked list and in allowed list) e.g. by
mandating the order in which ACL definitions are evaluated (e.g. most mandating the order in which ACL definitions are evaluated (e.g. most
specific expression first). 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.
REQ-E10: It MUST be possible to allow and disallow hidden membership
in a conference.
6.6 Floor control 6.6 Floor control
REQ-F1: It MUST be possible to assign and de-assign the users who are REQ-F1: It MUST be possible to define whether floor control is in use
allowed to manipulate floor policy. or not.
REQ-F2: It MUST be possible to define the algorithm to be used in
granting the floor.
Note: Example algorithms might be e.g. moderator-controlled, FCFS,
random.
REQ-F3: It MUST be possible to define how many users can have the
floor at the same time.
REQ-F4: It MUST be possible to have one floor for one or more media
types.
REQ-F5: It MUST be possible to have multiple floors in a conference.
REQ-F6: It MUST be possible to define whether a floor is
moderator-controlled or not.
REQ-F7: If the floor is moderator-controlled, it MUST be possible to
assign and replace the floor moderator.
6.7 Inviting and ejecting users 6.7 Inviting and ejecting users
REQ-G1: It MUST be possible to define a dial-out list of users that REQ-G1: It MUST be possible to define a dial-out list of users that
the conference focus invites. the conference focus invites.
REQ-G2: It MUST be possible to set a dial-out list in a single REQ-G2: It MUST be possible to set a dial-out list in a single
operation. operation.
REQ-G3: It MUST be possible to expel users from a currently occurring REQ-G3: It MUST be possible to expel users from a currently occurring
conference. conference.
REQ-G4: It MUST be possible to expel many users in a single REQ-G4: It MUST be possible to expel many users in a single
operation. operation.
REQ-G5: It SHOULD be possible to define list of users who the focus REQ-G5: It MUST be possible to define list of users who the focus
should refer to the conference (so that the referred users will dial should refer to the conference (so that the referred users will dial
in the conference). in the conference).
REQ-G6: It SHOULD be possible to set the list of referred users in a REQ-G6: It MUST be possible to set the list of referred users in a
single operation. single operation.
6.8 User Privileges 6.8 User Privileges
REQ-H1: It MUST be possible to give a privilege to a user. REQ-H1: It MUST be possible to give a privilege to a user.
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 SHOULD be possible to define users who are allowed to REQ-H5: It MUST be possible to define users who are allowed to
subscribe to conference event package [4] subscribe to the conference event package [4]
REQ-H6: It MUST be only be possible for a users with sufficient
privileges to manipulate conference policy.
Note: For example, the creator of the conference may manipulate
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
client-server protocol. Hence, it MUST have a positive response client-server protocol. Hence, it MUST have a positive response
indicating that the request has been received, or error response if indicating that the request has been received, or error response if
an error has occurred. an error has occurred.
REQ-CP-2: Manipulations of the policy collection MUST exhibit the REQ-CP-2: Manipulations of the policy collection MUST exhibit the
ACID property; that is, they MUST be atomic, be consistent, durable, ACID property; that is, they MUST be atomic, be consistent, durable,
skipping to change at page 12, line 5 skipping to change at page 13, line 5
REQ-CP-5: It MUST be possible for the client to authenticate the REQ-CP-5: It MUST be possible for the client to authenticate the
server. server.
REQ-CP-6: It MUST be possible for message integrity to be ensured REQ-CP-6: It MUST be possible for message integrity to be ensured
between the client and the server. between the client and the server.
REQ-CP-7: It MUST be possible for privacy to be ensured between the REQ-CP-7: It MUST be possible for privacy to be ensured between the
client and server. client and server.
7. Acknowledgements 7. Changes since draft-ietf-xcon-cpcp-reqs-00
The author would like to thank Eric Burger, Xiaotao Wu, Henning - floor control aligned with floor control requirements document
Schulzrinne, Simo Veikkolainen and IETF conferencing design team for
their feedback. - removed the concept of hidden user
- anonymous membership modified
- removed "inactive"
- added media type requirement (e.g. audio, video)
8. Acknowledgements
The authors would like to thank Eric Burger, Keith Drage, Brian
Rosen, Xiaotao Wu, Henning Schulzrinne, Simo Veikkolainen and IETF
conferencing design team for their feedback.
Normative References 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
skipping to change at page 15, line 29 skipping to change at page 17, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
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 which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

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