1 / 34

MEDIACTRL – IETF 73

MEDIACTRL – IETF 73. Eric Burger eburger@standardstrack.com Spencer Dawkins spencer@wonderhamster.org. Remote Logistics. mp3 Feed: SPEAK INTO THE MICROPHONE!!! http://videolab.uoregon.edu/events/ietf/ietf732.m3u Jabber Server: jabber.ietf.org Room: mediactrl

mikel
Download Presentation

MEDIACTRL – IETF 73

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. MEDIACTRL – IETF 73 Eric Burger eburger@standardstrack.com Spencer Dawkins spencer@wonderhamster.org IETF 73 - Minneapolis, USA

  2. Remote Logistics • mp3 Feed: SPEAK INTO THE MICROPHONE!!! • http://videolab.uoregon.edu/events/ietf/ietf732.m3u • Jabber • Server: jabber.ietf.org • Room: mediactrl • Logs: http://www.ietf.org/meetings/ietf-logs/mediactrl/ • Meeting Materials (Presentations, Agenda, etc.) • https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=73 • Supplemental Web Site • http://www.standardstrack.com/ietf/mediactrl IETF 73 - Minneapolis, USA

  3. Scribes and Transcribes • Jabber Scribe • Dan York • Note Takers IETF 73 - Minneapolis, USA

  4. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: the IETF plenary session, any IETF working group or portion thereof, the IESG or any member thereof on behalf of the IESG, the IAB or any member thereof on behalf of the IAB, any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3978 (and RFC 4748) for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. IETF 73 - Minneapolis, USA

  5. Agenda IETF 73 - Minneapolis, USA

  6. IVR Control Package Scott McGlashan, Tim Melanchuk, Chris Boulton draft-ietf-mediactrl-ivr-control-package-02 IETF 73 - Minneapolis, USA

  7. Open Issue: ‘fallback video’ • Request for new functionality: Add <media> child of <media> so that if parent <media> fails, then child is played • <media> fallback a la VoiceXML • Simplifies AS app development • But some objections • AS can handle most cases for fallback proactively (by audit of MS codecs/formats and B2B with UA) or reactively (gets an error, makes a decision) • Some complexity introduced in spec and implementation • Feature creep? • Decision please! IETF 73 - Minneapolis, USA

  8. Open Issue: Conformance Language • Issue with conformance language – too many RECOMMENDEDs • Proposed strategy: converted RECOMMENDEDs to MUSTs/MAYs • MAY: support playing multiple dialogs on same connection/conference • MUST: support for time, date and digits <variable> • MUST: support parallel playback of different media where mixing is not required • MUST: support playback of same media within a <seq> • MUST: support parallel <record> of different media • Any objections? IETF 73 - Minneapolis, USA

  9. Open Issue: Security review • Do we need an WG security review for IVR package? • If so, volunteer please • Same review could cover mixer package • Dan York already raised an issue with the case where another AS can take over management of dialogs created by an initiating AS • Relates to security policy described in Control Channel Framework • Any changes required? IETF 73 - Minneapolis, USA

  10. Next Version -03 • Address issues identified during WGLC • Nits, clarifications, etc • Open issues: • ‘fallback video’ • Conformance language • Security review IETF 73 - Minneapolis, USA

  11. Mixer Control Package Tim Melanchuk, Scott McGlashan, Chris Boulton draft-ietf-mediactrl-mixer-control-package-02 IETF 73 - Minneapolis, USA

  12. Next version: -03 • Address issues identified during WGLC • Nits, clarifications, etc • Fix <stream> issue with <volume> • Open issues: • Security review (shared with IVR package) • Really no open issues? IETF 73 - Minneapolis, USA

  13. Implementation reports Lorenzo Miniero IETF 73 - Minneapolis, USA

  14. A few words about the call flows... • draft-miniero-mediactrl-escs-03 • Currently reflects n-1 specs • Nothing much has changed anyway... • Will catchup in next version • State diagrams are back in the document • A lot of rewriting • A new scenario (phone call recording)‏ • Most of the scenarios are now detailed • Clarified that 3PCC examples are just examples IETF 73 - Minneapolis, USA

  15. Work in progress in Naples • Open source updated prototypereleased just a couple of weeks ago • http://mediactrl.sourceforge.net/ • Both the MS and the AS (including a full app)‏ • Used for all of the interoperability tests • Online video-enabled demo released Monday • sip:{mediactrlDemo,1234}@meetecho.com:5080 • A lot of scenarios from the draft are available • AS↔MS on http://www.meetecho.com/mediactrl IETF 73 - Minneapolis, USA

  16. Interoperability tests • So far involved three implementations • University of Napoli (AS)‏ • HP OCMP (MS)‏ • Dialogic (PoC MS)‏ • Only audio was involved • Future tests • Reversing the roles • Involve video • More implementations, hopefully IETF 73 - Minneapolis, USA

  17. UniNA AS ↔ HP OCMP MS (1)‏ • Major issue concerning the termination of PDUs with payloads (Content-Length)‏ • ABNF in the document said (i)‏ control-request = control-req-start *( headers ) CRLF [control-content] control-content = data CRLF data = *OCTET • UniNA incorrectly implemented it as (ii)‏ control-request = control-req-start *( headers ) CRLF [control-content] control-content = *OCTET • Proposed change in the framework spec • Use (ii) to align to other text-based protocols (e.g. SIP/HTTP/etc)‏ IETF 73 - Minneapolis, USA

  18. UniNA AS ↔ HP OCMP MS (2)‏ • A few minor issues • Content-Type in requests was not always correctly set • (e.g. “msc-ivr” instead of “msc-ivr/1.0”)‏ • AS didn't wait for the ACK to address connections • MS couldn't validate connectionid • Some leftovers (e.g. “mix-type” instead of “type”)‏ • Fixing the issues... • ... the audio application was successful • Will try again involving video as well IETF 73 - Minneapolis, USA

  19. UniNA AS ↔ Dialogic PoC MS (1)‏ • An SDP-related issue • MS didn't support the * in COMEDIA negotiation m=application 5757 TCP/CFW * a=connection:new a=setup:active a=cfw-id:5feb6486792a a=ctrl-package:msc-ivr/1.0 a=ctrl-package:msc-mixer/1.0 • Other specs use it (e.g. RFC4583 for BFCP)‏ • Format is optional in SDP... • Should implementations support it anyway? IETF 73 - Minneapolis, USA

  20. UniNA AS ↔ Dialogic PoC MS (2)‏ • A few minor issues • AS didn't wait for the ACK to address connections • MS couldn't validate connectionid • AS didn't tear down SIP control dialog when leaving • What should happen when the TCP connection alone is destroyed? • our MS hangs up the SIP dialog which originated it... • ... but a reINVITE with a “a:connection=new” might arrive • Fixing the issues... • ... the tests were fine at the framework level and at the IVR package level (<prompt> and <collect>)‏ IETF 73 - Minneapolis, USA

  21. Current implementations • Few implementations currently available • University of Napoli • HP • Dialogic • Broadsoft (?)‏ • Other implementations in progress or planned? IETF 73 - Minneapolis, USA

  22. Interop event • An Interop event (formal/informal) would be quite useful • IETF interim in Malta in January • MEDIACTRL will meet there • Scott and Lorenzo will likely be there as well • Could this be a suitable venue? IETF 73 - Minneapolis, USA

  23. Questions? http://mediactrl.sourceforge.net/ http://www.comics.unina.it/ http://www.meetecho.com/ IETF 73 - Minneapolis, USA

  24. MRB Chris Boulton draft-boulton-mediactrl-mrb-03 IETF 73 - Minneapolis, USA

  25. History • Changes in 03 version of the draft • Consumer interface now a basic HTTP+XML interface • Fleshed out early skeleton version of Consumer XML schema • Need to include detail in next version with group input • Publishing interface now proposes the use of a Control package IETF 73 - Minneapolis

  26. Goals!!!! • Good group discussion on viability of two proposed interfaces • Fulfil complete ‘toolkit’ for all deployment models covered in document • Conclude on alternatives TODAY if the group is not happy • Draft at appropriate stage to start filling in the detail for Malta interim • Will have skeleton version ready in preparation IETF 73 - Minneapolis

  27. Full Toolkit Usage IETF 73 - Minneapolis

  28. Consumer Interface - Discussion • Current Proposal – HTTP+xml interface using underlying protocol to pass appropriate requests/responses/errors • <mediaResourceRequest/> • Containing optional selection information • <mediaResourceResponse/> • Containing response to request • <mediaResourceError/> • Containing appropriate error information • Are we happy? Alternatives? IETF 73 - Minneapolis

  29. Publishing Interface - Discussion • Current proposal – Control Framework package for publication of MRB info • Use of Control Framework subscription /notification mechanism • Control Framework already supported by MS for other packages (IVR, Mixer) + also uses some basic auditing • Use Framework core capabilities (negotiation/security/SIP routing etc.) • Are we happy? Alternatives? IETF 73 - Minneapolis

  30. Next Steps…. • Use discussion feedback and decisions on interfaces for detailed next version (by Malta) • Craft new versions of interfaces based on community feedback • Work Group Item Discussion… IETF 73 - Minneapolis

  31. Interoperability Testing andInterim Discussion IETF 73 - Minneapolis, USA

  32. Malta • Grand interim meeting • Malta (Europe) • http://trac.tools.ietf.org/2009/jan-large-interim/ • Alternatives if Malta melts down? • Interoperability Event? • Malta, 19th, before meeting • Malta, 20th, after meeting but do not lose weekend prior • SIPit 24, May 18-24, Akihabara (Tokyo) • Not mutually exclusive IETF 73 - Minneapolis, USA

  33. Goals and Milestones * As agreed after IETF 71; never formally updated charter dates IETF 73 - Minneapolis, USA

  34. Thank You(and see you in Malta) MEDIACTRL IETF 73 - Minneapolis, USA

More Related