Last Modified: 2005-06-29
Oct 03 | Submit Requirements for Membership Manipulation for publication as Informational | |
Oct 03 | Submit Requirements for Basic Floor Control for publication as Informational | |
Nov 03 | Submit Conferencing Scenarios document for publication as Informational | |
Nov 03 | Submit Use Cases for Media Topology Control for publication as Informational | |
Dec 03 | Submit Requirements for Media Topology Control for publication as Informational | |
Feb 04 | Submit Basic Floor Control Protocol for publication as PS | |
Mar 04 | Submit Notification Event package extension for conference related events for publication as PS | |
May 04 | Submit Membership Manipulation Protocol for publication as PS | |
Jul 04 | Submit Protocol for Media Topology Control for publication |
IETF63 XCON Meeting
Notes by Brian Rosen No agenda bash Revised milestones presented to be proposed to AD All SIPPING conferencing documents are complete Only one draft moveing what can be done? HS - Need some simpler generic mechanisms, limit scope CJ - Agree on framework, then work on mechanism Mary Barnes presents updates to Framework Several updates (2 revs since ietf62) Open Issues State and Policy Manipulation Protocol: 4 on the tables, SOAP added as a 5th Need more work on conference policies Need more explicit distinctions between templates and blueprints Need to align framework with SIPPING conferencing stuff More work to do on Floor Control and Examples New work items: URI schemas for identifiers, mechanisms for conference policies, possible floor control based on tempates HS - Can we leverage presence work on policies MB - Does that imply xcap HS - No Protocol choice issues: No clear choice based on several criteria RM - Can't we cross some off the list now? HS - Ditch Netconf (in favor of SOAP, see later) RM - Ditch CPCP CJ - SOAP is like saying ASCII ?? - What happened to using requirements MB - They all meet the requirements ?? - What are the names of logical entities? Functional model? MB - we have them CJ - get people to commit to review doc <commitments from 6 people to do this> RE - How about resolving open issues MB - Deciding protocol would help a lot, reviewers will look at policy text again Henning Schultzrinne presents on SOAP based protocol No transactions Map to existing data structs Avoid 2 level mechanism (dial out user -> get/set/delete) Re-use well known RPC mechanism Use inheritance (no templates) Affinity to CCCP, but further simplified For adding users, requests can fail partially CJ - Are you adding them to the dial out list (which always works) or asking them to be called right now (which might fail for some HS - Oh, maybe it's not an issue Start/stop time missing, Conference media mixing, can we do something simple now? RM - Cullen came up with something that works, use it AR - How does this work for templates at all? HS - schema has an extension mechanism, extend for template CJ - Extend the WSDL? HS - Yes ?? - What are the names of the entities? Comment, merging is hard, adding lots of users is easy HS - "Conference Arithmetic" is very hard. Don't think we try to do that CJ - Agree don't need conference arithmetic, but need to move someone from one conf to another RE - Need to change client/server roles to enable things like this GC - Need to syncronize with sipping consent framework Chairs: Need to have discussion on mail list and try to knock down to one. ------- Key: AR - Adam Roach CJ - Cullen Jennings GC - Gonzalo Camarillo HS - Henning Schulzrinne MB - Mary Barnes RE - Roni Evan RM - Rohan Mahy |