draft-ietf-xcon-cpcp-reqs-01.txt   draft-ietf-xcon-cpcp-reqs-02.txt 
XCON WG P. Koskelainen XCON WG P. Koskelainen
Internet-Draft H. Khartabil Internet-Draft H. Khartabil
Expires: July 19, 2004 Nokia Expires: July 29, 2004 Nokia
January 19, 2004 January 29, 2004
Requirements for Conference Policy Control Protocol Requirements for Conference Policy Control Protocol
draft-ietf-xcon-cpcp-reqs-01 draft-ietf-xcon-cpcp-reqs-02
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 July 19, 2004. This Internet-Draft will expire on July 29, 2004.
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
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . 11 6.7 Inviting and ejecting users . . . . . . . . . . . . . . . . . 11
6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . . . 11 6.8 User Privileges . . . . . . . . . . . . . . . . . . . . . . . 11
6.9 General Protocol Requirements . . . . . . . . . . . . . . . . 11 6.9 General Protocol Requirements . . . . . . . . . . . . . . . . 12
7. Changes since draft-ietf-xcon-cpcp-reqs-00 . . . . . . . . . . 13 7. Changes since draft-ietf-xcon-cpcp-reqs-01 . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 8. Changes since draft-ietf-xcon-cpcp-reqs-00 . . . . . . . . . . 14
Normative References . . . . . . . . . . . . . . . . . . . . . 15 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
Informative References . . . . . . . . . . . . . . . . . . . . 16 Normative References . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16 Informative References . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 18
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
skipping to change at page 3, line 31 skipping to change at page 3, line 31
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 Conferencing framework describes also conference notification service
that is a logical function provided by the focus. It means that the that is a logical function provided by the focus. It means that the
focus can act as a notifier, accepting subscriptions to the focus can act as a notifier, accepting subscriptions to the
conference state. 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 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 can be used with other documents, such as Conferencing
framework document [3]. Moreover, [5] and [7] give useful background framework document [3]. Moreover, [5] and [7] 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.
skipping to change at page 7, line 8 skipping to change at page 7, line 8
resources are no longer floor- controlled), or change the floor resources are no longer floor- controlled), or change the floor
chair. chair.
The floor moderator just controls the access to the floor, according The floor moderator just controls the access to the floor, according
to the floor policy, defined by the conference policy at a time when to the floor policy, defined by the conference policy at a time when
the floor is created. 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 the conference
Users with sufficient privileges are able to manipulate conference policy. Users with sufficient privileges are able to manipulate
policy. For example, a user with sufficient privileges may conference policy. For example, a user with sufficient privileges
manipulate conference's access control list by adding a user into the may manipulate conference's access control list by adding a user into
ACL allowed list. the ACL allowed list.
6. CPCP Requirements 6. CPCP Requirements
This section describes requirements for the conference policy control This section describes requirements for the conference policy control
protocol (CPCP). 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.
skipping to change at page 8, line 43 skipping to change at page 8, line 43
an anonymous user. an anonymous user.
Note: A conference focus must not accept users to authenticate Note: A conference focus must not accept users to authenticate
themselves with a username "anonymous" (like in Digest themselves with a username "anonymous" (like in Digest
authentication). 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 session signaling protocol scheme that the conference, one for each session signaling protocol scheme that the
conference server supports. conference server supports.
REQ-A9: It MUST be possible to define the start and stop times for
the conference.
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
creator information (as is seen e.g. in SDP o line). creator information (as is seen e.g. in SDP o line).
skipping to change at page 13, 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. Changes since draft-ietf-xcon-cpcp-reqs-00 7. Changes since draft-ietf-xcon-cpcp-reqs-01
- time definition changed: only start/stop times required
8. Changes since draft-ietf-xcon-cpcp-reqs-00
- floor control aligned with floor control requirements document - floor control aligned with floor control requirements document
- removed the concept of hidden user - removed the concept of hidden user
- anonymous membership modified - anonymous membership modified
- removed "inactive" - removed "inactive"
- added media type requirement (e.g. audio, video) - added media type requirement (e.g. audio, video)
8. Acknowledgements 9. 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 and IETF
conferencing design team for their feedback. 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.
 End of changes. 

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