Minutes from IETF 74 Mediactrl

March 26 2009 San Francisco

 

Working Group Home Page

Chairs
        Eric Burger <eburger@standardstrack.com>
        Spencer Dawkins <spencer@wonderhamster.org>

 

Notes taken by Bill VerSteeg

 

Topic

Draft

Time

Discussion Leader

Agenda bash

none

5 min

chairs

Status review

none - see mailing list

0 min

chairs

MIXER Framework - WGLC comments

http://tools.ietf.org/id/draft-ietf-mediactrl-mixer-control-package-05.txt

15 min

Scott McGlashan

Media Resource Broker Protocol

http://tools.ietf.org/id/draft-boulton-mediactrl-mrb-04.txt

60 min

Lorenzo Miniero

Call Flows

http://tools.ietf.org/id/draft-ietf-mediactrl-call-flows-00.txt

60 min

Lorenzo Miniero

Work plan for IETF 75 and shutdown

charter

10 min

chairs

 

Mixer Framework

·                     Need to clarify that <codec> attribute in <create_conference> puts a limit on the conference; i.e., <codec> drives, but does not replace, SDP negotiation

·                     Ready for RAI review of next revision

Media Resource Broker

OK to have both HTTP+XML and SIP+XML (control channel) for MRB?

·                     Yes, HTTP+XML for redirect/oracle; SIP+XML for transparent pool

·                     If we need notifications, we’ll need to use SIP+XML

·                     Might be a burden for tiny, embedded MRB, but the expectation is that no MRB would be tiny as they are an element of a large network deployment

·                     Consensus is to mandate both protocols

 

Need to be able to identify sessions; consensus is to add a session ID

 

Publishing interface: new package to consolidate elements from individual MS packages; not clear what the package would be

 

Accuracy of MRB resource availability: consensus is that physics dictates availability will never be exact due to timing issues, computed as opposed to reserved resource consumption (e.g., DSP’s with fixed # of streams versus GPU’s with %CPU availability), and licensing (e.g., even if lots of CPU and memory available, licensing or other configuration elements may restrict number of stream types).  Therefore, will have text in draft to highlight this situation and why we do not attempt to report exact resource availability. The reminder to the implementer is that reserving the resource by establishing a session is the only way to guarantee the resource is available.

 

The chairs will confirm on-list that people are actually going to use audit support for resource allocation.

 

Also, we need to make sure the text is clear that MEDIACTRL in general and this reporting in particular has no relation to predictive resource allocation.  An example of that is a conference bridge that allows for oversubscription.  The oversubscription occurs at the application layer in the AS; requests to the MS must be for the actual number of streams requested.

 

Alan Hawrylyshen will submit text describing security considerations for audit. Issues include scoping requests and hiding data, support for multi-tenant applications, and associating security policy and resource visibility to the requestor's credentials.

 

·                     Presentation of excellent Gin from chairs to Jon Peterson, outgoing RAI AD

 

What to report in audit: base data elements with extension elements.  MRB aggregates status from MS in pool.

 

What does "supporting a codec" mean? Codec support can be ambiguous (decode, transcode, pass-through, RTP packetize, etc).  Do we need this information?

 

Will a client poll the infrastructure to find a resource, or will it be pre-configured to use a specific device?  Will the MRB hide the details of the servers?  Today, clients are associated with devices that provide transcoding, etc. Rolling the clock forward, may need to dynamically find assets.  Will take this issue to the list.

 

Proposal to use HTTP+XML, as done with CCMP, for the consumer interface had consensus in the room.

 

Items not in packages: Info the MRB needs which MS will/may not provide, like resource reservation, downtimes

 

Possibly in packages: more granularity on conference requests; geo location preference of MS location; language-related info for announcements and ASR.

Mediactrl Call Flows

Consensus is we have a sufficient number of use cases, with the addition of having some security-related call flows (SRTP, TLS, unauthorized requests) included. Nice to have XCON-related flows, but will not have a normative reference to XCON documents.

 

Chairs need to speak with mmusic to find out future of draft-boulton-mmusic-sdp-control-package-attribute-03.

 

Lorenzo finished with the usual well-received publicly-accessible demo.

Next Steps

Mixer to IESG moves from April 2009 to May 2009.

MRB WGLC stays in June 2009.

MRB to IESG moves from June 2009 to July 2009.

Call Flows WGLC stays in August 2009.

Call Flows to IESG stays in September 2009.