MEDIACTRL – IETF 76 Monday 17:40 – 19:30

Note well

No agenda comments – dramatic change in the agenda. Call flows first, updated call flows to summarize issues from the actual implementation experience.

Call Flows

Lorenzo Miniero presented latest changes: m-line, connection-id token - drafts were updated accordingly.

Flow updates - discussion on the mailing list.

MRB – package and considerations. Changes were implemented but not all of them.

Some issues with protocol will be solved in the next draft. MRB is a new package. MRB is A/S that can negotiate this new package.

Call flows will be update after development of the consumer interface.

No questions for call flows.

Spencer – chairs reviewed the draft. People made a changes based on the feedback. Using tcp as a transport. Changes made to Control Framework, IVR and Mixer framework were updated. MRB and call flows will be updated later.

IVR & Mixer

Eric Burger – anything for IVR and Mixer. No comments

MRB

Lorenzo Miniero. Want to achieve complete definition of the interfaces. Working on the consumer interface. Waiting for the feedback from the mailing list.

Publish interface: defined the control package. Already implemented. Question from Lorenzo Miniero: only generic subscription. Is always complete information required?

Question. Who read the draft? Couple of hands (chairs mostly)

Eric Burger: Who will build MRB? Alan Johnson: not sure

Comments from Jabber – MBR does not need to filter events

Question from Jabber – what are the options? Leave it as is? Spencer – we will not add anything without requirements from the group.

Filters are not needed from the publishing interface. Lorenzo Miniero – might be useful.

Eric Burger to Chris Boulton from the chat room – any opinions?

Ability to not receive all information can be useful.

Eric Burger: complex syntax will be required

Eric Burger: Chris Boulton says nice to have (filters) but happy to move on if no desire from the group. Agreed by the group

Lorenzo Miniero: it is a technical question for the future discussions

Lorenzo Miniero. What is currently missing in the publisher protocol.

Mixing-modes – audio and video.

Is it OK to support for video only for layout? Default layouts? Any questions?

Spencer – any reason not to reuse mixer package?

Roni Even: why not to do the same? it is the same resource as the mixer. Not supposed to be different.

Everybody agreed to reuse.

<Supported-tones> element.

Media server to support different characteristics of the tones (different countries etc.). Who has expertise?

Eric Burger: We need to find volunteer with expertise. Supporting country specific tones is mandatory requirement. Will keep it open (will not be addressed). Will be asked on the list for the expertise.

<asr-tts-support>

Which languages? Expert volunteer? ISO 639-1 codes proposed?

Chairs: right thing to do is to support ISO 639-1. Separate ASR&TTs languages sets.

<media-server-location>

Country/State codes proposed. Need volunteer?

Need finer support (civic address path). Like in Geopriv for location object (for reuse). Chris Boulton asked : who is the contact. Robert.

<encryption>

Is MS supports encryption. Is sufficient to indicate support for SRTP (bool). Or actual keying mechanism.

Eric Burger: anybody cares? Silence

Spencer: cost of doing simple indicator is small. Or we need to plan for the date when it will be wrong answer? SRTP as intermediate solution for foreseeable future?

Jon: SRTP, sdp – no provisioning there as well.

Eric Burger – for simplicity we will say yes.

Spencer – we not should be more specific then underlying protocol.

Decided for simple solution (bool)

Consumer Interface

Publish interface as input.

What is missing?

Consumer interface with Requires and Optional elements for query.

Do everybody agree?

Chris Boulton says – approach looks good

Everybody agree.

Required packages

Is it OK? Do we need more information.

No objections from the room

<session-info>

Provides optional sessional information. Lorenzo Miniero recommends to add it

Spencer: it is mandatory to support session management interface.

Agreement in the room

<Required-ivr-session>

Is it useful? Do we need more information?

Eric Burger: question to the manufactures?

Roni – no problem with audio codecs for influencing capacity

Group agrees

<Required file format>

Client asking for specific client format. Is it OK?

Group agrees

<required-dtmf-type>

Group agrees

<required-tones>

Depends on the decision on publish interface. It will be the same decision

<required-asr-tts>

As publisher interface as well

<required-vxml>

Group agrees

<required-location>

As in publisher interface element

<required-encryption>

Same (boolean)

<application-data>

Application data to supply application data.

Agreed

<required-max-prepared-duration>

Agreed

<Required-stream-mode>

Agreed

<requires-mixes>

Like for IVR session as well.

Spencer: The idea is it all possible combinations of the codecs or only codecs list?

Is it one-dimension or multi-dimensional? Which audio codecs with which video codecs?

Eric Burger: With todays processing capacity no need to such combinations

Agreed for one-dimensional list without any combinations

Chris Boulton agreed as well

<required-mix-mode>

As with publisher interface as well

Spencer: For the publisher interface than they should match and not one of each

Agreed

Question Why not put all elements under <required> element and not part of the name.

These elements will be exactly same if it Publish and Consumer. There will be specific elements for the Consumer Interface

Agreed

Next steps:

Accumulate feedback for the consumer interface. Next version of MRB will have consolidated version of the publisher interface.

No more questions

Eric Burger: we have to be done!

Chair slides (slide 11)

Spencer: red dates is bad (delays). Need to go forward. Mixer going to IESG.

Next items WGLC (broker protocol). Call flows are last

Eric Burger: suggestion if no interest in MRB, can we drop it and close the working group

Spencer: in order to justify working group more then on person need to work on it

Eric Burger: anybody here care? No hands. Chris Boulton and Lorenzo Miniero care.

Document can be ready in a few months with the right feedback.

Eric Burger: if we can done it quickly, lets finish it.

Spencer: Discussion back to working group on mailing list. Two more revision cycles on this document.

Chris Boulton claims two weeks.

Spencer: revision before Thanks Giving, WGLC. agreed

Chris Boulton in jabber room: can be done with help on location stuff

Spencer: will drop tones if no expertise will be available.

Agreed to get it ready for WGLC before Thanks Giving

Mixer s – December 2009

Broker – WGLC December 2009

Broker Protocol – IESG February 2010

Call Flows – WGLC Jan 2010

Call Flows – IESG Feb 2010

Chairs requested reviewers.

System Adaptations

Zhipeng Zhou– Huawei

Requirement 1: Dynamic Bandwidth allocation

Requirement 2: Dynamic Media Format allocations

Requirement 3: Dynamic adaption to terminals

Solution Server adaptation: media server should have transcoding capabilities

Eric Burger: Can anybody help to articulate the problem?

Can it be moved to Dispatch?