Floor Control draft-camarillo-xcon-bfcp-00.txt Issue tracker at:

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

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

Establishment Need to provide user name, conf ID, shared secret, and host URI obtained using CPCP SDP Offer/Answer Should we support both mechanisms? m=control 9999 bfcp * a=uri: 1

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

Transport Pure client/server protocol –No intermediaries TCP for now –SCTP may be added in the future Transport param NAPTR lookup if no transport param

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

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

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

Floor Request Operation

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

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