1 / 10

The Binary Floor Control Protocol (BFCP) draft-ietf-xcon-bfcp-00.txt

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

tab
Download Presentation

The Binary Floor Control Protocol (BFCP) draft-ietf-xcon-bfcp-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Binary Floor Control Protocol (BFCP)draft-ietf-xcon-bfcp-00.txt Gonzalo.Camarillo@ericsson.com

  2. 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

  3. Issue: Replay Protection • Integrity implemented in the protocol • Rely on TLS for replay protection • Should we implement replay protection in the protocol as well?

  4. 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

  5. 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

  6. Issue: 3rd Party Floor Request Authorization • Users need a means to authorize 3rd parties to request floors on their behalf • Does CPCP support this?

  7. Issue: Different Payload Types • Use the BFCP fixed header with payload types other than the TLVs • E.g., XML notifications

  8. Issue: Floor Request Modification • Users can modify ongoing floor requests (e.g., new topic or new priority) • Do we need this feature?

  9. 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

  10. 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

More Related