MEDIACTRL IETF 69 Meeting Minutes


Chairs:         Eric Burger            <eburger@bea.com>
                   Spencer Dawkins   <spencer@mcsr-labs.org>

With thanks to

Scribes:      Chris Boulton          <cboulton@ubiquity.net>
                   Mary Barnes          <mary.barnes@nortel.com>

MediaCtrl Requirements - Presented by Roni Even

- Result of the merging of two documents - draft-dolly-xcon-mediacntrlframe-03.txt and draft-even-media-server-req-02.txt.

- Probably two-thirds of attendees have read this draft, by show of hands.

- Have been some suggestions about changes to document structure, Roni will look at this.

- CONSENSUS -From mailing list that REQ-MCP-31/32 is definitely in scope.

- CONSENSUS IN ROOM - Capturing speech to replay later, etc. is in scope for these requirements.

- CONSENSUS IN ROOM - This document will be adopted as a work group item, and the next version will be submitted as draft-ietf-mediactrl-*.

MediaCtrl Framework Document - Lorenzo Miniero

- Chair thanks to MediaCtrl Framework design team members for their effort, and Xiao Wang for review to the mailing list before IETF 69.

- This document will not discuss reliability at the media control level.

- Tom Taylor - MSF – framework that includes MRB, SIP interface, etc – Is QoS in scope? Which component of the architecture is responsible for invoking quality-of-service – application server and media server guys both trying to toss this responsibility somewhere else. Where is QoS handled?

- Christer Holmberg/Chris Boulton - Need to define what QoS means in this context before making decisions.

- Considerable discussion about this point.

- CONSENSUS IN ROOM - That QoS should NOT be included in this document.

- Christer Holmberg - Document definitely needs more refinement - inclusion + deletion of certain concepts.

- Mary Barnes - Is this informational OR standards track document?

- Jon Peterson (AD) If document contains specific implementation detail - should be standards track.

- CONSENSUS IN ROOM -  that document should be informational.

- CONSENSUS IN ROOM - Should this be a work group item - Strong consensus - YES.

Media Resource Broker - Chris Boulton

More than half the participants in the room had read this draft, by show of hands.

(notes by Mary Barnes since notetaker was presenting)

- Clarification that this is not resource management.

- Discussion of appropriate models, with no clear consensus on which are most appropriate. Different views on where the MRB resides

- CONSENSUS IN ROOM - Document is not ready to be a WG document (even editor agrees).

Draft-burke-xml

- CONSENSUS IN ROOM - Adopt as a Work Group item - of those who have read the document - Should be adopted as WG, but only five people in the room had read the document, by show of hands.

NEXT STEPS

- Chairs will Last Call requirements immediately.

- Chairs will Last Call the edited revision of Framework.

- Chairs - MRB isn’t ready to consider for Last Call yet.

- Chairs - SIP Control Framework (draft-sip-control-framework) 

- Just under half the room had read some version of this draft, by show of hands.

- ACTION - Take to the list - will it be adopted as a work item?

- Chris + Chairs - Probably will require other WG interaction/expert review (SIP + MMUSIC).

- Mary - Might be good use for RAI review team.

- Chairs - MRB document could be WGLCed in October 2008.

- Chairs will solicit volunteers for two design teams (alternative is to hold interim meeting, prefer not to plan for interim meeting at this time.

- Post-meeting discussions – 3GPP document (24.880) – Spencer to chase this.