draft-miniero-bfcp-control-package-00

Alessandro AmiranteTobia Castaldi

Lorenzo MinieroSimon Pietro Romano

(University of Napoli Federico II)

draft-miniero-bfcp-control-package-00 2

A Control Package for BFCP

• Individual contribution to deal with floor control in the MCCF– When FCS co-located with the MS– AS co-located with the FCS doesn’t need this

• No explicit milestone for this in the charter, but it is related to the mixing stuff– Parallel/complementary development with the

mixing work (e.g. find additional requirements)

draft-miniero-bfcp-control-package-00 3

Requirements

• Need to provide the AS with means to configure and manage the moderation of a MS conference instance– Is conferencing the only target? (e.g. Push To Talk)

• Need mapping of media labels with floors– Which mixed streams are available?– How to enforce decisions?

• Need to support RFC4583– Is an explicit “add participant” needed?

• Need an event notification mechanism– Which events should be triggered? (apart from

‘granted/not granted anymore’…)

draft-miniero-bfcp-control-package-00 4

RFC4583 Support

• RFC4583 specifies a way to negotiate a BFCP connection in SIP/SDP (COMEDIA)

• Also provides clients with needed info (FCS transport address, BFCP-related identifiers, etc.)

• However, it assumes the FCS is already aware of the participant– Issue in signaling (INVITE precedes <join>)– Proper synchronization between 3PCC and Control

Channel is needed

draft-miniero-bfcp-control-package-00 5

RFC4583/3PCC v1

draft-miniero-bfcp-control-package-00 6

RFC4583/3PCC v2

draft-miniero-bfcp-control-package-00 7

Final Remarks

• Is the draft on the right track?– Are more directives/events needed?

• Which signaling pattern is to be preferred?• Should it be an extension of the mixing

package(s), or a package on its own?– Extension mechanism still undefined

• May extend optional packages

– Conferencing might not be the only target

• Suggestions? Comments?