Media Control Minutes - July 30, 2008 Taken by James Rafferty Chairs: Eric Burger Spencer Dawkins (Notes: Capture decisions or issues) Agenda Bash: Agenda accepted Status Review ============= Control Framework - Chris Boulton presenting The current document is: draft-ietf-mediactrl-sip-control-framework-03.txt Draft went through WGLC; RAI review from Ben; Main open issue is Security Section; need security expert - action item for chairs New version to be prepared directly after Dublin meeting. IVR RAI Comments - Scott McGlashan presenting Current version is the -00 control package draft-mediactrl-ivr-control-package-00.txt RAI expert review from Ben Campbell Editor has been making changes in response to comments IVR-200: request from Author for help in ASCII Art IVR-201: author proposal accepted IVR-202: remove "ndn"; MSCML had ndn, inherited from PacketCable; agreed to remove as national-specific IVR-203: XCON defines Codec type, but no other data supplied; any data needed; author recommends a field; agreed RAI comments: - Security needs beyond RFC 3023; proposal - add link to security section of framework document; other security issues? Response: Need to add meat into the section and add everything into text; Specifically, what are the security considerations for this document above and beyond the framework ASR Out of Scope - Ben questioned why ASR is out of scope; Should this be added to milestones View of chairs: VoiceXML covers 80% of Speech apps; get Media Control framework and 2 basic packages done; beyond that other uses could be considered in a re-chartered work group; Decision: No request from the room to address this (ASR) now. 4.2.1 "src" attribute: What URI schemes make sense here? Ben: What sort of URI would make sense, even if it is not specified; Decision: Need text on what sort of URI would make sense (even if not specific); need an error code for unsupported URI scheme 4.2.5.2 dtmf and timestamp attributes If multiple characters, what does timestamp mean? Answer: Last DTMF digit (completion of tone detection when it matched); agreed 4.3.1 behavior for prompt and record at same time is not defined; change how this is described so that it is clearer; this behavior will be described as "MAY" Discuss draft-mediactrl-mixer-control-package-00.txt = Scott McGlashan Mixer-001: should we define conferenceexit notification that conference exited (for example, no participants attached yet)? agreed Mixer-002 - Video Layouts - allow participants not providing a video input steam to conference to be displayed on layout (e.g., avatar case); support or leave for advanced mixer package; decision: out of scope Mixer-003 video layout - need ASCII pictures of the layouts. Mary volunteered to help Mixer-004 conference audit - more conf info needed? - Yes, current active layout Mixer-005 participants - Is this the right term? What to call connection endpoints?; participants is OK Next Draft (-01) will address issues in -00 editor's notes; will be prepared by author Chair: Encourages that WG participants offer comments on WG documents prior to WGLC Implementation reports - Presented by Lorenzo Miniero - Includes an AS (SIP Servlet) and MS - Framework related comments: Use of error codes in the framework is still sometimes unclear - From-to tag issue IVR - If repeatCount (overwrite or append); comments have been sent to the mailing list earlier today. Mixer - if each conf has fixed layout, that will help. His team has prepared a call flows draft - invididual contrib. Should it be a WG item? Chair: suggests it be an individual contribution Mary: Call flow documents are important; she'd think it should be normative; concern from chair about contradictions between normative docs and call flows Comments from floor: If the draft is important, make it a WG item Keith: 3GPP would not look for flows from IETF, but rather normative documents Chair: Should the call flow document be added to the charter? Roni: The packages documents are ahead of the call flows Martin: He finds the document valuable, as a tool to explain to the eventual implementers. Keith: What would the reason be to add: if there is a need for the document and the WG will work on it? Chair: Hum on objecting to adding it to the charter? Nobody objected Chair: Who in the WG will review the call flows document? Several hands were raised.? Roni: Concern that the call flows need to be correct and often will vary from the specs Comments: If call flows aren't created, then vendors will create them anyway with likely interop consequences. Christer: Call flows are good for talking with customers, but no substitute for the normative document. If contradiction, go back to normative document. Keith: is the goal to produce for sample call flows or implementation agreements for interop (torture tests) Names of call flow reviewers: Chris, Scott, Martin, Mary, Janet Gunn, and several others Also Presented by Scott M. HP Implementation ? Framework, IVR and Mixer packages; also VoiceXML support Many issues discovered and have been fed back Would like to start doing interop ? Planning for Broker Protocol - presented by Chris Boulton - -02 is the current draft; individual contribution; there is a? WG milestone - Author says that they need to refresh the document and add new material. - Should this draft become a WG item Discussion: Keith notes that 3GPP will be more likely to reference MRB work if it is more mature; Rel 8 (tight), potentially Rel 9?? Need to provide information to 3GPP about the Mediactrl MRB work? (not yet) Decision: People asked to read the draft and chairs will poll WG by August 15th on whether to make WG item Planning for interim/interop event - Chairs Need an interim meeting? Interop event?? Co-locate?? Christer: 3GPP CT1 meeting in October; potential to get participation Looks like 4 implementation so far.?? Dan York comment: why not do at SIPit? Comment: Looks like 3GPP will likely mandate the Mediactrl framework and packages for MRFC control; Result: Take the planning for interim and interop to the list. Work Plan for IETF 73 Any changes to milestones? Proposed Framework to IESG - August IVR control protocol WGLC - September Nov 2008 IVR to IESG Jan 2009 Mixer Control Protocol to WGLC Feb 2009 Mixer to IESG Feb 2009 Broker Protocol WGLC Mar 2009 Broker protocol to IESG No objections to the changes as above presented by the chairs.