1 / 16

Centralized Conferencing Framework

Centralized Conferencing Framework. by Chitra Agastya VOIP Security, Fall 2008 Prof. Henning Schulzrinne. XCON- Centralized Conferencing. Overview of XCON WG Floor Control and BFCP Conferencing Mechanisms Conference Object Conference Scheduling Conferencing Scenarios

brody
Download Presentation

Centralized Conferencing Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Centralized Conferencing Framework by Chitra Agastya VOIP Security, Fall 2008 Prof. Henning Schulzrinne

  2. XCON- Centralized Conferencing • Overview of XCON WG • Floor Control and BFCP • Conferencing Mechanisms • Conference Object • Conference Scheduling • Conferencing Scenarios • Security Considerations • References Contents

  3. XCON Overview • Scope limited to centralized conferences • Enable interoperability between different call signaling protocols • Independent of call set up protocol • Privacy, security and authorization are integral to the solution • Initial focus is on unicast media conferences Overview

  4. XCON Deliverables • Develop standard set of protocols for tightly coupled conferences • Provide mechanism for membership and authorization control • Provide mechanism to manipulate and describe media • Provide mechanism for notification of conference related events/changes • Provide a basic floor control protocol Overview

  5. Floor Control and BFCP • Floor is a shared resource in a conference • Floor control is temporary permission to access or manipulate the floor e.g. Access to whiteboard, who is to be heard? • Floor Control Operations Floor creation Floor request, granting, release • Optional feature for conferencing applications http://internetng.dit.upm.es/ponencias-jing/2005/SIP2.pdf

  6. Conference Control Server Floor Control Server Foci Notification Service Floor Control Client Conference Control Client Call Signaling Client Notification Client Conferencing Mechanism Logical representation of a conference instance Conferencing System Conference Object Maintains relationships with all participants Conference Object Notify subscribers about changes in conference state Conference Control Protocol SIP NOTIFY BFCP SIP Controls the state of a conference object Floor is a set of resource associated with a conference instance Conferencing Mechanism

  7. Conferencing Object Primary concept of XCON Framework Uniquely identified by XCON URI Uses the cloning tree concept Information in object defined using XML Conference Instance Conference Object Identifier Focus Conference Identifier Pr3 Conference Identifier ISUP Conference Client 1 Conference Client 2 Conference Client 3 Conference Identifier SIP Pr3 ISUP SIP Conferencing Object

  8. Pol icies Pol icies Pol icies Pol icies Pol icies Pol icies Pol icies Pol icies Pol icies Pol icies PARENT B CONF OBJECT CHILD 2 CONF OBJECT Child Conference Reservation Child Conference Reservation Child Conference Reservation Child Conference Reservation Conference Reservation CHILD 1 CONF OBJECT PARENT A CONF OBJECT Selected Conference Blueprint INDEPENDENT INDEPENDENT Conferencing Object – Cloning Tree • Parent enforceable Concept • Create standard templates for events that can be reused • Shares parent object’s policy and configuration • Explicit vs Implicit • Parent-child link need not be maintained Conferencing Object

  9. Conference Scheduling Conference reservation has a specified time Uses the “Internet Calendaring and Scheduling Core Object” Conference System Generic ICAL Resource Conference Instance Conference Objects Resource Scheduler Conference Control Server Request ICAL Conference Control Protocol Conferencing Client Recurring conferences? • iCal definition represents a series of recurring conference instances • Should support manipulation within a range of the series Conferencing Scheduling

  10. Conferencing Systems CCP Request <reserve, blueprintAConfObjID, confUserID> “Alice” Conference Control Server Conference Blueprint A Client Conference Reservation CCP Response <reservationConfObjID, confID> Conferencing Systems “Alice” Conferencing Systems CCP Request <blueprints> Conference Control Server Conference Blueprint(s) CCP Request <add, reservationConfObjID, confID,confUserID> “Alice” Client Conference Control Server Conference Reservation Client CCP Response <blueprintA, … blueprintZ, confUser ID> Active Conference CCP Response <activeConfObjID, confID> Conference Creation • Using a CCP request More flexibility in defining characteristics and capabilities Conferencing Scenarios

  11. Participant/Media Manipulations Using CCP, a client can affect its own state state of other participants state of resources Conferencing Systems Active Conference policies Conference Control Server CCP Request <Conf Object ID, Add, “Bob”> “Alice” “Alice” Notification Service NOTIFY <“Bob” =“added”> “Carol” “Bob” “Bob” NOTIFY <“Bob”=“added”> http://internetng.dit.upm.es/ponencias-jing/2005/SIP2.pdf

  12. Sidebar Manipulations Separate conference instance that exists within context of a parent Although viewed as independent, it cannot exist without a parent Internal Sidebar External Sidebar Conferencing Systems Conferencing Systems CCP Request <update, SideBarResvConfObjectID, confID, confUserID, Video=parent, Audio=sidebar> Conference Control Server CCP Request <createSideBar, activeConfObjectID, confUserID> Conference Object Identifier policies Active Conference Conference Control Server “Alice” “Alice” “Alice” CCP Response <SideBarResvConfObjectID, confID> CCP Response <activeSideConfObjectID, confID> “Bob” policies Active Conference Sidebar Conference Object Identifier Sidebar Conference Object Identifier Sidebar Conference Object Identifier “Carol” Sidebar Reservation Sidebar Reservation policies policies “Alice” Notification Server “Bob” “Bob” Notify <“Bob”=added> Conferencing Scenarios

  13. Other Scenarios Floor control using sidebars e.g. Q&A session in classroom session Whispering or private messages One time media targeted to a specific user Conference announcements and recordings e.g. Announcement to extend the audio bridge Observing and coaching e.g. Supervising a call Conferencing Scenarios

  14. Security Considerations • User authentication and authorization - call signaling protocol’s mechanism - Assigning passwords to specific users - Conference ID and PIN • Privacy of identity Hidden and Anonymous Users • Floor control security BFCP entities to implement TLS Security Considerations

  15. References • Requirements for Floor Control Protocol (RFC 4376) • Conferencing Scenarios (RFC 4597) • The Binary Floor Control Protocol (BFCP) (RFC4582) • Connection Establishment in the Binary Floor • Control Protocol (BFCP) (RFC 5018) • A Framework for Centralized Conferencing (RFC 5239) References

  16. Summary • XCON WG Focus and deliverables • Centralized Conferencing Mechanism/Components • Conference Object Cloning Tree • Conferencing Scenarios Participant/media/sidebar manipulations • Security Considerations User authorization and privacy Summary

More Related