XCON Working Group IETF 61 Washington, DC

The Normal Stuff NOTE WELL statement Minute Taker Jabber Scribe Blue Sheets

Agenda, Day 1 (Monday) TimeLengthDiscussion LeaderTopic minutesChairsAgenda Bash minutesChairsStatus Update minutesMary BarnesConferencing Framework Document minutesOrit LevinConferencing Data Model minutesChairsDiscussion minutesHisham KhartabilConference Policy

Agenda, Day 2 (Friday) TimeLengthDiscussion LeaderTopic minutesGonzalo CamarilloFloor Control / Floor Event Package minutesAlan JohnstonMedia Policy 1100 – minutesChairsAdditional Discussion, if necessary

Conference Scenarios No open issues remaining Will WGLC next week

Framework Document First draft now available Split from SIP Conference framework Will be presented momentarily

Media Policy Using conference scenarios document for use cases Media control draft paused on templates document Templates document now available; will be discussed Friday Likely to be impacted by framework changes discussion

Conference Policy Requirements document ready to be sent to IESG Speci  cation split into three documents; will be discussed today Likely to be impacted by framework changes discussion

Noti  cation Event Package On charter as deliverable, not yet started SIPPING Conference Package in WGLC XCON will extend Conference Package with –Media details –Control details –Other TBD information

Floor Control Requirements document ready to be sent to IESG New document available; will be discussed on Friday

Miscellaneous CCCP: New proposal to split conference state management from conference policy management. Principles discussed today, details on Friday Need examples/call  ow document as protocols are developed (volunteers?) Sidebars document: will likely be split up and incorporated into framework and examples/call  ows documents.

Framework Changes

Proposed Change #1: “Policy” Split Conference “Policy” has two parts: Template –Information used by focus to create the initial conference state –Can be system de  ned and used by multiple conferences –Is not affected by state changes during a conference Authorization Rules for state changes

Proposed Change #2: Media Combined with “Policy” and State Media information is neither separate from Conference “Policy,” nor from Conference State Media information spans across Conference “Policy” (i.e. Template and Rules) and Conference State

Proposed Change #3: State Directly Manipulated Operations to change conference state are performed directly on state, not indirectly by policy changes Conference Control Protocol operates directly on the conference state instance

Proposed Change #4: Conference State Based on Event Package Conference Control Protocol operates directly on the conference state instance, de  ned by the Conference Package and to be extended by XCON