1. Floor Control draft-camarillo-xcon-bfcp-00.txt Issue tracker at: http://s99.piuha.net/cgi-bin/roundup.cgi/floor-control Gonzalo.Camarillo@ericsson.com

2. Outline Requirements CPCP vs. SDP Floor IDs Transport Encoding Security Application-Layer Responses Privacy

3. Requirements draft-ietf-xcon-floor-control-req-00.txt Have been last called Waiting for a new revision to come up

4. Establishment Need to provide user name, conf ID, shared secret, and host URI obtained using CPCP –bfcp://1234:472@server34.example.com/4321 SDP Offer/Answer Should we support both mechanisms? m=control 9999 bfcp * a=uri: bfcp://1234:472@server34.example.com/432 1

5. Floor IDs How do clients learn which floor ID apply to which stream?

6. Transport Pure client/server protocol –No intermediaries TCP for now –SCTP may be added in the future Transport param –bfcp://5678:243@server45.example.com:20000/9876?transport=tcp NAPTR lookup if no transport param

7. Transport (cont.) Alternative –Rules to choose transport E.g., if no transport param, TCP is used –Only SRV lookups

8. Encoding Needs to be binary to meet requirements –TLVs –SUN RPCs

9. Security Client obtains user ID and shared secret at establishment time Adds a TLV that contains a hash of the messages and the shared secret Confidentiality, if needed, is achieved by using TLS

10. Floor Request Operation

11. Application-Layer Responses Only when needed –Add one between (4) and (5) ? –Actions if not received ?

12. Privacy Should we address privacy? –The identity of the floor requester/holder is not delivered to the other users and the chairs