[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00

XCON BOF                                                        O. Levin
Internet-Draft                                                 RADVISION
Expires: December 21, 2003                                 June 22, 2003


    Conference Policy Control Protocol for Centralized Conferencing
                        draft-levin-xcon-cpcp-00

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 21, 2003.

Copyright Notice

   Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

   This document lists operations to be addressed by a Conference Policy
   Control Protocol (CPCP). Each operation carries mandatory and
   optional parameters. Initially, for readability, the operations are
   presented using informal XML syntax. The actual protocol of choice
   and its formal syntax will be defined as a part the XCON working
   group process.










Levin                  Expires December 21, 2003                [Page 1]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


Table of Contents

   1.    Scope  . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.    General Assumptions  . . . . . . . . . . . . . . . . . . . .  3
   2.1   Get Info . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.1.1 Get Conference Profiles  . . . . . . . . . . . . . . . . . .  3
   2.2   Conference Management  . . . . . . . . . . . . . . . . . . .  4
   2.2.1 Conference Creation  . . . . . . . . . . . . . . . . . . . .  4
   2.2.2 Conference Termination . . . . . . . . . . . . . . . . . . .  5
   2.2.3 Conference Manipulation  . . . . . . . . . . . . . . . . . .  5
   3.    Participant Management . . . . . . . . . . . . . . . . . . .  6
   3.1   Invite Participant . . . . . . . . . . . . . . . . . . . . .  6
   3.1.1 Invite Participant Request . . . . . . . . . . . . . . . . .  6
   3.1.2 Invite Participant Response  . . . . . . . . . . . . . . . .  7
   3.2   Drop Participant . . . . . . . . . . . . . . . . . . . . . .  7
   3.2.1 Drop Participant Request . . . . . . . . . . . . . . . . . .  7
   3.2.2 Drop Participant Response  . . . . . . . . . . . . . . . . .  8
   4.    ACL  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
   5.    Side-bar Management  . . . . . . . . . . . . . . . . . . . .  8
   5.1   Set Participant to a Side-bar  . . . . . . . . . . . . . . .  8
   5.1.1 Set Participant to a Side-bar Request  . . . . . . . . . . .  8
   5.1.2 Set Participant to a Side-bar Response . . . . . . . . . . .  9
   6.    User Privilege Management  . . . . . . . . . . . . . . . . .  9
   6.1   Set Unset Privilege  . . . . . . . . . . . . . . . . . . . .  9
   6.1.1 Set Unset Privilege Request  . . . . . . . . . . . . . . . .  9
   6.1.2 Set Unset Privilege Response . . . . . . . . . . . . . . . .  9
   6.2   Take Release Privilege . . . . . . . . . . . . . . . . . . . 10
   6.2.1 Take Release Privilege Request . . . . . . . . . . . . . . . 10
   6.2.2 Take Release Privilege Response  . . . . . . . . . . . . . . 10
   7.    Functions and Issues Still to be Addressed . . . . . . . . . 10
   8.    Security Considerations  . . . . . . . . . . . . . . . . . . 10
   9.    Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
         Normative References . . . . . . . . . . . . . . . . . . . . 11
         Informative References . . . . . . . . . . . . . . . . . . . 11
         Author's Address . . . . . . . . . . . . . . . . . . . . . . 11
         Intellectual Property and Copyright Statements . . . . . . . 12















Levin                  Expires December 21, 2003                [Page 2]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


1. Scope

   This document lists operations to be addressed by a Conference Policy
   Control Protocol. Each operation carries mandatory and optional
   parameters. In this version, for readability, the operations are
   presented using informal XML syntax. The actual protocol of choice
   and its formal syntax will be defined as a part the XCON working
   group process.

2. General Assumptions

   CPCP is carried over a reliable transfer protocol.

   A CPCP primitive is implemented by a transaction. The simplest
   transaction consists of a Request and a Response. Each Request MUST
   contain a RequestID which MUST be returned in the corresponding
   Response.

        <RequestID> ReqID </RequestID>


2.1 Get Info

2.1.1 Get Conference Profiles

   This section fulfills the section 3.2 in the High Level Conferencing
   Requirements [3] document.

2.1.1.1 Get Profiles Request

   <Get_Profiles_Request>
        <RequestID> ReqID </RequestID>
   </Get_Profiles_Request>


2.1.1.2 Get Profiles Response

   <Get_Profiles_Response>
        <RequestID> ReqID </RequestID>
        <ReturnValue> ReturnValues </ReturnValue>
        <Profiles_List>
                <Profile>
                        <ProfileID> ID </ProfileID>
                        <ProfileDescription> description </ProfileDescription>
                </Profile>

                …




Levin                  Expires December 21, 2003                [Page 3]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


                <Profile>
                …
                </Profile>

        </Profiles_List>
   </Get_Profiles_Response>


2.2 Conference Management

   This section fulfills the section 5.1 in the Requirements for
   Conference Policy Data [4] document.

2.2.1 Conference Creation

2.2.1.1 Create Conference Request

   This command creates a new conference. All parameters are optional.
   Non-specified parameters MAY be filled in and returned in Response.

   Editor’s Note: The parameters can be specified both as a part of the
   profile and explicitly (i.e. overwriting the profile). The parameters
   below are for example only. How much flexibility is needed?


   In SIP:
   Name - Display Name
   ConfGID – SIP Conference URI


   <Create_Conference_Request>
        <RequestID> ReqID </RequestID>
        <ConfPassword> Conference password </ConfPassword>
        <ConfKeyword> Conference keyword </ConfKeyword>
        <Desc> Conference description </Desc>
        <ChairPassword> Chair password </ChairPassword>
        <TTL> INT time to live </TTL>
        <ProfileID> ProfileID </ProfileID>
        <StandByTimeOut> INT </StandByTimeOut>
        <Lang> Language </Lang>
        <InviteO> BOOL the conf is for invite only </InviteO>
        <ChInviteO> BOOL only chairman can invite </ChInviteO>
        <MinPorts> INT </MinPorts>
        <MaxPorts> INT </MaxPorts>
   </Create_Conference_Request>






Levin                  Expires December 21, 2003                [Page 4]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


2.2.1.2 Create Conference Response

   <Create_Conference_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <PolicyLink> PolicyLink </PolicyLink>
        <ReturnValue> ReturnValues </ReturnValue>
                </Create_Conference_Response>

   ReturnValue: OK / UserTerminated / MPCPFailure / Error /
   RegistrationFail / NotAuthorized / NoResources /
   BadOrMissingParameter

2.2.2 Conference Termination

   This section fulfills the section 5.1 in the Requirements for
   Conference Policy Data [4] document.

2.2.2.1 Terminate Conference Request

   This command disconnects all the users in the conference, terminates
   the conference and releases the internal resources associated with
   the conference.

   <Terminate_Conference_Request>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <RequestID> ReqID </RequestID>
   </Terminate_Conference_Request>


2.2.2.2 Terminate Conference Response

   <Terminate_Conference_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Terminate_Conference_Response>

   ReturnValue: OK / ConferenceNotFound / NoPermission /
   BadOrMissingParameter

2.2.3 Conference Manipulation

   This section fulfills the section 5.2 in the Requirements for
   Conference Policy Data [4] document.





Levin                  Expires December 21, 2003                [Page 5]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


2.2.3.1 Modify Conference Parameters Request

   This command modifies conference parameters that can be changed
   during the conference current state.

   <Modify_Conference_Request>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <RequestID> ReqID </RequestID>
        <ConfPassword> Conference password </ConfPassword>
        <ConfKeyword> Conference keyword </ConfKeyword>
        <Desc> Conference description </Desc>
        <ChairPassword> Chair password </ChairPassword>
        <TTL> INT time to live </TTL>
        <ProfileID> ProfileID </ProfileID>
        <StandByTimeOut> INT </StandByTimeOut>
        <Lang> Language </Lang>
        <InviteO> BOOL the conf is for invite only </InviteO>
        <ChInviteO> BOOL only chairman can invite </ChInviteO>
        <MinPorts> INT </MinPorts>
        <MaxPorts> INT </MaxPorts>

   </Modify_Conference_Request>


2.2.3.2 Modify Conference Parameters Response

   <Modify_Conference_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Modify_Conference_Response>

   ReturnValue: OK / ConferenceNotFound / NoPermission /
   BadOrMissingParameter

3. Participant Management

   This section fulfills the section 5.7 in the Requirements for
   Conference Policy Data [4] document.

3.1 Invite Participant

3.1.1 Invite Participant Request

   This command invites one or more participants to a given conference.

   <Invite_Participant_Request>



Levin                  Expires December 21, 2003                [Page 6]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <Invite_Part_List>
                <Invite_Part>
                        <DialStr> Participant alias </DialStr>
                    <Lang> Language </Lang>
                        <ProtocolType> type </ProtocolType>
                        <Set_Layout> TBD by MPCP </Set_Layout>
                      </Invite_Part>

                       …

                     <Invite_Part>
                     …
                    </Invite_Part>
              </Invite_Part_List>
   </Invite_Participant_Request>


3.1.2 Invite Participant Response

   <Invite_Participant_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Invite_Participant_Response>

   ReturnValues – OK / ConferenceNotFound / NoResources / HandleInvalid
   / MPCPFailure / UserTerminated / NoAnswer / Error /
   BadOrMissingParameter

3.2 Drop Participant

3.2.1 Drop Participant Request

   This command ejects a participant or participants from the
   conference.

   <Drop_Participant_Request>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <PID> PartID </PID>
        <ChairID> ChairID </ChairID>
   </Drop_Participant_Request>






Levin                  Expires December 21, 2003                [Page 7]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


3.2.2 Drop Participant Response

   <Drop_Participant_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Drop_Participant_Response>

   ReturnValue – OK / ConferenceNotFound / NoPermission / PartNotFound /
   BadOrMissingParameter

4. ACL

   This section fulfills the section 5.5 in the Requirements for
   Conference Policy Data [4] document.

   Editor’s Note: Access lists for a conference may be automatically
   derived from a default "service" or "domain" ACL upon the conference
   creation and later modified per conference using the primitives
   below.

   The primitives TBD.

   Manipulations on the access lists (ACL) for a conference may cause
   automatic disconnection of some participants by the focus (but not
   vice versa).

5. Side-bar Management

   This section fulfills the section 3.7 in the High Level Conferencing
   Requirements [3] document.

   This primitive moves a participant to a side-bar session, or back to
   the main conference. Participants in a side-bar can hear and see the
   main conference, but participants from the main session cannot hear/
   see them.

5.1 Set Participant to a Side-bar

5.1.1 Set Participant to a Side-bar Request

   <Set_Part_To_SB_Request>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <Set_SB_Part_List>
                <PID> PartID </PID>
                …



Levin                  Expires December 21, 2003                [Page 8]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


        </Set_SB_Part_List>
   <SBID> INT </SBID>
   </Set_Part_To_SB_Request>


5.1.2 Set Participant to a Side-bar Response

   <Set_Part_To_SB_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Set_Part_To_SB_Response>

   SBID – One of the Indexes of side bars for this conference (see
   conference info). Specify 0 for putting the participant back in the
   main session.

   ReturnValue – OK / ConferenceNotFound / NoPermission

6. User Privilege Management

   This section fulfills the section 5.8 in the Requirements for
   Conference Policy Data [4] document.

6.1 Set Unset Privilege

   This primitive assigns / retrieves specified privileges to/from a
   given user.

   If the list of privileges is omitted, the command refers to "all
   privileges" – i.e. - "a moderator".

6.1.1 Set Unset Privilege Request

   <Set_Unset_Privilege_Request>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <SetOn> BOOL </SetOn>
        <PList> list </PList>
        <ModeratorID> part GID </ModeratorID>
   </Set_Unset_Privilege_Request>


6.1.2 Set Unset Privilege Response

   <Set_Unset_Privilege_Response>
        <RequestID> ReqID </RequestID>



Levin                  Expires December 21, 2003                [Page 9]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Set_Unset_Privilege_Response>


6.2 Take Release Privilege

   Using this primitive a user can request for specific privileges or
   release previously owned privileges.

   If the list of privileges is omitted, the command refers to "all
   privileges" – i.e. - "a moderator".

6.2.1 Take Release Privilege Request

   <Take_Release_Privilege_Request>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ChairID> ChairID </ChairID>
        <SetOn> BOOL </SetOn>
        <PList> list </PList>
        <ModeratorID> part GID </ModeratorID>
   </Take_Release_Privilege_Request>


6.2.2 Take Release Privilege Response

   <Take_Release_Privilege_Response>
        <RequestID> ReqID </RequestID>
        <ConfGID> ConfGID </ConfGID>
        <ReturnValue> ReturnValues </ReturnValue>
   </Take_Release_Privilege_Response>


7. Functions and Issues Still to be Addressed

   Coordination between CPCP and Media Policy Control Protocol (MPCP)
   hasn’t been addressed yet. Some of the operations will require joined
   execution of CPCP and MPCP primitives in a single "atomic" operation.

   This version doesn’t include a set of operations required for
   cascading of conferences. Peer-to-peer conference cascading
   operations will be included in the next version of the document.

8. Security Considerations

   Editor’s Note: Will be provided in the next version of the document.




Levin                  Expires December 21, 2003               [Page 10]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


9. Contributors

   This work is based on the discussions among the members of the SIP
   Conferencing design team.

Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
        Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
        Session Initiation Protocol", RFC 3261, June 2002.

Informative References

   [3]  Levin, O. and R. Even, "High Level Requirements for Tightly
        Coupled SIP Conferencing",
        draft-ietf-sipping-conferencing-requirements-00 (work in
        progress), April 2003.

   [4]  Koskelainen, P., "Requirements for conference policy data",
        draft-koskelainen-sipping-conf-policy-req-00 (work in progress),
        February 2003.


Author's Address

   Orit Levin
   RADVISION
   266 Harristown Road
   Glen Rock, NJ  75024

   EMail: orit@radvision.com

















Levin                  Expires December 21, 2003               [Page 11]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2003). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   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
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Levin                  Expires December 21, 2003               [Page 12]


Internet-Draft     CPCP for Centralized Conferencing           June 2003


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.











































Levin                  Expires December 21, 2003               [Page 13]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/