110 likes | 287 Views
The Binary Floor Control Protocol (BFCP) draft-ietf-xcon-bfcp-00.txt. Gonzalo.Camarillo@ericsson.com. Additions to This Revision. Explanatory text added to this revision putting BFCP into context Third-party floor requests are now supported Several clarifications
E N D
The Binary Floor Control Protocol (BFCP)draft-ietf-xcon-bfcp-00.txt Gonzalo.Camarillo@ericsson.com
Additions to This Revision • Explanatory text added to this revision putting BFCP into context • Third-party floor requests are now supported • Several clarifications • Incorporated comments received on the mailing list
Issue: Replay Protection • Integrity implemented in the protocol • Rely on TLS for replay protection • Should we implement replay protection in the protocol as well?
Issue: Privacy TLV • Currently defined as a simple flag • Do not disclose my identity to anybody • Do we want more options? • E.g., your identity can be disclosed to the chairs, but no to other users
Issue: Mandatory TLVs Added by a Server • Can a server add new mandatory TLVs • We would need • a capability negotiation mechanism or • a way for clients to complain about unknown TLVs
Issue: 3rd Party Floor Request Authorization • Users need a means to authorize 3rd parties to request floors on their behalf • Does CPCP support this?
Issue: Different Payload Types • Use the BFCP fixed header with payload types other than the TLVs • E.g., XML notifications
Issue: Floor Request Modification • Users can modify ongoing floor requests (e.g., new topic or new priority) • Do we need this feature?
Issue: SDP Format • As a transport • m=application 20000 TCP/BFCP * • As a payload type • m=application 20000 TCP BFCP • BFCP would need to be MIME registered
Issue: Floor-Stream Mapping for Non-CPCP clients • Label streams and reference them • a=floorid:1 m-stream:10 • Add floorid attributes to the m lines • Other approach