1 / 19

XCON BOF

XCON BOF. IETF 57 Vienna, Austria July 15, 2003. Administriva. Conscripting a Scribe Note Well announcement (Read Section 10 of RFC 2026) Blue Sheets. Agenda. Welcome and Agenda Bashing (5 min) Problem Statement/Scope Overview (10 min) Charter Discussion (15 min)

jbose
Download Presentation

XCON BOF

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. XCON BOF IETF 57 Vienna, Austria July 15, 2003

  2. Administriva • Conscripting a Scribe • Note Well announcement (Read Section 10 of RFC 2026) • Blue Sheets

  3. Agenda • Welcome and Agenda Bashing (5 min) • Problem Statement/Scope Overview (10 min) • Charter Discussion (15 min) • Open Discussion (30 min)

  4. Problem Statement/Scope • Defining protocols necessary for participants to control centralized conferences: • Conference Policy Control • Two objects and two sets of operations on: • General policy and membership • Media policy • Floor Control • Motivated by SIP conferencing, but will be independent of call setup protocol. • Protocols developed will not be SIP or SIP extensions

  5. Conference Policy Control • Conference Lifespan • Who can participate (permissions) • What each participant can do (roles) • Notification of conference membership (roster) • Related Documents: • draft-koskelainen-xcon-cpcp-reqs-00.txt • draft-koskelainen-xcon-xcap-cpcp-usage-00.txt • draft-levin-xcon-cpcp-00.txt

  6. Media Policy Control • Defines how media is combined, selected, and modified in a conference • Multiple media types: audio, video, IM, etc. • Result of floor control is an input • Protocol defines how a topology is created, retrieved, and manipulated • Related Documents: • draft-even-xcon-media-policy-requirements-00.txt • draft-mahy-xcon-media-policy-control-00.txt

  7. Floor Control • Floor Definition • Temporary permission for a conference participant to access or manipulate a specific shared resource or group of resources. • Examples include: • Who gets to be heard or be seen by all participants • Who can control a shared whiteboard pointer • Floor Control Protocol Operations • Floor creation (related to media policy) • Floor requesting, granting, and releasing • Related Document: • draft-koskelainen-xcon-floor-control-req-00.txt

  8. Example Use Scenario • User is invited to a conference (dials in) and learns they are in a conference • Subscribes to the conference package and learns the roster and the conference policy URIs • Uses media policy and discovers that the conference is a "lecture" with audio and video and as a result enables video to fully participate in the conference. • Uses conference policy to establish a sidebar (sub-conference) with another participant • Uses floor control to request the floor to ask a question • draft-even-xcon-conference-scenarios-00.txt

  9. Example Topology: Central Control and Mixing Focus Out Of Scope Media Mixer Media Call Control

  10. Example Topology: Central Control, Full-Mesh Media Focus Media Call Control

  11. Example Topology: Cascaded Conferences User 1 User 4 Conference A Conference B Focus Focus User 2 Media Mixer Media Mixer User 3 Media Call Control

  12. Relation to Other WGs • SIPPING • MMUSIC • AVT • SIP • W3C SMIL

  13. Charter (1/4): Deliverables • A mechanism for membership and authorization control • A mechanism to manipulate and describe media "layout" or "topology" for multiple media types • A mechanism for notification of conference related events/changes (policy/floor events) • A basic floor control protocol

  14. Charter (2/4): NON-Deliverables • Voting • Multicast media (due to security concerns) • Fully distributed conferences • Loosely-coupled conferences (no central point of control) • Far-end device control • Protocol used between the conference controller and the mixer(s) • Capabilities negotiation of the mixer(s) • Master-slave cascaded conferences

  15. Charter (3/4): External Inputs • draft-ietf-sipping-conferencing-requirements-00.txt • draft-ietf-sipping-conferencing-framework-00.txt • draft-ietf-sipping-cc-conferencing-01.txt • draft-ietf-sipping-cc-framework-02.txt • draft-ietf-sipping-conference-package-01.txt(get copy from http://ee.wustl.edu/~alan/sip-conf/)

  16. Charter (4/4): Proposed Items • draft-even-xcon-conference-scenarios-00.txt • draft-koskelainen-xcon-cpcp-reqs-00.txt • draft-even-xcon-media-policy-requirements-00.txt • draft-koskelainen-xcon-floor-control-req-00.txt • draft-koskelainen-xcon-xcap-cpcp-usage-00.txt • draft-levin-xcon-cpcp-00.txt • draft-mahy-xcon-media-policy-control-00.txt

  17. Next Steps/Issues • Consensus/Approval for Charter • Finalize Conference Policy Requirements • Decide on protocol • XCAP/SOAP/XML-RPC • Continue work on Media Policy • Create policy notification packages • Define interface between Media Policy and Floor Control

  18. Open Discussion

  19. Further Info Mailing List: http://www.softarmor.com/mailman/listinfo/xcon SUBSCRIBE to xcon-request@softarmor.com BOF Chairs: Alan Johnston (alan.johnston@mci.com) Adam Roach (adam@dynamicsoft.com)

More Related