1. XCON Working Group IETF 61 Washington, DC

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

3. Agenda, Day 1 (Monday) TimeLengthDiscussion LeaderTopic 1930 - 19355 minutesChairsAgenda Bash 1935 - 194510 minutesChairsStatus Update 1945 - 202035 minutesMary BarnesConferencing Framework Document 2020 - 205030 minutesOrit LevinConferencing Data Model 2050 - 211020 minutesChairsDiscussion 2110 - 220050 minutesHisham KhartabilConference Policy

4. Agenda, Day 2 (Friday) TimeLengthDiscussion LeaderTopic 0900 - 094040 minutesGonzalo CamarilloFloor Control / Floor Event Package 0940 - 104060 minutesAlan JohnstonMedia Policy 1100 – 113050 minutesChairsAdditional Discussion, if necessary

5. Conference Scenarios No open issues remaining Will WGLC next week

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

7. 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

8. 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

9. 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

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

11. 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.

12. Framework Changes

13. 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

14. 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

15. 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

16. 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